Edition 56 at eth2.news
Danny Ryan's updates are the nearest thing you'll get to "official" news:
If you haven't been completely off the grid for the last two weeks, you will know that the deposit contract was announced on November 4th. It had actually been deployed three weeks earlier, pretty much exactly as I told you all.
The manner of its deployment adds to the Ethereum narrative in an interesting way. The funds for deployment came from TornadoCash, so are effectively untraceable. The leftover Ether was sent to Wikileaks' donation address. I suppose the intended implication is that (1) nobody has control, and (2) we support openness and censorship resistance. There's a parallel with Bitcoin suggesting its own manifesto in its genesis block.
At the same time as the deposit contract announcement, v1.0.0 of the spec was released with some very minor updates. This is an incredible milestone: the culmination of around 28 months of work, with direct contributions, both large and small, from over eighty people, and discussion, participation, and research from a huge host more.
For this week only, I am promoting client team updates, because it is important to know what to expect in the run up to genesis.
Bottom line is that all client teams expect to make a release between the 24th of November (when the genesis state should be known) and the 1st of December (genesis day). That release will bake in the genesis state and a good set of boot-nodes (as well as any last minute fixes) - the protocol gives us a week's grace to do this.
So, whichever client you plan to run, expect to update during that week, and be on the lookout for release announcements from teams. Teku has a new mailing list and a new Twitter account for this purpose, so, Teku users, please sign up.
A couple of the testnet launches were tripped up by stakers not updating clients in time for genesis. So, if you want a nice, smooth launch, you know what to do!
Medalla continues to run for the time-being, with 71,000 validators, but barely over 70% participation. The entry and exit queues are each over three weeks long now. The general view among devs is that Medalla has had a glorious run, but it's time to begin its wind-down. The spec version it runs is not up to date, and the long queues render it not useful for stakers who just want to test their configurations or get a little experience.
We spun up a quick devnet on Tuesday called Toledo with 16,384 validators restricted only to client teams. There's an Eth2Stats monitor for it. This is purely to test out the full mainnet spec in a benign environment. After settling down it has been running all but perfectly. Toledo is planned to live for only a few more days.
The next big public testnet will be Pyrmont, launching at noon UTC on Wednesday 18th November. We are starting it with 100,000 validators run by client teams, and will then open it to wider participation. Unlike Medalla, we will be asking people to run only a very small number of validators each. This is to keep the queues open for people to hop on and hop off, and also to reduce the risk of non-finalisation. It's undecided right now whether Pyrmont will become long-lived or not: watch this space (or Twitter, or whatever).
The most important news in this section is that the Ethereum Foundation announced Eth2 Staking Community Grants. These are to fund "the creation of tools, documentation, and resources to make for a delightful staking and validator experience." Get to it! The deadline for proposals is any time the day of Tuesday, December 22nd, 2020.
We discussed the Medalla Data Challenge last time. Since then, the EthStaker folk got some of the authors together to present their results live. Lots of good info in there.
This visualisation from Barnabé Monnot is incredible. So much information condensed into such a visually appealing format - I've watched it a hundred times. The accompanying notebook has some useful insights as well.
Alex Stokes is putting together a fork monitor for the beacon chain that promises to be super useful. It's monitoring the Toledo devnet at the moment, which is currently running near perfectly, so there aren't many interesting forks to see yet.
Jim McDonald has updated his chaind
beacon chain data extraction tool to work with the latest versions of Teku, Lighthouse, and Prysm.
Beacon Fuzz update 09 from Sigma Prime is out. In the last little while, the structural differential fuzzer was able to find two new critical vulnerabilities in Prysm, and a minor, non-exploitable issue in Teku.
Stakefish has created a batch deposit contract to save gas when making multiple deposits. They are seeking feedback and review. As discussed below: please exercise extreme diligence before sending your stakes anywhere unusual.
Yorick Downe is seeking to make life easier for Docker users, with "unofficial" docker build instructions for Eth2 clients. There is an accompanying YouTube tutorial.
While on the topic of tooling, Superphiz of EthStaker is seeking participants for an Ethereum Due Diligence Committee (EDDC) to evaluate and report on tools in our ecosystem. See also his bench chat, and contact him if this is up your street.
The place to make your deposits is on https://launchpad.ethereum.org/
. Do not use any other site that purports to accept Eth2 deposits without extreme due diligence!
The Launchpad itself reports progress towards the minimum deposit goal, while the Dune Analytics dashboard gives some more insight. You can even see pending transactions here, and explore past deposits on The Graph.
As I write, we are around 12% of the way to the goal of 16,384 validators. This may seem like a slow start, but per Tetranode, and Justin's poll, the majority haven't moved yet and I expect a huge uptick as the 24th approaches*. Anthony Sassano urges you to join The Genesis War Effort! Vitalik has done his duty.
(* Yes you read that right - if you want to guarantee being a genesis validator, you need to get your deposit into the contract before noon UTC on the 24th of November, a full week before genesis. After that, you may end up being queued and inducted well after genesis.)
Everybody's favourite topic–-the tax treatment of Eth2 deposits–-was vigorously debated on Twitter this week. The key issue is whether the act of sending a deposit to the deposit contract constitutes a disposal of Ether for capital gains tax purposes (a "taxable event" under US tax law, and I guess UK which is similar). This in turn likely depends on whether Ether on the Eth1 chain and Ether on the Eth2 chain are considered to be the same asset or different assets. James Prestwich (a noted contrarian) energetically argues that the two are distinct assets; Justin Leroux (an actual tax accountant) energetically argues that they are not. Other characters join the fray, including TokenTax; it's a sprawling discussion over many threads.
I am in the happy position of being able to side-step all of this. But the bottom line is that nobody knows what the various tax authorities globally might decide. As with many taxation matters, there is a variety of viewpoints the authorities might take, and they will decree whatever it suits their purposes to decree. Take this as a heads-up to be careful and intentional about tax liabilities. Do your own research; get professional advice; be cautious about making decisions based on a bunch of Twitter threads.
Relevant here could be Liquidstake, which was announced this week. It offers a way to borrow USDC against stakes placed through the scheme. The Block has a nice quote from Andrew Keys, "If you enter into a swap you have clarity on the regulatory and tax treatment. It allows users to have their stake and eat it too."
…and other media. I've got a long list of unordered things that I'm just going to insert below:
Collin Myers and Mara Schmiedt published a nice paper, The Internet Bond: Digital Work Agreements in the Web3.0 Era. They use the economic framework of bonds as a way of analysing staking in Eth2 and modelling the market for participation.
Vitalik is suggesting some modifications to the "quadratic leak" (aka the inactivity leak). This is the mechanism that kicks in during times of non-finalisation to accelerate the demise of non-active validators and allow the network to recover. The main observation from Medalla is that it overly punishes validators that are genuinely trying to do their best, but struggling due to the adverse network conditions. The proposal is designed to be much kinder to validators that have intermittent activity while still penalising those that don't show up at all.
Alex Vlasov of team TXRX is keen to make the Eth2 specifications more amenable to formal verification. He proposes a minimally disruptive approach to this in his article, Towards formal semantics of the beacon chain’s pyspec.
Call #52 took place on the 12th of November.
Some testnet chat, but the main thing that caught my attention was Vitalik's proposal to explicitly decouple future work on sharding, light client support, and the Eth1/Eth2 merge. This means that these three could effectively be delivered in any order, leading to designs like an executable beacon chain which could embed Eth1 directly into the beacon chain before we even get to shards.
This is all very fluid and dynamic right now, and it remains to be seen how it all pans out. It's also very pragmatic, and definitely an "engineering approach". I just need to get it out there that I mourn for our nice, pure Phase 0, Phase 1, Phase 2 roadmap, with its execution engines and beautiful abstractions. Then again, I also mourn for the original Web3 vision founded on Ethereum, Whisper, and Swarm. Apparently, I am a sucker for elegant but undeliverable designs.
Nothing to add… just turning my thoughts to getting some deposits done this weekend.
Follow me on Twitter to hear when the next edition is out 🙌.
We also have an RSS feed.