Tezos — a self-amending crypto-ledger

The problem the paper names

Forks that change the rules are political events coordinated off to the side. Tezos argues that the procedure for adopting a protocol change should itself be a protocol, so the ledger has a stated way to replace its own code.

What the design proposes

• A shell distinguishes the consensus-relevant protocol from the governance process that can swap it.
• Baking is the block production role. Delegation lets a holder assign rights without transferring ownership.
• Formal specification is part of the pitch: amendments should be arguments about a mathematical object, not only about a client repository.

How the mechanism is specified

• Stakeholders vote through a series of periods. The paper's process and the live governance process should not be assumed identical.
• Security deposits and penalties are how the design makes baking expensive to abuse.
• Self-amendment does not mean every social dispute fits in a vote. It means the rule-change path is explicit.

What this page does not treat as proven

• The 2014 paper is not the current Tezos protocol hash.
• Delegation creates representatives. The paper does not prove that representatives stay aligned with holders.
• Formal methods reduce a class of bugs. They do not replace key management or an honest specification.

Why a venture studio still reads it

A venture that expects to change settlement rules after launch should show the amendment path before the first version, not after the first argument. That is the part worth taking from Tezos.