AlertSourceDiscuss
Skip to content

EIP-7949: Genesis File Format

Schema for `genesis.json` files

⚠️ DraftInformational

Draft Notice

This EIP is in the process of being drafted. The content of this EIP is not final and can change at any time; this EIP is not yet suitable for use in production. Thank you!

AuthorsJustin Florentine, Jochem Brouwer (@jochem-brouwer)
Created2025-05-19

Abstract

This EIP defines a canonical structure for Ethereum genesis files (genesis.json) used to bootstrap Ethereum networks. The standard aligns with the de facto structure implemented by Geth (Go-Ethereum), and already adopted by other clients. It introduces a JSON Schema to ensure consistency and tool compatibility across clients.

Motivation

The lack of an official standard for the genesis.json file has led to incompatibilities, bugs and confusion, as well as added workload for those running multiple clients together in test networks. This EIP aims to reduce ambiguity by defining a consistent structure and enabling tooling through schema-based validation.

Specification

The canonical genesis file MUST be a JSON object with the following top-level fields:

Top-Level Fields

FieldDescription
configChain configuration object.
allocMap of addresses to pre-allocated balances and/or code/storage.
nonceDecimal or Hex nonce.
timestampDecimal or Hex UNIX timestamp.
extraDataArbitrary extra data.
gasLimitDecimal or Hex block gas limit.
difficultyDecimal or Hex block difficulty.
mixhashHex mix hash.
coinbaseHex address.

config Object

The config object contains hardfork activation block numbers and fork configurations. Known keys include:

FieldDescription
chainIdunique identifier for the blockchain.
<hardfork(Block|Time)>block height or timestamp to activate the named hardfork.
terminalTotalDifficultydifficulty after which to switch from PoW to PoS.
depositContractAddressEthereum address for the deposit contract
blobScheduleMap of hardforks and their EIP-4844 DAS configuration parameters.

blobSchedule Object

FieldDescription
targetdesired number of blobs to include per block
maxmaximum number of blobs to include per block
baseFeeUpdateFractioninput to pricing formula per EIP-4844

alloc Object

The alloc field defines the initial state at genesis. It maps addresses (as lowercase hex strings) to the following object:

FieldDescription
balancedecimal balance in wei.
codeHex-encoded EVM bytecode.
nonceDecimal or Hex value.
storageKey-value hex map representing initial storage.

JSON Schema

json

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$defs": {
    "hexOrDecimal48": {
      "type": "string",
      "pattern": "^((0x[0-9a-f]{1,12})|[0-9]{1,15})$"
    },
    "hexOrDecimal": {
      "type": "string",
      "pattern": "^((0x[0-9a-f]+)|[0-9]+)$"
    },
    "address": {
      "type": "string",
      "pattern": "^0x[0-9a-fA-F]{40}$"
    },
    "hash": {
      "type": "string",
      "pattern": "^0x[0-9a-f]{64}$"
    }
  },
  "title": "Ethereum Genesis File",
  "type": "object",
  "required": ["alloc", "gasLimit", "difficulty"],
  "properties": {
    "config": {
      "type": "object",
      "properties": {
        "chainId": { "type": "integer" },
        "homesteadBlock": { "type": "integer" },
        "daoForkBlock": { "type": "integer" },
        "eip150Block": { "type": "integer" },
        "tangerineWhistleBlock": {"type": "integer"},
        "eip155Block": { "type": "integer" },
        "spuriousDragonBlock": {"type": "integer"},
        "byzantiumBlock": { "type": "integer" },
        "constantinopleBlock": { "type": "integer" },
        "petersburgBlock": { "type": "integer" },
        "istanbulBlock": { "type": "integer" },
        "muirGlacierBlock": {"type": "integer"},
        "berlinBlock": { "type": "integer" },
        "londonBlock": { "type": "integer" },
        "arrowGlacierBlock": { "type": "integer" },
        "grayGlacierBlock": { "type": "integer" },
        "terminalTotalDifficulty": { "type": "integer" },
        "mergeNetsplitBlock": { "type": "integer"},
        "shanghaiTime": { "type": "integer"},
        "cancunTime": { "type": "integer"},
        "pragueTime": { "type": "integer"},
        "osakaTime": { "type": "integer"},
        "depositContractAddress": { "$ref": "#/$defs/address"},
        "blobSchedule": {
          "type": "object",
          "additionalProperties": {
            "type": "object",
            "properties": {
              "target": { "type": "integer" },
              "max": { "type": "integer" },
              "baseFeeUpdateFraction": { "type" : "integer" }
            }
          }
        }
      },
      "additionalProperties": true
    },
    "nonce": { "$ref": "#/$defs/hexOrDecimal48" },
    "timestamp": { "$ref": "#/$defs/hexOrDecimal48" },
    "extraData": {
      "anyOf": [
        {"type": "string", "const": "" },
        {"type": "string", "pattern": "^0x([0-9a-fA-F]{2})*$" }
      ]
    },
    "gasLimit": { "$ref": "#/$defs/hexOrDecimal48" },
    "difficulty": { "$ref": "#/$defs/hexOrDecimal48" },
    "mixhash": { "$ref": "#/$defs/hash" },
    "coinbase": { "$ref": "#/$defs/address" },
    "alloc": {
      "type": "object",
      "patternProperties": {
        "^(0x)?[0-9a-fA-F]{40}$": {
          "type": "object",
          "properties": {
            "balance": { "$ref": "#/$defs/hexOrDecimal" },
            "nonce": { "$ref": "#/$defs/hexOrDecimal48" },
            "code": { "type": "string", "pattern": "^0x([0-9a-f])*$" },
            "storage": {
              "type": "object",
              "patternProperties": {
                "^0x[0-9a-f]{64}$": {
                  "$ref": "#/$defs/hash"
                }
              }
            }
          }
        },
        "additionalProperties": false
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": true
}

Rationale

There are a growing number of EIPs that propose improvements to how a network is configured at genesis:

Add Blob Schedule to EL Config File

Blob Parameter Only Hardforks

eth_config JSON-RPC method

However, the root configuration element amended by these remains unspecified. Adopting a minimal schema to define that will make subsequent changes more accurate and concise.

Security Considerations

Since this is an optional and informational EIP, which offers only developer convenience, and must be used with admin access to the node, no new security concerns are introduced.

Copyright and related rights waived via CC0.

Citation

Please cite this document as:

Justin Florentine, Jochem Brouwer (@jochem-brouwer), "EIP-7949: Genesis File Format[DRAFT]," Ethereum Improvement Proposals, no. 7949, 2025/5/19. [Online serial]. Available: https://eips.ethereum.org/EIPS/eip-7949.