02Sheet 02.03.160 · Entries

A failed 14-operation offer transaction with two failure codes and twelve successes that changed nothing

One transaction manages 14 offers. Operation 4 fails with not_found and operation 13 with underfunded; the other twelve report success, some with the offer deleted.

FIG. · Where it sits · inside LedgerCloseMetapre-cap · H-C1
two failure codes (not_found at op 4, underfunded at op 13) in one failed tx; twelve other ops report success

The shape

One transaction manages 14 offers. Operation 4 fails with not_found and operation 13 with underfunded; the other twelve report success, some with the offer deleted. The transaction failed, so none of it happened: the meta has no operation changes. Each operation still has its own result, including results evaluated after the first failure. Readers that take the first failing code as the only one, or that apply "success" results of a failed transaction, get both wrong.

Variants

VariantProtocolNetworkSourceSizesha256
p12-mainnet-mined-l26588352P12mainnet passphrasemined from history887,884 B039ba91a4dfd…

What a correct reader returns

A correct reader findsValueBacked by
Operation 4 fails with not_found.not_foundsnapshotcorewalker
Operation 13 fails with underfunded.underfundedsnapshotcorewalker
Operation 0 reports success with its offer deleted, in the failed transaction.deletedsnapshotcorewalker
There are 14 operation results.length 14snapshot
No operation meta is recorded for the failed transaction.length 0snapshot

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.manage-offer.fourteen-ops-two-codes-p12 · compiled from catalog/failure.manage-offer.fourteen-ops-two-codes-p12.json · entry.json

On this page