<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Smartening up gbw-node</title>
	<atom:link href="http://jfxpt.com/2023/smartening-up-gbw-node/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfxpt.com/2023/smartening-up-gbw-node/</link>
	<description>The search for invariants</description>
	<pubDate>Tue, 28 Apr 2026 06:16:11 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2023/smartening-up-gbw-node/#comment-2378</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 25 Apr 2023 01:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=223#comment-2378</guid>
		<description>&lt;blockquote&gt;I'll most likely do a fetch-bitcoind update after letting it all marinate a little.&lt;/blockquote&gt;

And &lt;a href="http://jfxpt.com/code/trb/fetch-bitcoind-0005.sh" rel="nofollow"&gt;it's out&lt;/a&gt; ; &lt;a href="http://jfxpt.com/code/trb/fetch-bitcoind-0005.sh.asc" rel="nofollow"&gt;signed&lt;/a&gt;.

&lt;blockquote&gt;I was hoping to defer this until after full removal of dumpblock, but now that I'm thinking of a schema change as the best path there, I'm less inclined to block release of these improvements on what's likely to be a somewhat heavier upgrade.&lt;/blockquote&gt;

Behind the scenes, the schema and code updates for tracking the full set of block metadata and current unspent outputs are drafted, with a variety of functionality and performance testing ongoing. This includes a process to cleanly migrate user data from the prior version, although a full rescan will certainly still be required. Preliminary results indicate around 5 days to scan and 24 GB for the database. And it does indeed do away with use of dumpblock!</description>
		<content:encoded><![CDATA[<blockquote><p>I'll most likely do a fetch-bitcoind update after letting it all marinate a little.</p></blockquote>
<p>And <a href="http://jfxpt.com/code/trb/fetch-bitcoind-0005.sh" rel="nofollow">it's out</a> ; <a href="http://jfxpt.com/code/trb/fetch-bitcoind-0005.sh.asc" rel="nofollow">signed</a>.</p>
<blockquote><p>I was hoping to defer this until after full removal of dumpblock, but now that I'm thinking of a schema change as the best path there, I'm less inclined to block release of these improvements on what's likely to be a somewhat heavier upgrade.</p></blockquote>
<p>Behind the scenes, the schema and code updates for tracking the full set of block metadata and current unspent outputs are drafted, with a variety of functionality and performance testing ongoing. This includes a process to cleanly migrate user data from the prior version, although a full rescan will certainly still be required. Preliminary results indicate around 5 days to scan and 24 GB for the database. And it does indeed do away with use of dumpblock!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
