hwwhww on test-py39
Try Python 3.9 env CircleCI py3โฆ (compare)
hwwhww on test-py39
install setuptools and kick cacโฆ (compare)
hwwhww on test-py39
install setuptools (compare)
hwwhww on test-py39
Try Python 3.9 env (compare)
hwwhww on dev
add eth1 withdrawal credentialsโฆ Fix table for withdrawal credenโฆ Cleaner section title "Withdraโฆ and 16 more (compare)
<Brian (lithp)> Hi everyone, I'm not sure where to ask this, hope this is the right place.
What's the plan deal with rational miners during the switchover from ETH1 -> ETH2. The coinbase isn't spendable for x blocks, so if miners believe that the transition is going to happen, then they believe that they have no way of spending any reward they get from mining the x blocks before the switchover to ETH2 happens, so won't they just stop mining?
<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
<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
<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?
<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.)
MUST
in the p2p spec as constraining clients to keep the signed block data
<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