Public Beta · Non-Custodial · Open Source · AI Agent Permissions
BVCC Agent Wallet
Experimental non-custodial smart wallet for WebAuthn account abstraction and permission-limited AI agent execution.
Lost access?
Smart contracts may contain bugs. BVCC does not custody funds, recover wallets, or reverse transactions.
§01 — AI Agents
Delegate to an AI without giving up control.
The agent wallet lets an autonomous agent operate on your behalf within limits you define in detail. And if something is off, pause it instantly.
- ✦
Period budget
Define how much it can spend and how often it renews.
- ✦
Recipient whitelist
The agent only sends to addresses you authorise.
- ✦
Instant pause
Freeze all agent activity with a single signature.
- ✦
EOA agents only
External accounts only — never opaque contracts.
§02 — Connect your AI assistant
Plug your AI agent into a wallet it can't drain.
Already running an agent in Hermes, Claude, Cursor or LM Studio? BVCC speaks MCP natively. One command gives your assistant an agent wallet whose limits — budget, allowed tokens, recipients — are enforced on-chain, not on our servers. The agent holds its own keypair; BVCC never sees it.
Works with any MCP client
- ✦
Speaks MCP natively
Any MCP client connects with one command — no plugin to install, no custom adapter.
- ✦
Limits enforced on-chain
Budget, allowed tokens, recipients and pause live in the contract, not in a server it could bypass.
- ✦
The agent owns its keys
You generate the agent's keypair and authorise its address. No custodial API key in someone else's cloud.
$ npx -y @bvcc/agent-mcp
▸ 53 tools registered — send · swap · lend · provide liquidity
▸ Works in Hermes · Claude · Cursor · LM Studio
$ npm i @bvcc/agent-sdk
▸ Build your own bot on the same on-chain limits
§03 — Philosophy
We do not hold your keys. We do not know your name. There is no server that controls your wallet. You hold the keys; the contract executes only what you sign.
— Founding principle, BVCC
§04 — Capabilities
Built as a security-focused smart account, not just an app.
- 01
WebAuthn / Passkeys
Authentication uses passkeys/WebAuthn through the device's secure authentication system when available. BVCC does not receive, store, or custody private keys.
Passkey · WebAuthn · P256 - 02
Private by design
No emails, no KYC, no forms. There is no user database that can be leaked or subpoenaed. Ethereum is the only record of your account.
Zero personal data - 03
Sovereign recovery
You designate three trusted guardians. If you lose your device, two of them sign the key change — subject to a 48-hour timelock you can cancel.
2-of-3 · 48h timelock - 04
Real smart account
ERC-4337 for account abstraction and ERC-7821 for batch execution. Connect to any dApp via WalletConnect and operate like a real smart account.
ERC-4337 · ERC-7821
§05 — The journey
Register your face
A single biometric tap — Face ID, fingerprint or security key — creates your key pair inside the device.
Deploy your contract
CREATE2 derives the address from your public key. Deterministic, no server.
Operate freely
Send, receive, swap and connect dApps. Your account, your rules.
Recover if needed
Your guardians restore access without anyone else touching your funds.
§06 — Security
You self-custody your own funds — verifiable on-chain.
Your wallet address is derived from your public key via CREATE2: deterministic, verifiable, independent of any database. What you sign is exactly what gets executed. The code is open source so you can audit it yourself.
- WebAuthn / Passkeys
- Your passkey is managed by your device/browser. BVCC does not receive, store, or custody private keys.
- 2-of-3 guardians
- Social recovery without custodians or third parties.
- 48h timelock
- Every recovery is reversible while you wait.
- CREATE2
- Deterministic address, auditable on-chain.
§07 — Open source
Don't trust us. Verify it — and run it yourself.
The dashboard, contracts and bundler are open source. If the site goes down, if you prefer total sovereignty, or if you just want to audit every line: clone the repo and create and manage your wallets in your own local environment. Nothing depends on our servers.
View on GitHub →$ git clone github.com/blockventurechaincapital-crypto/bvcc-wallet-agent
$ cd bvcc-wallet-agent && npm install
$ npm run dev
▸ Local dashboard at http://localhost:3000
▸ BVCC does not receive, store, or custody private keys
§08 — Fees
Transparent and on-chain. The fee travels in the same transaction — no hidden charges, no subscriptions.
Deployed on
- 01
Ethereum - 02
Arbitrum - 03
Base - 04
BNB Chain - 05
Polygon
● Active testnet · Arbitrum Sepolia
§09 — FAQ
Frequently asked questions
What is the BVCC Agent Wallet?
The BVCC Agent Wallet is an experimental, non-custodial smart wallet (ERC-4337 account abstraction with WebAuthn passkeys) that lets you give an AI agent its own wallet with on-chain limits it cannot cross. You keep self-custody; the agent transacts only within the budget, tokens and recipients you allow.
What limits can I set on an AI agent?
You define the limits and the contract enforces them on-chain: spending caps (per transaction, daily, per period and total, in the native token and per ERC-20), an allowed-tokens list, the protocols it may call, an optional recipient whitelist, an expiry date, and an instant pause. The agent holds its own keypair and can never exceed them — BVCC never sees the agent keys.
Which AI agents and MCP clients can connect?
Any MCP (Model Context Protocol) client connects in one command, including Hermes, Claude, Cursor and LM Studio. The server registers 53 tools the agent calls to transact within its limits: transfers, Uniswap v3 and v4 swaps, Aave v3 lending, and Uniswap liquidity positions. Read-only mode and per-feature module filters let you expose fewer.
Is it really non-custodial?
Yes. BVCC never receives or stores your private keys, cannot recover wallets, and cannot reverse transactions. You authenticate with WebAuthn passkeys (Face ID, fingerprint or a security key), and Ethereum is the only record of your account.
Do I need KYC or an email?
No. There is no KYC, no email and no sign-up forms. You create a wallet directly with a passkey on your device.
Which networks are supported?
The wallet runs on Ethereum, Arbitrum, Base, BNB Chain and Polygon, using ERC-4337 account abstraction and ERC-7821 batch execution. Arbitrum Sepolia is the active testnet.
Is it open source?
Yes. The BVCC Agent Wallet is open source and self-hostable, with its code on GitHub. Smart contracts may still contain bugs — it is Public Beta, so use it accordingly.
§10 — About
Built by BlockVenture Chain Capital
A DeFi infrastructure studio
The BVCC Agent Wallet is built by BlockVenture Chain Capital, a DeFi infrastructure studio founded in 2024 that ships anti-bot hooks, this agent wallet, and on-chain analytics on Uniswap v4.
Live in production since 2026
The Agent Wallet runs in production across Ethereum, Arbitrum, Base, BNB Chain and Polygon, with Arbitrum Sepolia as the active testnet.
Non-custodial by design
You keep self-custody at all times. The agent holds its own key, which signs locally and is never transmitted to BVCC. No KYC.
Open and verifiable
The wallet is open source, and its agent tooling is public on npm and GitHub — @bvcc/agent-mcp and @bvcc/agent-sdk — so anyone can inspect or self-host it.
