A transaction left with an open sponsorship fails txBAD_SPONSORSHIP
BEGIN_SPONSORING_FUTURE_RESERVES without the matching END in the same transaction: every operation succeeds, then the transaction fails with txBAD_SPONSORSHIP and nothing it did is kept.
The shape
BEGIN_SPONSORING_FUTURE_RESERVES without the matching END in the same transaction: every operation succeeds, then the transaction fails with txBAD_SPONSORSHIP and nothing it did is kept. Its fee is charged and its sequence number consumed. Readers that take operation results at face value record sponsorship that never happened.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 15,640 B | 820df22c8284… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 15,640 B | ca7d8dc009b7… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The transaction fails with txBAD_SPONSORSHIP. p30-mainnet-generated | tx_bad_sponsorship | constructionsnapshotcorewalker |
| The transaction fails with txBAD_SPONSORSHIP. p30-testnet-generated | tx_bad_sponsorship | constructionsnapshotcorewalker |
| No operation changed state. p30-mainnet-generated | length 0 | snapshot |
| No operation changed state. p30-testnet-generated | length 0 | snapshot |
| The sequence number is consumed. p30-mainnet-generated | length 2 | snapshot |
| The sequence number is consumed. p30-testnet-generated | length 2 | snapshot |
Check it yourself
make verify # schema, hashes, the byte-for-byte round trip and every fact above
make oracle # the facts' values, re-read by stellar-core and the schema walkerEntry id failure.tx.bad-sponsorship · compiled from catalog/failure.tx.bad-sponsorship.json · entry.json
SET_TRUST_LINE_FLAGS fails with SET_TRUST_LINE_FLAGS_NO_TRUST_LINE
A transaction whose SET_TRUST_LINE_FLAGS operation fails at apply is still written into the closed ledger: its fee is charged, its sequence number is consumed, and none of its operations change state.
Apply order is not transaction-set order, and differs by network and protocol
The transaction set lists transactions in phases sorted by hash; core applies the classic phase first, then the Soroban phase, each in an order shuffled by the hash of the whole set (TxSetFrame.cpp ApplyTxSorter).