by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 23:01
    mratsim synchronize #1491
  • 23:01

    mratsim on switch-blst

    Use unified aggregation API (compare)

  • 23:00
    nbc-bump-bot[bot] synchronize #1484
  • 23:00

    nbc-bump-bot[bot] on nim-libp2p-auto-bump

    auto-bump nim-libp2p (compare)

  • 21:27
    dryajov synchronize #1474
  • 21:27

    dryajov on rework-pubsub

    use split out pubsub update inspector build bump libp2p and 1 more (compare)

  • 21:25
    dryajov synchronize #1474
  • 21:25

    dryajov on rework-pubsub

    fix merge issues (compare)

  • 21:17
    dryajov synchronize #1474
  • 21:17

    dryajov on rework-pubsub

    split subscribe into non-valida… Update issue templates (#1488) … share validator keys in EpochRe… (compare)

  • 20:24
    mratsim opened #1491
  • 20:17
    tersec commented #1486
  • 20:14
    arnetheduck commented #1486
  • 20:09

    mratsim on switch-blst

    Bump BLSCurve (compare)

  • 20:05
    tersec commented #1486
  • 19:46
    arnetheduck synchronize #1489
  • 19:46

    arnetheduck on balance-cache

    avoid rewind in fork choice app… (compare)

  • 19:39

    arnetheduck on share-epochref-keys

    (compare)

  • 19:39

    arnetheduck on devel

    share validator keys in EpochRe… (compare)

  • 19:39
    arnetheduck closed #1486
Autobot
@status-im-auto
SrAylr@discord: soz again
SrAylr@discord: > Hey guys is there a guide to running nimbus in docker anywhere?
@PeanutPete https://docs.teku.pegasys.tech/en/latest/HowTo/Get-Started/Run-Docker-Image/
SrAylr@discord: > Hey guys is there a guide to running nimbus in docker anywhere?
@PeanutPete https://docs.teku.pegasys.tech/en/latest/HowTo/Get-Started/Run-Docker-Image/ I'm bad at links.
Autobot
@status-im-auto
PeanutPete@discord: Hehe no worries at all man 🙂 I'm in the same boat. Setting them all up, had them all running on metal but moving them all to docker so it's easier to spin up another instance for a bit of fun
PeanutPete@discord: Nimbus is the only one I've not got around to yet, I saw the docker file in git so hopefully can figure it out, just thought would save time and ask just incase there was a guide already
PeanutPete@discord: I'm loving it, 4 of them all running in docker compose with grafana dashboards for them all, just need to make my own aggregated dashboard once they are all working.
tersec@discord: I don't think we're officially supporting Docker deployments. It's on the radar as something people want. The Docker file in Git is used to run CI instances.
PeanutPete@discord: Cheers tersec, can understand it's not a priority for something that's designed to run on embedded things 🙂
PeanutPete@discord: Cheers tersec, can understand it's not a priority for something that's designed to run on embedded / low spec things 🙂
SrAylr@discord: Good to know. I'm just trying to get them all working first. Gotta collect those POAPs. Teku and Lodestar validators activate in a couple days (epoch 2100 or so).
SrAylr@discord: Once things work I might try making everything super neat and tidy for myself
Autobot
@status-im-auto
PeanutPete@discord: Yea the poaps turned out to be a major incentive in this whole thing
SrAylr@discord: yup
SrAylr@discord: I'm still salty I missed the r/ethstaker launch party poap cuz I fell asleep 10 mins early
SrAylr@discord: but these are more important
PeanutPete@discord: Like to be honest you could just cheat and put the poap in for another client but it's more fun to actually get them working 😛
PeanutPete@discord: I got the launch party one 😛
SrAylr@discord: I considered that but I assumed it wouldn't work
PeanutPete@discord: I don't see how it would not as the only thing they have to go on is the graffiti tag
PeanutPete@discord: reckon if you used the same keys with multiple tags you would get snaffled tho
SrAylr@discord: I know you can move a validator to a different client no issues.
SrAylr@discord: So since I've got my lighthouse poap done I'm temporarily moving it to prysm so I have a better chance of getting that poap
PeanutPete@discord: I really think all the clients need to standardise the keystore / password management
PeanutPete@discord: it's a pain they way they are all different
PeanutPete@discord: in the case of a client issue you want to be able to swap your keys over to a new client right and quickly without having to through an import process
SrAylr@discord: yeah that's fair. I assume that will be a little closer to reality once everything is actually stable. Perhaps closer to phase 0.
PeanutPete@discord: but all the folder structures / password management mechanisms are slightly different so it's not just a matter of moving you keys to a different folder
SrAylr@discord: yeah you need to do a different import process for each client
PeanutPete@discord: yea, it's obviously not a priority for the teams right now
SrAylr@discord: I prefer functionality first 🙂
tersec@discord: Yes, well, https://github.com/status-im/nim-beacon-chain/#prerequisites-for-everyone currently documents how to set this up, and https://github.com/status-im/nim-beacon-chain/#connecting-to-testnets shows how to connect to Medalla.
PeanutPete@discord: but would be nice if there was just a standard key management folder structure all the clients agreed upon
Autobot
@status-im-auto
PeanutPete@discord: yea, it's cool tarsec. it's not hard to do or anything
PeanutPete@discord: all i am saying is that a standard adopted between the clients would make migration in the case of an issue with one client a lot easier
SrAylr@discord: That's for the people who need a more "user-friendly" experience. For now I'm happy fighting for POAPs
PeanutPete@discord: hehe 🙂 yup and setting up dashboards 😛
SrAylr@discord: 👍
Autobot
@status-im-auto
loudsubaruguy@discord: I'm having some trouble using the command line options for the beacon_node. Bare with me as I'm pretty new to this stuff. i have nimbus syncing with the medalla network and my validator should be active here in a few hours. However, for the life of me I can't get beacon_node commands to work. Does the beacon need to not be running to run those codes?
stefantalpalaru@discord: What are you executing?
Autobot
@status-im-auto
loudsubaruguy@discord: from within the nim-beacon-chain directory i try to run ./beacon node --help and i get beacon_node: command not found
loudsubaruguy@discord: to be fair if i try to run any command i end up with the same error. i've also attempted it inside nim-beacon-node/beacon-chain with the same result
loudsubaruguy@discord: also ran it beacon_node --help without ./ prior and same thing
Autobot
@status-im-auto
stefantalpalaru@discord: The binary is in ./build/beacon_node
stefantalpalaru@discord: Now, what are trying to change in make medalla?
stefantalpalaru@discord: Now, what are you trying to change in make medalla?
stefantalpalaru@discord: The binary is ./build/beacon_node
loudsubaruguy@discord: Thank you very much!! i got it to output --help. I wanted to make sure the wallet was setup correctly. and check the ports to make sure i allowed the correct ones
stefantalpalaru@discord: You can see the default ports in the top-level Makefile: https://github.com/status-im/nim-beacon-chain/blob/543cbdfc6b9bc16f0331df2797422b7dc4d61eeb/Makefile#L19
loudsubaruguy@discord: Thanks for the help!
stefantalpalaru@discord: You're welcome.