Diamonds, Multi-Facet Proxy

The five-minute read

One action, walked through

1. Open ERC 2535 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: This proposal standardizes diamonds, which are modular smart contract systems that can be upgraded/extended after deployment, and have virtually no size limit.
3. Name the object that changes: Diamonds, Multi-Facet Proxy.
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 2535 at the status the text itself states: Final.
• The object that has to change is Diamonds, Multi-Facet Proxy. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

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 must an implementation of Diamonds, Multi-Facet Proxy accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: Diamonds, Multi-Facet Proxy?

Terms

ERC 2535

The public text titled Diamonds, Multi-Facet Proxy.

Final

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

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• This proposal standardizes diamonds, which are modular smart contract systems that can be upgraded/extended after deployment, and have virtually no size limit.
• More technically, a diamond is a contract with external functions that are supplied by contracts called facets.
• Facets are separate, independent contracts that can share internal functions, libraries, and state variables.

How the mechanism is specified

• Taken from the specification, the next constraint is: More technically, a diamond is a contract with external functions that are supplied by contracts called facets.
• Locate Diamonds, Multi-Facet Proxy in ERC 2535 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

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• 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 2535 when a pitch says 'Diamonds, Multi-Facet Proxy' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.