From e34d70c0dda378a3d757dd94d0c099365bf84a37 Mon Sep 17 00:00:00 2001 From: 8144225309 Date: Wed, 21 Jan 2026 09:29:06 -0500 Subject: [PATCH] doc: clarify ZMQ data scope statement for accuracy The existing statement about ZMQ data scope predates the wallet publisher additions. This adjusts the wording to accurately reflect which notifications contain P2P-sourced data vs wallet-sourced data. --- doc/zmq.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/zmq.md b/doc/zmq.md index 5e283c82eed4..1e7cf88e3f03 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -172,8 +172,9 @@ hosts as well. If needed, this option has to be set on the client side too. From the perspective of bitcoind, the ZeroMQ socket is write-only; PUB sockets don't even have a read function. Thus, there is no state -introduced into bitcoind directly. Furthermore, no information is -broadcast that wasn't already received from the public P2P network. +introduced into bitcoind directly. Block and transaction notifications +relay data received from the public P2P network; wallet notifications +relay data from the local wallet. No authentication or authorization is done on connecting clients; it is assumed that the ZeroMQ port is exposed only to trusted entities,