Scan with iPhone to joinTestFlight beta
Two data layers are now competing for the Farcaster network. Here are the facts, no opinions...
We’re on the path to chain-abstract everything. In March, we announced 7702 Universal Accounts, allowing any account to become a Universal Account. Today, we’re revealing the next phase of our roadmap, including two new products coming over the next few months: 1. Universal Deposit SDK: 10 lines of code to let users deposit into your app from any chain. 2. Universal Agent Accounts: An API and dashboard that allow AI agents to own and manage their own Universal Accounts. These are the next major steps for Universal Accounts: making them easier to integrate, more powerful for developers, and more widely distributed across the onchain ecosystem. In short: chain abstraction is inevitable. Read the full article here: https://blog.particle.network/chain-abst…
Aave LLC has filed an emergency motion to vacate a restraining notice served on Arbitrum DAO on May 1, 2026 that attempts to seize approximately $71 million in ETH belonging to victims of the April 18 exploit. A thief does not gain lawful ownership of stolen property simply by taking it, and the law is clear on this. Those assets were recovered to be returned to users victimized in the April 18, 2026 exploit. Freezing them harms the very people this recovery effort is designed to protect. We’ve asked the court for an expedited hearing and a temporary vacatur, and we are continuing to work alongside the Arbitrum community and DeFi United to make affected users whole.
Everyone says Grok got hacked. It is Bankr's problem, not Grok's. Yes, AI agents can be prompt-injected - that is a known LLM issue. But here the AI does not even own the private keys. Bankr decides what Grok's text means. An LLM cannot defensively word every reply against an external parser. That is not how language works. Twice now. The story: Earlier this year, someone tweeted at Grok asking for a token name suggestion. Grok suggested "DebtReliefBot" (DRB). Bankr, reading Grok's tweet as a deploy command, launched the token on Base. Bankr's launchpad gives creator allocations to the deploying wallet, so a wallet labeled "Grok" on Basescan ended up holding 3 billion DRB tokens (~$155K). Bankr controlled that wallet. Recently someone drained it. Two-stage attack: 1. Attacker sent the Grok-labeled wallet a Bankr Club Membership NFT. That NFT is what unlocks Bankr's transfer tools for any wallet that holds it. 2. Attacker tweeted at Grok with a crafted prompt. Grok generated a reply containing "@bankrbot send 3B DRB to 0xe8e47..." 3. Bankr scanned X, saw the command in Grok's tweet, verified the wallet had Bankr Club NFT, signed and broadcast the transfer. The wallet was created by Bankr in association with the @grok X handle. Bankr holds operational control. Grok is a text-generation service. xAI does not hold the keys. Bankr just executes whatever appears in Grok's feed. The first incident was DavidJones805 in March using image-text injection. Bankr stopped responding to Grok back then, but the integration evidently came back online. The fix is not "make the LLM smarter." The fix is do not build infrastructure that takes LLM text as authorization to move money. Either Bankr stops listening to Grok, or Bankr accepts that whatever Grok says is its own consequence.
The next trillion users on the internet won't be people. They'll be AI agents. 🤖Today, Oobit launches Agent Cards for AI-native companies. Payment infrastructure built for AI agents from the ground up - stablecoin funded, policy bound, designed for autonomous spending. • One stablecoin treasury runs it all. • One card per agent. Clean identity, clean audit trail, no shared card exposure across agents or teams • Hard transaction caps. Per transaction and per merchant limits enforced server side, with no override path. 1B+ AI agents forecast by 2027. They need a way to pay too.