<?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>Posts on Pol Espinasa</title>
    <link>https://pesvi.xyz/posts/</link>
    <description>Recent content in Posts 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/posts/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>
    <item>
      <title>How the UTXO Set Can Help Us Synchronize a Bitcoin Node</title>
      <link>https://pesvi.xyz/posts/utxo_set_backup/</link>
      <pubDate>Sun, 06 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://pesvi.xyz/posts/utxo_set_backup/</guid>
      <description>&lt;p&gt;We all have encountered at some point that our Bitcoin node stops working, the raspberry fails, the disk dies, or we simply need the disk for other purposes and we end up without a Bitcoin node. In the future when we want to set up a node again we find that we have to go through the IBD (&lt;em&gt;initial block download&lt;/em&gt;) process to synchronize the blockchain. A heavy process, that can last in many cases days and that prevents us to use the node and to connect the wallets until the node is completely synchronized.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Grouphug - Batching transactions without interaction between users</title>
      <link>https://pesvi.xyz/posts/grouphug/</link>
      <pubDate>Mon, 20 May 2024 00:00:00 +0000</pubDate>
      <guid>https://pesvi.xyz/posts/grouphug/</guid>
      <description>How GroupHug works, a server programmed in Rust that allows grouping or batching of transactions without interaction between users using SigHash Single | AnyoneCanPay</description>
    </item>
    <item>
      <title>How to make a transaction with UTXOs of different wallets with Sparrow</title>
      <link>https://pesvi.xyz/posts/psbt_sparrow/</link>
      <pubDate>Sun, 07 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://pesvi.xyz/posts/psbt_sparrow/</guid>
      <description>How to make a Coinjoin or a grouping of transactions without interaction between users using Sparrow Wallet and Bitcoin Core</description>
    </item>
  </channel>
</rss>
