02Sheet 02.03.175 · Entries

Four path payments in a fee bump: two succeed through a liquidity pool, then NO_TRUST and SRC_NO_TRUST

Inside a fee bump, operations 0 and 1 report success with liquidity-pool claim atoms, operation 2 fails with no_trust and operation 3 with src_no_trust (the source holds no trustline for the asset it sends).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0015 · CAP-0038 · H-C1 · H-C2 · H-C8
PathPaymentStrictSendResult.PATH_PAYMENT_STRICT_SEND_SRC_NO_TRUST at op 3 of a failed inner tx
txFEE_BUMP_INNER_FAILED whose inner results mix pool trades and two failure codes
liquidity-pool claim atoms in the success result of an op inside a failed transaction

The shape

Inside a fee bump, operations 0 and 1 report success with liquidity-pool claim atoms, operation 2 fails with no_trust and operation 3 with src_no_trust (the source holds no trustline for the asset it sends). The inner transaction failed: none of the pool trades happened.

Variants

VariantProtocolNetworkSourceSizesha256
p29-mainnet-mined-l65485185P29mainnet passphrasemined from history2,495,988 Bfc6b3e490799…

What a correct reader returns

A correct reader findsValueBacked by
Operation 3 fails with src_no_trust.src_no_trustsnapshotcorewalker
Operation 2 fails with no_trust.no_trustsnapshotcorewalker
Operation 0 reports a trade through pool LAGSLLBP…, which did not happen.LAGSLLBP6I6A6H52VL7ZNGOSO6PU45Z5B5SZSWVICT7ZACK4PXCFDGA3snapshotcorewalker

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.path-payment-strict-send.src-no-trust-in-fee-bump-mainnet · compiled from catalog/failure.path-payment-strict-send.src-no-trust-in-fee-bump-mainnet.json · entry.json

On this page