04Sheet 04.06 · Hazards

Layer E: Events

Every hazard in layer E of the registry, each with its evidence and the test the corpus holds or will hold for it.

Unified events (CAP-0067), event data carrying muxed IDs and deep maps, and diagnostic events emitted twice.

H-E1in the corpusreplay probe
Unified events (CAP-0067): classic ops emit events; fee events before and after all txs
TestEvery C-ledger (events counted), S-ledgers (fee events)
H-E2in the corpusconformancereplay probe
Event data carrying muxed IDs (to_muxed_id), maps, deep ScVal
EvidenceCAP-0067, wallet-backend#756
TestS11, S19, S28, mainnet M:soroban-event-deep-scval
H-E3in the corpusreplay probe
Diagnostic events double-emitted
TestGalexie flag profile (recipes/flags/galexie.cfg, ENABLE_SOROBAN_DIAGNOSTIC_EVENTS): each contract event appears twice, in operations[].events and again as a contract-type diagnostic event. The diagnostic core_metrics event invoke_time_nsecs is wall-clock time, so these ledgers are not byte-reproducible; the normalised form zeroes it (tools/lib.mjs normalise)

The hazards come straight from caps/registry.json. A tag says which check will exercise each one: replay probe, conformance, linter, guide or verify facts. In the corpus means an entry already targets it.