Skip to content

bitfinity.md

Latest commit

 

History

History
92 lines (59 loc) · 3.47 KB

bitfinity.md

File metadata and controls

92 lines (59 loc) · 3.47 KB

Bitfinity Reth Node

Introduction

Bitfinity Reth is an archive node built on Reth, a rust implementation of the Ethereum protocol. It is designed to be fast, efficient, and secure.

Getting Started

Prerequisites

Building from Source

make build

Bitfinity commands

Running the node as EVM archiver

When running the node, it will also run a block import process. This process will download the blocks from the network and import them into the database. This process can take a long time, depending on the network speed and the number of blocks to import.

To run the node, use the following command:

reth node -vvv --http --http.port 8080 --http.addr 0.0.0.0 --http.api "debug,eth,net,trace,txpool,web3" --disable-discovery --ipcdisable --no-persist-peers -r https://testnet.bitfinity.network -i 30 -b 100 --datadir /reth/data

With cargo:

cargo run -p reth -- node -vvv --http --http.port 8080 --http.addr 0.0.0.0 --http.api "debug,eth,net,trace,txpool,web3" --disable-discovery --ipcdisable --no-persist-peers -r https://block-extractor-testnet-1052151659755.europe-west9.run.app -i 30 -b 100 --max-fetch-blocks 5000 --log.file.directory ./target/logs --datadir ./target/reth

You can query the node using the JSON-RPC API. For example, to get the block number, you can use the following command:

curl -X POST -H 'content-Type: application/json' --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' http://localhost:8080

Optional arguments

  • send-raw-transaction-rpc-url: If provided, every eth_sendRawTransaction will be forwarded to this URL. When not provided, the rpc_url will be used instead as forwarding URL.

Running the node with Docker

You can locally build the docker image by using the provided docker-compose.yml file

docker compose build

Then to start it:

docker run -d -p 8080:8080 bitfinity/reth node --http.port 8080 --http.addr 0.0.0.0 --http.api "debug,eth,net,trace,txpool,web3" --disable-discovery --ipcdisable --no-persist-peers -r https://testnet.bitfinity.network -i 15 -b 1000

Alternatively, you can use the prebuilt Docker image from ghcr.io:

docker run ghcr.io/bitfinity-network/bitfinity-reth:main node --http.port 8080 --http.addr 0.0.0.0 --http.api "debug,eth,net,trace,txpool,web3" --disable-discovery --ipcdisable --no-persist-peers -r https://testnet.bitfinity.network

Reset the EVM canister state

You can use the current node state to reset the state of an EVM canister. By the end of this process, the EVM canister will have the same state root and last block as the Reth node.

Preconditions: The IC account must have admin rights on the EVM canister.

To execute the reset command, follow these steps:

  1. Shut down the reth node.

  2. Disable the EVM canister:

dfx canister --network=ic call EVM_CANISTER_ID admin_disable_evm '(true)'
  1. Run the EVM reset command. For example:
cargo run -p reth -- bitfinity-reset-evm-state -vvv --datadir ./target/reth --ic-identity-file-path PATH_TO_IDENTITY/identity.pem --evm-network https://ic0.app --evmc-principal EVM_CANISTER_ID --evm-datasource-url https://evm-testnet-block-extractor-app-hvnsf.ondigitalocean.app/
  1. Enable the EVM canister:
dfx canister --network=ic call EVM_CANISTER_ID admin_disable_evm '(false)'