Cardano Modular Restaking

Architecture map

Canonical state boundaries and value flows

No architecture matchesTry another search term.

MVP lifecycle

Release target: every success and rejection must replay through model → UPLC → emulator
1DepositAssets enter a controlled strategy vault.
2DelegatePositions select an operator pool.
3AllocateExposure activates after visible notice.
4Reward / SlashFunded reward or attributable capped loss.
5WithdrawRelease follows every evidence and claim tail.

Evidence-gated delivery, not document-driven completion.

The source-stable vault evidence records 44 passing tests, 1,078,417 assertions, a 15-vector pinned EigenLayer v1.12.0 arithmetic differential, a finite depth-five explorer with 1,299 attempted edges and 672 unique state/slot nodes, and a 10,000-attempt campaign with 8,872 accepted model transitions and 1,128 expected rejections. A strict offline audit confirms the canonical manifests, current source hashes, run options, logs, and counters; a fresh same-host checkout reproduced all five deterministic model/formal projections. A separate clean Lean build checks 17 named theorems only against an abstract vault-totals model and satisfies PPA-10. Twelve other alpha gates fail, so this remains a pure-model milestone: independent reproduction, validator implementation, UPLC evaluation, Blaze emulation, implementation refinement, and public-testnet execution have not started.

REVIEWED 2026-08-05
PhaseStateExit evidencePrimary source

Progress discipline

  1. Resolve value-bearing choices in docs/DECISION_LOG.md before implementing their paths.
  2. Keep every incomplete validator and policy fail-closed.
  3. Advance status only with source-bound, reproducible evidence using the repository vocabulary.
  4. Update this explorer in the same change as architecture, transition, phase, or evidence changes.

Claims stop exactly where the evidence stops.

The project uses a deliberately strict vocabulary so pure models, transaction construction, evaluator execution, emulator acceptance, public-ledger inclusion, formal proofs, and release decisions cannot be conflated.

OPEN RELEASE GATES ↗

Release tiers

  1. Pre-production alpha: generated UPLC and Blaze emulator evidence, explicitly not public-chain execution.
  2. Testnet-executed alpha: named public-testnet transactions, reconstructed state, and exercised operational recovery.
  3. Production: additional soak, independent review, deployed governance controls, monitoring, and budget headroom.