diff options
| author | João Barbosa <joao.paulo.barbosa@gmail.com> | 2019-07-17 14:38:15 +0100 |
|---|---|---|
| committer | João Barbosa <joao.paulo.barbosa@gmail.com> | 2019-08-19 01:05:58 +0100 |
| commit | 6bc1ff915dd495f05985d3402a34dbfc3b6a08b4 (patch) | |
| tree | 9ad811620312b4ee5e018cfc69484f1d8d29de1a /doc | |
| parent | e8a6d52724651e1a6d7c35165d5c6fe575a11b83 (diff) | |
| download | bitcoin-6bc1ff915dd495f05985d3402a34dbfc3b6a08b4.tar.xz | |
doc: Add note regarding ZMQ block notification
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/zmq.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/zmq.md b/doc/zmq.md index 7ffc5623b6..a309abd0cc 100644 --- a/doc/zmq.md +++ b/doc/zmq.md @@ -111,7 +111,9 @@ using other means such as firewalling. Note that when the block chain tip changes, a reorganisation may occur and just the tip will be notified. It is up to the subscriber to -retrieve the chain from the last known block to the new tip. +retrieve the chain from the last known block to the new tip. Also note +that no notification occurs if the tip was in the active chain - this +is the case after calling invalidateblock RPC. There are several possibilities that ZMQ notification can get lost during transmission depending on the communication type you are |