Skip to content

Chain parameters ​

Launch values, set in app/launch_defaults.go and applied to genesis.

ParameterValueRationale
Total supply100,000,000,000 BKChard cap, fixed at genesis
x/mint inflation0capped supply; staking rewards are pre-funded
Staking reward pool20,000,000,000 BKC over 15 yearsdecays 12% a year, from a locked module account
Account / validator key typesmldsa65 onlycustody policy; governance cannot widen it
Sign modeSIGN_MODE_DIRECT only
auth TxSigLimit4~21 KiB of ML-DSA signer overhead, below the tx cap
ML-DSA signature verify gas6,000above the measured 5.4× ecrecover CPU ratio
consensus block.max_bytes8 MiB1,000 average 5.5 KB transactions + commit + margin
consensus block.max_gas200,000,000500 transactions × 400,000 gas declared by a signed send
Max gas per transaction30,000,000Ethereum mainnet's block gas limit; 15% of a BKC block
feemarket min_gas_price5,000,000also the floor of the EIP-1559 base fee
feemarket base_fee5,000,000starts at the floor
EIP-1559 elasticity2target 100,000,000 gas per block
gov min_deposit10 BKCscaled for 18 decimals
gov expedited_min_deposit50 BKC
gov min_initial_deposit_ratio0.25a proposal needs a quarter of the deposit at submission
mempool max_tx_bytes256 KiBlarge multi-signer and contract deployment transactions
mempool max_txs_bytes256 MiB
mempool size / cache10,000 / 20,000
timeout_commit0.5 s~1 s blocks under load

Why max_gas matters even if blocks are not full ​

ProcessProposal sums the gas each transaction declares, not what it uses. A signed MsgSend uses about 257,000 gas and declares 400,000, so 200,000,000 fits 500 of them. Leaving CometBFT's default -1 would disable baseapp's block gas check, stop the EIP-1559 controller from ever seeing a busy block, and report MaxUint64 to the EVM's GASLIMIT opcode.

Sizes that drive everything ​

Bytes
ML-DSA-65 public key1,952
ML-DSA-65 signature3,309
Average signed transaction~5,500
Commit per validator~3,437 (signature + vote fields)

Out of scope on the testnet ​

IBC (standard light clients cannot verify the forked consensus), hardware wallets, Amino/textual signing, ML-DSA multisig UX. The testnet has not had an external security audit.

BKC testnet is unaudited. Do not hold value on it.