aboutsummaryrefslogtreecommitdiff
path: root/doc/zmq.md
diff options
context:
space:
mode:
authorKarel BĂ­lek <kb@karelbilek.com>2017-08-19 11:26:40 +0200
committerKarel Bilek <kb@karelbilek.com>2017-08-19 11:30:35 +0200
commit06a3aecf06a52ff44370ee20462cc45b25e88d6a (patch)
treeef0e0fb8e2ae3243b8c5e178e19b69aa8c7a7961 /doc/zmq.md
parent262167393d05eb46b962cf0515a6dc73c4cec8ea (diff)
downloadbitcoin-06a3aecf06a52ff44370ee20462cc45b25e88d6a.tar.xz
Docs: Hash in ZMQ hash is raw bytes, not hex
Transaction hash cannot be in hexadecimal, that would be 64 bytes. In reality it's just raw bytes.
Diffstat (limited to 'doc/zmq.md')
-rw-r--r--doc/zmq.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/zmq.md b/doc/zmq.md
index 1019ff6653..38c58fb7fd 100644
--- a/doc/zmq.md
+++ b/doc/zmq.md
@@ -72,7 +72,7 @@ For instance:
Each PUB notification has a topic and body, where the header
corresponds to the notification type. For instance, for the
notification `-zmqpubhashtx` the topic is `hashtx` (no null
-terminator) and the body is the hexadecimal transaction hash (32
+terminator) and the body is the transaction hash (32
bytes).
These options can also be provided in bitcoin.conf.