WalletChan MCP for Hermes

WalletChan is an AI-powered browser wallet and local MCP server that lets an agent safely execute onchain actions from a user's main wallet without handing the agent the user's private key or requiring a popup for every transaction.

For this hackathon, we built a delegated agent-wallet flow using MetaMask Smart Accounts Kit ERC-7710 delegations, 1Shot relaying, and an external Venice-powered agent harness. The user pairs WalletChan once, creates or imports a local encrypted agent wallet in WalletChan MCP, and signs a scoped delegation from their main WalletChan wallet. After that, the agent can execute approved DeFi workflows on Base, such as preparing and depositing USDC into Morpho vaults, through 1Shot's ERC-7710 relayer.

The core product idea is a safer agent wallet for real DeFi actions: the user's main wallet remains the source of funds, permissions are scoped, the agent wallet key is encrypted locally, raw agent EOA spending is never used as a silent fallback, and transaction execution can still route back through the normal WalletChan popup path when the user wants direct approval.

WalletChan MCP also keeps existing walletconnect execution profiles, so users can choose between normal WalletChan approval, delegated agent execution, and explicit raw agent-wallet execution. This makes the agent flow useful for demos while preserving user control and debuggability.

During the hackathon we extended WalletChan MCP from a WalletConnect-backed wallet adapter into a multi-profile agent execution system.

We added local encrypted agent wallet storage, execution-profile management, and ERC-7710 delegation lifecycle tools. MCP can now create or import an agent wallet, prepare a MetaMask Smart Accounts Kit delegation, open a WalletChan typed-data signature request through the existing extension, verify and store the signed delegation, and use that delegation for later transactions.

We integrated 1Shot's public relayer for delegated ERC-7710 execution. MCP can fetch 1Shot capabilities and fee data, resolve the correct relayer target address, prepare reusable function-call delegations for DeFi protocols, submit delegated call bundles, and poll task status. We also hardened the flow around practical relayer issues: prepared DeFi calls are simulated against the main delegator wallet instead of the raw agent EOA, 1Shot fee transfers are estimated and buffered, protocol approvals are preserved when relayer fees change, and failed estimates now stop before submitting doomed tasks.

We connected the delegated agent profile to existing WalletChan/Base DeFi tooling. Existing prepared-call flows, including Morpho CLI-based vault deposits, can now run through `agent:<walletId>` using the main wallet's delegated permissions. We tested the flow end-to-end with Base USDC and Morpho: the agent prepared the vault deposit, requested the correct scoped delegation when needed, then submitted the approval and deposit through 1Shot without requiring a WalletChan popup for the final in-scope execution.

We also researched x402 delegation support across hackathon projects. Because many public x402 endpoints do not yet advertise ERC-7710 delegated payment, we parked arbitrary x402 consumption for later and documented a future WalletChan-owned x402 endpoint idea around paid calldata decoding and clear-signing analysis. For the final hackathon scope, the submission focuses on delegated DeFi execution for Best Agent, 1Shot relayed ERC-7710 transactions for Best use of 1Shot, and Venice as the external agent LLM/provider layer.

none