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 100 passing tests across 19 files, 1,085,648 assertions, seven accepted vault/operator actions, and a finite depth-five explorer with 11,550 attempted edges across 2,894 unique state/slot nodes. Selected-source inventories bind the allocation, reward, governance, and complete 283-file middleware archives. The middleware graph recursively closes at 310 Solidity files and 1,402 edges with zero unresolved. Hash-pinned Forge/Solidity compilation succeeds; a fixed-seed non-fork EVM run records 839 pass and six skip. A deterministic replay classifies the earlier allowlist proxy-admin collision as an upstream fuzz-domain/assertion mismatch with no authorization bypass. Of 43 direct project-core counterparts, 19 are compatible only at the reviewed source level, one StrategyManager path is reviewed source-incompatible because project core adds mandatory share-mutation hooks, and 23 remain manually queued. The storage relocation and hook findings are not EVM storage-layout proofs, bytecode-equivalence results, Cardano translations, or approved divergences; compatibility remains open and zero middleware behavior is accepted for Cardano. A separate exact-bigint allocation oracle remains model-only. Complete pre-validator plans keep 60 unresolved or prohibited seams absent and fail closed. The pinned Catalyst stack and project guards/codecs provide 106 non-protocol UPLC evaluations; F-001 remains open. Pinned Blaze builds/tests pass and one generic non-protocol transfer is constructed, signed, and emulated. No protocol transition has been UPLC-evaluated, Blaze-emulated, or testnet-executed. The strict release report remains NOT_RELEASED.

The middleware corpus closes the reachable Solidity graph from 78 source files, 97 test files, and two scripts at 310 files and 1,402 import edges with zero unresolved, while recording 121 normalized source declarations, 618 named source functions, 116 test families, and 800 named tests. Its 921 exact review records still accept zero Cardano behavior. Hash-pinned Foundry v1.3.6 and Solidity 0.8.27 compile all 310 files; a fixed-seed non-fork EVM run records 839 passing and six skipped. A deterministic overlay reproduces the upstream assertion mismatch and confirms the transparent proxy's expected admin rejection before the call reaches Allowlist. The 43-path semantic triage resolves 19 paths as source-compatible, classifies one StrategyManager path as source-incompatible due to new mandatory hooks, and queues 23 for manual semantic review. Three project-core hook test files are hash-bound but unexecuted. These findings are not storage-layout proofs, bytecode equivalence, Cardano translation, or approved divergence. This is partial upstream EVM evidence, not Cardano compatibility or execution.

Current revision reconciliation is bound to self-contained evidence checkpoint 49cdc1b31d4e34ff60c96607ae2cc1cf9ed23716: all revision-bound dependency and middleware Forge reports are current, the same-host clean checkout matched five projections in 208,478 ms, and the release gate records one pass and twelve failures, 106 non-protocol UPLC evaluations, one generic Blaze acceptance, zero protocol or public-testnet executions, 19 source-compatible, one reviewed source-incompatible, and 23 manually queued direct-core paths, and NOT_RELEASED.

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.