Exit to App
Getting Started

What is MOI?

Understanding the non-custodial treasury operating system, its boundary separation, and core operating principles.

MOI is not a generic chatbot, an unregulated trading bot, or a custodial bank. It is a deterministic orchestration runtime deployed on Celo Mainnet (chainId: 42220) that couples programmatic agent intelligence with strict cryptographic policy boundaries.

MOI System Boundary & Governance Architecture

  1. Owner Authority

    • Master Owner Wallet

      Controls funds, sets mandates, signs first trade

    • EIP-4361 SIWE Session

      HttpOnly secure JWT with cryptographic nonce

  2. Enforcement Layer

    • Deterministic Policy Engine

      18 invariant checks (caps, corridor, reactor)

    • HMAC Policy Attestation

      Cryptographic binding between quote and execution

  3. Execution Subsystem

    • Textile FX v2 RFQ

      Zero-slippage market maker settlement reactor

    • buy / x402 Protocol

      HTTP 402 agent-to-agent microservice payments

  4. Audit & Telemetry

    • ERC-8004 Identity #164

      Onchain canonical registry verification

    • ERC-8021 Attribution

      Tag celo_c9cb9a59fc4c on every transaction

    • Double-Entry Ledger

      Strict balanced journal entries in PostgreSQL

Figure 1: Complete separation of powers between Owner Governance, Policy Enforcement, and Execution Infrastructure.

The Three Inviolable Architectural Principles#

  • Separation of Custody and Execution: The owner wallet retains ultimate legal and cryptographic title to treasury capital. The agent wallet holds only strictly allocated operational balances or signing delegation within immutable spending ceilings.
  • Zero-Slippage Institutional Settlement: Rather than dumping tokens into automated market maker liquidity pools with high price impact and front-running risk, MOI routes conversions exclusively through Textile FX v2 RFQ reactors.
  • Cryptographic Audit Trail: Every transaction broadcast to Celo Mainnet appends the official ERC-8021 attribution tag celo_c9cb9a59fc4c and resolves against the ERC-8004 Agent Identity #164.