LibraryInteroperability2016Design paperCorpus record
Polkadot: Vision for a heterogeneous multi-chain framework
Polkadot. Gavin Wood.
Wood's 2016 vision paper: a relay chain that provides shared security and a queue of cross-chain messages, with parachains that keep their own state transition. It is a vision paper. The live protocol has a specification of its own.
Polkadot's vision paper asks for many specialised chains that share a security layer, so a new chain need not recruit its own miners before it can be taken seriously.
The five-minute read
A relay, and parachains under it
The relay chain coordinates. Parachains do the application work and hand the relay a proof that their block was valid.
Shared security is the product
Validators assigned by the relay check parachain blocks. A parachain inherits that validator set instead of inventing a token only to pay miners.
Slots are scarce on purpose
In the vision, not every chain is a parachain. A slot is allocated, later by auction in the live design. The paper's heterogeneity includes the fact that some chains are outside.
Messages cross by the relay's rules
A parachain does not whisper to another. It posts a message the relay's routing can take. Cross-chain is a protocol, not a bridge someone bolted on.
The 2016 text is a vision
Nominated proof of stake, crowdloans and XCM are later specifications. Cite them as later. Cite this paper as the heterogeneous multi-chain argument.
One action, walked through
- A parachain collects transactions and produces a candidate block plus a proof of validity.
- Relay validators assigned to that parachain check the proof and include the header on the relay.
- Once the relay finalises that header, the parachain block is as final as the relay.
- An outbound message sits in the parachain's egress. The relay makes it available to the destination parachain.
- The destination applies the message under its own logic, citing the relay's commitment as the reason to trust the source.
The argument, unpacked
Shared security cuts both ways
A parachain that misbehaves is contained if the relay validators do their job. A relay failure is a failure of every parachain at once. The design concentrates risk on purpose so that small chains do not each carry their own weak security. That concentration should be said plainly.
A slot is a political object
If only some chains receive the relay's validators, allocation is governance. Auctions, leases and common-good slots came later to make that allocation explicit. A vision that says 'any chain' without a slot rule is unfinished.
Heterogeneous means the relay must not know every app
The relay checks a proof and routes bytes. It does not understand a parachain's internal accounting. That is how specialised chains stay specialised. It is also why a bug inside a parachain's proof logic can be finalised by honest validators who checked the wrong predicate.
What has to be true
- Relay validators can be assigned randomly enough that a parachain cannot pick its checkers.
- Validity proofs are cheap to check and hard to fake.
- The relay itself has a finality gadget and an honest majority under its staking rules.
- Message queues do not grow without bound. Routing that cannot keep up is a lost cross-chain promise.
What happened after the paper
Polkadot launched with a relay chain, parachain slots, and a cross-consensus messaging format that post-dates the vision paper. The shared-security thesis is still the sentence to test: does this parachain stand on the relay's validators, or has it become its own chain with a bridge?
What to check before you use the idea
- Who validates this chain's blocks, the relay set or a separate set?
- How does a chain obtain a slot, and when does the slot expire?
- What is final: the parachain block, or the relay block that cites it?
- Can the relay's validators read the application's rules, or only a proof?
Terms
- Relay chain
- The coordinating chain that finalises parachain headers and routes messages.
- Parachain
- An application chain whose blocks are checked by relay validators.
- Shared security
- The arrangement in which a small chain borrows the relay's validator set instead of recruiting its own.
- Slot
- The right to be one of the parachains the relay currently secures.
The problem the paper names
A family of chains that each hire their own validators do not share security, and they move messages by trusted bridges. Polkadot's paper proposes one relay set that checks many parachain candidates and orders the messages between them.
What the design proposes
- Parachains are heterogeneous. The relay chain does not require them to share a virtual machine.
- Collators produce parachain blocks. Validators assigned by the relay chain attest to them.
- A message-passing queue is a relay-chain object, so delivery is something the shared security layer can reason about.
How the mechanism is specified
- Shared security is the claim that a parachain does not recruit a separate economic set.
- The relay chain's own consensus and governance are sketched. Nominated proof of stake and the later runtime are developments beyond the 2016 text.
- Slots, auctions and coretime are later allocation mechanisms. Do not read them back into the vision paper as if they were specified there.
What this page does not treat as proven
- A vision paper is not the Polkadot host specification.
- Shared security is only as strong as the relay-chain validator set and the availability of parachain data.
- Heterogeneous does not mean arbitrary. A parachain still has to produce a proof the relay chain accepts.
Why a venture studio still reads it
The sentence we keep is: interoperability is a security problem, not a bridge widget. If each domain hires its own validators, you have a partnership, not this design.
This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.
Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.