Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Age Manning
    @AgeManning
    Probably should point out, a validator cannot just come along and produce blocks. They need to deposit eth on the eth1 chain and then wait for the global chain to accept and activate them as a validator before they can start participating in the network (all beacon nodes) will know they are validator before they can start doing anything
    James Zaki
    @jzaki
    @michaelsproul thanks for linking the spec issue 1269 with #407, might be a good first issue for me though. Will keep an eye on it for next week :thumbsup:
    Michael Sproul
    @michaelsproul
    I'm kind of hopeful that we get to keep the next epoch cache! But yeah, keep an eye on it and there will likely be something you can work on out of that :)
    James Zaki
    @jzaki
    aaand, It's out -> https://medium.com/@james.zaki/eth2-0-phase-0-basics-for-new-contributors-8a0a22bc38c7
    Let me know what you think :)
    Looking forward to focusing on code/issues next week :D
    Age Manning
    @AgeManning
    ^^ nice!! Well done
    James Zaki
    @jzaki
    Thanks mate đź‘Ť
    gzuhlwang
    @gzuhlwang
    hi, guys. I fix good first issue #421.
    Age Manning
    @AgeManning
    Thanks for the input! We'll review it today :)
    Diederik Loerakker
    @protolambda
    If someone has the time (and online :earth_asia: ), could you please take a look at ethereum/eth2.0-specs#1311 and send me a survey response? (or just a few suggestions, anything helps)
    John Adler
    @adlerjohn
    When building with --all-targets (i.e., cargo build --all-targets) I get a bunch of errors, that don't pop up without that flag. Are those expected?
    Paul Hauner
    @paulhauner
    Yeah, it’s probably some benches failing. We’ll clean those up soon :)
    Paul Hauner
    @paulhauner
    We've just merged v0.8.1 into master! Yay!
    I'm going fix those --all-release issues :)
    Paul Hauner
    @paulhauner
    Hey all, following suit from the EF, we now have a Discord! https://discord.gg/cyAszAh
    We'll setup a bridge at some point, for the time being I'll watch both of these but I recommend using the Discord instead.
    Diederik Loerakker
    @protolambda
    Awesome
    rytikovroman1994
    @rytikovroman1994
    Hello everyone, I have a problem.
    lighthouse does not work well in the cycle.
    Checks one link, and already on the second strongly to slow down.
    Someone faced with such problem?
    image.png
    image.png
    Paul Hauner
    @paulhauner
    Hey, I think you might have the wrong lighthouse. This one is an Ethereum 2 implementation
    rytikovroman1994
    @rytikovroman1994
    what do you mean?
    did I set something wrong? Or not the chat?
    Diederik Loerakker
    @protolambda
    What you are looking for is https://developers.google.com/web/tools/lighthouse/
    What this project is: https://github.com/sigp/lighthouse
    thojest
    @thojest
    congrats for receiving grant :)
    Paul Hauner
    @paulhauner
    Thanks @thojest!!
    Andrew Quentson
    @Aquentson_twitter
    Hi, are we expecting an eth2 testnet launch this week?
    Age Manning
    @AgeManning
    We are debugging and experimenting interoperability between clients. There are a number of stages to this. It's unclear if a long standing multiclient testnet will be made at the moment
    Paul Hauner
    @paulhauner
    [for the record: inapproriate comments were reported and are no longer visible]
    Andrew Quentson
    @Aquentson_twitter
    Hi, are we expecting the testnet to launch anytime soon? Sounds like next month at best now?
    Age Manning
    @AgeManning
    By "the testnet", I assume you are talking about a long lived public multi client testnet? If so, yes. We will be doing some internal multi client testnets before then
    Andrew Quentson
    @Aquentson_twitter
    Hi, just saw the latest update, is that referring to the multi-client public testnet? As in the final stage before launch @AgeManning
    and this will be out next week?
    Age Manning
    @AgeManning
    This is referring to our single client public testnet. We will be on boarding other clients as it progresses
    Max Johansen
    @macsj200
    Hello all, I'm trying to sync the lighthouse docker image, but I'm having trouble discovering peers
    Age Manning
    @AgeManning
    The old testnet is down. We will be updating the docker soon for the new testnet.
    We are more active in our discord server, so you'll get faster responses there for future issues
    Andrew Quentson
    @Aquentson_twitter
    So have you guys gone to discord now or somewhere else @AgeManning ?
    Was also wondering how that 100k testnet is progressing?
    Naeim Ahmed
    @naeim249
    How to do i update my profiles
    JosefJ
    @JosefJ
    Dumb question: Does anyone have a hint for a parameter to set a remote Eth1 RPC when starting the client?
    Diederik Loerakker
    @protolambda
    --help shows everything
    But for real help, try the lighthouse discord
    The gitter is very inactive
    boomerango
    @boomerango
    Hi guys, I am running lh programatically, it ok on local machine but I need to make it work on a remote. Does lh accept something like an endpoint in order to pass the full url? the url to connect to a remote looks like : hostname:port/devtools/${browser.sessionId}/
    George Carder
    @georgercarder

    Hi I am encountering an error when I run lighthouse vc --testnet medalla

    According to msg board posts I have seen, this error is supposed to be routine/expected before genesis, but it is now after genesis. Does anyone know how to resolve this issue?
    the error:
    Sep 29 12:15:02.463 ERRO Unable to connect to beacon node error: "ReqwestError(reqwest::Error { kind: Request, url: \"http://localhost:5052/node/version\", source: hyper::Error(Connect, ConnectError(\"tcp connect error\", Os { code: 111, kind: ConnectionRefused, message: \"Connection refused\" })) })"

    Nicolò Paternoster
    @adv0r
    Hi everyone! Good night!
    I'm running a validator on a raspberry using lighthouse for beacon and validator. The thing is pretty stable 24/7 online, with power monitoring wired ether connection and optic fiber. Still, my node missed all the "blocks proposals", despite getting most of attestations
    https://beaconcha.in/validator/5377
    The last missed block was 1d ago, and in the same period of time, it was getting attestations as you can see. So I have two questions:
    a. howcome my node has many missed attestations anyway, despite being online 24/7 in the last 15 days?
    b. howcome did it missed yesterday's block proposal?