Base Fee Floor
A consensus-enforced minimum base fee: chain 2800 rejects any block header whose base fee falls below the floor, keeping spam costly and fees predictable.
Every block on an EVM chain publishes a base fee in its block header: the minimum price a transaction must pay, per unit of work, to be included in that block. Under the standard EIP-1559 rules the base fee is elastic. It rises when blocks are congested and decays when they are not. On chain 2800, which produces a block roughly every 500 ms, quiet stretches would let that decay compound block after block, driving the base fee toward zero. A near-zero base fee makes spam close to free, and it makes fee estimation unstable the moment real demand returns.
The base fee floor closes that gap. It is a consensus rule enforced at header validation, active from a fixed block height: a header whose base fee sits below the floor is invalid, and the network refuses it. The floor is a lower bound only. It does not cap fees, and above it the normal elastic adjustment applies unchanged.
On chain 2800 the rule is checked by each of the nine validators that run QBFT consensus, where a block needs a quorum of six to advance, and independently by a second client built from a separate codebase (see client diversity). A header that violates the floor cannot gather a quorum, so it can never reach finality. Because the floor lives in the standard EIP-1559 header field, wallets and tooling read it with no changes (see EVM compatibility).
Verify it yourself
Verify it yourself: POST {"jsonrpc":"2.0","id":1,"method":"eth_getBlockByNumber","params":["latest",false]} to https://rpc.aere.network and read the baseFeePerGas field of the returned header; sample consecutive blocks during a quiet period and the value holds at a fixed minimum instead of decaying toward zero.