docs: note that different ZMQ sockets must be used with bitcoind

This commit is contained in:
Wilmer Paulino committed 2018-08-08 20:26:31 -07:00
1 parent 936fcc1f16
commit e58486b599
2 files changed
+44 -22

No files matched your search

+10 -10
View File
@@ -205,11 +205,11 @@ bitcoin.node=btcd
; (other than for a remote bitcoind instance).
; bitcoind.rpcpass=kek
; ZMQ socket which sends rawblock and (optionally) rawtx notifications from
; bitcoind. By default, lnd will attempt to automatically obtain this
; information, so this likely won't need to be set (other than for a remote
; bitcoind instance).
; bitcoind.zmqpath=tcp://127.0.0.1:28332
; ZMQ socket which sends rawblock and rawtx notifications from bitcoind. By
; default, lnd will attempt to automatically obtain this information, so this
; likely won't need to be set (other than for a remote bitcoind instance).
; bitcoind.zmqblockhost=tcp://127.0.0.1:28332
; bitcoind.zmqtxhost=tcp://127.0.0.1:28333
[neutrino]
@@ -283,11 +283,11 @@ litecoin.node=ltcd
; (other than for a remote litecoind instance).
; litecoind.rpcpass=kek
; ZMQ socket which sends rawblock and (optionally) rawtx notifications from
; litecoind. By default, lnd will attempt to automatically obtain this
; information, so this likely won't need to be set (other than for a remote
; litecoind instance).
; litecoind.zmqpath=tcp://127.0.0.1:28332
; ZMQ socket which sends rawblock and rawtx notifications from litecoind. By
; default, lnd will attempt to automatically obtain this information, so this
; likely won't need to be set (other than for a remote litecoind instance).
; litecoind.zmqblockhost=tcp://127.0.0.1:28332
; litecoind.zmqtxhost=tcp://127.0.0.1:28333
[autopilot]