02Sheet 02.03.102 · Entries

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.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0005 · H-C18
GeneralizedTransactionSet component baseFee 2000 against header base_fee 100

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

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0127,356 B310ce9a4d22a…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.0127,356 Bd04302229a55…

What a correct reader returns

A correct reader findsValueBacked by
The classic component's base fee is 2000.2000constructionsnapshotcorewalker
The header base fee stays 100.100constructionsnapshotcorewalker
The 3000-per-operation bidder is charged 100000 for 50 operations: 2000 each.100000constructionsnapshotcorewalker
It bid 150000.150000constructionsnapshotcorewalker

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 surge.classic-oversubscribed · compiled from catalog/surge.classic-oversubscribed.json · entry.json

On this page