Bitcoin full node and query server

Oct 22, 2026

View in context in the libbitcoin Slack #general mirror.

evoskuil15:33
This test is initiated over P2P, one transaction at a time, from a single peer connection in the test client:
  1. The client announces the transaction with an inv message.
  2. It waits for the server to request it with getdata. Transactions not requested within 1 second are recorded as unrequested and skipped.
  3. It sends the tx message. The clock starts as that send completes.
  4. The clock stops when that exact transaction arrives on the ZMQ rawtx subscription. If it doesn’t arrive within 1 second, it’s recorded as unnotified.
The 28,142 transactions of blocks 950,001–950,009 are sent this way in block order, each only after the previous one finishes. So the latency is the server’s full path: receive and parse the transaction, validate it, accept it to the pool, and publish the notification. The inv/getdata round trip is timed separately and not included.