<?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>Bitcoin-Core on Chris Zeng</title>
    <link>https://chris-zeng.pages.dev/tags/bitcoin-core/</link>
    <description>Recent content in Bitcoin-Core on Chris Zeng</description>
    <image>
      <title>Chris Zeng</title>
      <url>https://chris-zeng.pages.dev/img/headshot.jpg</url>
      <link>https://chris-zeng.pages.dev/img/headshot.jpg</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://chris-zeng.pages.dev/tags/bitcoin-core/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fix for bitcoind&#39;s Silent ZMQ Bug</title>
      <link>https://chris-zeng.pages.dev/posts/bitcoind-silent-zmq-failure/</link>
      <pubDate>Wed, 05 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://chris-zeng.pages.dev/posts/bitcoind-silent-zmq-failure/</guid>
      <description>bitcoind can publish new blocks and transactions over ZMQ, and tools like LND depend on it. But if a configured ZMQ socket can&amp;rsquo;t bind at startup, bitcoind starts anyway and only logs it at debug level — so the problem surfaces days later, in someone else&amp;rsquo;s process. This is the bug, the 2019 history behind it, and the two-function design that fixes it.</description>
    </item>
  </channel>
</rss>
