diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-08-22 08:23:09 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2017-08-22 08:23:46 +0200 |
| commit | 271e40a98984965b666eff4a0e5540fe987236c8 (patch) | |
| tree | b8af147ed66483c94d77f8c87a188f073200fb48 | |
| parent | c559884cac90c296d668dd847ecefb28ce613a21 (diff) | |
| parent | 06a3aecf06a52ff44370ee20462cc45b25e88d6a (diff) | |
Merge #11094: Docs: Hash in ZMQ hash is raw bytes, not hex
06a3aec Docs: Hash in ZMQ hash is raw bytes, not hex (Karel Bílek)
Pull request description:
Transaction hex cannot be in hexadecimal, that would be 64 bytes. In reality it's just raw bytes.
Tree-SHA512: 0f884c73a370be1fe39a1354e2b7ef02d4ff27348dbb8d35a77bbd309f417024959589b28a560b2c9e2713074b90534771fe8c29ff8c0ee1999966997a4827a0
| -rw-r--r-- | doc/zmq.md | 2 |
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. |