Skip to content
MANDATE owl logoMANDATE

Demo

A visualization and record of the documented local MVP demo — a real compliance proof, a real on-chain commitment, a valid order accepted, and an invalid order rejected.

Demo policy

RuleDemo value
Approved marketConfigured whitelist market (whitelist index 0)
Maximum order notional1,000,000
Maximum positionConfigured position limit
Maximum daily lossConfigured daily loss limit
AuthorizationRegistered session key
Policy identityOn-chain commitment hash (Poseidon2)
Execution windowActive commit phase of the current epoch
Emergency controlCircuit breaker (active / inactive)

Order notional = quantity × limit price — the key metric the policy enforces. It measures the total value of an order, not just its quantity or price in isolation.

Valid order

Buy 250 units at 3,500 — notional 875,000, under the 1,000,000 limit. Proof generated: yes. Result: Submitted.

Invalid order

Buy 10,000 units at 3,500 — notional 35,000,000, 35× over the 1,000,000 limit. Proof generated: no. Result: Rejected — proof generation failed.

Execution flow visualization

A visualization of the documented local MVP demo — not a live transaction simulator.

  1. Agent proposes order

  2. Check against policy

  3. Generate ZK compliance proof

  4. Submit to batch auction

Side
buy
Quantity
250
Limit price
3,500
Policy limit
1,000,000
Notional (qty × price)
875,000
Proof generated
Yes

Result

Submitted

Verified results

These results were produced during a live local test of the MVP — real MCP tool calls, a real on-chain transaction, and a real proof-generation failure (not simulated outcomes).

FieldValue
Epoch396
Agent ID0x2c4fd536018985d83870a4ed4a18dc1a4ded2c3343f7c3da46af50a92846b420
Order commitment (valid order)0x12a254be...5e74d89
Transaction hash (valid order)0xdee28569...9a60bc01

Confirmed in the MVP

  • MoonPay Agent can discover and connect to the MANDATE MCP server
  • Read-only tools return accurate current state
  • Portfolio state root matches the on-chain committed value
  • A compliant order generates a valid Noir compliance proof
  • A compliant order is successfully committed to the on-chain batch auction
  • An on-chain transaction is produced with a verifiable transaction hash
  • A non-compliant order fails proof generation
  • The non-compliant order is not submitted — no on-chain transaction created
  • The MCP server remains fully available after rejecting a non-compliant order
  • Execution is isolated behind a single, controlled tool

Not yet proven

  • Mainnet safety or real-money security
  • Real-fund custody adequacy
  • Production-scale decentralization
  • External security audit results
  • Production-scale proof generation performance
  • Multi-market or cross-chain liquidity
  • Cross-chain settlement
  • State-transition validity (sequencer posts state roots after clearing; operator trust for state updates not yet eliminated)

Running locally

The one-command demo (from a clone of the repository):

./demo/run.sh

Or, for the persistent MCP-agent setup:

npm run local:start
npm run local:status
npm run local:stop

See Quickstart for the full walkthrough and prerequisites.