Lifecycle stages
All backends live onmain (chains are directories and target ids, not
branches). Lifecycle stages follow the target notes.
Current product implementation is governed by the primary-chain completion
covenant (D-045): finish solana-sbpf-asm, then evm, then wasm-near to
production-grade quality before advancing any additional chain beyond docs-only
research or frozen spike maintenance.
Status table
| Target id | Pipeline | Stage | Local validation |
|---|---|---|---|
evm | Lean / portable IR → Yul → solc → bytecode | Baseline (mature) | golden Yul, diagnostics, Foundry runtime smoke, Anvil deploy |
solana-sbpf-asm | portable IR → sBPF assembly → sbpf → ELF | Experimental | Mollusk tests, Surfpool/Web3.js live smokes, Pinocchio equivalence gates |
wasm-near | portable IR → EmitWat (Wasm AST → WAT) → wat2wasm | Experimental | 45-case diagnostics, IR coverage manifests, formal trace obligations, offline host smoke |
psy-dpn | portable IR → .psy → Dargo → DPN circuit JSON | Experimental (restricted subset) | golden sources, diagnostics, dargo execute smokes |
aleo-leo | portable IR → Leo package → leo build/leo test | Research spike | Counter/PureMath golden fixtures and smokes |
wasm-cloudflare-workers | portable IR → TypeScript Worker | Research (off-chain host, D-033) | tsc type-check, wrangler dry-run |
Token SDK
The multi-chain Token SDK (TokenSpec, RFC 0006)
routes one token intent to ERC-20 bytecode on EVM or SPL Token / Token-2022
deployment plans on Solana.
Gate status
- Gate G0 — Closed (2026-07-03): shared-scenario behavior/resource-budget
parity on
evm+solana-sbpf-asm+wasm-near. - Gate P0 — Open: production-grade completion of the three priority chains.