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 model evidence records 63 passing tests, 1,078,949 assertions, direct register/delegate/delegated-deposit/queue coverage, a 15-vector pinned EigenLayer v1.12.0 arithmetic differential, and a finite depth-five one-owner/two-operator explorer with 11,550 attempted edges across 2,894 unique state/slot nodes. Its 8,174 expected rejections include 3,375 action-specific single-fault transaction-fact mutations paired with every planned-success non-create edge; each rejects exactly without state interference and the report explicitly declares that these rejected fact edges never create nodes. The accepted graph still covers 764 registrations, 288 delegations, delegation to either operator, delegated deposit, partial/full queue, and attributed completion paths. A deterministic source-inventory corpus now binds ten pinned AllocationManager files, 7 interfaces, 21 errors, 11 structs, 15 events, 51 functions, 28 selected test families with 165 named tests, and 31 named but unexecuted Certora declarations. Ten unresolved local service/set/allocation/exit actions map to those comparison seams while remaining absent from the accepted action union and rejecting with V016_INVALID_STATE at derivation and execution without state interference. This is source-inventory plus planning/fail-closed evidence, not modeled service behavior or upstream execution. The operator-aware 10,000-attempt campaign adds 8,506 accepted transitions, 1,494 expected rejections, and 920 transaction-fact mutations. A strict offline audit binds the canonical manifests, current source hashes, run options, logs, fact/scenario partitions, and counters. A fresh same-host checkout reproduced exact source revision f345a31ed10226641fc2e1c1a970c84d7d52af13; all five deterministic model/formal projections matched in 212,397 ms. The source-bound release report passes PPA-10 only, fails 12 gates, and records NOT_RELEASED. Independent reproduction, validator implementation, UPLC evaluation, Blaze emulation, implementation refinement, and public-testnet execution remain open.

REVIEWED 2026-08-06
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.