DC-COMPAT-01
DC derived enforcedCardano compatibility is proven ONLY on observable surfaces — per-block accept/reject verdict, selected tip hash, block hashes, cardano-cli query-utxo result, protocol transcripts — with named fixtures pinning oracle versions (cardano_node_version, cardano_cli_version) and reproducible inputs. Asserting Ade's internal ledger fingerprint == a Haskell/cardano-node serialized-state hash is FORBIDDEN and CI-blocked. The only valid fingerprint-equality is internal Ade-vs-Ade (genesis-path == snapshot-path).
- Source
docs/clusters/PHASE4-N-Y/S5-compatibility-evidence.md
- Cluster
- PHASE4-N-Y
- Introduced in
- PHASE4-N-Y
Enforcement trace
Tests 1
- sync_differential_snapshot_to_tip
Cross-references
Attack rationale
Comparing Ade's Ade-canonical fingerprint to a Haskell serialized-state hash would either always fail (different serialization) or, if forced to pass, would smuggle a false equivalence claim. Compatibility must be proven on the surfaces both implementations actually expose.