<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Opinion on Pol Espinasa</title>
    <link>https://pesvi.xyz/categories/opinion/</link>
    <description>Recent content in Opinion on Pol Espinasa</description>
    <generator>Hugo -- 0.139.4</generator>
    <language>english</language>
    <lastBuildDate>Tue, 02 Sep 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pesvi.xyz/categories/opinion/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A technical overview and opinion about mempool filters</title>
      <link>https://pesvi.xyz/posts/mempool_filters/</link>
      <pubDate>Tue, 02 Sep 2025 00:00:00 +0000</pubDate>
      <guid>https://pesvi.xyz/posts/mempool_filters/</guid>
      <description>&lt;h2 id=&#34;what-is-the-mempool&#34;&gt;What is the Mempool?&lt;/h2&gt;
&lt;p&gt;The simplest definition for the mempool is: &lt;em&gt;&lt;strong&gt;the mempool&lt;/strong&gt;&lt;/em&gt; &lt;em&gt;is a cache that stores unconfirmed consensus valid transactions.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&#34;but-why-do-we-need-a-mempool&#34;&gt;&lt;strong&gt;But why do we need a mempool?&lt;/strong&gt;&lt;/h3&gt;
&lt;p&gt;The mempool is an important resource for each node and it mainly allows the peer-to-peer transaction relay network.&lt;/p&gt;
&lt;p&gt;Every ~10 minutes when a new block is found, nodes without a mempool experience a bandwidth spike and a computational-intensive period validating each transaction in the block. On the other hand, it is likely that nodes that implement a mempool have already seen all or most of the transactions inside a new block and have them stored in their mempools.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
