A Soroban transaction fails txNO_ACCOUNT at apply and its fee is never refunded
Core applies a ledger's classic phase before its Soroban phase and re-checks the source account, sequence number, signatures and sequence-age preconditions at apply (TransactionFrame::commonValid;…
The shape
Core applies a ledger's classic phase before its Soroban phase and re-checks the source account, sequence number, signatures and sequence-age preconditions at apply (TransactionFrame::commonValid; OperationFrame::checkSignature with forApply). Here a classic transaction earlier in the same ledger merges the source account after its fee was charged, so this Soroban transaction fails with txNO_ACCOUNT. The refund has nowhere to go: there is no post-apply fee change and no refund event, and fee_charged is the full declared maximum (TransactionFrame.cpp:998-1001). Readers that compute the fee as charge minus refund, or expect a refund for every Soroban transaction, get it wrong.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 17,236 B | dbc26aa0d752… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 17,228 B | b464fb610c5d… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 17,132 B | 93d7ae80867e… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 17,124 B | e7e04e4b8cdf… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The transaction fails with tx_no_account although it was valid when submitted. p30-mainnet-generated | tx_no_account | constructionsnapshotcorewalker |
| The transaction fails with tx_no_account although it was valid when submitted. p28-mainnet-generated | tx_no_account | constructionsnapshotcorewalker |
| The transaction fails with tx_no_account although it was valid when submitted. p30-testnet-generated | tx_no_account | constructionsnapshotcorewalker |
| The transaction fails with tx_no_account although it was valid when submitted. p28-testnet-generated | tx_no_account | constructionsnapshotcorewalker |
| The transaction that caused it is in the same ledger. p30-mainnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| The transaction that caused it is in the same ledger. p28-mainnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| The transaction that caused it is in the same ledger. p30-testnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| The transaction that caused it is in the same ledger. p28-testnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| The sequence number is not consumed: no change before apply. p30-mainnet-generated | length 0 | snapshot |
| The sequence number is not consumed: no change before apply. p28-mainnet-generated | length 0 | snapshot |
| The sequence number is not consumed: no change before apply. p30-testnet-generated | length 0 | snapshot |
| The sequence number is not consumed: no change before apply. p28-testnet-generated | length 0 | snapshot |
| No operation was applied: the operation meta is empty. p30-mainnet-generated | length 0 | snapshot |
| No operation was applied: the operation meta is empty. p28-mainnet-generated | length 0 | snapshot |
| No operation was applied: the operation meta is empty. p30-testnet-generated | length 0 | snapshot |
| No operation was applied: the operation meta is empty. p28-testnet-generated | length 0 | snapshot |
| The transaction source is the account changed earlier in the ledger. p30-mainnet-generated | GDPTVINFP7QFK2MM7ECSZY6DTOBOTVSV45GDHKAQKYCUBMN7SDU5SIVC | constructionsnapshotcorewalker |
| The transaction source is the account changed earlier in the ledger. p28-mainnet-generated | GDPTVINFP7QFK2MM7ECSZY6DTOBOTVSV45GDHKAQKYCUBMN7SDU5SIVC | constructionsnapshotcorewalker |
| The transaction source is the account changed earlier in the ledger. p30-testnet-generated | GDPTVINFP7QFK2MM7ECSZY6DTOBOTVSV45GDHKAQKYCUBMN7SDU5SIVC | constructionsnapshotcorewalker |
| The transaction source is the account changed earlier in the ledger. p28-testnet-generated | GDPTVINFP7QFK2MM7ECSZY6DTOBOTVSV45GDHKAQKYCUBMN7SDU5SIVC | constructionsnapshotcorewalker |
| No refund: there is no post-apply fee processing. p30-mainnet-generated | length 0 | snapshot |
| No refund: there is no post-apply fee processing. p28-mainnet-generated | length 0 | snapshot |
| No refund: there is no post-apply fee processing. p30-testnet-generated | length 0 | snapshot |
| No refund: there is no post-apply fee processing. p28-testnet-generated | length 0 | snapshot |
| fee_charged is the full declared maximum: 100 stroops inclusion plus the whole 100,000,000-stroop resource fee. p30-mainnet-generated | 100000100 | constructionsnapshotcorewalker |
| fee_charged is the full declared maximum: 100 stroops inclusion plus the whole 100,000,000-stroop resource fee. p28-mainnet-generated | 100000100 | constructionsnapshotcorewalker |
| fee_charged is the full declared maximum: 100 stroops inclusion plus the whole 100,000,000-stroop resource fee. p30-testnet-generated | 100000100 | constructionsnapshotcorewalker |
| fee_charged is the full declared maximum: 100 stroops inclusion plus the whole 100,000,000-stroop resource fee. p28-testnet-generated | 100000100 | constructionsnapshotcorewalker |
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 tx.apply-time.no-account-fee-not-refunded · compiled from catalog/tx.apply-time.no-account-fee-not-refunded.json · entry.json
A transaction valid at submission fails txBAD_SEQ at apply
Core applies a ledger's classic phase before its Soroban phase and re-checks the source account, sequence number, signatures and sequence-age preconditions at apply (TransactionFrame::commonValid;…
ACCOUNT_MERGE fails with ACCOUNT_MERGE_HAS_SUB_ENTRIES
A transaction whose ACCOUNT_MERGE 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.