jleony/nanoreth
1
0
Fork 0
mirror of https://github.com/hl-archive-node/nanoreth.git synced 2025-12-06 10:59:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add the Sigma Prime audit (#8728)

Browse Source
This commit is contained in:
Georgios Konstantopoulos
2024-06-10 13:08:34 -07:00
committed by GitHub
parent ad0be4ca06
commit 1bc9d8b145
8 changed files with 16 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
book/run/optimism.md
View File

@ -14,12 +14,6 @@ the [L2 EL specification][l2-el-spec], and the [OP Stack specification][op-stack
## Running on Optimism
> `op-reth` is currently in the *alpha* stage of development. It is not yet ready for production use, and therefore does not have a stable release. To run it, you must build the `op-reth` binary from source.
> If you do encounter any bugs during this early stage of development, please report them in an issue on the [GitHub repository][reth].
>
> `op-reth` also does **not** currently support OP Stack chains with legacy, pre-Bedrock state, i.e. `Optimism Mainnet` and `Optimism Goerli`. This will be possible once a database migration tool for pre-Bedrock
> state is released, with the capability to extract the legacy state from the old `l2geth` LevelDB datadir and transplant it into Reth's MDBX database.
You will need three things to run `op-reth`:
1. An archival L1 node, synced to the settlement layer of the OP Stack chain you want to sync (e.g. `reth`, `geth`, `besu`, `nethermind`, etc.)
1. A rollup node (e.g. `op-node`, `magi`, `hildr`, etc.)

2
book/run/troubleshooting.md
View File

@ -1,7 +1,5 @@
# Troubleshooting
As Reth is still in alpha, while running the node you can experience some problems related to different parts of the system: pipeline sync, blockchain tree, p2p, database, etc.
This page tries to answer how to deal with the most popular issues.
## Database