Matic Network white paper

The problem the paper names

Ethereum applications wanted cheaper state changes without abandoning Ethereum as the place value ultimately settles. Matic's paper proposes a sidechain of producers, a checkpoint on Ethereum, and exits in the Plasma tradition.

What the design proposes

• Block producers on the sidechain, with staking and a checkpoint commitment upward.
• A dual set of roles in the paper: producers of blocks, and a checkpointing or validator layer.
• Assets move by deposit on Ethereum and a corresponding credit on the sidechain, with a withdrawal path back.

How the mechanism is specified

• Checkpoints are how Ethereum learns a hash of sidechain state. They are not a re-execution of every sidechain transaction.
• The exit path is the user's remedy against a bad producer, and it only works if it exists in the contracts, not only in the paper.
• Later Polygon proofs, zk systems and a CDK are other documents.

What this page does not treat as proven

• Do not describe today's Polygon PoS chain as 'the Matic white paper, implemented verbatim'.
• A checkpoint of a hash is not a validity proof. The paper's security story has to be read for what it actually checks.
• We do not review later bridge incidents on this page.

Why a venture studio still reads it

Useful as the document a team is often actually copying when they say 'sidechain plus checkpoints', even if they name a newer brand. Ask what the checkpoint attests to, and what a user does when the sidechain censors them.