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.
| Parameter | Value | Note |
|---|---|---|
| Maximum supply | 252,288,000 MIGO | |
| Halving interval | 1051200 blocks | |
| DevFund sunset block | 1051200 blocks | Coincides with the same block as halving |
| Dividend vesting period | 288000 blocks | |
| Treasury share (fees) | 60% | |
| Node pool share (fees) | 40% | |
| Validator collateral threshold | 108,000 MIGO | |
| Masternode collateral | 25,000 MIGO |
| Active validators (N) | Total per block | DevFund | Validator pool | Per validator | Masternode pool | Dust (wei) |
|---|---|---|---|---|---|---|
| 7 | 35 MIGO | 3.5 MIGO | 28.35 MIGO | 4.05 MIGO | 3.15 MIGO | 0 |
| 8 | 37.333 MIGO | 3.733 MIGO | 30.24 MIGO | 3.78 MIGO | 3.36 MIGO | 1 |
| 10 | 40 MIGO | 4 MIGO | 32.4 MIGO | 3.24 MIGO | 3.6 MIGO | 0 |
| 13 | 44.2 MIGO | 4.42 MIGO | 35.802 MIGO | 2.754 MIGO | 3.978 MIGO | 0 |
| 15 | 45 MIGO | 4.5 MIGO | 36.45 MIGO | 2.43 MIGO | 4.05 MIGO | 0 |
| 20 | 60 MIGO | 6 MIGO | 48.6 MIGO | 2.43 MIGO | 5.4 MIGO | 0 |
| 25 | 75 MIGO | 7.5 MIGO | 60.75 MIGO | 2.43 MIGO | 6.75 MIGO | 0 |
| 30 | 90 MIGO | 9 MIGO | 72.9 MIGO | 2.43 MIGO | 8.1 MIGO | 0 |
| 35 | 105 MIGO | 10.5 MIGO | 85.05 MIGO | 2.43 MIGO | 9.45 MIGO | 0 |
| 40 | 120 MIGO | 12 MIGO | 97.2 MIGO | 2.43 MIGO | 10.8 MIGO | 0 |
| 45 | 120 MIGO | 12 MIGO | 97.2 MIGO | 2.16 MIGO | 10.8 MIGO | 0 |
| 50 | 120 MIGO | 12 MIGO | 97.2 MIGO | 1.944 MIGO | 10.8 MIGO | 0 |
