My crypto predictions for 2023. Mostly about Eth related tech, just for fun. Let's see if next year is as full of surprises as this year was. 1) Withdrawals will ship before end of March, with peak FUD the day of the upgrade, but back to a larger deposit queue than withdrawal queue two months later.

At @EthereumDenver we hacked together a full data-blob-transaction prototype! (a.k.a. mini-danksharding)

Data blobs are the first milestone towards full ethereum sharding, enabling rollups like @optimismPBC to grow 100x in capacity.

Here's a tweet thread about the prototype 🧵 The teams:

Execution-layer: @lightclients @adietrichs (Quilt), @asn_d6 (EF), @protolambda (@optimismPBC)

Consensus-layer: @terencechain @rauljordaneth @preston_vanloon (@prylabs) Big sean (@sigp_io)

Specs help: @icebearhww @dankrad @VitalikButerin (EF) + EL/CL impl feedback

I Support EIP-4488! Let's make rollups cheaper!

Let me explain what this is about, and why I support it 🧵

#supportEIP4488 Technical TLDR: EIP-4488 reduces the calldata cost from 16 to 3 gas per byte, with a cap on calldata per block to mitigate security risks.

End-user TLDR: rollup cost overhead decreases, thus lowering L2 fees.

Libra TAKE-2. Whitepaper is somewhat confusing, source code is where it's at to get the details. Dug through it for you. Not an audit, just fun. Comparing with Eth1/Eth2 where relevant. Getting in merkleization/hashing/crypto/misc, but not consensus.
Tweetstorm ⬇️ 🧐 0. First of all, source code is located here: github.com/libra/libra
Apache 2.0 license. 👏

A first technical impression of Libra, aka "facebook coin", compared against Eth 1 and Eth 2.
tweetstorm:
🧐⬇️

#ethereum #libra #eth2 0. data keying:
- 32 byte keys seem to be the future. Not only Ethereum 2 is using them in SSZ, Libra will use them for account keys
- static generalized indices, can't find much for "light" clients, you're either a powerful validator, or a user (to be expected)