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).
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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p29-mainnet-mined-l65485185 | P29 | mainnet passphrase | mined from history | 2,495,988 B | fc6b3e490799… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| Operation 3 fails with src_no_trust. | src_no_trust | snapshotcorewalker |
| Operation 2 fails with no_trust. | no_trust | snapshotcorewalker |
| Operation 0 reports a trade through pool LAGSLLBP…, which did not happen. | LAGSLLBP6I6A6H52VL7ZNGOSO6PU45Z5B5SZSWVICT7ZACK4PXCFDGA3 | snapshotcorewalker |
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.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
PATH_PAYMENT_STRICT_SEND fails with PATH_PAYMENT_STRICT_SEND_NO_TRUST
A transaction whose PATH_PAYMENT_STRICT_SEND 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.
A strict-send path payment fails with TOO_FEW_OFFERS inside a fee bump on mainnet
No path has enough liquidity: the inner operation fails with too_few_offers.