research VS ConsensusLayerWithdrawalProtection

Vitalik teases twitter that "Sharding is coming" with the release of research code, and provides more info here

Casper Version 1 Implementation Guide sees the light.

I would definitely love for there to be more work on ZK programming languages. Exposing the internals more to help people do this was one of my motivations for attempting the task of making my own PLONK implementation. We need more tools to help people write circuits, and verify circuits; we should get to the point where verifying a verification key can be done eg. on etherscan as easily as verifying solidity code can be today.

> they have zero power to do anything related to consensus.

Suggest reading what Vitalik has to say if you're going to offer this kind of objection:

https://github.com/ethereum/research/blob/master/papers/disc...

Infura collects upwards of 80 percent of the fees that flow into Ethereum and is in a position to control exactly who participates profitably. If your solution is "minority will fork" the obvious question is surely "with what scalable infrastructure?"

The main difference between all recent Ethereum sharding proposals since ~2020 (both Danksharding and pre-Danksharding) and most non-Ethereum sharding proposals is Ethereum’s rollup-centric roadmap (see also: [1] [2] [3]): instead of providing more space for transactions, Ethereum sharding provides more space for blobs of data, which the Ethereum protocol itself does not attempt to interpret. Verifying a blob simply requires checking that the blob is available - that it can be downloaded from the network. The data space in these blobs is expected to be used by layer-2 rollup protocols that support high-throughput transactions.

Vitalik Buterin gives a (not so sneak) peek at the current version of the Casper contract.

Quite surprised at this comment. The reason I got into blockchain was _because_ of the incredibly difficult technical challenges it poses. Among the few I get to work on:

- How to implement robust p2p networking algorithms for sharding in a distributed system such as Ethereum (a very deep rabbit hole), as Ethereum is migrating to a "sharded" architecture

- How to solve the "data availability problem" https://github.com/ethereum/research/wiki/A-note-on-data-ava.... The current solution uses advanced cryptography known as KZG commitments https://dankradfeist.de/ethereum/2020/06/16/kate-polynomial-...

- How to solve the problem of "transaction frontrunning", in which miners have an asymmetric advantage in ordering transactions they put in blocks for their benefit, which can adversely affect users creating those transactions. This is a problem known as MEV (Miner Extractable Value) https://research.paradigm.xyz/MEV and there is some incredibly sophisticated work going into this problem. It is a deep engineering problem as well

I could go on and probably give you 20 other incredibly technical, challenging problems that are on the bleeding-edge of this technology. If you're interested, would be happy to chat more!

Verkle trees (very important concept): slides, doc, code

All ethereum research is open source https://github.com/ethereum/research including the cryptography they plan to use for eth2. If you want an overview of what eth2 could look like take a look at the roadmap https://twitter.com/VitalikButerin/status/1333922620857745408 or the eth2 specs https://github.com/ethereum/eth2.0-specs

I have been also reading also about EIP-4736 and Consensus Layer Withdrawal Protection, but apparently, they don't accept more submissions.

git clone https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection.git cd ConsensusLayerWithdrawalProtection

I did basically the same on goerli network as i did not want to bother resync a validator node from scratch: 1. go here and get the offline preparation file: https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection 2. on a live ubuntu (from an usb stick) + ethdo and the offline preparation file, prepare the json file to sign the exit, instructions here: https://github.com/wealdtech/ethdo/blob/master/docs/changingwithdrawalcredentials.md 3. once shapella is live on main net, use the beaconcha.in endpoint to broadcast the json file ref: https://beaconcha.in/tools/broadcast

There's some group trying to do this https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection

The easiest is using ethdo using the offline process. You don't have to run a node yourself, if you download the offline preparation file from here: https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/tree/main (offline-preparation.json is just a big text file containing the ids, validator pubkeys, and withdraw pubkeys of all validators).

# Navigate to the folder containing the "ethdo" utility cd /path/to/ethdoFolder # Download the CLWP submissions: git clone https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection.git # Install jq (Example: apt install -y jq) and use it to combine all CLWP submissions together into a single change-operations.json file jq -s 'add' ConsensusLayerWithdrawalProtection/mainnet/*.json > change-operations.json # Run ethdo to connect to your beacon node (specify the valid host and port), allowing local insecure connections using HTTP, and it will broadcast all messages in the change-operations.json file. ./ethdo validator credentials set --connection http://YourNodeIP:5052 --allow-insecure-connections echo $?

If you have an Ethereum validator, and have not stored your validator seed phrase securely offline, we would encourage you to consider using CLWP (EIP-4736) to set your withdrawal address. We will broadcast these submissions at the Capella hard fork. This may help you win against an attacker. We are accepting open submissions until 2/28. Over 750 validators have used CLWP. We are happy to help anyone who has questions. https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection

#!/bin/bash NOT_FOUND="Not Found" if [ $# -eq 0 ] then echo "You must provide at least one argument. \n Use with ./clwpCheck.sh ..." fi # Check cURL command if available (required), abort if does not exists type curl >/dev/null 2>&1 || { echo >&2 "Required curl but it's not installed. Aborting."; exit 1; } echo "🕵️ Checking the public CLWP list at https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/tree/main/mainnet" for i in "$@"; do echo RESPONSE=`curl -s "https://github.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/commits/main/mainnet/"$i".json.atom"` if [ "$RESPONSE" == "$NOT_FOUND" ]; then echo "🟢 Validator $i not found in the broadcast list." else JSONRESPONSE=`curl -s "https://raw.githubusercontent.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/main/mainnet/"$i".json"` startIndex=$(echo $JSONRESPONSE | grep -b -o 'to_execution_address' | cut -d: -f1) withdrawalAddress=${JSONRESPONSE:$startIndex+23:42} echo "🔴 Validator $i: Watch out, there is a request to change the withdrawal address to "$withdrawalAddress echo " If you didn't request this change, you should contact CLWP right away 👉 https://clwp.xyz/index.php/contact.html" echo " This signed message will be broadcast at Shangai 👉 https://raw.githubusercontent.com/benjaminchodroff/ConsensusLayerWithdrawalProtection/main/mainnet/"$i".json" fi done