Blueprint contract format

The five-minute read

One action, walked through

1. Open ERC 5202 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: Define a standard for "blueprint" contracts, or contracts which represent initcode that is stored on-chain.
3. Name the object that changes: EXTCODECOPY, CREATE, CREATE2.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing ERC 5202 at the status the text itself states: Final.
• The object that has to change is EXTCODECOPY, CREATE, CREATE2. A neighbouring document with a similar name is not this one.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

What happened after the paper

The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does Blueprint contract format charge, reject, or redefine on the first touch versus a later one?
• Does a reverted subcall roll the change back?
• Can you point at the object in a client: EXTCODECOPY, CREATE, CREATE2?

Terms

ERC 5202

The public text titled Blueprint contract format.

Final

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

What the design proposes

• Define a standard for "blueprint" contracts, or contracts which represent initcode that is stored on-chain.
• To decrease deployer contract size, a useful pattern is to store initcode on chain as a "blueprint" contract, and then use EXTCODECOPY to copy the initcode into memory, followed by a call to CREATE or CREATE2.
• However, this comes with the following problems: - It is hard for external tools and indexers to detect if a contract is a "regular" runtime contract or a "blueprint" contract.

How the mechanism is specified

• Taken from the specification, the next constraint is: To decrease deployer contract size, a useful pattern is to store initcode on chain as a "blueprint" contract, and then use EXTCODECOPY to copy the initcode into memory, followed by a call to CREATE or CREATE2.
• Locate EXTCODECOPY, CREATE, CREATE2 in ERC 5202 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.
• The source marks this final. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use ERC 5202 when a pitch says 'Blueprint contract format' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.