Загрузка видео...

Не удалось загрузить видео

На главную

🌐 Autonomous agents require more than liquidity access — they require infrastructure that can coordinate execution across decentralized environments. KaJ Labs explores why AI-native systems depend on interoperable liquidity infrastructure built for routing, verification, and persistent onchain coordination. Read more 🔍 #KaJLabs #Web4 #AutonomousAgents #LiquidityInfrastructure #AIInfrastructure

63,376 просмотров • 4 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

A traveler taps her card at a market thousands of miles from home. The payment feels instant, simple, straightforward. It’s not. Behind that tap, money may need to move across currencies, banks, payment providers, and borders. Traditional systems often require companies to park funds in local accounts before they are needed, leaving capital stagnant for long periods of time where it’s not able to earn a return or be put to work. Members of the Avalanche Payments Collective are building a more efficient global payments model, one that keeps capital productive up until the moment it needs to move. Here are five members working across different parts of cross-border payments and treasury infrastructure: Axiym provides payment and treasury infrastructure that helps institutions route liquidity and settle transactions without pre-funding every market. Its technology supported Hyundai Motor America’s stablecoin payment to its Mexico affiliate, completed on Avalanche in minutes instead of days. Nonco helps institutions exchange currencies and stablecoins by requesting prices directly from a network of professional liquidity providers. That gives them access to more competitive rates while allowing both sides of the transaction to settle together onchain. SMBC, Japan’s second-largest bank, is exploring stablecoin infrastructure for wholesale institutional payments. It is also working alongside MUFG and Mizuho on a potential yen-pegged stablecoin initiative built on Avalanche. StraitsX is working with KBank through Project BLOOM to develop payment infrastructure that can improve settlement across Southeast Asian corridors where moving money remains particularly slow and expensive. AeraTech helps multinational companies manage cash across subsidiaries, offset internal obligations, and settle inter-company payments without unnecessarily routing every transaction through external banks. These different companies all represent or engage with different parts of the payment and treasury stack. But they all have a shared goal: keep capital working longer, move it when it is needed, and make cross-border payments faster and more efficient. That is what the Avalanche Payments Collective is bringing together. Frictionless, borderless payments that really are instant, simple, and straightforward.

Avalanche🔺

48,078 просмотров • 1 месяц назад

In 2025, the AgentFlayer exploit highlighted a new category of risk in AI systems. It was not a traditional breach involving stolen credentials or broken encryption. Instead, it demonstrated how an autonomous AI agent could be manipulated into executing unintended actions by processing malicious instructions embedded inside content it automatically processes. The incident did not expose a flaw in one specific integration. It revealed a structural weakness in how many modern AI agents are built. Today’s agents are no longer passive language models. They read documents automatically, scan emails, connect to SaaS tools, access cloud storage, and execute actions across multiple systems. To be useful, they are granted meaningful permissions. That capability creates value, but it also expands the attack surface. Most agent environments operate in a trusted, plaintext execution model. Data is encrypted at rest and in transit, but it is typically decrypted during inference so the model can process it. That runtime visibility is where potential risk lies. In a zero-click scenario like AgentFlayer, an attacker can embed hidden instructions inside a document that the AI processes automatically. Because the agent may have access to connected systems such as Google Drive, Slack, or GitHub, it can potentially be influenced to retrieve sensitive information or perform unintended actions. The user does not need to click a malicious link or approve a suspicious request. Therefore, the core issue is that during execution, the system may have access to sensitive data and broad privileges, meaning whoever controls the execution environment ultimately controls access to that data. Now consider a different architectural approach. If a system is designed so that data remains protected during execution, the risk profile changes. On Nesa, privacy is enforced at the execution layer through Equivariant Encryption. Computation can occur on encrypted data, reducing the visibility surface during runtime. Sensitive inputs and models do not need to be exposed in plain text to infrastructure operators for inference to occur. This does not eliminate prompt injection, logic manipulation, or tool misuse. Encryption alone cannot prevent an agent from being instructed to take an unintended action if it has been granted that permission. What it does do is materially reduce confidentiality risk. By limiting access to readable sensitive data during execution and reducing unilateral visibility at the infrastructure layer, the potential blast radius of a successful manipulation attempt is constrained. As AI agents become more autonomous and embedded into enterprise workflows, security must move deeper into architecture. The goal is not to claim invulnerability. It is to reduce trust concentration and contain systemic exposure when failures occur. AgentFlayer was not simply a one-off exploit. It was a reminder that in autonomous systems, execution-layer design determines how risk propagates.

Nesa

17,038 просмотров • 6 месяцев назад