<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title> - Ethereum</title>
    <link rel="self" type="application/atom+xml" href="https://sysrex.com/tags/ethereum/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://sysrex.com"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2025-05-10T00:00:00+00:00</updated>
    <id>https://sysrex.com/tags/ethereum/atom.xml</id>
    <entry xml:lang="en">
        <title>Why Ethereum Execution Clients Are Being Rewritten in Rust</title>
        <published>2025-05-10T00:00:00+00:00</published>
        <updated>2025-05-10T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://sysrex.com/posts/ethereum-execution-clients-rust/"/>
        <id>https://sysrex.com/posts/ethereum-execution-clients-rust/</id>
        
        <summary type="html">&lt;p&gt;If you&#x27;ve spent any time around L2 rollups — including the op-stack setup
covered in an earlier post here — you&#x27;ve run into &quot;execution clients&quot;:
the piece of software responsible for actually running transactions and
maintaining state. Go has dominated this space for years via Geth. More
recently, a wave of new clients (Reth being the most visible) have been
written in Rust instead. The reasons why are a good case study in what
Rust is actually for.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
