Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 25 23:30
    ralexstokes synchronize #2201
  • Feb 25 19:26
    ralexstokes synchronize #2201
  • Feb 25 19:14
    ralexstokes synchronize #2201
  • Feb 25 19:12
    ralexstokes synchronize #2201
  • Feb 25 19:11
    ralexstokes synchronize #2201
  • Feb 25 19:10
    ralexstokes synchronize #2201
  • Feb 25 13:43
    mcdee commented #2213
  • Feb 25 13:39
    vshvsh commented #2213
  • Feb 25 09:23
    hwwhww commented #2214
  • Feb 25 07:53
    JustinDrake commented #2214
  • Feb 25 06:09
    hwwhww commented #2214
  • Feb 25 05:50

    hwwhww on test-py39

    Try Python 3.9 env CircleCI py3… (compare)

  • Feb 25 05:46

    hwwhww on test-py39

    install setuptools and kick cac… (compare)

  • Feb 25 05:32

    hwwhww on test-py39

    install setuptools (compare)

  • Feb 25 05:25

    hwwhww on test-py39

    Try Python 3.9 env (compare)

  • Feb 25 05:20
    ralexstokes synchronize #2201
  • Feb 25 01:46

    hwwhww on dev

    add eth1 withdrawal credentials… Fix table for withdrawal creden… Cleaner section title "Withdra… and 16 more (compare)

  • Feb 25 01:46
    hwwhww closed #2215
  • Feb 25 00:21
    lsankar4033 commented #2213
  • Feb 25 00:05
    djrtwo commented #2202
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<ralexstokes> @Brian (lithp) there are some more details in a proposal here: https://ethresear.ch/t/the-eth1-eth2-transition/6265
<ralexstokes> i think it depends on how extreme we want to change the eth1 protocol during a merge -- we could effectively pause the chain and do a bunch of "upgrades" when moving the state root under the eth2 consensus
<ralexstokes> i dont think the concern is miners stopping mining early (they should be able to generate block rewards through the last proof-of-work block) but more that miners could keep mining a fork of the proof-of-work chain in the event that they don't want to support the transition to eth2
<ralexstokes> i think it is generally accepted though that the norms in the community called "Ethereum" have planned on this transition since the beginning so i would put the probability of such fork (and esp one that sees a lot of use) pretty low
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<Brian (lithp)> Thanks @Adrian Sutton , you're right, I had thought Ethereum copied Bitcoin but you made me look at geth and the coinbase is indeed immediately spendable
Eth-Gitter-Bridge
@Eth-Gitter-Bridge

<Brian (lithp)> > i dont think the concern is miners stopping mining early (they should be able to generate block rewards through the last proof-of-work block) but more that miners could keep mining a fork of the proof-of-work chain in the event that they don't want to support the transition to eth2

Oh, they'll definitely do this! Won't they? If there's any chance that the transition won't go through they'll want to have been collecting rewards from the PoW chain, and there's no good way to punish them for trying

<ralexstokes> sure but hopefully we can keep our "chain pause" to a short period of time so that it becomes obvious that the transition was successful
<ralexstokes> so that miners can spin down hardware w/in some small number of blocks after the Last Block (TM)
<telegram bridge> SamWilsn
I mean, even if the transition succeeds, aren't miners incentivized to continue mining anyway? Ethereum Super Classic (TM)
<ralexstokes> it is possible that you may be able to contribute to the eth2 network as a state provider or even join as a validator and join the eth1x shard so that you aren't just suddenly jettisoned from the ecosystem/community after the Last Block (TM)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<ralexstokes> it is possible we will be stuck w/ ethcash (what i have been calling ethereum super classic) indefinitely
<ralexstokes> as eth2 enthusiasts it is somewhat on us to encourage a thorough migration to the new system once it is ready
<ralexstokes> w/ incentives if possible but moreover also via social coordination off chain, (e.g. historical norms to move to proof-of-stake, showing network stability w/ the new system, this kind of stuff)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<Adrian Sutton> It does make me wonder if a 2-way eth bridge and running ETH2 and ETH1 in parallel makes sense for a good while so people see just how much better ETH2 is and want to migrate. But part of being better is being able to utilise the existing ETH1 stuff so ETH1 winds up having to at least act like an ETH2 shard even if it's still PoW driven. And then it all gets weird and I see why people want to bundle ETH1 into a shard asap. 🙂
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<djrtwo> eth2 call in 13 hours
agenda: ethereum/eth2.0-pm#129
stream: https://www.youtube.com/watch?v=tLiMgFoG_vs
Eth-Gitter-Bridge
@Eth-Gitter-Bridge

<djrtwo> eth2 call in 35 minutes
zoom: https://ethereumfoundation.zoom.us/j/132793896

warning, I'm going to ask for biggest bottleneck, what you're doing to solve it, and open up others for comment/advice

Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<benjaminion> And mine 😀 https://hackmd.io/@benjaminion/SygoFBrVL
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<hsiao-wei (hwwhww)> ----- sorry to the telegram bridge ppl, I ruined the survey ----- try again:
[tentative indication survey 1] would you be interested in attending an eth2 teams lunch on March 6th in Paris? 👍 for def YES, 🤞 for interested but not 100% , 👎 for def NO
<hsiao-wei (hwwhww)> [tentative indication survey 2] would you be interested in attending an eth2 teams co-work day on March 6th in Paris? 👍 for def YES, 🤞 for interested but not 100% , 👎 for def NO
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<tkstanczak> would you please send an invitation to matilote#6205
<tkstanczak> he is a DevOps person at Nethermind
<herman> Right click on the Eth 2.0 logo in the app, then "Invite People"
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<tkstanczak> thanks, somehow I assumed I did not have permissions
Eth-Gitter-Bridge
@Eth-Gitter-Bridge

<Sebastian> Hi! is there going to be an ETHLondon group? I looked at this document: https://notes.ethereum.org/@protolambda/eth2_start

and I'm wondering if there is anything left to hack on after EthDenver?

Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<djrtwo> The hacks in that doc are fresh and wide open!
We had pretty limited engagement at ethdenver and would be super excited with anyone picking up any of those challenges
<Sebastian> Cool! 😃
<djrtwo> here is the description of the ethlondon eth2 bounties -- https://notes.ethereum.org/@djrtwo/ETHLondon-hacks
Pooja Ranjan
@poojaranjan
Ethereum 2.0 Implementers Call 34 Notes
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<proto> That doc is fully up to date, and you're welcome to hack on any of those challenges, or your own thing, @Sebastian 👏
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<djrtwo> networking call this Wednesday! Please add items in the comments on the agenda
ethereum/eth2.0-pm#131
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<hsiao-wei (hwwhww)> Hi, just send the Paris Lunch/Brunch invite RSVP to Eth2 implementers list! It seems some addresses are unavailable now. If you didn't get the mail and want to join, please DM me soon. :)
(RSVP deadline: TODAY, sorry!)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<hsiao-wei (hwwhww)> Hi, I just sent the Paris Lunch/Brunch invite RSVP to Eth2 implementers calls list! It seems some addresses are unavailable now. If you didn't get the mail and want to join, please DM me soon. :)
(RSVP deadline: TODAY, sorry!)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge

<sly> I can't find it in the spec, but I presume the intention is that clients keep a record of SignedBeaconBlock that they receive, so that they can respond to requests such as BeaconBlocksByRange.

The spec says clients must support the request, and respond if they have the requested signed blocks, but there is nothing in the spec that requires them to keep a record of signed blocks. (Fork Choice only requires a record of BeaconBlock, not the signed envelope.)

Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<ralexstokes> clients are generally going to persist any signed beacon blocks they see come off the wire (you could argue for dropping some of them but the naive thing is to just keep it all unless you detect there is an obvious dos or something...); i interpret the MUST in the p2p spec as constraining clients to keep the signed block data
<ralexstokes> and for things like state txn or fork choice you can just think about operating over a subset of this data anyway (aka chop off the signatures)
Eth-Gitter-Bridge
@Eth-Gitter-Bridge

<djrtwo> Networking call in about 13.5 hours
ethereum/eth2.0-pm#131

Top priority -- iron out how to use fork_version in planned forks, across chains, and other usecases. I have a proposal to start us off and we can go from there
Then we can get the last couple of PRs cleaned and merged

Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<djrtwo> Call in 20.
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<herman> Are we recording this call @djrtwo ?
Eth-Gitter-Bridge
@Eth-Gitter-Bridge
<djrtwo> I usually do, but havent posted them in the past due to lack of demand
<djrtwo> so I'll record again and share if people want
<djrtwo> which it seems you do ?
<herman> 👍
<herman> > so I'll record again and share if people want
If I qualify as "people" 😂
<djrtwo> call now!
<djrtwo> hmm, might need one more voice
<djrtwo> 😂
<herman> 😞