Polkadot

Gavin Wood's 2016 white paper did not propose one general-purpose chain that would host every application. It proposed a heterogeneous multi-chain framework: a relay chain would coordinate consensus while distinct chains could carry different state-transition rules. That architectural split became Polkadot's identity.

Web3 Foundation launched the initial network on 26 May 2020 after a staged development program led with substantial work by Parity Technologies. The early rollout began under foundation control and progressively enabled validator selection, governance and transfers. That history matters because today's on-chain authority did not exist fully formed at genesis.

The first production model treated a relay-chain core like a long lease. Projects locked DOT through auctions for continuous parachain slots, often with crowdloans. This secured scarce capacity but forced a chain to acquire a large block of time whether its blocks were full or empty.

Runtime 1.2.0 ended those auctions on 19 September 2024. Existing leases became bulk coretime, while new users could buy scheduled bulk regions or place pay-as-you-go orders. A parachain remains its own layer-one state machine; the purchased object is access to Polkadot validation and interoperability, not ownership of the relay chain.

OpenGov replaced Governance V1's Council and Technical Committee with public referenda organized into 15 origins and tracks. Root can authorize the highest-privilege calls; spending and administration use narrower tracks. Approval, support, deposits and time limits differ by track, and conviction lets voters trade longer locks for more voting weight.

Technical expertise still has an institutional channel. The Fellowship can approve RFCs and whitelist calls, but its whitelist does not enact code: DOT voters must pass a referendum. PCF fills a different gap by signing contracts or handling off-chain administration when OpenGov authorizes and funds it. Neither institution turns DOT into shares, and large holders or delegates can still acquire outsized voting influence.

NPoS uses bonded DOT to select and support validators, with variable rewards and liquidity constraints. The older staking guide exposes both validators and nominators to slashing. Parity’s March 2, 2026 roadmap proposed unslashable nominators and 24–48-hour unbonding for April; the later official post still called these future updates. These sources do not confirm their activation, so this account does not promise either protection or a current withdrawal period. Nominators back validators, and the protocol distributes stake across the active set. Rewards depend on activity, era points, commission and other protocol conditions; inactivity is a further risk.

The November 2024 model issued 120 million DOT yearly, allocating 85% to stakers and 15% to treasury. Polkadot later reported a 2.1 billion cap and stepped issuance effective March 14, 2026. Its announcement gives about 56.88 million annually and a 53.6% cut, but that cut from 120 million equals 55.68 million. Parity describes issuing 13.14% of the remaining headroom every two years; the later post instead describes a 13.14% reduction in issuance. These accounts do not establish one reconciled current rate. The new framework replaces treasury burns with the Dynamic Allocation Pool (DAP), an account intended to collect issuance, fees, coretime revenue and penalties for governance-directed budgets. Parity described a phased rollout; this review does not verify every routing change in the live runtime. The older Wiki still describes the former system. DOT continues to buy computation and support votes, without granting equity in Parity, Web3 Foundation, PCF or independent parachains.

JAM reframes Polkadot's center as a more general join-accumulate machine whose services could include the work now done for parachains. The Gray Paper is a draft specification, and implementations are prototypes. That makes JAM a researched direction, not the software presently securing user assets and parachain blocks.

The JAM FAQ makes the political dependency explicit: replacement of the relay chain would proceed only through decentralized governance. Existing parachain logic is intended to continue as a service, but timing, implementation conformance and migration risk remain open. Polkadot's biography therefore ends with a proposal placed before the same token electorate that can change supply and runtime code today.