Wayleave
Human-approved payments for AI agents, from purchase request to settlement and delivery.
Demo
About
Wayleave lets AI agents request purchases while humans retain control of every payment. Instead of giving an agent a wallet key, the owner links an ENS identity and an NFT-owned smart account, then grants scoped, expiring MCP access. The agent can inspect information, discover an offering, get a quote, and create a payment request. You approve and sign it with funds that come directly from your wallet. The owner reviews the recipient, amount, route, and fee bound before signing the exact operation. The first merchant is Wayleave itself, offering a versioned Developer Pack. The purchase workflow connects product discovery, an approval inbox, an implemented Arc Testnet-to-Ethereum Sepolia USDC route using Circle CCTP, and artifact retrieval. Source execution, destination settlement, and delivery are distinct milestones with durable records for recovery. Wayleave also exposes account-scoped indexed payment history through MCP, helping an agent explain known activity before proposing another purchase. Results identify their chain, token scope, and coverage limitations. The public app is deployed, covers ENSv2 namespace registration and resolution, Arc contract deployment, an E2E USDC payment flow through CCTP, and live subgraph queries.
How it's made
Wayleave is a Bun and TypeScript monorepo with Next.js, React, wagmi, viem, and Reown AppKit for the owner dashboard. Solidity contracts are built and tested with Foundry. The smart account combines pinned Kernel v4, EntryPoint 0.9, and an NFT owner validator. The owner signs the exact UserOperation, while a capped token allowance supports spending directly from the owner's balance. Agents never receive payment-signing authority. A SQL gateway, hosted with Turso, persists requests, approvals, settlement records, and merchant fulfillment. Local stdio and hosted HTTP MCP expose scoped tools. Owner-issued bearer credentials bind permissions, expiry, identity, chain, and account; current authority and revocation are checked on use. ENSv2 uses the dedicated ETHOnline deployment on Sepolia. A permissioned namespace and identity adapter resolve account names to stable Kernel addresses. ENS identity verification remains separate from authority over an Arc payment account. The implemented Circle CCTP route atomically pulls the approved USDC amount, grants the exact Circle allowance, burns on Arc, and clears the allowance. The gateway correlates source execution, attestation, and destination mint before recording settlement. Merchant delivery additionally verifies the artifact version and digest. The end-to-end route was validated with a live 1 USDC Arc Testnet → Ethereum Sepolia CCTP transfer, with separate source execution, attestation, destination settlement, and delivery records. The Graph subgraph indexes Sepolia account registration, configured-token transfers, and UserOperation outcomes. MCP provides bounded history queries and summaries with source event IDs and coverage metadata. Studio deployment and reconciliation with live RPC receipts are recorded; Arc indexing and decentralized-network publication are not claimed. A key engineering challenge was recovery without accidental duplicate payment. Another was evidence attribution: a successful outer transaction is insufficient when an inner UserOperation fails, and a token transfer does not prove delivery. These distinctions drive the verification logic and UI.