Error running a fuel-core test node on an ARM64 board

Fuel Network
1

Hi.

I tried to run fuel-core (official binary 0.36.0) on an ARM64 board (Rock 5B) following this guide:

I getting this error:

Error: InvalidMnemonic

This is the command I ran:

fuel-core run --service-name=fuel-sepolia-testnet-node \
--keypair /home/ethereum/fuel_p2p.txt --relayer http://localhost:8545 \
--ip=0.0.0.0 --port=4000 --peering-port=30333 \
--db-path=/home/ethereum/.fuel-sepolia-testnet \
--snapshot /home/ethereum/chain-configuration/ignition-test \
--utxo-validation --poa-instant false --enable-p2p \
--reserved-nodes /dns4/p2p-testnet.fuel.network/tcp/30333/p2p/16Uiu2HAmDxoChB7AheKNvCVpD4PHJwuDGn8rifMBEHmEynGHvHrf \
--sync-header-batch-size 100 --enable-relayer \
--relayer-v2-listening-contracts=0x01855B78C1f8868DE70e84507ec735983bf262dA \
--relayer-da-deploy-height=5827607 --relayer-log-page-size=500 \
--sync-block-stream-buffer-size 30

I synced a Sepolia node on the Rock 5 and compiled fuel-core natively to discard a crosscompilation issue as well.

Let me know if you need more info or any action from my side.

Thanks!

2

Hi @diegolosada,

I think it may be the --keypair argument you’re using. Are you able to use the inline --keypair <secretkey> locally to see if that works?

If that works, then I think I know what the problem is and we’ll have to rework how --keypair is implemented.

NOTE: although it’s only the testnet, DO NOT paste online - this is only for your local testing.

3

Yes, that was it, --keypair with the secret key in HEX.

Working now.

Thanks!!!

1 Like
4

Excellent, thanks. I’ll create an Issue to get that fixed.

5

I’m getting this now (stuck with this):

2024-09-28T10:44:03.600403Z ERROR new{name=fuel-sepolia-testnet-node}:initialize_loop{service="P2P"}: fuel_core_p2p::peer_report: 164: Dial failure: peer id Some(PeerId(“16Uiu2HAmDxoChB7AheKNvCVpD4PHJwuDGn8rifMBEHmEynGHvHrf”))with errorFailed to negotiate transport protocol(s): [(/dns4/p2p-testnet.fuel.network/tcp/30333/p2p/16Uiu2HAmDxoChB7AheKNvCVpD4PHJwuDGn8rifMBEHmEynGHvHrf: : Handshake failed: Handshake failed: Handshake failed: Protocol negotiation failed.)]`

Is it possible that it is only getting the private key but not the peer_id in the --keypair flag?.

6

Usually this error means an incorrect snapshot. can you please confirm you are using the updated chain config?

1 Like
7

Yes, wrong config dir (ignition instead of ignition-test).

Now everything seems fine.

Thanks again!

1 Like