docs(book): add sigma_prime_audit_v1.pdf (#8942)

Signed-off-by: 9547 <29431502+9547@users.noreply.github.com>
Co-authored-by: Oliver <onbjerg@users.noreply.github.com>
This commit is contained in:
Marquis Shanahan
2024-06-20 22:49:26 +08:00
committed by GitHub
parent e90b526a66
commit b3cb1fde75

View File

@ -56,7 +56,7 @@ We want to solve for node operators that care about fast historical queries, but
We also want to support teams and individuals who want both sync from genesis and via "fast sync".
We envision that Reth will be configurable enough for the tradeoffs that each team faces.
We envision that Reth will be configurable enough for the tradeoffs that each team faces.
## Who is this for?
@ -76,7 +76,10 @@ Reth implements the specification of Ethereum as defined in the [ethereum/execut
1. We operate multiple nodes at the tip of Ethereum mainnet and various testnets.
1. We extensively unit test, fuzz test and document all our code, while also restricting PRs with aggressive lint rules.
We intend to also audit / fuzz the EVM & parts of the codebase. Please reach out if you're interested in collaborating on securing this codebase.
We have completed an audit of the [Reth v1.0.0-rc.2](https://github.com/paradigmxyz/reth/releases/tag/v1.0.0-rc.2) with [Sigma Prime](https://sigmaprime.io/), the developers of [Lighthouse](https://github.com/sigp/lighthouse), the Rust Consensus Layer implementation. Find it [here](https://github.com/paradigmxyz/reth/blob/bf9cac7571f018fec581fe3647862dab527aeafb/audit/sigma_prime_audit_v1.pdf).
[Revm](https://github.com/bluealloy/revm) (the EVM used in Reth) underwent an audit with [Guido Vranken](https://twitter.com/guidovranken) (#1 [Ethereum Bug Bounty](https://ethereum.org/en/bug-bounty)). We will publish the results soon.
## Sections