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

docs: clarify instructions for running a mainnet node (#5)

Browse Source 
* docs: clarify instructions for running a mainnet node

* docs: fix last section re running the node
This commit is contained in:
zilayo
2025-07-06 05:12:14 +02:00
committed by GitHub
parent 4994f7fd5e
commit 88a58a5c81
1 changed files with 26 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
README.md
View File

@ -8,18 +8,35 @@ Deposit transactions from `0x222..22` to user addresses are intentionally record
This change simplifies block explorers, making it easier to track deposit timestamps. This change simplifies block explorers, making it easier to track deposit timestamps.
Ensure careful handling when indexing. Ensure careful handling when indexing.
## Prerequisites
Building NanoReth from source requires Rust and Cargo to be installed:
`$ curl https://sh.rustup.rs -sSf | sh`
## How to run (mainnet) ## How to run (mainnet)
```sh 1) `$ aws s3 sync s3://hl-mainnet-evm-blocks/ ~/evm-blocks --request-payer requester # one-time` - this will backfill the existing blocks from HyperLiquid's EVM S3 bucket.
# Fetch EVM blocks
$ aws s3 sync s3://hl-mainnet-evm-blocks/ ~/evm-blocks --request-payer requester # one-time
$ goofys --region=ap-northeast-1 --requester-pays hl-mainnet-evm-blocks evm-blocks-bak # realtime
# Run node 2) `$ make install` - this will install the NanoReth binary.
$ make install
$ reth node --http --http.addr 0.0.0.0 --http.api eth,ots,net,web3 \ 3) Start NanoReth which will begin syncing using the blocks in `~/evm-blocks`:
--ws --ws.addr 0.0.0.0 --ws.origins '*' --ws.api eth,ots,net,web3 --ingest-dir ~/evm-blocks --ws.port 8545
``` ```sh
$ reth node --http --http.addr 0.0.0.0 --http.api eth,ots,net,web3 --ws --ws.addr 0.0.0.0 --ws.origins '*' --ws.api eth,ots,net,web3 --ingest-dir ~/evm-blocks --ws.port 8545
```
4) Once the node logs stops making progress this means it's caught up with the existing blocks.
Stop the NanoReth process and then start Goofys: `$ goofys --region=ap-northeast-1 --requester-pays hl-mainnet-evm-blocks evm-blocks`
Goofys will mount the AWS S3 bucket into `~/evm-blocks` and save new blocks as they are added to the bucket.
You can now restart NanoReth using the same command as above:
```sh
$ reth node --http --http.addr 0.0.0.0 --http.api eth,ots,net,web3 --ws --ws.addr 0.0.0.0 --ws.origins '*' --ws.api eth,ots,net,web3 --ingest-dir ~/evm-blocks --ws.port 8545
```
## How to run (mainnet) (with local block sync) ## How to run (mainnet) (with local block sync)