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

Updated top level README.md

Browse Source 
updated instructions and prefer the s3sync-runner tool
This commit is contained in:
Nicholas Wehr
2025-08-28 11:34:18 -07:00
committed by GitHub
parent bf51dc83e5
commit fa9f8fc5df
1 changed files with 11 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -20,6 +20,13 @@ The current state of the block files comprise of millions of small objects total
1) this will backfill the existing blocks from Hyperliquid's EVM S3 bucket: 1) this will backfill the existing blocks from Hyperliquid's EVM S3 bucket:
> use our rust based s3 tool wrapper to optimize your download experience - [read more](./etc/evm-block-sync/README.md)
```shell
chmod +x ./etc/evm-block-sync/s3sync-runner.sh
./etc/evm-block-sync/s3sync-runner.sh
```
> or use the conventional [aws cli](https://aws.amazon.com/cli/)
```shell ```shell
aws s3 sync s3://hl-mainnet-evm-blocks/ ~/evm-blocks \ aws s3 sync s3://hl-mainnet-evm-blocks/ ~/evm-blocks \
--request-payer requester \ --request-payer requester \
@ -27,17 +34,17 @@ The current state of the block files comprise of millions of small objects total
--size-only \ --size-only \
--only-show-errors --only-show-errors
``` ```
> consider using this [rust based s3 tool wrapper](https://github.com/wwwehr/hl-evm-block-sync) alternative to optimize your download experience
2) `$ make install` - this will install the NanoReth binary.
3) Start NanoReth which will begin syncing using the blocks in `~/evm-blocks`: 1) `$ make install` - this will install the NanoReth binary.
2) Start NanoReth which will begin syncing using the blocks in `~/evm-blocks`:
```sh ```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 $ 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. 3) 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` Stop the NanoReth process and then start Goofys: `$ goofys --region=ap-northeast-1 --requester-pays hl-mainnet-evm-blocks evm-blocks`