Polkadot: Vision for a heterogeneous multi-chain framework

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.