Economics Facts

Economics facts for simulations

This page summarizes the machine-readable v1.3 economics subset in `_facts/roko-v1.3-economics-subset.json`. It is intended for simulation consumers that need stable inputs for block time, fee routing, pwROKO, staking inflation, and EVM fee caveats.

Canonical current facts

AreaCurrent factSimulation treatment
Mainnet block timeThe mainnet runtime is compiled for 3-second blocks. Use 3 seconds for canonical mainnet v1.3 scenarios.
Testnet block timeThe current testnet runtime runs 2-second blocks; 6 seconds is a production-testnet target, not current runtime state. Use 2 seconds for current testnet calibration and 6 seconds only as a planned/sensitivity case.
Runtime fee splitTransaction fees and tips split 20% Treasury, 50% block author, and 30% TemporalFeePool in both runtimes. Use 20/50/30 as the canonical non-EVM runtime fee split.
TemporalFeePoolThe 30% TemporalFeePool share is distributed by recorded timestamper weights, with block-author fallback when no weights exist. Track TemporalFeePool separately from generic treasury revenue.
EVM pricingEVM gas uses an EIP-1559-style base fee with 1 gwei default base fee and a 75,000,000 block gas limit. Model EVM gas demand separately from Substrate extrinsic fees.
EVM fee routing caveatTestnet EVM fees route through `DealWithFees`, but mainnet currently sets `OnChargeTransaction = ()`. Do not assume mainnet EVM fees follow 20/50/30 until implementation is changed or confirmed.
pwROKO lockingpwROKO is minted by reserving native ROKO 1:1, is non-transferable, and unlocks through a cooldown flow. Enforce 1:1 backing and non-transferability as hard invariants.
Staking assetStaking uses pwROKO in both testnet and mainnet runtimes. Model staking and governance power through backed pwROKO.
Reward backingStaking rewards are minted with direct native backing before equal pwROKO is minted. Do not model unbacked pwROKO issuance.
Staking inflationStaking rewards follow a 2.5%–10% inflation curve, targeting 50% ideal stake with 5% falloff. Use inflation as canonical L1 security issuance; fixed pools are separate incentive scenarios.
Legacy ERC-20 migrationNo bridge or wrap mechanism for the Ethereum ERC-20 ROKO exists in the runtime repo today. Treat migration as planned/unimplemented until bridge or governance implementation evidence exists.

Contradictions that affect simulations

  • Block time: current testnet is 2 seconds, planned production-testnet is 6 seconds, and mainnet is 3 seconds. Unqualified 6-second simulation defaults are stale unless clearly labeled as a planned testnet sensitivity.
  • Staking currency: runtime staking uses pwROKO in both runtimes. Older claims that mainnet staking uses native ROKO are stale.
  • EVM fees: Substrate runtime fees use the 20/50/30 split, but mainnet EVM fees are not currently wired through `DealWithFees`. EVM fee revenue should be a caveated sensitivity until the mainnet path is resolved.
  • Reward model: the runtime uses the 2.5%–10% staking inflation curve. A fixed pre-allocated reward pool can be modeled only as a temporary incentive program, not canonical L1 security issuance.
  • Legacy migration: runtime evidence does not show an ERC-20 bridge today. Holder migration should be modeled as a planned adoption/cutover process until implementation lands.

Whitepaper alignment

The normalized subset maps these code-backed facts to the v1.3 whitepaper economics sections:

  • Section 5: native L1 operating model, EVM compatibility, and existing-holder migration context.
  • Section 7.2: staking rewards, pwROKO governance/staking mechanics, and fee allocation.
  • Table 1: economic flows and staking/reward assets.

See also