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
This commit is contained in:
Wladimir J. van der Laan 2017-08-22 08:23:09 +02:00 committed by Pasta
parent 9d58c98753
commit 7654c786b6
No known key found for this signature in database
GPG Key ID: 52527BEDABE87984

View File

@ -84,7 +84,7 @@ For instance:
Each PUB notification has a topic and body, where the header Each PUB notification has a topic and body, where the header
corresponds to the notification type. For instance, for the corresponds to the notification type. For instance, for the
notification `-zmqpubhashtx` the topic is `hashtx` (no null 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). bytes).
These options can also be provided in dash.conf. These options can also be provided in dash.conf.