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 shape
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 3000 bidder pays 2000 per operation, less than it bid, more than the header base_fee of 100.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 127,356 B | 310ce9a4d22a… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 127,356 B | d04302229a55… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The classic component's base fee is 2000. | 2000 | constructionsnapshotcorewalker |
| The header base fee stays 100. | 100 | constructionsnapshotcorewalker |
| The 3000-per-operation bidder is charged 100000 for 50 operations: 2000 each. | 100000 | constructionsnapshotcorewalker |
| It bid 150000. | 150000 | 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 surge.classic-oversubscribed · compiled from catalog/surge.classic-oversubscribed.json · entry.json
A Soroban call in a fee bump paid by a muxed account: charge and refund on the fee source
The resource fee is charged at the maximum and the unused part refunded after apply; both go to the fee source bob (via M(bob, 13)), not to the inner source alice.
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.