Skip to content
Blockchain LabBlockchain LabTHE VENTURE STUDIO

LibraryScaling2025Design paperCorpus record

Deterministic Factory Contract

EIP 7997. Francisco Giordano , Toni Wahrstätter , Nick Johnson , Jochem Brouwer.

EIP 7997, Deterministic Factory Contract. 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.

Status in the source: Review. A reading of the public specification, not a copy of it and not a certification.

Deterministic Factory Contract is worth reading for the rule it actually adds: 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.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
7

Code

Source, repository, and what is actually hosted

  • EIP 7997https://eips.ethereum.org/EIPS/eip-7997
  • The source URL is not a GitHub repository. No code remote is invented.
  • Full text is not mirrored. Public availability is not a licence to copy the file onto this site.
  • Add to a reading list

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The rule

    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.

  2. Claim 02 · Paper model

    What was already failing

    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.

  3. Claim 03 · Paper model

    What the number does not mean

    The source marks this review. It is not a live consensus rule just because it has a number.

  4. Claim 04 · Paper model

    What a builder should be able to point at

    An implementation either constrains CREATE2, EVM or it is a different design.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The rule

    Observation

    What the study says

    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.

    Model

    What has to hold

    The object that has to change is CREATE2, EVM. A neighbouring document with a similar name is not this one.

    Falsifier

    What would retire it

    What does Deterministic Factory Contract charge, reject, or redefine on the first touch versus a later one?

  2. 02 What was already failing

    Observation

    What the study says

    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.

    Model

    What has to hold

    The object that has to change is CREATE2, EVM. A neighbouring document with a similar name is not this one.

    Falsifier

    What would retire it

    Can you point at the object in a client: CREATE2, EVM?

  3. 03 What the number does not mean

    Observation

    What the study says

    The source marks this review. It is not a live consensus rule just because it has a number.

    Model

    What has to hold

    You are implementing EIP 7997 at the status the text itself states: Review.

    Falsifier

    What would retire it

    Can you point at the object in a client: CREATE2, EVM?

  4. 04 What a builder should be able to point at

    Observation

    What the study says

    An implementation either constrains CREATE2, EVM or it is a different design.

    Model

    What has to hold

    The object that has to change is CREATE2, EVM. A neighbouring document with a similar name is not this one.

    Falsifier

    What would retire it

    Can you point at the object in a client: CREATE2, EVM?

03 Sequence

One action, as an operating tape

  1. 01Open EIP 7997 and read the status line before the examples.
  2. 02Write 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. 03Name the object that changes: CREATE2, EVM.
  4. 04Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the text is allowed to settle

    The cut

    Ethereum Improvement Proposal 7997 can settle the shape of Deterministic Factory Contract. It cannot settle whether a later client, a later fork, or a later wallet still does this.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

  2. What this page will not pretend

    The cut

    There is no benchmark, no adoption number, and no claim that the mechanism is safe outside the assumptions written in the source.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    The source marks this review. It is not a live consensus rule just because it has a number.

05 Register

What has to be true

  • Model · Not re-measured

    You are implementing EIP 7997 at the status the text itself states: Review.

  • Model · Not re-measured

    The object that has to change is CREATE2, EVM. A neighbouring document with a similar name is not this one.

  • Model · Not re-measured

    Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

06 Divergence

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.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it 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 the desk 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.

09 Lexicon

Terms, opened into the record

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.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.