Polkadot enabled parachain registration and crowdloans after governance vote

Polkadot’s on-chain governance approved Referendum 42 on November 4, 2021, and enacted runtime version 9122, opening the network’s parachain-registration and crowdloan functions. The change mattered because it moved Polkadot’s long-promised multichain design from launch planning into an operational funding and onboarding phase, one week before the first slot auction was scheduled to begin.

Governance cleared the launch plumbing

Referendum 42 was not the parachain auction itself. It authorized a runtime upgrade: a change to the rules executed by Polkadot’s Relay Chain. The proposal had followed a council motion and a fast-tracked public vote. Polkadot’s official account said before enactment that, if approved, teams would be able to register parachains and open crowdloans on November 4 at approximately 19:15 Central European Time.

The surviving governance record shows the referendum passed. That record is the central evidence for this reconstruction; contemporaneous coverage published earlier on November 4 still described the vote as pending and nearly unanimous. The distinction is important. Before the voting period ended, activation was an expectation. After the on-chain result and enactment, registration and crowdloan calls became available under runtime 9122.

Why crowdloans mattered

Polkadot was designed around a Relay Chain that supplies shared security to connected, application-specific chains called parachains. In the 2021 launch model, projects competed for limited connection slots through auctions. A crowdloan allowed DOT holders to support a project by locking DOT through the protocol so the project could use that backing in a slot bid.

That structure did not mean contributors purchased equity, lent money to a conventional borrower or transferred ownership of DOT to the project team. If a supported project won, the contributed DOT could remain locked for the lease period; project teams separately determined any token rewards. Those distinctions mattered institutionally because the upgrade created usable capital-formation machinery, but it did not validate any bidder, guarantee a reward, or remove technical, liquidity or legal risk.

The November 4 activation therefore represented a protocol milestone rather than completed adoption. Teams could register and begin gathering support, while the first auction remained scheduled for November 11. Winning parachains were not yet producing application blocks on Polkadot because of Referendum 42 alone.

Market context, with limits

CoinMarketCap’s historical snapshot for November 4 listed DOT at $53.88, with a market capitalization of $53.21 billion and a seven-day gain of 28.71%. The instrument is DOT quoted in U.S. dollars; the window is the provider’s seven-day snapshot comparison. These figures are not an official closing auction, since crypto trades continuously across venues, and the surviving page does not fully expose its venue mix, calculation timestamp or historical aggregation methodology.

The figures show that the upgrade arrived during strong demand for DOT. They do not prove Referendum 42 caused the entire seven-day move. Expectations for parachain auctions had been public before November 4, so some market response could have preceded enactment, while broader crypto-market conditions could also have influenced the token.

What November 4 did—and did not—settle

The verified development was narrow: governance passed and enacted the runtime that enabled registration and crowdloans. It did not start the first auction, select a winning parachain, establish future network usage or determine the regulatory treatment of DOT or crowdloan rewards in any jurisdiction.

Later context

Polkadot’s later official review records that the first auction batch ran from November 11 through December 16, 2021. That later outcome confirms the launch sequence, but it is not projected backward into what was known when runtime 9122 activated on November 4.