Nimbus ethereum client, More channels on discord: https://discord.gg/XRxWahP
Suicida95@discord: Hi, im trying to sync to kiln using nimbus and geth using the guide in here: https://nimbus.guide/kiln.html#22g-start-the-client
Suicida95@discord: However the geth node is stuck on block 55k (which is when kiln merged i think) and nimbus is stuck on 8% for hours
Suicida95@discord: anything Im doing wrong?
dec3ntraliz3d@discord: I am currently syncing my beacon chain node. It's taking a while so wanted to sync from a trusted node. I wanted to check if my steps are correct. 1. Stop nimbus services 2. Start nimbus trusted node sync using
build/nimbus_beacon_node trustedNodeSync --network:mainnet \
--data-dir=build/data/shared_mainnet_0 \
--trusted-node-url=<my_trusted_node_infura> 3. wait for sync to finish from trusted node. 4. Start nimbus service .
dec3ntraliz3d@discord: I am currently syncing my beacon chain node. It's taking a while so wanted to sync from a trusted node. I wanted to check if my steps are correct. 1. Stop nimbus services 2. Start nimbus trusted node sync using
build/nimbus_beacon_node trustedNodeSync --network:mainnet \
--data-dir=/var/lib/nimbus
\
--trusted-node-url=<my_trusted_node_infura> 3. wait for sync to finish from trusted node. 4. Start nimbus service .
zahary@discord: The steps you listed are correct and step 3 can be considered optional. The backfilling process takes some time, but you can interrupt it at will. It will continue once you restart the Nimbus service in step 4. In fact, many users prefer to run
trustedNodeSync --backfill=false which will result in step 3 taking just few seconds
mratsim@discord: There is a common BN + VC separation API that clients support and can use for interop and Prysm has also their own Prysm only grpc base API.
Looking at their docs here: https://docs.prylabs.network/docs/prysm-usage/parameters/
I think the first 2 options are what should match Nimbus RPC options
https://cdn.discordapp.com/attachments/613988663034118153/969476774708801557/unknown.png
lilok@discord: @mratsim Yes, i already have a prysm validator client connected to a remote beacon node via grpc. So from your answer i can understand that grpc is a non ethereum standard clients interconnection protocol, or maybe the future standard protocol. I saw that in Nimbus i can activate rpc server with --rpc Enable the JSON-RPC server but why is it marked as (deprecated) ? Thanks
mratsim@discord: Somehow thr discoversbility is strangr but the standard is REST: https://docs.prylabs.network/docs/1.x.x/how-prysm-works/ethereum-public-api/
mratsim@discord: Somehow the discoverability is strange but the standard is REST: https://docs.prylabs.network/docs/1.x.x/how-prysm-works/ethereum-public-api/
tharda@discord: hey there 🙂 I am trying to use checkpoint sync but I am unable to do so, I keep getting this
its a raspberry PI
pi@raspi:~/nimbus_checkpoint_sync $ nimbus-eth2/build/nimbus_beacon_node trustedNodeSync --network:mainnet --data-dir=build/data/shared_mainnet_0 --trusted-node-url=http://X.X.X.X:5051
nimbus_beacon_node does not accept arguments
Try nimbus_beacon_node --help for more information.this is version 1.6.0, any ideas?
Thanks!
arnetheduck@discord: 1.6.0 did not yet support checkpoint sync, you need a newer version (latest recommended): https://nimbus.guide/trusted-node-sync.html
tharda@discord: Cant I set the metrics listen address?
```Unrecognized option 'metrics'
```Unrecognized option 'metrics'
```--metrics --metrics-address=0.0.0.0
tharda@discord: it hanged here
NOT 2022-05-03 18:36:05.265+02:00 Starting trusted node sync databaseDir=/home/pi/.cache/nimbus/BeaconNode/db restUrl=http://139.99.75.0:5051 blockId=finalized backfill=true
INF 2022-05-03 18:36:05.547+02:00 Writing genesis state stateRoot=7e76880e genesis_validators_root=4b363db9
INF 2022-05-03 18:36:14.753+02:00 Writing genesis block blockRoot=4d611d5b blck="(slot: 0, proposer_index: 0, parent_root: \"00000000\", state_root: \"7e76880e\", eth1data: (deposit_root: 0000000000000000000000000000000000000000000000000000000000000000, deposit_count: 0, block_hash: 0000000000000000000000000000000000000000000000000000000000000000), graffiti: \"\", proposer_slashings_len: 0, attester_slashings_len: 0, attestations_len: 0, deposits_len: 0, voluntary_exits_len: 0, sync_committee_participants: -1)"
NOT 2022-05-03 18:36:15.391+02:00 Downloading checkpoint block restUrl=http://139.99.75.0:5051 blockId=finalized
NOT 2022-05-03 18:36:16.174+02:00 Downloading checkpoint state restUrl=http://139.99.75.0:5051 checkpointSlot=3730912
INF 2022-05-03 18:36:27.953+02:00 Writing checkpoint state
tharda@discord: it hanged here
NOT 2022-05-03 18:36:05.265+02:00 Starting trusted node sync databaseDir=/home/pi/.cache/nimbus/BeaconNode/db restUrl=http://X.X.X.X:5051 blockId=finalized backfill=true
INF 2022-05-03 18:36:05.547+02:00 Writing genesis state stateRoot=7e76880e genesis_validators_root=4b363db9
INF 2022-05-03 18:36:14.753+02:00 Writing genesis block blockRoot=4d611d5b blck="(slot: 0, proposer_index: 0, parent_root: \"00000000\", state_root: \"7e76880e\", eth1data: (deposit_root: 0000000000000000000000000000000000000000000000000000000000000000, deposit_count: 0, block_hash: 0000000000000000000000000000000000000000000000000000000000000000), graffiti: \"\", proposer_slashings_len: 0, attester_slashings_len: 0, attestations_len: 0, deposits_len: 0, voluntary_exits_len: 0, sync_committee_participants: -1)"
NOT 2022-05-03 18:36:15.391+02:00 Downloading checkpoint block restUrl=http://139.99.75.0:5051 blockId=finalized
NOT 2022-05-03 18:36:16.174+02:00 Downloading checkpoint state restUrl=http://139.99.75.0:5051 checkpointSlot=3730912
INF 2022-05-03 18:36:27.953+02:00 Writing checkpoint state
tharda@discord: it hanged here
NOT 2022-05-03 18:36:05.265+02:00 Starting trusted node sync databaseDir=/home/pi/.cache/nimbus/BeaconNode/db restUrl=http://X.X.X.X:5051 blockId=finalized backfill=true
INF 2022-05-03 18:36:05.547+02:00 Writing genesis state stateRoot=7e76880e genesis_validators_root=4b363db9
INF 2022-05-03 18:36:14.753+02:00 Writing genesis block blockRoot=4d611d5b blck="(slot: 0, proposer_index: 0, parent_root: \"00000000\", state_root: \"7e76880e\", eth1data: (deposit_root: 0000000000000000000000000000000000000000000000000000000000000000, deposit_count: 0, block_hash: 0000000000000000000000000000000000000000000000000000000000000000), graffiti: \"\", proposer_slashings_len: 0, attester_slashings_len: 0, attestations_len: 0, deposits_len: 0, voluntary_exits_len: 0, sync_committee_participants: -1)"
NOT 2022-05-03 18:36:15.391+02:00 Downloading checkpoint block restUrl=http://X.X.X.X:5051 blockId=finalized
NOT 2022-05-03 18:36:16.174+02:00 Downloading checkpoint state restUrl=http://X.X.X.X:5051 checkpointSlot=3730912
INF 2022-05-03 18:36:27.953+02:00 Writing checkpoint state
tharda@discord: oh okay, I believe it is now synced and it starts backfilling
INF 2022-05-03 18:39:32.417+02:00 Backfilling timeleft=02d10h21m slotsPerSecond=17.75988633672744 remainingSlots=3730687
INF 2022-05-03 18:39:45.595+02:00 Backfilling timeleft=03d13h20m slotsPerSecond=12.14345257941412 remainingSlots=3730601
INF 2022-05-03 18:39:58.326+02:00 Backfilling timeleft=04d03h53m slotsPerSecond=10.3733604692167 remainingSlots=3730514
INF 2022-05-03 18:40:11.027+02:00 Backfilling timeleft=04d12h42m slotsPerSecond=9.531988855849532 remainingSlots=3730425
INF 2022-05-03 18:40:23.268+02:00 Backfilling timeleft=04d20h00m slotsPerSecond=8.93267383935653 remainingSlots=3730345
tharda@discord: is it possible to disable the backfilling? I just want to test how what is the performance of the client once synced
firebredd@discord: Hi guys, I'm new to Nimbus, I've some questions.
- Can we run a nibus excecution node and consensus node with the help of docker? rather than downloading and installing the binaries.?
- If yes what is the stable or latest version of the docker image for the Nimbus?
- Can someone send me the documentation how do we make use of docker to run Nimbus execution layer client and consensus client?
firebredd@discord: Hi guys, I'm new to Nimbus, I've some questions.
- Can we run a nibus consensus node with the help of docker? rather than downloading and installing the binaries.?
- If yes what is the stable or latest version of the docker image for the Nimbus?
- Can someone send me the documentation how do we make use of docker to run Nimbus execution layer client and consensus client?
mratsim@discord: The EL client is not ready for prime-time yet.
Mkkoll@discord: Ive already got a mainnet prysm validator and beacon node set up so im not unfamiliar with CLI staking
Mkkoll@discord: Could anybody point me to any guides on how to setup for nimbus on one of the testnet merges?
andrewrobbins@discord: Hey everyone. I've finished setting up Nimbus and importing my validator keys. However my
https://cdn.discordapp.com/attachments/613988663034118153/976589678943809556/Screen_Shot_2022-05-18_at_3.58.27_PM.png
nextActionWait value is saying n/a. What am I doing wrong?https://cdn.discordapp.com/attachments/613988663034118153/976589678943809556/Screen_Shot_2022-05-18_at_3.58.27_PM.png
firebredd@discord: Hi, I'm running goerli geth as my eth1 client using this command:docker run -it -d -v /home/ec2-user/.geth:/root -p 8545:8545 -p 30303:30303 --name geth-node --net=host ethereum/client-go:v1.10.15 --datadir=/root --http --http.port=8545 --http.addr=0.0.0.0 --http.vhosts=* --http.api=eth,net,web3,personal --goerli
The Node is running perfectly fine and is now SYNCING
Now I'm running Nimbus Beacon and Validator Node as my eth2 client, where I'm getting this error
Eth1 chain monitoring failure, restarting topics="eth1" err="getBlockByHash(m.dataProvider,\n BlockHash(m.depositsChain.finalizedBlockHash.data)) failed 3 times. Last error: Failed to send POST Request with JSON-RPC."
But the beacon node is syncing properly, is the error is because of the geth which is not completely synced?
You can see the logs in the snapshot attached.
https://cdn.discordapp.com/attachments/613988663034118153/976764603105181696/Screenshot_2022-05-19_at_2.02.51_PM.png