Legacy testnet demo · V3 commerce beta

RuleWallet documentation

A narrow, inspectable permission layer between an AI agent and an onchain policy account. V3 adds named accounts, ETH/USDG budgets, merchant/category/time controls, single-use approvals, EIP-712 schedules, secure-signer gates, and exact transaction previews. The public legacy demo remains available while V3 deployment and production credentials stay explicit release gates.

Start guided demo Hackathon submission View live receipts

01 / Model

Separate intent, authority, and execution.

The agent produces a structured request. A versioned policy evaluates it. A scoped signer can act only when the decision permits it. High-risk but otherwise valid requests enter a human approval queue.

Intent

Structured call proposed by the agent.

Policy

Deterministic constraints and evidence.

Authority

Scoped key—not the owner's master secret.

02 / Policy object

Portable, readable rules.

The initial format stays deliberately small enough to inspect in one screen.

{
  "network": "robinhood-chain-testnet",
  "account": "travel budget",
  "agent": "booking assistant",
  "asset": "USDG",
  "limits": {
    "perTransaction": "75.00",
    "rolling24Hours": "150.00",
    "monthly": "600.00"
  },
  "merchant": "0x...",
  "category": "travel",
  "allowedUtcHours": "07:00-22:00",
  "approvalAbove": "50.00",
  "pauseAvailable": true
}

03 / Evaluation

One of three explicit outcomes.

Allowed

Every hard rule passes and the request stays below the human threshold.

Needs approval

Hard rules pass, but a person must authorize the action.

Blocked

At least one hard rule fails; approval cannot override it.

const decision = evaluateTransfer(policy, {
  asset: "native-eth",
  amountEth: "0.0001",
  recipient: "0x...",
  spentRolling24HoursEth: "0.0012",
  agentRoleActive: true,
  policyPaused: false
});

// { status: "allowed", rules: [...] }

04 / Architecture

Testable layers with narrow responsibilities.

01Agent adapterNormalizes MCP, SDK, or API intent into a request.

02SimulatorDecodes calls, estimates effects, and enriches market data.

03Policy accountEnforces allowlists, per-asset limits, nonces, expiry, and pause onchain.

04Approval rolesCollect independent wallet approvals for high-value requests.

05Wallet signerShows and signs the exact simulated transaction without backend custody.

06Event receiptsPublish requests, approvals, and execution results as explorer-verifiable events.

05 / Notifications

Alerts observe execution. They never authorize it.

After an execution record is durably stored, RuleWallet can deliver a versioned event through an authenticated HTTPS webhook. The event covers confirmed executions, approval requirements, failures, and unusual requests stopped by policy.

Provider-neutral delivery

Route one server-side webhook to email, Telegram, Slack, or an incident platform without exposing credentials to the browser.

Fail-safe boundary

A notification outage cannot change policy, create an approval, or convert a blocked request into a transfer.

TESTNET_NOTIFICATION_WEBHOOK_URL=https://alerts.example.com/rulewallet
TESTNET_NOTIFICATION_WEBHOOK_TOKEN=<server-only bearer token>

Inspect notification readiness

06 / MVP boundary

What this build does—and does not do.

Included

Wallet-created named spending accounts and a legacy public testnet demo

Versioned non-upgradeable V3 factory, account, and policy registry

ETH/USDG asset, merchant, category, period, and approval controls

EIP-712 schedules and approvals, secure-signer interface, receipts, pause, and owner recovery

Unit, fork, 512-run fuzz, reentrancy, and V1/V2/V3 invariant tests

Still gated

V3 factory/account deployment and every required wallet signature

Independent audit and formal verification

Configured non-exportable signer, dual managed RPC, alert delivery, and monitored canary

Provider purchase execution without a verified, credentialed adapter

Routers, token approvals, swaps, bridges, or tokenized-stock trading

Open playground

Legacy testnet demo · V3 commerce beta

RuleWallet documentation

Start guided demo Hackathon submission View live receipts

01 / Model

Separate intent, authority, and execution.

Intent

Structured call proposed by the agent.

Policy

Deterministic constraints and evidence.

Authority

Scoped key—not the owner's master secret.

02 / Policy object

Portable, readable rules.

The initial format stays deliberately small enough to inspect in one screen.

{
  "network": "robinhood-chain-testnet",
  "account": "travel budget",
  "agent": "booking assistant",
  "asset": "USDG",
  "limits": {
    "perTransaction": "75.00",
    "rolling24Hours": "150.00",
    "monthly": "600.00"
  },
  "merchant": "0x...",
  "category": "travel",
  "allowedUtcHours": "07:00-22:00",
  "approvalAbove": "50.00",
  "pauseAvailable": true
}

03 / Evaluation

One of three explicit outcomes.

Allowed

Every hard rule passes and the request stays below the human threshold.

Needs approval

Hard rules pass, but a person must authorize the action.

Blocked

At least one hard rule fails; approval cannot override it.

const decision = evaluateTransfer(policy, {
  asset: "native-eth",
  amountEth: "0.0001",
  recipient: "0x...",
  spentRolling24HoursEth: "0.0012",
  agentRoleActive: true,
  policyPaused: false
});

// { status: "allowed", rules: [...] }

04 / Architecture

Testable layers with narrow responsibilities.

01Agent adapterNormalizes MCP, SDK, or API intent into a request.

02SimulatorDecodes calls, estimates effects, and enriches market data.

03Policy accountEnforces allowlists, per-asset limits, nonces, expiry, and pause onchain.

04Approval rolesCollect independent wallet approvals for high-value requests.

05Wallet signerShows and signs the exact simulated transaction without backend custody.

06Event receiptsPublish requests, approvals, and execution results as explorer-verifiable events.

05 / Notifications

Alerts observe execution. They never authorize it.

Provider-neutral delivery

Route one server-side webhook to email, Telegram, Slack, or an incident platform without exposing credentials to the browser.

Fail-safe boundary

A notification outage cannot change policy, create an approval, or convert a blocked request into a transfer.

TESTNET_NOTIFICATION_WEBHOOK_URL=https://alerts.example.com/rulewallet
TESTNET_NOTIFICATION_WEBHOOK_TOKEN=<server-only bearer token>

Inspect notification readiness

06 / MVP boundary

What this build does—and does not do.

Included

Wallet-created named spending accounts and a legacy public testnet demo

Versioned non-upgradeable V3 factory, account, and policy registry

ETH/USDG asset, merchant, category, period, and approval controls

EIP-712 schedules and approvals, secure-signer interface, receipts, pause, and owner recovery

Unit, fork, 512-run fuzz, reentrancy, and V1/V2/V3 invariant tests

Still gated

V3 factory/account deployment and every required wallet signature

Independent audit and formal verification

Configured non-exportable signer, dual managed RPC, alert delivery, and monitored canary

Provider purchase execution without a verified, credentialed adapter

Routers, token approvals, swaps, bridges, or tokenized-stock trading

Open playground

RuleWallet documentation

Separate intent, authority, and execution.

Portable, readable rules.

One of three explicit outcomes.

Testable layers with narrow responsibilities.

Alerts observe execution. They never authorize it.

What this build does—and does not do.

Preparing RuleWallet

RuleWallet documentation

Separate intent, authority, and execution.

Portable, readable rules.

One of three explicit outcomes.

Testable layers with narrow responsibilities.

Alerts observe execution. They never authorize it.

What this build does—and does not do.