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.
The shape
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. The result carries the operation's result code (no_trust). Readers that skip failed transactions lose the fee and sequence change; readers that assume a failed transaction changed something record effects that never happened.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 15,640 B | 820df22c8284… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 15,640 B | ca7d8dc009b7… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The operation fails with no_trust. p30-mainnet-generated | no_trust | constructionsnapshotcorewalker |
| The operation fails with no_trust. p30-testnet-generated | no_trust | constructionsnapshotcorewalker |
| No operation changed state: the operation meta is empty. p30-mainnet-generated | length 0 | snapshot |
| No operation changed state: the operation meta is empty. p30-testnet-generated | length 0 | snapshot |
| The sequence number is still consumed: the source account changes before apply (state, updated). p30-mainnet-generated | length 2 | snapshot |
| The sequence number is still consumed: the source account changes before apply (state, updated). p30-testnet-generated | length 2 | snapshot |
| The fee is still charged: the fee source changes in fee processing. p30-mainnet-generated | length 2 | snapshot |
| The fee is still charged: the fee source changes in fee processing. p30-testnet-generated | length 2 | snapshot |
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.no-trust · compiled from catalog/failure.path-payment-strict-send.no-trust.json · entry.json
A strict-send path payment to an account that does not exist, on mainnet
The destination account is missing: no_destination.
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).