
seongwan.eth : : FP
222 posts

seongwan.eth : : FP
@seongwan_eth
Ethereum Solo Validator #439919 since 2022/ Ph.D candidate /@decipherglobal / Interests: data collection&analysis, consensus






There's a path to fix Ethereum L2 fragmentation and horrible UX. superchain interop, intents etc. It's gonna happen, eth community is galvanized around unifying Ethereum and they'll fix it. But I still don't see how all this L2 activity gets reflected on Ethereum mainnet. Layer 2s are getting Ethereum security for free right now, only paying for block space, which they will pay even less for with larger blobs. I know lots of ethereans are triggered when people say Layer 2s are parasitic, and I get that Ethereum couldn't scale without them, so of course l2s are a net positive to the Ethereum ecosystem. But right now it doesn't seem like their contributions match the benefits they're getting. This means that even if all of crypto's most successful use cases are on Ethereum Layer 2s, ETH the asset will only partially benefit. I imagine that's why even with all the real adoption happening on Ethereum, ETH just keeps sliding.


History-expiry update: More than 80% of Ethereum full node disk space is occupied by history, so data not needed to validate new blocks. With the latest 1.31.* releases, @nethermind is fully ready to drop pre-merge history via ERA files. Dropping history requires cross-client consensus, and all teams have agreed to remove pre-merge history from full nodes on 1st May. History expiry is desired for further scaling. Once activated, your full node will require ~320 GB of pre-merge blocks and receipts history. A full Nethermind execution node without dropping pre-merge history today takes around 700 GB. If we drop all blocks and all receipts and keep only what is needed to verify the latest block, it would be less than 200 GB for full node. Nethermind team keeps working on history expiry (portal-network integration, rolling history expiry, ERA files, EIP-7801). Node without pre-merge history 👇






In March, EIP-4844 upgrade introduced blobs to enable rollup scalability and reduce fees. Eight months in, blobs have significantly lowered batch posting costs for rollups, but adoption remains gradual. Let’s dive into EIP-7762 & EIP-7691 and their significance for blobs. 🧵

We’re thrilled to announce the findings from the 4844 Data Challenge! 🧑🔬📊 Researchers explored rollup costs & blob txs, revealing key insights into EIP-4844’s impact on Ethereum’s scaling future. More data challenges are coming soon! 🔗 blog.ethereum.org/2024/09/13/484…

We’re thrilled to announce the findings from the 4844 Data Challenge! 🧑🔬📊 Researchers explored rollup costs & blob txs, revealing key insights into EIP-4844’s impact on Ethereum’s scaling future. More data challenges are coming soon! 🔗 blog.ethereum.org/2024/09/13/484…










