<?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: The passive threads that would like to be given some blocks</title>
	<atom:link href="http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/</link>
	<description>The search for invariants</description>
	<pubDate>Sat, 04 Apr 2026 23:54:07 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sending buffer overflows fixed in bitcoind, and other cleanups &#171; Fixpoint</title>
		<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/#comment-2038</link>
		<dc:creator>Sending buffer overflows fixed in bitcoind, and other cleanups &#171; Fixpoint</dc:creator>
		<pubDate>Sat, 21 May 2022 22:33:54 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=181#comment-2038</guid>
		<description>[...] Bitcoin code reading efforts led naturally to another round of editing, in a one-two ratchet towards the object of full [...]</description>
		<content:encoded><![CDATA[<p>[...] Bitcoin code reading efforts led naturally to another round of editing, in a one-two ratchet towards the object of full [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/#comment-2035</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Mon, 09 May 2022 01:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=181#comment-2035</guid>
		<description>Also worth a link, more for the prior discussion than the specific patch attempted: &lt;a href="http://thetarpit.org/2020/a-cursory-look-at-the-infamous-trb-wedge-bug" rel="nofollow"&gt;A cursory look at the infamous TRB "wedge" bug&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Also worth a link, more for the prior discussion than the specific patch attempted: <a href="http://thetarpit.org/2020/a-cursory-look-at-the-infamous-trb-wedge-bug" rel="nofollow">A cursory look at the infamous TRB "wedge" bug</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/#comment-2034</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Fri, 06 May 2022 14:53:33 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=181#comment-2034</guid>
		<description>@Diana Coman: yeee.</description>
		<content:encoded><![CDATA[<p>@Diana Coman: yeee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diana Coman</title>
		<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/#comment-2033</link>
		<dc:creator>Diana Coman</dc:creator>
		<pubDate>Fri, 06 May 2022 10:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=181#comment-2033</guid>
		<description>These are such a pleasure to read, thank you. Combined with the &lt;a href="http://jfxpt.com/2022/two-patches-and-a-new-fetch-bitcoind-release/" rel="nofollow"&gt;releases&lt;/a&gt;, they really make the case for giving this another go as node-code that you actively maintain so I guess it'll soon get to the point where I'll have to do it, huh.

&lt;blockquote&gt;
and even that only due to the "aggression" patch which I guess we could now call... passive-aggression?
&lt;/blockquote&gt;
Bwahaha, a very fitting description, I say!</description>
		<content:encoded><![CDATA[<p>These are such a pleasure to read, thank you. Combined with the <a href="http://jfxpt.com/2022/two-patches-and-a-new-fetch-bitcoind-release/" rel="nofollow">releases</a>, they really make the case for giving this another go as node-code that you actively maintain so I guess it'll soon get to the point where I'll have to do it, huh.</p>
<blockquote><p>
and even that only due to the "aggression" patch which I guess we could now call... passive-aggression?
</p></blockquote>
<p>Bwahaha, a very fitting description, I say!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Two patches and a new fetch-bitcoind release &#171; Fixpoint</title>
		<link>http://jfxpt.com/2022/the-passive-threads-that-would-like-to-be-given-some-blocks/#comment-2032</link>
		<dc:creator>Two patches and a new fetch-bitcoind release &#171; Fixpoint</dc:creator>
		<pubDate>Thu, 05 May 2022 21:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=181#comment-2032</guid>
		<description>[...] getting into the deeper code study this week, I had made some more basic changes which are suitable for production use, and updated [...]</description>
		<content:encoded><![CDATA[<p>[...] getting into the deeper code study this week, I had made some more basic changes which are suitable for production use, and updated [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
