{"id":13633523,"url":"https://github.com/testinprod-io/op-erigon","last_synced_at":"2025-04-18T14:33:08.837Z","repository":{"id":79795990,"uuid":"598013738","full_name":"testinprod-io/op-erigon","owner":"testinprod-io","description":"Optimism implementation on the efficiency frontier","archived":false,"fork":true,"pushed_at":"2024-11-05T17:22:06.000Z","size":332883,"stargazers_count":87,"open_issues_count":12,"forks_count":15,"subscribers_count":3,"default_branch":"op-erigon","last_synced_at":"2024-11-05T18:30:33.464Z","etag":null,"topics":["blockchain","erigon","ethereum","go","optimism"],"latest_commit_sha":null,"homepage":"https://op-erigon.testinprod.io","language":"Go","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"protolambda/erigon","license":"lgpl-3.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/testinprod-io.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":".github/CONTRIBUTING.md","funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2023-02-06T07:58:37.000Z","updated_at":"2024-11-05T17:22:14.000Z","dependencies_parsed_at":"2023-09-27T12:25:37.472Z","dependency_job_id":"2511402d-cc5b-45c3-ab22-a5ad02c83aa9","html_url":"https://github.com/testinprod-io/op-erigon","commit_stats":null,"previous_names":[],"tags_count":260,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/testinprod-io%2Fop-erigon","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/testinprod-io%2Fop-erigon/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/testinprod-io%2Fop-erigon/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/testinprod-io%2Fop-erigon/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/testinprod-io","download_url":"https://codeload.github.com/testinprod-io/op-erigon/tar.gz/refs/heads/op-erigon","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":223782527,"owners_count":17201798,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["blockchain","erigon","ethereum","go","optimism"],"created_at":"2024-08-01T23:00:47.484Z","updated_at":"2025-04-18T14:33:08.828Z","avatar_url":"https://github.com/testinprod-io.png","language":"Go","funding_links":[],"categories":["Clients"],"sub_categories":[],"readme":"# Optimistic Erigon\n[![CI](https://github.com/testinprod-io/op-erigon/actions/workflows/ci.yml/badge.svg)](https://github.com/testinprod-io/op-erigon/actions/workflows/ci.yml) [![Integration tests](https://github.com/testinprod-io/op-erigon/actions/workflows/test-integration.yml/badge.svg)](https://github.com/testinprod-io/op-erigon/actions/workflows/test-integration.yml) [![](https://dcbadge.vercel.app/api/server/42DFTeZwUZ?style=flat\u0026compact=true)](https://discord.gg/42DFTeZwUZ)\n\nA fork of [Erigon](https://github.com/ledgerwatch/erigon) that supports the [execution engine](https://github.com/ethereum-optimism/optimism/blob/develop/specs/exec-engine.md) of [OP stack](https://stack.optimism.io). Check out the fork status here: [https://op-erigon.testinprod.io](https://op-erigon.testinprod.io)\n\n[`testinprod-io/erigon-lib`](https://github.com/testinprod-io/erigon-lib) has minimal backwards-compatible changes to add Optimism engine-api fields on the `op-erigon` branch.\n\n[`testinprod-io/erigon-interfaces`](https://github.com/testinprod-io/erigon-interfaces) defines the protobuf changes for `erigon-lib` on the `op-erigon` branch.\n- [Optimistic Erigon Project Status](#optimistic-erigon-project-status)\n  + [Features that work correctly](#features-that-work-correctly)\n  + [Features that don't work (or yet to be confirmed)](#features-that-dont-work-or-yet-to-be-confirmed)\n- [Getting started with Optimism](#getting-started-with-optimism)\n- [Example: Running An Optimism Mainnet Node](#example-running-an-optimism-mainnet-node)\n- [Need any help?](#need-any-help)\n- [Thanks](#thanks)\n- [Original Erigon README.md](#erigon)\n \n## Optimistic Erigon Project Status\nOptimistic Erigon is still under development. Please note that some features are not fully implemented or tested.\n \n### Features that work correctly\n- Validator mode (Synchronizing to the Optimism Network with op-node)\n- Ethereum standard JSON-RPC API\n- JSON-RPC API for Otterscan\n- All-in-One binary mode\n- P2P transaction gossip\n\n### Features that don't work (or yet to be confirmed)\n- Block producing as a Sequencer\n- Sequencer and proposer mode\n- Running Erigon services as separate processes\n- Erigon Snapshot\n\n### Stability (dogfooding)\n- We've been running an op-erigon public RPC here:\n  - [https://op-erigon.mainnet.testinprod.io](https://op-erigon.mainnet.testinprod.io)\n  - [https://op-erigon.sepolia.testinprod.io](https://op-erigon.sepolia.testinprod.io)\n- Our Otterscan (block explorer) uses our public RPC\n  - [https://otterscan.mainnet.testinprod.io](https://otterscan.mainnet.testinprod.io)\n  - [https://otterscan.sepolia.testinprod.io](https://otterscan.sepolia.testinprod.io)\n\n### Node Snapshots\n\nWe provide node snapshots at https://snapshot.testinprod.io. You can download the node snapshots(chaindata) by using the endpoints provided. Note that the keyword **snapshot** is different with the erigon's snapshot feature. Node snapshot is distributed in the compressed form using zstd compression.\n\n## Getting started with Optimism\nTo build from the code, you can use the same command described below(`make erigon`)\n\nYou can use every flag erigon has. But there are some required flags and newly added flags for Optimism.\n\n### `--datadir`\n**[Required]**\nop-erigon cannot execute state transition before the bedrock update. So if the chain was created before bedrock update, preconfigured data file is required to run the node. It includes blocks and states of the pre-bedrock chain.\n\nYou can download the chain data from following links:\n- Optimism Mainnet:\n  - [https://op-erigon-backup.mainnet.testinprod.io](https://op-erigon-backup.mainnet.testinprod.io)\n  - Compressed: 115 GB, Uncompressed: 380 GB.\n  - Including blocks up to [105235064](https://optimistic.etherscan.io/block/105235064) (June 2023)\n\n### `--externalcl`\n**[Deprecated]**\nAn Optimism node needs a consensus client(op-node) and an execution client. op-erigon is intended to have an external consensus client though Erigon has its own consensus client.\n\nThis option specifies that Erigon will have an external consensus client. This is **required up to version `v2.39.0-0.1.1`**. In subsequent versions, this behavior has been made the default, and **using the flag will result in an error**.\n\n### `--authrpc.addr`, `--authrpc.port`, `--authrpc.jwtsecret`\n**[Required]** \nAuthenticated RPC configs that specify engine API connection info for the consensus client.\n\n### `--rollup.sequencerhttp`\n**[New flag / Optional]** \nHTTP endpoint of the sequencer. op-erigon will route `eth_sendRawTransaction` calls to this URL. This is **required** for transaction submission since Bedrock does not currently have a public mempool. Refer to the documentation for the network you are participating in to get the correct URL.\n\nFor the OP-Mainnet, set the sequencer endpoint: `https://mainnet-sequencer.optimism.io`.\n\nFor the OP-Sepolia Testnet, set the sequencer endpoint: `https://sepolia-sequencer.optimism.io`\n\n### `--rollup.historicalrpc`\n**[New flag / Optional]** \nThe historical RPC endpoint. op-erigon queries historical execution data that op-erigon does not support to historical RPC—for example, pre-bedrock executions. For OP-Sepolia Testnet, please set this value to the Legacy Geth endpoint.\n\nFor more information about legacy geth, refer the [Optimism's node operator guide](https://community.optimism.io/docs/developers/bedrock/node-operator-guide/#legacy-geth).\n\n### `--db.size.limit=8TB`\n**[Required]**\nExisting nodes whose MDBX page size equals 4kb must add --db.size.limit=8TB flag. Otherwise you will get MDBX_TOO_LARGE error. To check the current page size you can use `make db-tools \u0026\u0026 ./build/bin/mdbx_stat datadir/chaindata`.\nIf your chain is the one of `op-mainnet` \u0026 `op-sepolia`, or your chain is synced before version `v2.55`, this flag is **REQUIRED**\n\n\n### `--txpool.gossip.disable`\n**[Optional]** \nDisables transaction pool gossiping. Though this is not required, it's useful to set this to true since transaction pool gossip is currently unsupported in the Optimism protocol. If not provided, default value is set to `false`.\n\n### `--maxpeers=0`, `--nodiscover`, `--v5disc=false`\n**[Optional]** \nDisable P2P. This can save resources if you are only using op-node to sync the chain instead of using execution-layer syncing.  \n\n## Support Chains\nop-erigon supports every OP Stack chains listed in [superchain-registry](https://github.com/ethereum-optimism/superchain-registry).\nYou can config any superchain easily by setting `--chain` flag with the chain name written in the superchain registry, in lowercase. (e.g. `op-mainnet`, `base-sepolia`, etc.)\n### Caution\nIf the chain was created before bedrock update, you need to download **pre-bedrock chain data**. See the following example to sync op-mainnet!\n\n## Example: Running An Optimism Mainnet Node\n### 1. Download and decompress the pre-bedrock chain data\nYou can download the pre-bedrock chain data from [https://op-erigon-backup.mainnet.testinprod.io](https://op-erigon-backup.mainnet.testinprod.io). Compressed: 115 GB, Uncompressed: 380 GB.\n```bash\nwget -c -O \"backup.tar.gz\" https://op-erigon-backup.mainnet.testinprod.io\ntar -zxvf backup.tar.gz\n```\nAfter untaring, you will get a folder named `database` which contains a folder `chaindata` with two files inside: `mdbx.dat` and `mdbx.lck`. Use this directory as a datadir(`$DATADIR`) for erigon. For example,\n```bash\nexport DATA_DIR=`pwd`/database\n```\n\n### 2. Configuring op-erigon\nThere are three options to run op-erigon. Please refer to the preceding descriptions for the required flags.\n1. Build from the source\n```bash\n(build from the source)\n$ make erigon\n\n(example execution command)\n$ ./build/bin/erigon \\\n    --datadir=$DATA_DIR \\\n    --private.api.addr=localhost:9090 \\\n    --http.addr=0.0.0.0 \\\n    --http.port=8545 \\\n    --http.corsdomain=\"*\" \\\n    --http.vhosts=\"*\" \\\n    --authrpc.addr=0.0.0.0 \\\n    --authrpc.port=8551 \\\n    --authrpc.vhosts=\"*\" \\\n    --authrpc.jwtsecret=$JWT_SECRET_FILE \\\n    --rollup.sequencerhttp=\"https://mainnet-sequencer.optimism.io\" \\\n    --rollup.historicalrpc=\"https://mainnet.optimism.io\" \\\n    --txpool.gossip.disable=true \\\n    --chain=op-mainnet \\\n    --db.size.limit=8TB\n```\n2. Use the Docker image: You can get the official Docker image from [testinprod/op-erigon](https://hub.docker.com/r/testinprod/op-erigon).\n3. Use the Helm chart: If you want to deploy op-erigon to the K8S cluster, you can use [Helm chart](https://artifacthub.io/packages/helm/op-charts/erigon).\n\n### 3. Configuring op-node\nop-node is a consensus engine of OP stack. You can also build from the source, use official Docker image(`us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node`), or [Helm chart](https://artifacthub.io/packages/helm/op-charts/op-node).\n\n```bash\n(example execution command)\n$ op-node \\\n    --l1=$L1_RPC_ENDPOINT \\\n    --l2=$OP_ERIGON_ENGINE_API_ENDPOINT \\\n    --l2.jwt-secret=$JWT_SECRET_FILE \\\n    --network=op-mainnet \\\n    --rpc.addr=0.0.0.0 \\\n    --rpc.port=9545 \\\n    --l2.enginekind=erigon\n```\n\n#### Execution Layer Syncing\nBy default, op-node and op-erigon work together to derive every L2 block from the chain. However, this can take a while if the chain is large.\n\nInstead, you can use `execution-layer` syncmode on op-node to download L2 blocks from the peers in the network. \nThis will allow op-erigon to download and execute large number of blocks at once, resulting in a shorter sync time. \n\nRefer to [Optimism's guide for execution layer syncing here](https://docs.optimism.io/builders/node-operators/management/snap-sync#enabling-execution-layer-sync-for-alternative-clients).\n\nTo enable execution layer syncing, set the following flags on op-node\n```bash\n    --syncmode=execution-layer \\ \n    --l2.enginekind=erigon\n```\n\nFor more information for op-node, refer the [Optimism's node operator guide](https://community.optimism.io/docs/developers/bedrock/node-operator-guide/#configuring-op-node).\n\n## Need any help?\n[![](https://dcbadge.vercel.app/api/server/42DFTeZwUZ?style=flat\u0026compact=true)](https://discord.gg/42DFTeZwUZ) If you need help or find a bug, please share it with our discord!\n\n## Thanks\n- Erigon team for building this amazing, super fast, and cutting-edge efficient client.\n- Willian for building an awesome open-sourced block explorer, Otterscan.\n- Optimism Collective and OP Labs for the huge support and for building this amazing technology stack.\n- Kelvin, Proto, and Lindsay for guiding and helping us a lot. Also, forkdiff is amazing.\n- and Ethereum ❤️\n\n_Let's stay Optimistic_ 🔴\n\n---\n\n\u003c!-- Original Erigon README starts. --\u003e\n\n# Erigon\n\nErigon is an implementation of Ethereum (execution layer with embeddable consensus layer), on the efficiency\nfrontier. [Archive Node](https://ethereum.org/en/developers/docs/nodes-and-clients/archive-nodes/#what-is-an-archive-node)\nby default.\n\nAn accessible and complete version of the documentation is available at **[erigon.gitbook.io](https://erigon.gitbook.io)**.\n\u003cbr\u003e\n\n![Build status](https://github.com/erigontech/erigon/actions/workflows/ci.yml/badge.svg) [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=erigontech/_erigon\u0026metric=coverage)](https://sonarcloud.io/summary/new_code?id=erigontech/_erigon)\n\n\u003c!--ts--\u003e\n\n- [System Requirements](#system-requirements)\n- [Usage](#usage)\n\n  - [Getting Started](#getting-started)\n  - [Logging](#logging)\n  - [Testnets](#testnets)\n  - [Block Production](#block-production-pow-miner-or-pos-validator)\n  - [Windows](#windows)\n  - [GoDoc](https://godoc.org/github.com/erigontech/erigon)\n  - [Beacon Chain](#beacon-chain-consensus-layer)\n  - [Dev Chain](#dev-chain)\n  - [Caplin (Internal Consensus Layer)](#caplin)\n\n- [Key features](#key-features)\n  - [More Efficient State Storage](#more-efficient-state-storage)\n  - [Faster Initial Sync](#faster-initial-sync)\n  - [JSON-RPC daemon](#json-rpc-daemon)\n  - [Run all components by docker-compose](#run-all-components-by-docker-compose)\n  - [Grafana dashboard](#grafana-dashboard)\n  - [Internal Consensus Layer](#caplin)\n- [Documentation](#documentation)\n- [FAQ](#faq)\n- [Getting in touch](#getting-in-touch)\n  - [Erigon Discord Server](#erigon-discord-server)\n  - [Reporting security issues/concerns](#reporting-security-issues/concerns)\n  - [Team](#team)\n- [Known issues](#known-issues)\n  - [`htop` shows incorrect memory usage](#htop-shows-incorrect-memory-usage)\n\n\u003c!--te--\u003e\n\n**Disclaimer**: this software is currently a tech preview. We will do our best to keep it stable and make no breaking\nchanges but we don't guarantee anything. Things can and will break.\n\n**Important defaults**: Erigon is an Archive Node by default (to remove history see: `--prune` flags\nin `erigon --help`). We don't allow change this flag after first start.\n\n\u003ccode\u003eIn-depth links are marked by the microscope sign (🔬) \u003c/code\u003e\n\n# System Requirements\n\n- For an Archive node of Ethereum Mainnet we recommend \u003e=3.5TB storage space: 2.3TiB state (as of March 2024),\n  643GiB snapshots (can symlink or mount folder `\u003cdatadir\u003e/snapshots` to another disk), 200GB temp files (can symlink or mount folder `\u003cdatadir\u003e/temp` to another disk). Ethereum Mainnet Full node (\n  see `--prune*` flags): 1.1TiB (March 2024).\n\n- Goerli Full node (see `--prune*` flags): 189GB on Beta, 114GB on Alpha (April 2022).\n\n- Gnosis Chain Archive: 1.7TiB (March 2024). Gnosis Chain Full node (`--prune=hrtc` flag): 530GiB (March 2024).\n\n- Polygon Mainnet Archive: 8.5TiB (December 2023). `--prune.*.older 15768000`: 5.1Tb (September 2023). Polygon Mumbai Archive:\n  1TB. (April 2022).\n\nSSD or NVMe. Do not recommend HDD - on HDD Erigon will always stay N blocks behind chain tip, but not fall behind.\nBear in mind that SSD performance deteriorates when close to capacity.\n\nRAM: \u003e=16GB, 64-bit architecture.\n\n[Golang version \u003e= 1.21](https://golang.org/doc/install); GCC 10+ or Clang; On Linux: kernel \u003e v4\n\n\u003ccode\u003e🔬 more details on disk storage [here](https://erigon.substack.com/p/disk-footprint-changes-in-new-erigon?s=r)\nand [here](https://erigontech/.github.io/turbo_geth_release.html#Disk-space).\u003c/code\u003e\n\n# Usage\n\n### Getting Started\n\nFor building the latest release (this will be suitable for most users just wanting to run a node):\n\n```sh\ngit clone --branch release/\u003cx.xx\u003e --single-branch https://github.com/erigontech/erigon.git\ncd erigon\nmake erigon\n./build/bin/erigon\n```\n\nYou can check [the list of releases](https://github.com/erigontech/erigon/releases) for release notes.\n\nFor building the bleeding edge development branch:\n\n```sh\ngit clone --recurse-submodules https://github.com/erigontech/erigon.git\ncd erigon\ngit checkout devel\nmake erigon\n./build/bin/erigon\n```\n\nDefault `--snapshots` for `mainnet`, `goerli`, `gnosis`, `chiado`. Other networks now have default `--snapshots=false`.\nIncrease\ndownload speed by flag `--torrent.download.rate=20mb`. \u003ccode\u003e🔬 See [Downloader docs](./cmd/downloader/readme.md)\u003c/code\u003e\n\nUse `--datadir` to choose where to store data.\n\nUse `--chain=gnosis` for [Gnosis Chain](https://www.gnosis.io/), `--chain=bor-mainnet` for Polygon Mainnet,\n`--chain=mumbai` for Polygon Mumbai and `--chain=amoy` for Polygon Amoy.\nFor Gnosis Chain you need a [Consensus Layer](#beacon-chain-consensus-layer) client alongside\nErigon (https://docs.gnosischain.com/node/manual/beacon).\n\nRunning `make help` will list and describe the convenience commands available in the [Makefile](./Makefile).\n\n### Datadir structure\n\n- chaindata: recent blocks, state, recent state history. low-latency disk recommended.\n- snapshots: old blocks, old state history. can symlink/mount it to cheaper disk. mostly immutable. must have ~100gb\n  free space (for merge recent files to bigger one).\n- temp: can grow to ~100gb, but usually empty. can symlink/mount it to cheaper disk.\n- txpool: pending transactions. safe to remove.\n- nodes: p2p peers. safe to remove.\n\n### Logging\n\n_Flags:_\n\n- `verbosity`\n- `log.console.verbosity` (overriding alias for `verbosity`)\n- `log.json`\n- `log.console.json` (alias for `log.json`)\n- `log.dir.path`\n- `log.dir.prefix`\n- `log.dir.verbosity`\n- `log.dir.json`\n\nIn order to log only to the stdout/stderr the `--verbosity` (or `log.console.verbosity`) flag can be used to supply an\nint value specifying the highest output log level:\n\n```\n  LvlCrit = 0\n  LvlError = 1\n  LvlWarn = 2\n  LvlInfo = 3\n  LvlDebug = 4\n  LvlTrace = 5\n```\n\nTo set an output dir for logs to be collected on disk, please set `--log.dir.path` If you want to change the filename\nproduced from `erigon` you should also set the `--log.dir.prefix` flag to an alternate name. The\nflag `--log.dir.verbosity` is\nalso available to control the verbosity of this logging, with the same int value as above, or the string value e.g. '\ndebug' or 'info'. Default verbosity is 'debug' (4), for disk logging.\n\nLog format can be set to json by the use of the boolean flags `log.json` or `log.console.json`, or for the disk\noutput `--log.dir.json`.\n\n### Modularity\n\nErigon by default is \"all in one binary\" solution, but it's possible start TxPool as separated processes.\nSame true about: JSON RPC layer (RPCDaemon), p2p layer (Sentry), history download layer (Downloader), consensus.\nDon't start services as separated processes unless you have clear reason for it: resource limiting, scale, replace by\nyour own implementation, security.\nHow to start Erigon's services as separated processes, see in [docker-compose.yml](./docker-compose.yml).\n\n### Embedded Consensus Layer\n\nOn Ethereum Mainnet, Görli, and Sepolia, the Engine API can be disabled in favour of the Erigon native Embedded\nConsensus Layer.\nIf you want to use the internal Consensus Layer, run Erigon with flag `--internalcl`.\n_Warning:_ Staking (block production) is not possible with the embedded CL.\n\n### Testnets\n\nIf you would like to give Erigon a try, but do not have spare 2TB on your drive, a good option is to start syncing one\nof the public testnets, Görli. It syncs much quicker, and does not take so much disk space:\n\n```sh\ngit clone --recurse-submodules -j8 https://github.com/erigontech/erigon.git\ncd erigon\nmake erigon\n./build/bin/erigon --datadir=\u003cyour_datadir\u003e --chain=goerli\n```\n\nPlease note the `--datadir` option that allows you to store Erigon files in a non-default location, in this example,\nin `goerli` subdirectory of the current directory. Name of the directory `--datadir` does not have to match the name of\nthe chain in `--chain`.\n\n### Block Production (PoW Miner or PoS Validator)\n\n**Disclaimer: Not supported/tested for Gnosis Chain and Polygon Network (In Progress)**\n\nSupport only remote-miners.\n\n- To enable, add `--mine --miner.etherbase=...` or `--mine --miner.miner.sigkey=...` flags.\n- Other supported options: `--miner.extradata`, `--miner.notify`, `--miner.gaslimit`, `--miner.gasprice`\n  , `--miner.gastarget`\n- JSON-RPC supports methods: eth_coinbase , eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate\n- JSON-RPC supports websocket methods: newPendingTransaction\n\n\u003ccode\u003e 🔬 Detailed explanation is [here](/docs/mining.md).\u003c/code\u003e\n\n### Windows\n\nWindows users may run erigon in 3 possible ways:\n\n- Build executable binaries natively for Windows using provided `wmake.ps1` PowerShell script. Usage syntax is the same\n  as `make` command so you have to run `.\\wmake.ps1 [-target] \u003ctargetname\u003e`. Example: `.\\wmake.ps1 erigon` builds erigon\n  executable. All binaries are placed in `.\\build\\bin\\` subfolder. There are some requirements for a successful native\n  build on windows :\n\n  - [Git](https://git-scm.com/downloads) for Windows must be installed. If you're cloning this repository is very\n    likely you already have it\n  - [GO Programming Language](https://golang.org/dl/) must be installed. Minimum required version is 1.21\n  - GNU CC Compiler at least version 13 (is highly suggested that you install `chocolatey` package manager - see\n    following point)\n  - If you need to build MDBX tools (i.e. `.\\wmake.ps1 db-tools`)\n    then [Chocolatey package manager](https://chocolatey.org/) for Windows must be installed. By Chocolatey you need\n    to install the following components : `cmake`, `make`, `mingw` by `choco install cmake make mingw`. Make sure\n    Windows System \"Path\" variable has:\n    C:\\ProgramData\\chocolatey\\lib\\mingw\\tools\\install\\mingw64\\bin\n\n  **Important note about Anti-Viruses**\n  During MinGW's compiler detection phase some temporary executables are generated to test compiler capabilities. It's\n  been reported some anti-virus programs detect those files as possibly infected by `Win64/Kryptic.CIS` trojan horse (or\n  a variant of it). Although those are false positives we have no control over 100+ vendors of security products for\n  Windows and their respective detection algorithms and we understand this might make your experience with Windows\n  builds uncomfortable. To workaround the issue you might either set exclusions for your antivirus specifically\n  for `build\\bin\\mdbx\\CMakeFiles` sub-folder of the cloned repo or you can run erigon using the following other two\n  options\n\n- Use Docker : see [docker-compose.yml](./docker-compose.yml)\n\n- Use WSL (Windows Subsystem for Linux) **strictly on version 2**. Under this option you can build Erigon just as you\n  would on a regular Linux distribution. You can point your data also to any of the mounted Windows partitions (\n  eg. `/mnt/c/[...]`, `/mnt/d/[...]` etc) but in such case be advised performance is impacted: this is due to the fact\n  those mount points use `DrvFS` which is a [network file system](#blocks-execution-is-slow-on-cloud-network-drives)\n  and, additionally, MDBX locks the db for exclusive access which implies only one process at a time can access data.\n  This has consequences on the running of `rpcdaemon` which has to be configured as [Remote DB](#for-remote-db) even if\n  it is executed on the very same computer. If instead your data is hosted on the native Linux filesystem non\n  limitations apply.\n  **Please also note the default WSL2 environment has its own IP address which does not match the one of the network\n  interface of Windows host: take this into account when configuring NAT for port 30303 on your router.**\n\n### Using TOML or YAML Config Files\n\nYou can set Erigon flags through a YAML or TOML configuration file with the flag `--config`. The flags set in the\nconfiguration\nfile can be overwritten by writing the flags directly on Erigon command line\n\n### Example\n\n`./build/bin/erigon --config ./config.yaml --chain=goerli`\n\nAssuming we have `chain : \"mainnet\"` in our configuration file, by adding `--chain=goerli` allows the overwrite of the\nflag inside\nof the yaml configuration file and sets the chain to goerli\n\n### TOML\n\nExample of setting up TOML config file\n\n```\ndatadir = 'your datadir'\nport = 1111\nchain = \"mainnet\"\nhttp = true\n\"private.api.addr\"=\"localhost:9090\"\n\n\"http.api\" = [\"eth\",\"debug\",\"net\"]\n```\n\n### YAML\n\nExample of setting up a YAML config file\n\n```\ndatadir : 'your datadir'\nport : 1111\nchain : \"mainnet\"\nhttp : true\nprivate.api.addr : \"localhost:9090\"\n\nhttp.api : [\"eth\",\"debug\",\"net\"]\n```\n\n### Beacon Chain (Consensus Layer)\n\nErigon can be used as an Execution Layer (EL) for Consensus Layer clients (CL). Default configuration is OK.\n\nIf your CL client is on a different device, add `--authrpc.addr 0.0.0.0` ([Engine API] listens on localhost by default)\nas well as `--authrpc.vhosts \u003cCL host\u003e` where `\u003cCL host\u003e` is your source host or `any`.\n\n[Engine API]: https://github.com/ethereum/execution-apis/blob/main/src/engine\n\nIn order to establish a secure connection between the Consensus Layer and the Execution Layer, a JWT secret key is\nautomatically generated.\n\nThe JWT secret key will be present in the datadir by default under the name of `jwt.hex` and its path can be specified\nwith the flag `--authrpc.jwtsecret`.\n\nThis piece of info needs to be specified in the Consensus Layer as well in order to establish connection successfully.\nMore information can be found [here](https://github.com/ethereum/execution-apis/blob/main/src/engine/authentication.md).\n\nOnce Erigon is running, you need to point your CL client to `\u003cerigon address\u003e:8551`,\nwhere `\u003cerigon address\u003e` is either `localhost` or the IP address of the device running Erigon, and also point to the JWT\nsecret path created by Erigon.\n\n### Caplin\n\nCaplin is a full-fledged validating Consensus Client like Prysm, Lighthouse, Teku, Nimbus and Lodestar. Its goal is:\n\n- provide better stability\n- Validation of the chain\n- Stay in sync\n- keep the execution of blocks on chain tip\n- serve the Beacon API using a fast and compact data model alongside low CPU and memory usage.\n\nThe main reason why developed a new Consensus Layer is to experiment with the possible benefits that could come with it. For example, The Engine API does not work well with Erigon. The Engine API sends data one block at a time, which does not suit how Erigon works. Erigon is designed to handle many blocks simultaneously and needs to sort and process data efficiently. Therefore, it would be better for Erigon to handle the blocks independently instead of relying on the Engine API.\n\n#### Caplin's Usage.\n\nCaplin can be enabled through the `--internalcl` flag. from that point on, an external Consensus Layer will not be need anymore.\n\nCaplin also has an archivial mode for historical states and blocks. it can be enabled through the `--caplin.archive` flag.\nIn order to enable the caplin's Beacon API, the flag `--beacon.api=\u003cnamespaces\u003e` must be added.\ne.g: `--beacon.api=beacon,builder,config,debug,node,validator,lighthouse` will enable all endpoints. \\*\\*NOTE: Caplin is not staking-ready so aggregation endpoints are still to be implemented. Additionally enabling the Beacon API will lead to a 6 GB higher RAM usage.\n\n### Multiple Instances / One Machine\n\nDefine 6 flags to avoid conflicts: `--datadir --port --http.port --authrpc.port --torrent.port --private.api.addr`.\nExample of multiple chains on the same machine:\n\n```\n# mainnet\n./build/bin/erigon --datadir=\"\u003cyour_mainnet_data_path\u003e\" --chain=mainnet --port=30303 --http.port=8545 --authrpc.port=8551 --torrent.port=42069 --private.api.addr=127.0.0.1:9090 --http --ws --http.api=eth,debug,net,trace,web3,erigon\n\n\n# sepolia\n./build/bin/erigon --datadir=\"\u003cyour_sepolia_data_path\u003e\" --chain=sepolia --port=30304 --http.port=8546 --authrpc.port=8552 --torrent.port=42068 --private.api.addr=127.0.0.1:9091 --http --ws --http.api=eth,debug,net,trace,web3,erigon\n```\n\nQuote your path if it has spaces.\n\n### Dev Chain\n\n\u003ccode\u003e 🔬 Detailed explanation is [DEV_CHAIN](/DEV_CHAIN.md).\u003c/code\u003e\n\n# Key features\n\n\u003ccode\u003e🔬 See more\ndetailed [overview of functionality and current limitations](https://erigontech/.github.io/turbo_geth_release.html). It\nis being updated on recurring basis.\u003c/code\u003e\n\n### More Efficient State Storage\n\n**Flat KV storage.** Erigon uses a key-value database and storing accounts and storage in a simple way.\n\n\u003ccode\u003e 🔬 See our detailed DB walkthrough [here](./docs/programmers_guide/db_walkthrough.MD).\u003c/code\u003e\n\n**Preprocessing**. For some operations, Erigon uses temporary files to preprocess data before inserting it into the main\nDB. That reduces write amplification and DB inserts are orders of magnitude quicker.\n\n\u003ccode\u003e 🔬 See our detailed ETL explanation [here](https://github.com/erigontech/erigon-lib/blob/main/etl/README.md).\u003c/code\u003e\n\n**Plain state**.\n\n**Single accounts/state trie**. Erigon uses a single Merkle trie for both accounts and the storage.\n\n### Faster Initial Sync\n\nErigon uses a rearchitected full sync algorithm from\n[Go-Ethereum](https://github.com/ethereum/go-ethereum) that is split into\n\"stages\".\n\n\u003ccode\u003e🔬 See more detailed explanation in the [Staged Sync Readme](/eth/stagedsync/README.md)\u003c/code\u003e\n\nIt uses the same network primitives and is compatible with regular go-ethereum nodes that are using full sync, you do\nnot need any special sync capabilities for Erigon to sync.\n\nWhen reimagining the full sync, with focus on batching data together and minimize DB overwrites. That makes it possible\nto sync Ethereum mainnet in under 2 days if you have a fast enough network connection and an SSD drive.\n\nExamples of stages are:\n\n- Downloading headers;\n\n- Downloading block bodies;\n\n- Recovering senders' addresses;\n\n- Executing blocks;\n\n- Validating root hashes and building intermediate hashes for the state Merkle trie;\n\n- [...]\n\n### JSON-RPC daemon\n\nMost of Erigon's components (txpool, rpcdaemon, snapshots downloader, sentry, ...) can work inside Erigon and as\nindependent process.\n\nTo enable built-in RPC server: `--http` and `--ws` (sharing same port with http)\n\nRun RPCDaemon as separated process: this daemon can use local DB (with running Erigon or on snapshot of a database) or\nremote DB (run on another server). \u003ccode\u003e🔬 See [RPC-Daemon docs](./cmd/rpcdaemon/README.md)\u003c/code\u003e\n\n#### **For remote DB**\n\nThis works regardless of whether RPC daemon is on the same computer with Erigon, or on a different one. They use TPC\nsocket connection to pass data between them. To use this mode, run Erigon in one terminal window\n\n```sh\nmake erigon\n./build/bin/erigon --private.api.addr=localhost:9090 --http=false\nmake rpcdaemon\n./build/bin/rpcdaemon --private.api.addr=localhost:9090 --http.api=eth,erigon,web3,net,debug,trace,txpool\n```\n\n#### **gRPC ports**\n\n`9090` erigon, `9091` sentry, `9092` consensus engine, `9093` torrent downloader, `9094` transactions pool\n\nSupported JSON-RPC calls ([eth](./cmd/rpcdaemon/commands/eth_api.go), [debug](./cmd/rpcdaemon/commands/debug_api.go)\n, [net](./cmd/rpcdaemon/commands/net_api.go), [web3](./cmd/rpcdaemon/commands/web3_api.go)):\n\nFor a details on the implementation status of each\ncommand, [see this table](./cmd/rpcdaemon/README.md#rpc-implementation-status).\n\n### Run all components by docker-compose\n\nDocker allows for building and running Erigon via containers. This alleviates the need for installing build dependencies\nonto the host OS.\n\n#### Optional: Setup dedicated user\n\nUser UID/GID need to be synchronized between the host OS and container so files are written with correct permission.\n\nYou may wish to setup a dedicated user/group on the host OS, in which case the following `make` targets are available.\n\n```sh\n# create \"erigon\" user\nmake user_linux\n# or\nmake user_macos\n```\n\n#### Environment Variables\n\nThere is a `.env.example` file in the root of the repo.\n\n- `DOCKER_UID` - The UID of the docker user\n- `DOCKER_GID` - The GID of the docker user\n- `XDG_DATA_HOME` - The data directory which will be mounted to the docker containers\n\nIf not specified, the UID/GID will use the current user.\n\nA good choice for `XDG_DATA_HOME` is to use the `~erigon/.ethereum` directory created by helper\ntargets `make user_linux` or `make user_macos`.\n\n#### Check: Permissions\n\nIn all cases, `XDG_DATA_HOME` (specified or default) must be writeable by the user UID/GID in docker, which will be\ndetermined by the `DOCKER_UID` and `DOCKER_GID` at build time.\n\nIf a build or service startup is failing due to permissions, check that all the directories, UID, and GID controlled by\nthese environment variables are correct.\n\n#### Run\n\nNext command starts: Erigon on port 30303, rpcdaemon on port 8545, prometheus on port 9090, and grafana on port 3000.\n\n```sh\n#\n# Will mount ~/.local/share/erigon to /home/erigon/.local/share/erigon inside container\n#\nmake docker-compose\n\n#\n# or\n#\n# if you want to use a custom data directory\n# or, if you want to use different uid/gid for a dedicated user\n#\n# To solve this, pass in the uid/gid parameters into the container.\n#\n# DOCKER_UID: the user id\n# DOCKER_GID: the group id\n# XDG_DATA_HOME: the data directory (default: ~/.local/share)\n#\n# Note: /preferred/data/folder must be read/writeable on host OS by user with UID/GID given\n#       if you followed above instructions\n#\n# Note: uid/gid syntax below will automatically use uid/gid of running user so this syntax\n#       is intended to be run via the dedicated user setup earlier\n#\nDOCKER_UID=$(id -u) DOCKER_GID=$(id -g) XDG_DATA_HOME=/preferred/data/folder DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 make docker-compose\n\n#\n# if you want to run the docker, but you are not logged in as the $ERIGON_USER\n# then you'll need to adjust the syntax above to grab the correct uid/gid\n#\n# To run the command via another user, use\n#\nERIGON_USER=erigon\nsudo -u ${ERIGON_USER} DOCKER_UID=$(id -u ${ERIGON_USER}) DOCKER_GID=$(id -g ${ERIGON_USER}) XDG_DATA_HOME=~${ERIGON_USER}/.ethereum DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 make docker-compose\n```\n\nMakefile creates the initial directories for erigon, prometheus and grafana. The PID namespace is shared between erigon\nand rpcdaemon which is required to open Erigon's DB from another process (RPCDaemon local-mode).\nSee: https://github.com/erigontech/erigon/pull/2392/files\n\nIf your docker installation requires the docker daemon to run as root (which is by default), you will need to prefix\nthe command above with `sudo`. However, it is sometimes recommended running docker (and therefore its containers) as a\nnon-root user for security reasons. For more information about how to do this, refer to\n[this article](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user).\n\nWindows support for docker-compose is not ready yet. Please help us with .ps1 port.\n\n### Grafana dashboard\n\n`docker compose up prometheus grafana`, [detailed docs](./cmd/prometheus/Readme.md).\n\n###\n\nold data\n\nDisabled by default. To enable see `./build/bin/erigon --help` for flags `--prune`\n\n# Documentation\n\nThe `./docs` directory includes a lot of useful but outdated documentation. For code located\nin the `./cmd` directory, their respective documentation can be found in `./cmd/*/README.md`.\nA more recent collation of developments and happenings in Erigon can be found in the\n[Erigon Blog](https://erigon.substack.com/).\n\n# FAQ\n\n### How much RAM do I need\n\n- Baseline (ext4 SSD): 16Gb RAM sync takes 6 days, 32Gb - 5 days, 64Gb - 4 days\n- +1 day on \"zfs compression=off\". +2 days on \"zfs compression=on\" (2x compression ratio). +3 days on btrfs.\n- -1 day on NVMe\n\nDetailed explanation: [./docs/programmers_guide/db_faq.md](./docs/programmers_guide/db_faq.md)\n\n### Default Ports and Firewalls\n\n#### `erigon` ports\n\n| Component | Port  | Protocol  | Purpose                     | Should Expose |\n| --------- | ----- | --------- | --------------------------- | ------------- |\n| engine    | 9090  | TCP       | gRPC Server                 | Private       |\n| engine    | 42069 | TCP \u0026 UDP | Snap sync (Bittorrent)      | Public        |\n| engine    | 8551  | TCP       | Engine API (JWT auth)       | Private       |\n| sentry    | 30303 | TCP \u0026 UDP | eth/68 peering              | Public        |\n| sentry    | 30304 | TCP \u0026 UDP | eth/67 peering              | Public        |\n| sentry    | 9091  | TCP       | incoming gRPC Connections   | Private       |\n| rpcdaemon | 8545  | TCP       | HTTP \u0026 WebSockets \u0026 GraphQL | Private       |\n\nTypically, 30303 and 30304 are exposed to the internet to allow incoming peering connections. 9090 is exposed only\ninternally for rpcdaemon or other connections, (e.g. rpcdaemon -\u003e erigon).\nPort 8551 (JWT authenticated) is exposed only internally for [Engine API] JSON-RPC queries from the Consensus Layer\nnode.\n\n#### `caplin` ports\n\n| Component | Port | Protocol | Purpose | Should Expose |\n| --------- | ---- | -------- | ------- | ------------- |\n| sentinel  | 4000 | UDP      | Peering | Public        |\n| sentinel  | 4001 | TCP      | Peering | Public        |\n\nIf you are using `--internalcl` aka `caplin` as your consensus client, then also look at the chart above\n\n#### `beaconAPI` ports\n\n| Component | Port | Protocol | Purpose | Should Expose |\n| --------- | ---- | -------- | ------- | ------------- |\n| REST      | 5555 | TCP      | REST    | Public        |\n\nIf you are using `--internalcl` aka `caplin` as your consensus client and `--beacon.api` then also look at the chart above\n\n#### `shared` ports\n\n| Component | Port | Protocol | Purpose | Should Expose |\n| --------- | ---- | -------- | ------- | ------------- |\n| all       | 6060 | TCP      | pprof   | Private       |\n| all       | 6060 | TCP      | metrics | Private       |\n\nOptional flags can be enabled that enable pprof or metrics (or both) - however, they both run on 6060 by default, so\n\nyou'll have to change one if you want to run both at the same time. use `--help` with the binary for more info.\n\n#### `other` ports\n\nReserved for future use: **gRPC ports**: `9092` consensus engine, `9093` snapshot downloader, `9094` TxPool\n\n#### Hetzner expecting strict firewall rules\n\n```\n0.0.0.0/8             \"This\" Network             RFC 1122, Section 3.2.1.3\n10.0.0.0/8            Private-Use Networks       RFC 1918\n100.64.0.0/10         Carrier-Grade NAT (CGN)    RFC 6598, Section 7\n127.16.0.0/12         Private-Use Networks       RFC 1918\n169.254.0.0/16        Link Local                 RFC 3927\n172.16.0.0/12         Private-Use Networks       RFC 1918\n192.0.0.0/24          IETF Protocol Assignments  RFC 5736\n192.0.2.0/24          TEST-NET-1                 RFC 5737\n192.88.99.0/24        6to4 Relay Anycast         RFC 3068\n192.168.0.0/16        Private-Use Networks       RFC 1918\n198.18.0.0/15         Network Interconnect\nDevice Benchmark Testing   RFC 2544\n198.51.100.0/24       TEST-NET-2                 RFC 5737\n203.0.113.0/24        TEST-NET-3                 RFC 5737\n224.0.0.0/4           Multicast                  RFC 3171\n240.0.0.0/4           Reserved for Future Use    RFC 1112, Section 4\n255.255.255.255/32    Limited Broadcast          RFC 919, Section 7\nRFC 922, Section 7\n```\n\nSame\nin [IpTables syntax](https://ethereum.stackexchange.com/questions/6386/how-to-prevent-being-blacklisted-for-running-an-ethereum-client/13068#13068)\n\n### How to run erigon as a separate user? (e.g. as a `systemd` daemon)\n\nRunning erigon from `build/bin` as a separate user might produce an error:\n\n    error while loading shared libraries: libsilkworm_capi.so: cannot open shared object file: No such file or directory\n\nThe library needs to be _installed_ for another user using `make DIST=\u003cpath\u003e install`. You could use `$HOME/erigon` or `/opt/erigon` as the installation path, for example:\n\n    make DIST=/opt/erigon install\n\nand then run `/opt/erigon/erigon`.\n\n### How to get diagnostic for bug report?\n\n- Get stack trace: `kill -SIGUSR1 \u003cpid\u003e`, get trace and stop: `kill -6 \u003cpid\u003e`\n- Get CPU profiling: add `--pprof flag`\n  run `go tool pprof -png  http://127.0.0.1:6060/debug/pprof/profile\\?seconds\\=20 \u003e cpu.png`\n- Get RAM profiling: add `--pprof flag`\n  run `go tool pprof -inuse_space -png  http://127.0.0.1:6060/debug/pprof/heap \u003e mem.png`\n\n### How to run local devnet?\n\n\u003ccode\u003e 🔬 Detailed explanation is [here](/DEV_CHAIN.md).\u003c/code\u003e\n\n### Docker permissions error\n\nDocker uses user erigon with UID/GID 1000 (for security reasons). You can see this user being created in the Dockerfile.\nCan fix by giving a host's user ownership of the folder, where the host's user UID/GID is the same as the docker's user\nUID/GID (1000).\nMore details\nin [post](https://www.fullstaq.com/knowledge-hub/blogs/docker-and-the-host-filesystem-owner-matching-problem)\n\n### How to run public RPC api\n\n- `--txpool.nolocals=true`\n- don't add `admin` in `--http.api` list\n- to increase throughput may need\n  increase/decrease: `--db.read.concurrency`, `--rpc.batch.concurrency`, `--rpc.batch.limit`\n\n### Run RaspberyPI\n\nhttps://github.com/mathMakesArt/Erigon-on-RPi-4\n\n### How to change db pagesize\n\n[post](https://github.com/erigontech/erigon/blob/devel/cmd/integration/Readme.md#copy-data-to-another-db)\n\n# Getting in touch\n\n### Erigon Discord Server\n\nThe main discussions are happening on our Discord server. To get an invite, send an email to `bloxster [at] proton.me`\nwith\nyour name, occupation, a brief explanation of why you want to join the Discord, and how you heard about Erigon.\n\n### Reporting security issues/concerns\n\nSend an email to `security [at] torquem.ch`.\n\n# Known issues\n\n### `htop` shows incorrect memory usage\n\nErigon's internal DB (MDBX) using `MemoryMap` - when OS does manage all `read, write, cache` operations instead of\nApplication\n([linux](https://linux-kernel-labs.github.io/refs/heads/master/labs/memory_mapping.html)\n, [windows](https://docs.microsoft.com/en-us/windows/win32/memory/file-mapping))\n\n`htop` on column `res` shows memory of \"App + OS used to hold page cache for given App\", but it's not informative,\nbecause if `htop` says that app using 90% of memory you still can run 3 more instances of app on the same machine -\nbecause most of that `90%` is \"OS pages cache\".\nOS automatically frees this cache any time it needs memory. Smaller \"page cache size\" may not impact performance of\nErigon at all.\n\nNext tools show correct memory usage of Erigon:\n\n- `vmmap -summary PID | grep -i \"Physical footprint\"`. Without `grep` you can see details\n  - `section MALLOC ZONE column Resident Size` shows App memory usage, `section REGION TYPE column Resident Size`\n    shows OS pages cache size.\n- `Prometheus` dashboard shows memory of Go app without OS pages cache (`make prometheus`, open in\n  browser `localhost:3000`, credentials `admin/admin`)\n- `cat /proc/\u003cPID\u003e/smaps`\n\n  Erigon uses ~4Gb of RAM during genesis sync and ~1Gb during normal work. OS pages cache can utilize unlimited amount\n  of\n  memory.\n\n  **Warning:** Multiple instances of Erigon on same machine will touch Disk concurrently, it impacts performance - one\n  of\n  main Erigon optimisations: \"reduce Disk random access\".\n  \"Blocks Execution stage\" still does many random reads - this is reason why it's slowest stage. We do not recommend\n  running\n  multiple genesis syncs on same Disk. If genesis sync passed, then it's fine to run multiple Erigon instances on same\n  Disk.\n\n### Blocks Execution is slow on cloud-network-drives\n\nPlease read https://github.com/erigontech/erigon/issues/1516#issuecomment-811958891\nIn short: network-disks are bad for blocks execution - because blocks execution reading data from db non-parallel\nnon-batched way.\n\n### Filesystem's background features are expensive\n\nFor example: btrfs's autodefrag option - may increase write IO 100x times\n\n### Gnome Tracker can kill Erigon\n\n[Gnome Tracker](https://wiki.gnome.org/Projects/Tracker) - detecting miners and kill them.\n\n### the --mount option requires BuildKit error\n\nFor anyone else that was getting the BuildKit error when trying to start Erigon the old way you can use the below...\n\n```\nXDG_DATA_HOME=/preferred/data/folder DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 make docker-compose\n```\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftestinprod-io%2Fop-erigon","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftestinprod-io%2Fop-erigon","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftestinprod-io%2Fop-erigon/lists"}