URL: https://x.com/brian_armstrong/status/2021661132734288131 Topic: Coinbase Agentic Wallets for AI agents
Draft Reply: This is huge. Guardrails + autonomous wallet = the missing piece for AI agents operating at scale.
ERC-7710-style delegation will be critical here → agents need scoped permissions (spend limits, time windows, specific contracts) without full key access.
The sandboxed approach on Base is smart. Curious: how are you thinking about permission revocation when an agent goes off-rails?
URL: https://x.com/OpenZeppelin/status/1918260179025707114 Topic: ERC-7702 delegation guide
Draft Reply: Great guide. One thing folks miss: ERC-7702 isn't just "smart EOAs" — it's a UX bridge.
The wallet controls the implementation → apps get batched ops & sponsored txs WITHOUT direct account delegation. Wallets become the permission layer.
ERC-5792 + ERC-7715 become the complementary standards for fine-tuned what apps can actually DO with that delegated execution.
URL: https://x.com/CoinbaseDev/status/2021647661871640726 Topic: Official Agentic Wallets announcement
Draft Reply: The built-in guardrails are the real unlock here.
Without scoped permissions, AI wallets = instant hack target. Your x402 protocol approach (allowlists, spend limits, time windows) maps directly to what the delegation standards folks have been iterating on.
Question: how are you handling permission revocation? If an agent starts behaving unexpectedly, can you freeze access instantly?
URL: https://x.com/KamesGeraghty/status/1796588872589324531 Topic: ERC-7710 and session keys
Draft Reply: Exactly this. ERC-7710's external account delegation removes the module-installation friction that killed ERC-4337 adoption.
Wallet approves once → that external account (could be another smart contract, an AI agent, a game server) gets scoped perms. No custom modules per app.
The "no additional modules" requirement is what makes this actually deployable at scale.
- These are VALUE-based replies connecting to Sam's delegation/permissions expertise
- Use → arrows sparingly (one per reply max)
- Keep under 280 characters to avoid edits
- Space out posts (don't post all at once)
- Tag Sam: @samdevrel