Matic Network white paper

The five-minute read

One action, walked through

1. A user locks an asset on Ethereum in the root contract.
2. The sidechain credits the user and processes transactions under its proof-of-stake producers.
3. Producers publish a checkpoint of the resulting state to the root contract.
4. A withdrawal asks Ethereum to honour the checkpoint after the challenge window, or sooner if a later variant says so.
5. A challenger who shows the checkpoint does not follow the sidechain's rules can get it rolled back and the producer slashed, under the paper's dispute rules.

The argument, unpacked

What has to be true

• At least one watcher will challenge a bad checkpoint before the window ends.
• Ethereum will include that challenge. Prolonged censorship on the root is a sidechain failure mode.
• The state committed is the state users can download. Withheld data recreates the Plasma problem.
• Producer stake is large relative to the value a false checkpoint could extract.

What happened after the paper

Matic became Polygon. The proof-of-stake chain and its Ethereum checkpoints shipped, and the company later pursued zk rollups and other stacks. Withdrawal delays and the role of Ethereum in the original paper remain the right questions, even when a newer stack answers them with a validity proof instead of a challenge window.

What to check before you use the idea

• How often is a checkpoint posted, and how long is the challenge window?
• Who can challenge, and what do they need to store?
• Is a sidechain balance being described as final on Ethereum before the window?
• Is the system being cited the 2019 checkpoint chain or a later zk design?

Terms

Checkpoint

A hash of sidechain state posted to Ethereum, which withdrawals and disputes refer to.

Challenge window

The period during which a bad checkpoint can be proven false on the root chain.

Sidechain

A chain with its own producers, whose link to Ethereum is the checkpoint rather than re-execution.

Root contract

The Ethereum contract that holds deposits and judges checkpoints.

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.