Loading video...

Video Failed to Load

Go Home

The next phase of on-chain AI requires more than execution and models. It requires identity. We’ve partnered with Unstoppable Domains to launch .openx, a dedicated domain designed just for on-chain AI systems. .openx provides a human-readable identity layer that maps directly to wallet addresses, without changing execution logic, permissions,...

12,725 views • 6 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

🚨 BIG EVENT ANNOUNCEMENT! 🚨 The Snapshot was officially taken at 11:59 PM UTC on March 31st, and we’re now processing the data. A huge thank you to everyone who stayed active, fed their Capybaras, and contributed to this incredible journey! ❤️ But trust us—the best is yet to come! ⸻ 🎉 THE BIG EVENT REVEALED! We’ve been searching for a way to reward our community in a massive way… far beyond the typical $5 airdrops from other SocialFi projects. And we’ve found the perfect solution! 🚀 $500,000+ in Multi-Chain Identities! We’re excited to announce a major partnership with a Web3 infrastructure company specializing in identity management across modular blockchains. Their Modular Naming Service (MNS) allows users to transform complex wallet addresses into simple, recognizable identities usable across multiple blockchains. By securing your unique username through MNS, you can: • Simplify Transactions: Replace complex wallet addresses with a single, easy-to-remember name across multiple blockchains. • Unify Your Identity: Manage a single, recognizable identity across various platforms, enhancing your presence in the Web3 ecosystem. • Assess Your On-Chain Value: Utilize the AI Identity Score feature to evaluate your on-chain activity. A higher score may increase your eligibility for future airdrops and rewards. Who Gets These Identities? ✅ Player Card NFT Holders: • Each identity is valued between $40 and $1,250. • Distribution is based on your Leaderboard position at the time of the Snapshot, considering Player Card NFT holders after adjusting balances for Money Bag multipliers. ✅ All Capybara Users (even without an NFT): • Every participant who has earned at least 100,000 points qualifies for a $10 identity. ⸻ 🤖 COMING SOON: AI-POWERED TWITTER TOOL! We’re developing an AI Twitter Agent designed to help Capybara players enhance their social media presence and engagement and unlock additional rewards. ⸻ 🔥 CAPYBARA COMMUNITY TOKEN LAUNCHING IN Q2! We’re thrilled to announce the upcoming launch of the Capybara Community Token in Q2 to reward our ecosystem with an exciting airdrop! 🎉 —- 📢 More details on the claiming process will be revealed TOMORROW, April 2! Be sure to check back to learn how to claim your identity

Capybara on Sui

27,274 views • 1 year ago

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 views • 4 months ago