Nimbus ethereum client, More channels on discord: https://discord.gg/XRxWahP
Rémy Roy@discord: I'm moving out of the dark room. I'll be just outside near the door.
tersec@discord: debugging something that came up
tersec@discord: black and white flannel
mratsim@discord: There is currently an infura outage, if you use Infura, keep track of this webpage, you will not be able to propose blocks but attestation production is not impacted https://status.infura.io/
dec3ntraliz3d@discord: Guys quick question. Does this mean the consensus layer node is still syncing or the execution layer node? My nimbus node is pointed to local geth node ( same host) .
Syncing in progress; skipping validator duties for now topics="beacval" slot=2847469 headSlot=207113
dec3ntraliz3d@discord: Thanks . Looks like I need to wait 2 more days .
sync="01d23h28m (35.34%)
mratsim@discord: CL is still syncing
Somer@discord: Hi Nimbus team - is anyone available over the next couple of days to take a quick look at a basic analysis I've done between Nimbus and Prysm for a guide I'm working on with Danny Ryan? There are a few interesting differences I need an expert interpretation on.
arnetheduck@discord: This is being discussed in the community right now: https://ethereum-magicians.org/t/og-council-post-merge-testnets/9034
arnetheduck@discord: if you have access to a trusted node, there's a faster way to get started: https://nimbus.guide/trusted-node-sync.html
Somer@discord: Friend request sent.
inadyttap@discord: is there a risk of dynamically switching my network connection while my validator is active? my internet provider has gone down a couple of times last couple of weeks and when it happens i switch my validator network connection to a wifi tether to my smartphone's mobile connection.
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