Eth2 progress update (as of 2/27/2021)
source|What's New in Eth2
source|
Top picks article recommended readingThe Final Part of Coogan Brennan's Personal Pledge Long March EssayYes, the article covered migrating his validators from AWS to Digital Ocean, saving some money. This whole series is great. Coogan is an excellent writer and I can attest that he has done his homework on every detail of his articles.
beacon chain
beacon chainThe decimal milestone was reached this week, and theActive validators have exceeded 100,000
. Developers are more than happy to see binary milestones, so let's have a party when we hit 131,072 validators.PyrmontMore importantly, the capacity of the mainnet is now approaching that of the testnet
capacity (currently 118,000 validators). Pyrmont is useful for stakers who want to test their setup on a network that approximates the actual network capacity, but development teams will want to test their clients on a much larger network to catch issues early. As discussed in this week's developer meeting, we are considering building a new, larger testnet as soon as possible. Just discussing how big the capacity should be.Another Milestone: The Highest Earning Validator Since Genesis Has Now EarnedA whole ETH——It is not bad to have such an income in less than three months. And the first to getone ETHThe lucky one is validator 11111. This verifier helped to propose2 forfeit reports, and proposed up to17 blocks
. And the best performing validator I run has only proposed 10 blocks so far, for a total gain of 0.9533 ETH.
In the absence of heated discussions at all, in fact, there was aspecificationspecification
Published, the first specification in four months.The only significant change is to add。
A new format for withdrawal vouchers
There is a reason for this. In the original design, Eth2 has a completely different address space from Eth1, and is secured by BLS keys instead of Eth1's current ECDSA keys. This is why the withdrawal mechanism is now via a BLS key pair, and the withdrawal certificate is a guarantee of this key pair. Unfortunately, this is not friendly to trustless staking pools, and hindered the launch of Rocket Pool in particular.
Slowly, the execution layer of Eth2 looks more and more like Eth1 today. Therefore, it is reasonable to now allow withdrawals from Eth1 addresses (accounts or contracts) directly using the old keys and wallets we are familiar with. Thankfully, the spec writers had the foresight to set up a versioning scheme for withdrawal vouchers. So now we have the original 0x00 version, and a 0x01 version that is compatible with the new Eth1. Of course, there will be some ways to use the original 0x00 version to withdraw funds to Eth1 addresses without requiring stakers to operate. We haven't decided on those methods yet, but we have time.Note that there is also a proposal to allow validators if neededTo adapt to the new scheme (not yet written into the specification).
tool
toolPaul HaunerThis week, some important developments in our shared infrastructure - the "date-to-slot converter" debate: Lighthouse'sJacekFirst on Twitter, then on NimbusAdrian Sutton, and finally Teku's
. This is really a lot of progress, and I think what we really need is a "slot-to-date converter". If there is a genius among readers who wants to challenge, you might as well give it a try.beaconcha.inAnother useful tool isBrowsers now offer multiple formats ofValidator income data download
. It took me a while to find it: Click on the "View Daily statistics" icon at the top of a validator's page, right after the title "Validator NNNN". Taxes are also included!
Upgrade 11。
Plans for the first Beacon Chain upgrade are being finalized. We plan to be able to deploy in June
Here are some relevant documents:fairly detailedcontent description
specificationspecification
update list
The changes are relatively minor, at least compared to later developments, but are still very much worth implementing. Here is a short summary:
Adds a sync committee to the beacon chain to condition light clients
The first level of computing reform: the validator participation record is continuously updated in the epoch, instead of a large update at the end of each epoch.
The second level of computing reform: (a) only adjust the validator set every 64 epochs, which can avoid potential DoS risks, and (b) make the inactivity leak more flexible.
Increase the penalty for the current "trial round" to the value in the final spec
There are also two changes to the fork selection rules deployed at the same time (these changes do not necessarily need to be very closely coordinated and do not break consensus). Both aim to overcome different theoretical attacks.
The beacon chain is an odd blockchain in that it is slot/time driven rather than block driven. Dealing with empty slots in fork choices has always been a pain point. The first change modifies the fork selection rules to better handle this in terms of (block, slot) pairs."there is a fix
CheckCheckOverview document
to learn more about it.
nameGitHub issueof all planssummarysummary
. Submissions are no longer being accepted.The one with the highest number of votes is obviously "Star Name". Authenticator POAP holder pair (a)Whether to use star nameswhich name to use firstofofTimed Voting Opportunity
(24 hours). Click on "Show current results" to view the results (non-binding). Seems like Alcor won, but I'll wait for the official announcement...
Updates beyond the Beacon ChainIn the AllCoreDev conference last week, Ethereum 2.0 entered the conference agenda for the first time,Discussion topic is the merger of Eth1 and Eth2
(link to start of discussion). This is a major development. Obviously, we still have a lot of work to do to get everyone comfortable with the transition from Eth1 to Eth2, but we're on the way.Here's what the (Eth1 and Eth2) core devs will be doing in the coming months: DraftExecutable Beacon Chain Specification
. The content of this part will continue to be discussed in the ACD meeting, but there will be another regular meeting to discuss the specification in more detail.List of EVM features potentially worth removingAdditionally, Vitalik proposed a "List of EVM features that may be worth removing (
"Mergers" may be our last chance to get rid of these problems, and this article will explain why.
Paraphrase
ParaphraseVitalik on my last weekeditorial sectionDid some work on rollup and executable shardinggood comment
. No path is easy, but rollup's roadmap gets there faster.why it's so important to go statelessDankrad wrote the article "Why Statelessness Matters"Verkle tree". He makes a very powerful argument about pushing the boundaries of statelessness on Ethereum. We now have the underlying technology to achieve statelessness - withform. On the advancement of stateless Ethereum, there has recently been。
The Secret Shared Validators initiative on Eth2 has received an overwhelming response, receiving the latest round from the Ethereum Foundation communitysponsorsponsor. last weekfireside chat, discussed "How SSV can help staking servicers, home-run stakers, and staking pools" (also visited Dankrad!). from thisrecent articlesDiscordLearn more about SSV's technology. The March 3rd community meeting will feature Blox Staking. Welcome
Get the latest updates.
News, Podcasts & ArticlesValid PointsCoindesk latestMapping Out Eth2.0Eth2 information. Could follow up on their experience running a validator. recent
Stake It - The Daily Gwei #185The podcast is also good, with Raul on the subject of forfeiting. This podcast series is worth watching. 😉
- Anthony Sassano is very passionate about personal staking and avoiding centralized serviceseth2 update 011Viktor Bunin of Bison Trails:
Superphiz：State of the Stake! Covers Secret Shared Validators, Eth1/Eth2 Merge, and more.
implementers meeting
Agenda
conference videomineshorthandlive tweet
Job Offers
Job Offers
I'm not trying to repeat Evan Van Ness, so this board won't be regular content, but I've noticed some nice opportunities to get involved with Eth2 recently:QuiltConsenSys
client
other news
other newsEth2tweets:
book progressBy Raul Jordan of the Prysm team:
Lighthouse Track down performance issueslatest update
Block broadcast time and beacon chain client memory usage are also explored
This concludes this issue.
