04Sheet 04.04 · Hazards

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.

Failed transactions that still change state, fee bumps, sponsorship, Soroban failures, order-book matching, liquidity pools, claimable balances, and fees that differ from what was bid.

H-C1in the corpusreplay probeverify facts
Failed transactions in ledgers (fees charged, no effects, result codes)
TestFailure suite C41–C49: one result code per tx, about 45 codes; tx_failed C32
H-C2in the corpusreplay probeverify facts
Fee-bump inner success and failure
TestC30, C31, mainnet
H-C3in the corpusreplay probe
Sponsorship sandwiches, revocation, txBAD_SPONSORSHIP
Evidencestellar-etl#323 (sponsor missing in state tables)
TestC22, C23, C40 (signer), C44 revoke signer, C45 failures, mainnet M:sponsorship
H-C4in the corpusconformancereplay probe
Preconditions v2 (ledger bounds, min seq, extra signers) and no preconditions
EvidenceCAP-0021
TestC33, PRECOND_NONE C44
H-C5in the corpusreplay probe
Several operations with different sources in one tx
Evidenceparticipants-from-envelope rule
TestC9 (three op sources), C22
H-C6in the corpusreplay probe
Soroban failures: trapped, resource exceeded, archived entry
Evidencestellar-etl#452 (in_successful_contract_call hard-coded true)
TestTrapped S23; mainnet M:soroban-failed (3 ledgers); archived entry todo
H-C7in the corpusreplay probe
Order-book matching: one op claims many offers; offers removed by crossing
Evidencestellar-etl#456 (spurious offer effects)
TestC12 (3 offers), C14, mainnet M:offer-crosses-many
H-C8in the corpusreplay probe
Liquidity pools: deposit, withdraw, pool claim atoms, pool-share trustline without pool row
TestC13, C15, C44 (strict receive through pool), mainnet; pool-share limit-only ChangeTrust c-base pool-share-limit-only-change-trust
H-C9in the corpusreplay probe
Claimable balances: nested predicates, claim, clawback, flags
TestC16–C19, C40 (expired predicate) + C45 cannot-claim, mainnet
H-C10in the corpusreplay probe
Clawback and trustline authorization states (authorized, maintain-liabilities, deauthorized)
Evidencestellar-etl#457 (allow_trust effect types)
TestC20, C21, allow_trust C44, mainnet M:clawback-and-trustline-flags; full deauthorization (authorized and maintain-liabilities both cleared): c-base revoke-trustline-with-offers-and-pool-shares
H-C11in the corpusreplay probe
Sequence bumps and account merges (entry removed)
Evidence
TestC37, C38, mainnet
H-C12in the corpusreplay probe
Transaction apply order differs from transaction-set order
EvidenceR02
TestMulti-tx ledgers C40–C45, mainnet
H-C13in the corpusreplay probeverify facts
Soroban fee charged at the maximum, refunded in post_tx_apply_fee_processing; fee_charged is net
Evidencestellar-etl#453, #511; CAP-0063; measured on S10
TestFacts on existing S-ledgers; Soroban fee bump with a muxed fee source, charge and refund both on the fee source: s-base soroban-fee-bump-muxed-fee-source; fee source merged earlier in the same ledger: no refund, no refund event, fee_charged is the full maximum (TransactionFrame.cpp:998-1001): s-base race-victim-txNO_ACCOUNT
H-C14in the corpusreplay probe
Fee-bump identity: outer hash in TransactionResultPair, inner hash in InnerTransactionResultPair; inner source seq consumed even on failure, fee source seq not
Evidencestellar-etl#464, #477, #465; measured on C31
TestFacts on C30/C31
H-C15in the corpusreplay probe
Failed transactions still change state: sequence bump in tx_changes_before; pre-auth signer removed even when the transaction fails (CAP-0028)
Evidencemeasured on C32, C35; wallet-backend.md:143
TestNew: a pre-auth transaction that fails
H-C16in the corpusverify facts
Transaction-level failures at apply time: txBAD_SEQ, txNO_ACCOUNT, txBAD_AUTH, opBAD_AUTH (state changed earlier in the same ledger or tx)
Evidence15 TransactionResultResult arms uncovered
TestOne ledger, classic attackers then Soroban victims (core applies the classic phase first; within a phase the order is a hash shuffle): txBAD_SEQ, txNO_ACCOUNT, txBAD_AUTH, txBAD_MIN_SEQ_AGE_OR_GAP, and txFAILED with opBAD_AUTH and opNO_ACCOUNT, all valid at submission (TransactionFrame::commonValid, OperationFrame::checkSignature forApply): s-base race-victim-*
H-C17in the corpusreplay probeverify facts
Liabilities: available ≠ balance (UNDERFUNDED with balance > amount; LINE_FULL from buying liabilities)
EvidenceCAP-0003
TestAccount with an open offer pays balance − liabilities + 1
H-C18in the corpusverify facts
Fee paid ≠ fee bid: generalized tx-set component baseFee (surge pricing)
TestClassic: oversubscribed ledger with distinct bids: component baseFee 2000 against header base_fee 100, the 3000 bidder charged below its bid, the 1000 bidder applied one ledger later: c-base surge-priced-oversubscribed, surge-left-over-applies-next-ledger (equal bids are broken by a random seed, SurgePricingUtils.cpp:122). Soroban: ledgerMaxTxCount 2 with bids 3000/2000/1000: phase base_fee 2000, both kept transactions charged the same, the third one ledger later at 100: s-base soroban-surge-priced, soroban-surge-left-over-applies-next-ledger
H-C19in the corpusconformancereplay probe
An operation result whose type differs from its operation: CREATE_PASSIVE_SELL_OFFER returns a MANAGE_SELL_OFFER result
Evidencestellar-core CreatePassiveSellOfferOpFrame.cpp:13 sets the operation body type to MANAGE_SELL_OFFER, so the OperationResult arm is manage_sell_offer; measured on c-base CREATE_PASSIVE_SELL_OFFER
Testc-base CREATE_PASSIVE_SELL_OFFER: envelope create_passive_sell_offer, result arm manage_sell_offer

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.