Maroo Agent Wallet Stack (MAWS) Architecture
A layered architecture connecting AI agents to on-chain Maroo wallets with built-in compliance.
The Maroo Agent Wallet Stack (MAWS) bridges the gap between autonomous AI agents and the Maroo blockchain. It provides a Model Context Protocol (MCP) server that exposes wallet operations as standard tool calls, allowing agents to hold value, transact, and manage policies. The architecture is built on a layered model—Identity, Knowledge, Interface, Wallet, Compliance, and Commerce—ensuring that agent actions remain secure, compliant, and traceable.
Key Features
MCP Tool Integration
Exposes Maroo wallet capabilities directly to Claude, Cursor, and other MCP-compatible clients.
Two-Layer Policy Enforcement
Combines off-chain preflight checks with on-chain Programmable Compliance Layer (PCL) rules.
Flexible Gas Sponsorship
Supports Paymaster (sponsored), Self-funded, and Owner-funded gas modes for agent transactions.
Architecture
graph TD
A[AI Agent / LLM] -->|MCP Protocol| B(MAWS MCP Server)
B -->|Off-chain| C{AgentManager}
B -->|API| D[WaaS Backend]
C -->|Preflight Check| E[(IdentityRegistry)]
D -->|Submit Tx| F[Maroo Chain]
F -->|AnteHandler| G{PCL Enforcement}
G -->|Pass| H[Execute Transfer] MAWS intercepts agent intents, performs off-chain policy preflight via the AgentManager, and routes transactions through WaaS to the Maroo chain where PCL enforces final compliance.
The Layered Model
agent., policy., transfer.*). The Wallet Layer is powered by the Maroo WaaS (Wallet-as-a-Service), which provisions Account Abstraction (AA) wallets for each agent. This abstracts away private key management, allowing the human owner to retain ultimate control while the agent operates autonomously.Crucially, the Compliance Layer operates in two stages. Before a transaction is ever signed, the
AgentManager performs an off-chain preflight check against the agent's ERC-8004 Identity Registry record. If the agent attempts to exceed its spending limit or send to an unauthorized address, the MCP server rejects the tool call immediately, returning a structured ToolError that the LLM can understand and recover from. If the preflight passes, the transaction is submitted to the Maroo chain, where the Programmable Compliance Layer (PCL) acts as the final on-chain backstop.