Layer B: Values and encodings
Every hazard in layer B of the registry, each with its evidence and the test the corpus holds or will hold for it.
Asset ordering, map keys that collide, amounts past 2⁵³, wide integers, invalid UTF-8, maximum lengths and nesting depth: values that change, or break, when they are converted or decoded.
pool-issuers-sort-differently-by-text-and-bytescreate-whale-1e9-xlm, payment-above-2-pow-53-stroops; offer ids above 2^53 (API vector)scval-every-number-and-time-type; boundaries where a signed reading of the low 64 bits goes wrong (i128 2^63, -2^63, -1; u256 2^127; timepoint 2^63): scval-wide-integer-boundaries; a SAC balance held by a contract above int64 max: sac-mint-to-contract-beyond-int64M:memo-text-non-utf8; ScString S28; manage-data binary C24 + mainnet; home domain and data name cannot hold non-ASCII: core requires printable ASCII (SetOptionsOpFrame.cpp:320, ManageDataOpFrame.cpp:115, util/types.cpp isStringValid)operations-100-muxed-ids; max signers 20 S25; over-length as lane S (SDK only), planned in B5deploy-with-auth-tree-depth-245M:alphanum12-asset; issued "xlm" code c-base trust-issued-xlm-code, payment-issued-xlm-codePrice{n,d} at int32 extremes; prices as floatspath<5>, claimants<10>, extraSigners<2>, dataName 64, operations<100>, AllowTrust 12-char codevectors-at-maximum-length; operations<100> alone in its ledger (the classic set holds exactly 100 operations): operations-100-muxed-idsauth-tree-depth-245-max, auth-tree-depth-246-trapped) as entries in B4, expected divergences pre-registered in B5nestedDelegates)custom-account-nested-delegates; XP002 recursive types include itaddress-v2-credentials; ADDRESS_WITH_DELEGATES in custom-account-nested-delegates (H-B14)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.
Layer A: Addresses and identities
Every hazard in layer A of the registry, each with its evidence and the test the corpus holds or will hold for it.
Layer C: Transaction lifecycle and results
Every hazard in layer C of the registry, each with its evidence and the test the corpus holds or will hold for it.