02Sheet 02.03.143 · Entries

CLAWBACK fails with CLAWBACK_NO_TRUST

A transaction whose CLAWBACK 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.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0035 · H-C1
OperationResult.clawback.no_trust in a closed ledger

The shape

A transaction whose CLAWBACK 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

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.01,812 Bc7a5a4085675…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.01,812 B109b4eda832b…

What a correct reader returns

A correct reader findsValueBacked by
The operation fails with no_trust.no_trustconstructionsnapshotcorewalker
No operation changed state: the operation meta is empty.length 0snapshot
The sequence number is still consumed: the source account changes before apply (state, updated).length 2snapshot
The fee is still charged: the fee source changes in fee processing.length 2snapshot

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.clawback.no-trust · compiled from catalog/failure.clawback.no-trust.json · entry.json

On this page