04Sheet 04.08 · Hazards
Layer G: Protocol and network variants
Every hazard in layer G of the registry, each with its evidence and the test the corpus holds or will hold for it.
Bytes that depend on the network passphrase, older protocols, mainnet-only code paths in core, and CAPs gated before mainnet.
H-G1in the corpusconformanceverify facts
Passphrase-dependent bytes (hashes, contract IDs, signatures)
EvidenceF4; R01
Testp30-mainnet and p30-testnet for every generated entry
H-G2in the corpusreplay probe
Older protocol a pre-fix indexer can decode
EvidenceR02
TestP28 runs of the Soroban lane are part of make generate; sighting entries get P28 variants in B4
H-G3guide
Mainnet-only code paths in core (
gIsProductionNetwork)Evidence
gaps-and-risks §3.3: P24 key filter, P15→16 offer fix, P24 hot-archive fix, one historical offerTestDocumented: none reachable by a standalone P30 generator; mined mainnet entries (planned) will cover real-network behaviour
H-G4verify facts
Gated CAPs before mainnet (
next/)Test
next/ channel per upgradeThe 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.