Project Roadmap

Four milestones. One network.

“It is good to have an end to journey toward; but it is the journey that matters, in the end.”
— Ursula K. Le Guin

The whole build, end to end — nothing skipped, nothing overclaimed. The compilation engine is proven on-chain today, and the full atlas of translator families is shipped and byte-verified. The counter is taking shape in hardware; the network is deploying. Here is everything we've banked, everything in flight, and everywhere we're headed — in order.

✓ Done — banked In progress — in flight now Planned — on the path ahead
Milestone I
The Engine
Proven on-chain
Milestone II
The Merchants’ Counter
Building now
Milestone III
The Network
Designed, deploying
Milestone IV
The Atlas
Families shipped
I
The Engine
● Proven on-chain
Compilation, proven on the chain itself.

The foundation everything else stands on: a deterministic pipeline that takes payment intent and emits native chain instructions — the same input, the same output, every time, no inference and no guesswork. This milestone isn't a promise. Every claim below is clickable on a public block explorer.

Progress10 of 12 done
  • ✓
    Universal intent IR coredone
    The deterministic intermediate representation every translator compiles from — the spine of the protocol.
  • ✓
    EVM translator — 298 verified instruction pairsdone
    One model reaches the entire EVM family — Ethereum, Base, Arbitrum, Optimism, Polygon, BNB, Avalanche and more. Base is the live proof.
  • ✓
    Hashgraph adapter — native Hedera HTSdone
    A distinct execution environment settled live on mainnet alongside the EVM family in the same run.
  • ✓
    SVM translator — Solana & Eclipsedone
    Deterministic, 100% accuracy, zero inference — settled in the live exhibit from a single model.
  • ✓
    Deterministic compilation codecdone
    Same intent in, same calldata out — the property that makes the engine auditable and the moat hard to cross.
  • ✓
    Gas & wallet machinery abstracted out of sightdone
    Chains, gas, and keys compiled away beneath the intent — the user never touches them.
  • ✓
    111 mainnet settlements from a single compiled triggerdone
    Base, Solana, and Hedera — three VM families fanned out from one intent. Real, irreversible, on-chain.
  • ✓
    Every settlement public & auditabledone
    All 111 hashes live on public explorers — basescan, solscan, hashscan. Nothing hidden, including the day-one fixes.
  • ✓
    10 provisional patents filed with the USPTOdone
    The deterministic core, gas abstraction, wallet-node convergence, and compile-time compliance — sealed.
  • ✓
    Live exhibit publisheddone
    The full chain of custody — first fire, the four fixes caught on day one, and the completed run — in the open.
  • ◆
    Cross-domain rails — compilation beyond chainsin progress
    Extending the same pipeline across commercial settlement rails so intent compiles to wherever value needs to land, not just on-chain.
  • ◆
    Independent third-party validation of the enginein progress
    External review of the determinism and the full compilation surface — engaged and underway with an independent auditor.
II
The Merchants’ Counter
◆ Building now
From an engine to a product you can hold.

The compilation layer becomes a checkout counter. Every device is a node — the terminal on the merchant's counter, the unit in your pocket, the wallet in your hand, the vault in the drawer. This is the milestone in motion right now: design is done, the hardware is being ordered and brought up, and the wallet node moves from render to working device.

Progress4 of 10 done
  • ✓
    Wallet-node + POS-node convergencedone
    The product thesis, filed in the patents: the wallet is the storefront and the checkout, and every terminal is a doorway to the next user.
  • ✓
    Four-product hardware line designeddone
    The counter, the pocket, and the vault — flagship terminal, mobile unit, downloadable wallet node, and cold-wallet node. Designed and rendered.
  • ✓
    Hardware lead on boarddone
    Royce — a production-hardware veteran who has carried go-to-market devices from concept to factory — is building the terminal alongside the founder.
  • ✓
    POS terminals on orderdone
    This isn't a render waiting on a partner — the point-of-sale terminals are ordered and in the pipeline.
  • ◆
    Wallet-node hardware sourced & orderedin progress
    Placing the hardware orders for the wallet-node devices so the build can move from design into the physical units.
  • ◆
    Wallet-node design implementationin progress
    Firmware and on-device build — bringing the compilation node onto the actual hardware once the units arrive.
  • ◆
    On-device settlement testingin progress
    Compile-to-chain from the terminal itself — proving the same settlement that ran in the exhibit fires from the device in hand.
  • ◆
    Crypto-to-fiat settlement partnerin progress
    Merchant settlement capability is built; the merchant settles in stablecoin, with fiat resolution coming through a partner we're in active discussions with.
  • First merchant pilot at a live counterplanned
    A real customer, a real merchant, a real swipe — the loop closed from intent to settlement at a physical point of sale.
  • Production hardware runplanned
    Moving from validated prototypes to a manufactured run ready to put on counters.
III
The Network
○ Designed, deploying
Every device joins a self-expanding mesh.

The counter doesn't just transact — it joins a network the moment it powers on. The infrastructure isn't built ahead of demand; it builds itself as demand arrives. The four-tier architecture is designed and the partnerships intake is opening; the rollout below is the deployment ahead.

Progress2 of 11 done
  • ✓
    Four-tier node architecture designeddone
    From every-wallet T1 nodes, up through T2 compilation and POS nodes, to the regional masternode backbone — the full topology is specified.
  • ✓
    Self-expanding mesh modeldone
    Each terminal is a node and a doorway to the next user — the network grows with adoption rather than requiring it upfront.
  • ◆
    Partnerships & merchant-onboarding intakein progress
    Opening the paths to partner, collaborate, or onboard as a merchant — each with its own route into the network.
  • ◆
    T1 wallet-node architecture assembly & testingin progress
    The every-wallet T1 nodes moving from render into physical assembly and bench testing — the broad entry tier taking shape as real hardware.
  • ◆
    T2 POS-node device acquisition & architectural programmingin progress
    The T2 point-of-sale node devices negotiated and on order — the node architecture being programmed onto the merchant-tier hardware.
  • ◆
    T1 cold-wallet procurement & architectural implementationin progress
    Cold-wallet node units negotiated and on order — implementing the compilation-node architecture on the vault-tier device.
  • T1 wallet-node participation liveplanned
    Every wallet becomes an active network node — the broad, accessible entry point to the mesh.
  • T2 compilation & POS node operatorsplanned
    The merchant storefront nodes that wallets graduate into — the working core of the commerce layer.
  • 15-region masternode backboneplanned
    The designed global footprint — fifteen regional T4 masternodes placed for low-latency reach worldwide.
  • Node economics & operator incentivesplanned
    Revenue from real work — compilations, not speculation — flowing to the operators who carry the network.
  • Regional latency mesh in serviceplanned
    Nodes placed where users are, so settlement is fast wherever the swipe happens.
IV
The Atlas
● Families shipped
One translator family at a time, to every chain.

VXIR reaches a whole virtual-machine family from a single translator — the family-multiplier proven on EVM, on mainnet, then extended across the atlas. Every family below is a shipped, byte-deterministic translator, verified and now in independent audit; the IR core and the chain-adapter seam never change.

Progress15 of 15 done
  • ✓
    Family-multiplier architecture provendone
    One EVM translator and 298 pairs reach the entire EVM family — the multiplier working exactly as designed, on mainnet.
  • ✓
    N×N integration collapse designeddone
    A handful of translator families instead of hundreds of one-off integrations — the scaling thesis, mapped.
  • ✓
    Move family — Sui & Aptosdone
    The Move object model — one family reaching Sui and Aptos, compiled deterministically.
  • ✓
    UTXO family — Bitcoin, Lightning & Cardanodone
    The UTXO model and a Lightning path — deterministic compilation across the oldest rails in the space.
  • ✓
    Cosmos / IBC stablecoin clusterdone
    One translator unlocks the IBC stack — the connected Cosmos stablecoin ecosystem, 100+ zones, in a single family.
  • ✓
    Stellar & Sorobandone
    Classic payment operations as trivial deterministic encodes; Soroban for smart-contract reach.
  • ✓
    TVM — TRONdone
    The leading chain for stablecoin settlement and remittance volume — the highest payments-ROI family.
  • ✓
    TON — Telegram-native distributiondone
    A consumer-wallet path riding Telegram's reach straight into everyday hands.
  • ✓
    WASM family — MultiversX & ICPdone
    A distinct WASM execution model — one family across MultiversX and ICP.
  • ✓
    Canton — enterprise, RWA & compliance tierdone
    The regulated, real-world-asset tier — tied directly to the compile-time compliance patent.
  • ✓
    AVM — Algoranddone
    Native Algorand compilation — live behind the x402 pay-per-compile endpoint.
  • ✓
    XRPL — XRP Ledgerdone
    Native XRP Ledger payment instructions, compiled deterministically.
  • ✓
    NEARdone
    The NEAR runtime as its own deterministic translator target.
  • ✓
    Polkadotdone
    Substrate-based compilation reaching the Polkadot ecosystem.
  • ✓
    Starknetdone
    The Cairo / Starknet execution target — zk-rollup reach.
Where it lands

A dozen translators. An entire on-chain economy.

The four milestones converge on one outcome: a checkout counter that speaks every chain, carried by a network that grows itself, settling real value the moment intent is expressed. Proven where it counts, building where it's next.

The reach: the full atlas of translator families compiling to 2,400+ native-transaction targets — the N×N collapse working as designed. A handful of translators, not hundreds of integrations.