[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-5668":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":19,"compositeScore":20,"rankGlobal":10,"rankLanguage":10,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":22,"hasPages":24,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":34,"readmeContent":35,"aiSummary":36,"trendingCount":16,"starSnapshotCount":16,"syncStatus":37,"lastSyncTime":38,"discoverSource":39},5668,"reth","paradigmxyz\u002Freth","paradigmxyz","Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol, in Rust","https:\u002F\u002Freth.rs\u002F",null,"Rust",5627,2471,63,76,0,9,62,4,41,"Apache License 2.0",false,"main",true,[26,27,28,29,30,31,32,33],"blockchain","contributor-friendly","distributed-systems","ethereum","execution-layer","modular","p2p","rust","2026-06-12 02:01:13","# reth\n\n[![bench status](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Factions\u002Fworkflows\u002Fbench.yml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Factions\u002Fworkflows\u002Fbench.yml)\n[![CI status](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fworkflows\u002Funit\u002Fbadge.svg)][gh-ci]\n[![cargo-lint status](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Factions\u002Fworkflows\u002Flint.yml\u002Fbadge.svg)][gh-lint]\n[![Telegram Chat][tg-badge]][tg-url]\n\n**Modular, contributor-friendly and blazing-fast implementation of the Ethereum protocol**\n\n![](.\u002Fassets\u002Freth-2.png)\n\n**[Install](https:\u002F\u002Freth.rs\u002Finstallation\u002Finstallation)**\n| [User Docs](https:\u002F\u002Freth.rs)\n| [Developer Docs](.\u002Fdocs)\n| [Crate Docs](https:\u002F\u002Freth.rs\u002Fdocs)\n\n[gh-ci]: https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Factions\u002Fworkflows\u002Funit.yml\n[gh-lint]: https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Factions\u002Fworkflows\u002Flint.yml\n[tg-badge]: https:\u002F\u002Fimg.shields.io\u002Fendpoint?color=neon&logo=telegram&label=chat&url=https%3A%2F%2Ftg.sumanjay.workers.dev%2Fparadigm%5Freth\n\n## What is Reth?\n\nReth (short for Rust Ethereum, [pronunciation](https:\u002F\u002Fx.com\u002Fkelvinfichter\u002Fstatus\u002F1597653609411268608)) is a production-ready Ethereum execution layer client focused on modularity, performance, and user-friendliness. Reth is compatible with all Ethereum Consensus Layer (CL) implementations that support the [Engine API](https:\u002F\u002Fgithub.com\u002Fethereum\u002Fexecution-apis\u002Ftree\u002Fa0d03086564ab1838b462befbc083f873dcf0c0f\u002Fsrc\u002Fengine). It is built and driven forward by [Paradigm](https:\u002F\u002Fparadigm.xyz\u002F), and is licensed under the Apache and MIT licenses.\n\n> **Note:** OP-Reth has moved to [ethereum-optimism\u002Foptimism](https:\u002F\u002Fgithub.com\u002Fethereum-optimism\u002Foptimism). Git history has been preserved.\n\n## Goals\n\n1. **Modularity**: Every component is built to be used as a library: well-tested, documented and benchmarked. Import crates, mix and match, and innovate on top of them. Learn more about the project's components [here](.\u002Fdocs\u002Frepo\u002Flayout.md).\n2. **Performance**: Built with Rust, [Alloy](https:\u002F\u002Fgithub.com\u002Falloy-rs\u002Falloy\u002F), [revm](https:\u002F\u002Fgithub.com\u002Fbluealloy\u002Frevm\u002F), and [Foundry](https:\u002F\u002Fgithub.com\u002Ffoundry-rs\u002Ffoundry\u002F) — battle-tested and optimized for speed. Check the [ethPandaOps Lab Dashboard](https:\u002F\u002Flab.ethpandaops.io\u002Fethereum\u002Fexecution\u002Ftimings) for a third-party comparison against other Ethereum clients.\nHere's what that looks like in practice, measured with [reth-bench](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Ftree\u002Fmain\u002Fbin\u002Freth-bench) on Ethereum Mainnet:\n\n![](.\u002Fassets\u002Freth-perf.png)\n\n3. **Free for anyone to use any way they want**: Apache\u002FMIT licensed, no business license restrictions.\n4. **Client Diversity**: More client implementations make Ethereum more antifragile.\n5. **Support as many EVM chains as possible**: Reth can sync Ethereum and other EVM chains. If you're building one, reach out.\n6. **Configurability**: Profiles for different use cases — from high-performance RPC operators to hobbyists on consumer hardware.\n\n## Status\n\nReth is production ready, and suitable for usage in mission-critical environments such as staking or high-uptime services. We also actively recommend professional node operators to switch to Reth in production for performance and cost reasons in use cases where high performance with great margins is required such as RPC, MEV, Indexing, Simulations, and P2P activities.\n\n- We released **Reth 2.0** in April 2026. See the [release notes](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Freleases\u002Ftag\u002Fv2.0.0) and [blog post](https:\u002F\u002Fwww.paradigm.xyz\u002F2026\u002F04\u002Freleasing-reth-2-0).\n- We released 1.0 \"production-ready\" stable Reth in June 2024.\n  - Reth completed an audit with [Sigma Prime](https:\u002F\u002Fsigmaprime.io\u002F), the developers of [Lighthouse](https:\u002F\u002Fgithub.com\u002Fsigp\u002Flighthouse), the Rust Consensus Layer implementation. Find it [here](.\u002Faudit\u002Fsigma_prime_audit_v2.pdf).\n  - Revm (the EVM used in Reth) underwent an audit with [Guido Vranken](https:\u002F\u002Fx.com\u002Fguidovranken) (#1 [Ethereum Bug Bounty](https:\u002F\u002Fethereum.org\u002Fen\u002Fbug-bounty)).\n- We released multiple iterative beta versions, up to [beta.9](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Freleases\u002Ftag\u002Fv0.2.0-beta.9) on Monday June 3, 2024, the last beta release.\n- We released [beta](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Freleases\u002Ftag\u002Fv0.2.0-beta.1) on Monday March 4, 2024, our first breaking change to the database model, providing faster query speed, smaller database footprint, and allowing \"history\" to be mounted on separate drives.\n- We shipped iterative improvements until the last alpha release on February 28, 2024, [0.1.0-alpha.21](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Freleases\u002Ftag\u002Fv0.1.0-alpha.21).\n- We [initially announced](https:\u002F\u002Fwww.paradigm.xyz\u002F2023\u002F06\u002Freth-alpha) [0.1.0-alpha.1](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Freleases\u002Ftag\u002Fv0.1.0-alpha.1) on June 20, 2023.\n\n### Storage compatibility\n\nStorage V2 is the default for new nodes in Reth 2.0. Existing V1 nodes continue to work, but V1 support will be removed in a future release — all users are encouraged to migrate. V2 snapshots are available at [snapshots.reth.rs](https:\u002F\u002Fsnapshots.reth.rs\u002F).\n\n![](.\u002Fassets\u002Freth-storage.png)\n\n## For Users\n\nSee the [Reth documentation](https:\u002F\u002Freth.rs\u002F) for instructions on how to install and run Reth.\n\n## For Developers\n\n### Using reth as a library\n\nYou can use individual crates of reth in your project.\n\nThe crate docs can be found [here](https:\u002F\u002Freth.rs\u002Fdocs\u002F).\n\nFor a general overview of the crates, see [Project Layout](.\u002Fdocs\u002Frepo\u002Flayout.md).\n\n### Contributing\n\nIf you want to contribute, or follow along with contributor discussion, you can use our [main telegram](https:\u002F\u002Ft.me\u002Fparadigm_reth) to chat with us about the development of Reth!\n\n- Our contributor guidelines can be found in [`CONTRIBUTING.md`](.\u002FCONTRIBUTING.md).\n- See our [contributor docs](.\u002Fdocs) for more information on the project. A good starting point is [Project Layout](.\u002Fdocs\u002Frepo\u002Flayout.md).\n\n### Building and testing\n\n\u003C!--\nWhen updating this, also update:\n- Cargo.toml\n- .github\u002Fworkflows\u002Flint.yml\n-->\n\nThe Minimum Supported Rust Version (MSRV) of this project is [1.93.0](https:\u002F\u002Fblog.rust-lang.org\u002F2026\u002F01\u002F22\u002FRust-1.93.0\u002F).\n\nSee the docs for detailed instructions on how to [build from source](https:\u002F\u002Freth.rs\u002Finstallation\u002Fsource\u002F).\n\nTo fully test Reth, you will need to have [Geth installed](https:\u002F\u002Fgeth.ethereum.org\u002Fdocs\u002Fgetting-started\u002Finstalling-geth), but it is possible to run a subset of tests without Geth.\n\nFirst, clone the repository:\n\n```sh\ngit clone https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\ncd reth\n```\n\nNext, run the tests:\n\n```sh\ncargo nextest run --workspace\n\n# Run the Ethereum Foundation tests\nmake ef-tests\n```\n\nWe highly recommend using [`cargo nextest`](https:\u002F\u002Fnexte.st\u002F) to speed up testing.\nUsing `cargo test` to run tests may work fine, but this is not tested and does not support more advanced features like retries for spurious failures.\n\n> **Note**\n>\n> Some tests use random number generators to generate test data. If you want to use a deterministic seed, you can set the `SEED` environment variable.\n\n## Getting Help\n\nIf you have any questions, first see if the answer to your question can be found in the [docs][book].\n\nIf the answer is not there:\n\n- Join the [Telegram][tg-url] to get help, or\n- Open a [discussion](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fdiscussions\u002Fnew) with your question, or\n- Open an issue with [the bug](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fissues\u002Fnew?assignees=&labels=C-bug%2CS-needs-triage&projects=&template=bug.yml)\n\n## Security\n\nSee [`SECURITY.md`](.\u002FSECURITY.md).\n\n## Acknowledgements\n\nReth is a new implementation of the Ethereum protocol. In the process of developing the node we investigated the design decisions other nodes have made to understand what is done well, what is not, and where we can improve the status quo.\n\nNone of this would have been possible without them, so big shoutout to the teams below:\n\n- [Geth](https:\u002F\u002Fgithub.com\u002Fethereum\u002Fgo-ethereum\u002F): We would like to express our heartfelt gratitude to the go-ethereum team for their outstanding contributions to Ethereum over the years. Their tireless efforts and dedication have helped to shape the Ethereum ecosystem and make it the vibrant and innovative community it is today. Thank you for your hard work and commitment to the project.\n- [Erigon](https:\u002F\u002Fgithub.com\u002Fledgerwatch\u002Ferigon) (fka Turbo-Geth): Erigon pioneered the [\"Staged Sync\" architecture](https:\u002F\u002Ferigon.substack.com\u002Fp\u002Ferigon-stage-sync-and-control-flows) that Reth is using, as well as [introduced MDBX](https:\u002F\u002Fgithub.com\u002Fledgerwatch\u002Ferigon\u002Fwiki\u002FChoice-of-storage-engine) as the database of choice. We thank Erigon for pushing the state of the art research on the performance limits of Ethereum nodes.\n- [Akula](https:\u002F\u002Fgithub.com\u002Fakula-bft\u002Fakula\u002F): Reth uses forks of the Apache versions of Akula's [MDBX Bindings](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fpull\u002F132), [FastRLP](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fpull\u002F63) and [ECIES](https:\u002F\u002Fgithub.com\u002Fparadigmxyz\u002Freth\u002Fpull\u002F80). Given that these packages were already released under the Apache License, and they implement standardized solutions, we decided not to reimplement them to iterate faster. We thank the Akula team for their contributions to the Rust Ethereum ecosystem and for publishing these packages.\n\n## Warning\n\nThe `NippyJar` and `Compact` encoding formats and their implementations are designed for storing and retrieving data internally. They are not hardened to safely read potentially malicious data.\n\n[book]: https:\u002F\u002Freth.rs\u002F\n[tg-url]: https:\u002F\u002Ft.me\u002Fparadigm_reth\n","Reth 是一个使用 Rust 语言实现的以太坊协议客户端，专注于模块化、性能和易用性。其核心功能包括高度模块化的组件设计，每个部分都可作为库单独使用，并且经过了充分测试和文档记录；通过利用 Rust 以及如 Alloy、revm 和 Foundry 等工具，Reth 在执行速度上表现出色。此外，它还支持广泛的 EVM 链同步，适用于从高性能 RPC 操作到个人爱好者在消费级硬件上的多种场景。Reth 适合需要快速可靠以太坊节点解决方案的各种应用场合，特别是那些重视灵活性与自定义配置能力的项目。",2,"2026-06-11 03:04:36","top_language"]