02Sheet 02.03.192 · Entries

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.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0033 · H-C3 · H-C1
TransactionResult.txBAD_SPONSORSHIP
txBAD_SPONSORSHIP: a failed transaction whose operations report success

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

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.015,640 B820df22c8284…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.015,640 Bca7d8dc009b7…

What a correct reader returns

A correct reader findsValueBacked by
The transaction fails with txBAD_SPONSORSHIP.
p30-mainnet-generated
tx_bad_sponsorshipconstructionsnapshotcorewalker
The transaction fails with txBAD_SPONSORSHIP.
p30-testnet-generated
tx_bad_sponsorshipconstructionsnapshotcorewalker
No operation changed state.
p30-mainnet-generated
length 0snapshot
No operation changed state.
p30-testnet-generated
length 0snapshot
The sequence number is consumed.
p30-mainnet-generated
length 2snapshot
The sequence number is consumed.
p30-testnet-generated
length 2snapshot

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 walker

Entry id failure.tx.bad-sponsorship · compiled from catalog/failure.tx.bad-sponsorship.json · entry.json

On this page