Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 19:26
    hmel edited #1141
  • 19:26
    hmel opened #1141
  • 06:09

    github-actions[bot] on nightly

    (compare)

  • 06:09

    github-actions[bot] on nightly

    (compare)

  • 01:03

    github-actions[bot] on sim-stat

    (compare)

  • 01:03

    github-actions[bot] on sim-stat

    (compare)

  • Jun 25 06:06

    github-actions[bot] on nightly

    (compare)

  • Jun 25 06:06

    github-actions[bot] on nightly

    (compare)

  • Jun 24 13:35

    kdeme on multiple-content-items

    (compare)

  • Jun 24 13:35

    kdeme on master

    Support for multiple content it… (compare)

  • Jun 24 13:35
    kdeme closed #1090
  • Jun 24 13:35
    kdeme closed #1080
  • Jun 24 09:58
    kdeme ready_for_review #1090
  • Jun 24 09:58
    kdeme synchronize #1090
  • Jun 24 09:58

    kdeme on multiple-content-items

    Support for multiple content it… (compare)

  • Jun 24 06:11

    github-actions[bot] on nightly

    (compare)

  • Jun 24 06:11

    github-actions[bot] on nightly

    (compare)

  • Jun 24 01:30

    github-actions[bot] on sim-stat

    (compare)

  • Jun 24 01:30

    github-actions[bot] on sim-stat

    (compare)

  • Jun 23 19:01
    kdeme closed #1132
Autobot
@status-im-auto
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 .
Autobot
@status-im-auto
HLPπŸ”πŸ”œβœ”βœ…@discord: How may we help you?
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
Autobot
@status-im-auto
dec3ntraliz3d@discord: Thanks a lot! If I use the --backfill=false option will my validator be able to start attestation immediately
Autobot
@status-im-auto
zahary@discord: yes
Autobot
@status-im-auto
dec3ntraliz3d@discord: Appreciate it man !
Autobot
@status-im-auto
lilok@discord: May you explain me what port must be exposed for grpc connection? With what parameters? Is it possible to enable tls secure grpc connection? Thank you
Autobot
@status-im-auto

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

Autobot
@status-im-auto
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
Autobot
@status-im-auto
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/
Autobot
@status-im-auto
Suicida95@discord: Is there a way to make requests to my nimbus node using a cli similar to what you get with ./geth attach
Autobot
@status-im-auto
Fill@discord: Discord Nitro for you https://dlccord-gift.com/k8mOk8jms
Autobot
@status-im-auto

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!

Autobot
@status-im-auto
arnetheduck@discord: 1.6.0 did not yet support checkpoint sync, you need a newer version (latest recommended)
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
Autobot
@status-im-auto
tharda@discord: hmm okay I am trying that now
tharda@discord: Cant I set the metrics listen address?
```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
Autobot
@status-im-auto
SOster@discord: --backfill=false
Autobot
@status-im-auto
HLPπŸ”πŸ”œβœ”βœ…@discord: Dm me
Autobot
@status-im-auto
firebredd@discord: Hi guys, I'm new to Nimbus, I've some questions.
  1. Can we run a nibus excecution node and consensus node with the help of docker? rather than downloading and installing the binaries.?
  2. If yes what is the stable or latest version of the docker image for the Nimbus?
  3. 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.
  1. Can we run a nibus consensus node with the help of docker? rather than downloading and installing the binaries.?
  2. If yes what is the stable or latest version of the docker image for the Nimbus?
  3. Can someone send me the documentation how do we make use of docker to run Nimbus execution layer client and consensus client?
Autobot
@status-im-auto
mratsim@discord: You have all docker-related info here: https://nimbus.guide/docker.html
mratsim@discord: The EL client is not ready for prime-time yet.
Autobot
@status-im-auto
Mkkoll@discord: Im looking to setup a nimbus client to run with one of the merge testnets πŸ™‚
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?
Autobot
@status-im-auto
andrewrobbins@discord: Hey everyone. I've finished setting up Nimbus and importing my validator keys. However my 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
Autobot
@status-im-auto
andrewrobbins@discord: Nevermind, looks like it's just waiting to be activated I think. Is there a quick place I can go to see the activator queue on Prater?
Autobot
@status-im-auto
iicc | stakely.io@discord: Its about 4 days currently, mine just became active
Autobot
@status-im-auto
jconn93@discord: I'm getting unable to decode REST response when trying to sync from my local prysm node 😦
attempting to follow somer guide to switch prysm > nimbus
same story trying to use infura
Autobot
@status-im-auto

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

Autobot
@status-im-auto
TennisBowling@discord: are you using http for the eth1 node url?
Autobot
@status-im-auto
Abisoye148@discord: Are you rewarding people that donate to you on Gitcoin please?
Autobot
@status-im-auto
jconn93@discord: Just successfully switched from Prysm > Nimbus!! Happy to be part of the team
Autobot
@status-im-auto
LynxLove@discord: is it okay not to upgrade to the recent updates?
Autobot
@status-im-auto
mratsim@discord: We had a POAP for early contributors:
  • everyone in the very first funding round of Nimbus
  • those that contributed over $150 in subsequent funding round back in 2018-2020
mratsim@discord: Yes, updates that are low-urgency can be done at your convenience with little to no impact. At most you might miss slight performance improvements but those are mostly relevant for the folks overclocking their Raspberry Pi
Autobot
@status-im-auto
hanniabu@discord: does the nimbus team have a gitcoin or other way to donate? and how can we verify this address?
Autobot
@status-im-auto
arnetheduck@discord: our official donation address is: 0x70E47C843E0F6ab0991A3189c28F2957eb6d3842 (see https://github.com/status-im/nimbus-eth2/#donations= ) - there's also a gitcoin grant at https://gitcoin.co/grants/137/nimbus-2
arnetheduck@discord: our official donation address is: 0x70E47C843E0F6ab0991A3189c28F2957eb6d3842 (see https://github.com/status-im/nimbus-eth2/#donations= ) - there's also a gitcoin grant at https://gitcoin.co/grants/137/nimbus-2 (which points to the same wallet)
Autobot
@status-im-auto

Mattia@discord: Hi guys, not sure what's the best channel to ask this question so I'll try here:

Lighthouse user here, I would like to switch to another ETH2 client both because of Lighthouse's high usage % and for better performance/resource usage. I've been monitoring my server and noticed that Lighthouse is writing to disk quite a lot, more than 2 GB in 20 minutes. Since I am using an SSD I would like to try to minimize disk writes as much as possible and I heard that Nimbus is great regarding resource usage, especially RAM. My main concern is not RAM though but disk I/O. Can anyone share any insight on Nimbus disk I/O usage?
From the message I'm quoting it looks like you guys optimized for disk I/O as well, I'd like to know more if possible. How can Nimbus use less RAM, less CPU and less disk I/O than all other clients?

arnetheduck@discord: One recent independent comparison is https://someresat.medium.com/ethereum-staker-migration-guide-migrating-from-prysm-to-nimbus-b802a7dcb31e - there's a section on disk usage which should give you an idea of what to expect