Deterministic Factory Contract

The five-minute read

One action, walked through

1. Open EIP 7997 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: The availability of a well-known CREATE2 factory at 0x4e59b44847b379578588920cA78FbF26c0B4956C is made a formal requirement to enable deterministic deployments at identical addresses across EVM chains.
3. Name the object that changes: CREATE2, EVM.
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 EIP 7997 at the status the text itself states: Review.
• The object that has to change is CREATE2, EVM. 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 review. It is not a live consensus rule just because it has a number. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does Deterministic Factory Contract 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: CREATE2, EVM?

Terms

EIP 7997

The public text titled Deterministic Factory Contract.

Review

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

• The availability of a well-known CREATE2 factory at 0x4e59b44847b379578588920cA78FbF26c0B4956C is made a formal requirement to enable deterministic deployments at identical addresses across EVM chains.
• This benefits developer experience, user experience, and security, in particular for multi-chain and cross-chain applications, including account abstraction.
• There are now a large number of EVM chains where users want to transact and developers want to deploy applications, and we can expect this number to continue to grow in line with Ethereum's rollup-centric roadmap and the general adoption of programmable blockchains.

How the mechanism is specified

• Taken from the specification, the next constraint is: This benefits developer experience, user experience, and security, in particular for multi-chain and cross-chain applications, including account abstraction.
• Locate CREATE2, EVM in EIP 7997 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 review. It is not a live consensus rule just because it has a number.

Why a venture studio still reads it

Use EIP 7997 when a pitch says 'Deterministic Factory Contract' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.