02Sheet 02.03.103 · Entries
The transaction left out of an oversubscribed ledger applies in the next one at the normal fee
The 1000 bidder did not fit the previous ledger; it applies here, where the set is not full, at base fee 100.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0005 · H-C18
a transaction excluded by surge pricing applies one ledger later at the header base fee
The shape
The 1000 bidder did not fit the previous ledger; it applies here, where the set is not full, at base fee 100.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,400 B | 73e3d4bee4f1… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,400 B | aa3ab5af6a36… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| It is charged 100. | 100 | constructionsnapshotcorewalker |
| The component base fee is the header's 100. | 100 | 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 surge.left-over-next-ledger · compiled from catalog/surge.left-over-next-ledger.json · entry.json
An oversubscribed ledger: the transaction set's base fee is 2000, not the header's 100
101 operations queued for a 100-operation set, bids 3000, 2000 and 1000 per operation: core keeps the two highest and sets the component base fee to the lowest kept bid.
The Soroban transaction left out applies next at base fee 100
The 1000 bidder applies one ledger later where the phase is not full.