<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>discv5 on Guillaume Michel</title><link>https://guillaume.michel.id/tags/discv5/</link><description>Recent content in discv5 on Guillaume Michel</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 28 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://guillaume.michel.id/tags/discv5/index.xml" rel="self" type="application/rss+xml"/><item><title>QUIC Support in the Ethereum Network</title><link>https://guillaume.michel.id/posts/discv5-quic/</link><pubDate>Thu, 28 Nov 2024 00:00:00 +0000</pubDate><guid>https://guillaume.michel.id/posts/discv5-quic/</guid><description>Originally published on ethresear.ch in November 2024. Mirrored here for preservation.
TL;DR: We (ProbeLab) analyzed the adoption of QUIC among Ethereum Consensus Layer (CL) clients using the Nebula Crawler. Approximately 42% of CL nodes support QUIC, primarily because Lighthouse has it enabled by default. While QUIC support is growing, mainly over IPv4, there&amp;rsquo;s minimal adoption over IPv6. This post details our findings and encourages monitoring future trends on probelab.io.</description></item><item><title>Ethereum Dencun Upgrade</title><link>https://guillaume.michel.id/posts/dencun-upgrade/</link><pubDate>Fri, 14 Jun 2024 00:00:00 +0000</pubDate><guid>https://guillaume.michel.id/posts/dencun-upgrade/</guid><description>Originally published on the ProbeLab blog on 14 June 2024, co-authored with Mikel Cortes. The original post (probelab.io/blog/deep-dive-dencun) is no longer online — this is a preserved copy, with all figures and interactive charts mirrored from the original source.
Introduction Link to heading The networking layer is the core component of any distributed blockchain or peer-to-peer (p2p) network. It is the base and the channel of any interaction across participating nodes that makes the higher-level application protocols work.</description></item></channel></rss>