Add EIP: Ethereum Network Configuration for DApps

[bogdan]

Moved to ERC

ethereum/ERCs#1003

History

This standard defines a universal format for specifying network configurations in decentralized applications (dApps). The configuration includes essential information about Ethereum networks, such as:

• available RPC URLs
• native currencies
• contract addresses
• block explorers.

The goal of this standard is to simplify network configuration for dApp developers and enhance interoperability across Ethereum-compatible networks.

{
  "version": "0.0.1",
  "timestamp": "2025-01-01T12:22:46.471Z",
  "summary": "NFT Artwork",
  "description": "Artwork published by independent artist. Carefully crafted with style in one of the creative studios of the world."
  "abiRoot": "https://nft-artwork.example.com/developer/abi"
  "networks": {
    "1": {
      "name": "Ethereum Mainnet",
      "testnet": false,
      "nativeCurrency": {
        "name": "Ether",
        "symbol": "ETH",
        "decimals": 18
      },
      "rpcs": {
        "main": {
          "url": "https://eth-rpc.example.com"
        },
        "backup": {
          "url": "https://eth-rpc.backup.example.com"
        }
      },
      "relations": {
        "mainnetChainId": null,
        "parentChainId": null
      },
      "explorers": {
        "megascan": {
          "root": "https://example.org",
          "block": "/block/:number",
          "address": "/address/:address",
          "tx": "/tx/:tx",
          "nft": "/nft/:address/:token"
        },
        "marketplace": {
          "root": "https://nft.marketplace/networks/eth",
          "block": null,
          "address": "/:address",
          "tx": null,
          "nft": "/:address/:token"
        }
      },
      "contracts": {
        "Registry": {
          "address": "0x57928ff7b0BBc3Ee4D84481e320DdB8B941f986A",
          "blockCreated": 1234567,
          "abiUrl": "./Registry.sol/Registry.json"
        },
        "OwnerWallet": {
          "address": "0xC12237E57B088e9191BD8054Df4f5B772646a4B6",
          "blockCreated": 1
        }
      }
    },
    "11155111": {
      "name": "Sepolia",
      "testnet": true,
      "nativeCurrency": {
        "name": "Sepolia Ether",
        "symbol": "ETH",
        "decimals": 18
      },
      "rpcs": {
        "main": {
          "url": "https://sepolia-rpc.example.com"
        },
        "backup": {
          "url": "https://sepolia-rpc.backup.example.com"
        }
      },
      "relations": {
        "mainnetChainId": 1,
        "parentChainId": null
      },
      "explorers": {
        "megascan": {
          "root": "https://sepolia.example.org",
          "block": "/block/:number",
          "address": "/address/:address",
          "tx": "/tx/:tx",
          "nft": "/nft/:address/:token"
        },
        "marketplace": {
          "root": "https://testnets.nft.marketplace/networks/sepolia",
          "block": null,
          "address": "/:address",
          "tx": null,
          "nft": "/:address/:token"
        }
      },
      "contracts": {
        "Registry": {
          "address": "0xE13471e6E5d11205AF290261f42108f89dCae72E",
          "blockCreated": 183882,
          "abiUrl": "./Registry.sol/Registry.json" 
        },
        "OwnerWallet": {
          "address": "0xC12237E57B088e9191BD8054Df4f5B772646a4B6",
          "blockCreated": 1
        }
      }
    }
  }
}

[eth-bot]

File EIPS/eip-7876.md

Requires 1 more reviewers from @g11tech, @lightclient, @SamWilsn, @xinbenlv

[g11tech]

do you think this is better specified/provided in ERC? because this seems not be linked to ethereum protocol and client development which is what EIPs are for.

[bogdan]

do you think this is better specified/provided in ERC?

Based on reading a few articles, its falls right in between ERC and EIP as per definition.
The vast majority of ERCs have solidity interface included. That is the only thing that makes this standard look not like ERC.

However, there are a few ERCs around JSON schema definition and interoperability.
Ex: https://github.com/ethereum/ERCs/blob/master/ERCS/erc-2678.md

So I think it makes sense, but I would prefer someone from regular maintainers to make final decision on that.

[g11tech]

only

so EIPs are what L1 clients implement, i.e. EL clients and CL clients, I don't see why they would need to implement this and not have someone/anyone add a contract that provides/serves this data to the Dapps, which is why this might be an ERC

[bogdan]

Move to ERC: ethereum/ERCs#1003