Mainnet Node Delay

Fuel Network
1

I am running a mainnet node locally, but it is consistently lagging about 2 blocks behind the public node (mainnet.fuel.network).
I am using default configs specified in the tutorial .

fuel-core run \
--enable-relayer \
--service-name fuel-mainnet-node \
--keypair {P2P_PRIVATE_KEY} \
--relayer {ETHEREUM_RPC_ENDPOINT} \
--ip=0.0.0.0 --port 4000 --peering-port 30333 \
--db-path ~/.fuel-mainnet \
--snapshot ./your/path/to/chain_config_folder \
--utxo-validation --poa-instant false --enable-p2p \
--bootstrap-nodes /dnsaddr/mainnet.fuel.network \
--sync-header-batch-size 100 \
--relayer-v2-listening-contracts=0xAEB0c00D0125A8a788956ade4f4F12Ead9f65DDf \
--relayer-da-deploy-height=20620434 \
--relayer-log-page-size=100 \
--sync-block-stream-buffer-size 30

I have checked the latest block height obtained from the chain_info() function of Rust SDK on both my node and the public node.
The time taken to retrieve the block height is about 5ms for the former and 200ms for the latter, so I don’t believe the execution time is affecting this.

My machine meets the hardware requirements sufficiently:
CPU: 16 Core
Memory: 128GB
Storage: 4TB

Are there any optional variable settings to resolve the delay?

2

Can you please share the output for the fuelup show command from the terminal? also, please sure that that chain config is updated to the latest.

3

Thanks for your reply.
I cloned the chain-configuration repository on the day of mainnet launch and specify the ignition directory as --snapshot.

The result of fuelup show is as follows

Installed toolchains

latest-x86_64-unknown-linux-gnu
mainnet-x86_64-unknown-linux-gnu (default)
testnet-x86_64-unknown-linux-gnu

active toolchain

mainnet-x86_64-unknown-linux-gnu (default)
forc : 0.66.2
- forc-client
- forc-deploy : not found
- forc-run : not found
- forc-crypto : not found
- forc-debug : not found
- forc-doc : not found
- forc-fmt : not found
- forc-lsp : not found
- forc-tx : not found
- forc-wallet : 0.11.0
fuel-core : 0.40.0
fuel-core-keygen : 0.40.0

fuels versions

forc : 0.66.9
forc-wallet : 0.66.9

4

I would also check your eth rpc endpoint and make sure you are not being rate limited there

1 Like
5

I have tried RPC node providers like Infura, Alchemy, and Blast, but the results were not singificantly different. The next possible cause could be network performance, but I have been running nodes on several networks and have not experienced delays like this. Currently, I am checking the configuration variables with fuel-core run --help and trying to modify some of them.