milo
system

Architecture

What exists today and what is designed but not yet deployed. Each layer below carries its real status — nothing here is described as running when it is not.

live in this builddesigned, not deployed
  1. 01

    User wallet

    live

    Positions stay where they already are. Milo never takes custody, and the wallet is the root of every permission below it.

    • EIP-6963 wallet discovery
    • Robinhood Chain · 4663
    • Read access only in this build
  2. 02

    Milo strategy account

    designed

    A user-controlled account that would hold the mandate's working capital. The user remains the owner and can withdraw without Milo's involvement.

    • User-owned
    • Withdrawal is user-only
    • Not deployed in this build
  3. 03

    Permission and policy engine

    designed

    The mandate, expressed as enforceable limits: token allowlist, position ceiling, reserve floor, turnover cap, approval threshold and session expiry.

    • Scoped sessions
    • Expiring authority
    • Deny by default
  4. 04

    Market and corporate-action observers

    live

    Live reads of Stock Token metadata, prices and corporate actions from the official Robinhood endpoints, plus onchain uiMultiplier() through Multicall3.

    • /rhj/assets · /rhj/prices · /rhj/corporate-actions
    • uiMultiplier() per ERC-8056
    • Multicall3 at the canonical address
  5. 05

    Decision engine

    designed

    Turns observations into proposals: measure, compare against the mandate, form the smallest corrective action, validate it against every other boundary.

    • Deterministic rules
    • Smallest-action bias
    • Full journal output
  6. 06

    Execution router

    designed

    Would route validated actions to Robinhood Chain. Nothing routes today — no strategy contract is deployed and no allowance exists.

    • Allowlist-constrained
    • Size-capped per action
    • Not deployed in this build
  7. 07

    Stock Token positions

    live

    Standard ERC-20 tokens with 18 decimals whose corporate actions are expressed through an onchain multiplier rather than a cash distribution.

    • ERC-20 · 18 decimals
    • ERC-8056 multiplier
    • Read live from chain 4663
  8. 08

    Onchain decision receipts

    designed

    A durable record of what Milo decided and why, committed onchain so the journal cannot be quietly rewritten after the fact.

    • Append-only
    • Hash-linked to evidence
    • Not deployed in this build
  9. 09

    Emergency guardian

    designed

    A kill switch the user holds unilaterally. Closing the session revokes authority immediately, with no countersignature and no unwind period.

    • User-triggered
    • No countersignature
    • Immediate revocation
eventual security model

How authority stays bounded

These are the properties the deployed system is designed to hold. They are commitments about the architecture, not claims that it has been audited or is in production.

User-controlled strategy account

The account holding working capital is owned by the user. Milo is a permitted operator, never the owner.

Scoped session permissions

Authority is granted per session, for a named basket, with a named allowlist. Nothing is granted implicitly.

No arbitrary withdrawal

The agent has no path to move assets to an address it chooses. Withdrawal destinations are the user's alone.

Token allowlist

Only Stock Tokens the user has approved for the mandate can be touched, and only those verified as active on chain 4663.

Maximum trade size

Each individual action is capped. A single mistake cannot become a large one.

Concentration limits

Position ceilings and reserve floors are checked before and after every proposed action, not only before.

User kill switch

The user can revoke at any moment without Milo's cooperation.

Expiring authority

Sessions end on their own. Continued authority requires a deliberate new signature.

Human approval above threshold

Any action larger than the configured threshold waits for explicit approval, regardless of how confident Milo is.

current status, stated plainly
  • No strategy contract is deployed.
  • No token allowance has been requested from any wallet.
  • No audit has been performed, and none is claimed.
  • Opening a session produces a signature, not a transaction — there is no hash and no block for it.
  • Market data, network state, token metadata, multipliers and corporate actions are read live from chain 4663 and the official Robinhood endpoints.
references
Robinhood Chain documentationConnecting to the chainStock TokensStock Token APIsContractsBlock explorer