02Sheet 02.03.190 · Entries

SET_OPTIONS fails with LOW_RESERVE inside a sponsorship sandwich in a fee bump, on mainnet

A fee bump whose inner transaction is a sponsorship sandwich: begin sponsoring, remove one signer, add another, end sponsoring.

FIG. · Where it sits · inside LedgerCloseMetapre-cap · CAP-0015 · CAP-0033 · H-C1 · H-C2 · H-C3
SetOptionsResult.SET_OPTIONS_LOW_RESERVE at op index 2; the other ops report success in a failed tx
txFEE_BUMP_INNER_FAILED with a four-op inner result on mainnet
sponsorship sandwich whose sponsored signer add fails for the sponsor's reserve

The shape

A fee bump whose inner transaction is a sponsorship sandwich: begin sponsoring, remove one signer, add another, end sponsoring. The sponsor lacks the reserve for the new signer, so operation 2 fails with low_reserve and the whole inner transaction fails (txFEE_BUMP_INNER_FAILED). The inner result still lists every operation's code: the three others report success, although none of their effects were kept.

Variants

VariantProtocolNetworkSourceSizesha256
p29-mainnet-mined-l65024796P29mainnet passphrasemined from history2,405,204 Bd0baaddf24b1…

What a correct reader returns

A correct reader findsValueBacked by
The inner SET_OPTIONS at op index 2 fails with low_reserve.low_reservesnapshotcorewalker
Op 0 (begin sponsoring) still reports success in the failed inner transaction.successsnapshotcorewalker
The failing op adds a signer with weight 20.20snapshotcorewalker
The inner result has four operation results.length 4snapshot

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.set-options.low-reserve-in-fee-bump-mainnet · compiled from catalog/failure.set-options.low-reserve-in-fee-bump-mainnet.json · entry.json

On this page