Emission

MigoChain has zero pre-mine: no address holds a balance at the genesis block. Every MIGO in circulation is minted by the protocol itself as a validator reward — there is no allocation set aside in advance for the founding team, investors or any other address. This is not a marketing claim; it is a protocol invariant that can be verified directly by reading the genesis state.

The reward minted per block follows a curve that depends on the number of active validators (N): as N grows, the total reward per block grows too, but the share per individual validator flattens out gradually. This reward is split four ways: the DevFund, the validator pool (to the validator whose turn it is), the masternode pool (shared across all active masternodes), and a small rounding remainder (“dust”) shown as its own column in the table below. The table below matches the emission report generated directly from the protocol code, one for one.

At a given block height, emission halves: this is a recurring event at a fixed block interval, defined as a protocol parameter rather than a number pulled from a table. The DevFund allocation also ends at that same block (the DevFund sunset) — the two events coinciding at the same block is intentional, and it partially cushions the effect of the halving, because the per-validator share is relieved of the DevFund deduction at the same moment.

No burning

Not a single MIGO is destroyed by the protocol — including the EIP-1559 base fee. Unlike many other EVM chains, the base fee is not sent to a “burn” address and removed from circulation; instead it is routed to the treasury, contributing to the network’s sustainable funding. Fee revenue is split between the treasury and the node pool at a fixed ratio depending on transaction type — that ratio, too, comes from a protocol constant in the table below.

Collateral and dividends

Becoming a validator requires locking a collateral threshold set by the protocol; running a masternode requires a separate, lower collateral. Collateral is not an asset the treasury can seize at will — it is subject to protocol-level slashing for violations such as downtime or double-signing.

A portion of the revenue flowing into the treasury is distributed to collateral holders as dividends in periodic rounds. A distributed dividend does not become usable instantly; it is spread across a linear vesting schedule, which encourages sustained participation in the network over short-term speculation. The vesting period is also shown in the table below as a protocol constant.

Supply and distribution parameters
ParameterValueNote
Maximum supply252,288,000 MIGO
Halving interval1051200 blocks
DevFund sunset block1051200 blocksCoincides with the same block as halving
Dividend vesting period288000 blocks
Treasury share (fees)60%
Node pool share (fees)40%
Validator collateral threshold108,000 MIGO
Masternode collateral25,000 MIGO
Phase 1 emission table — per-block distribution by n active validators
Active validators (N)Total per blockDevFundValidator poolPer validatorMasternode poolDust (wei)
735 MIGO3.5 MIGO28.35 MIGO4.05 MIGO3.15 MIGO0
837.333 MIGO3.733 MIGO30.24 MIGO3.78 MIGO3.36 MIGO1
1040 MIGO4 MIGO32.4 MIGO3.24 MIGO3.6 MIGO0
1344.2 MIGO4.42 MIGO35.802 MIGO2.754 MIGO3.978 MIGO0
1545 MIGO4.5 MIGO36.45 MIGO2.43 MIGO4.05 MIGO0
2060 MIGO6 MIGO48.6 MIGO2.43 MIGO5.4 MIGO0
2575 MIGO7.5 MIGO60.75 MIGO2.43 MIGO6.75 MIGO0
3090 MIGO9 MIGO72.9 MIGO2.43 MIGO8.1 MIGO0
35105 MIGO10.5 MIGO85.05 MIGO2.43 MIGO9.45 MIGO0
40120 MIGO12 MIGO97.2 MIGO2.43 MIGO10.8 MIGO0
45120 MIGO12 MIGO97.2 MIGO2.16 MIGO10.8 MIGO0
50120 MIGO12 MIGO97.2 MIGO1.944 MIGO10.8 MIGO0