aboutsummaryrefslogtreecommitdiff
path: root/test/functional/mempool_package_limits.py
diff options
context:
space:
mode:
authorW. J. van der Laan <laanwj@protonmail.com>2021-09-09 15:25:59 +0200
committerW. J. van der Laan <laanwj@protonmail.com>2021-09-09 15:37:13 +0200
commitb05d3e76e7c72387b302cc21d420f31f384c8b10 (patch)
tree45e3ee5f6dddb00e6dbf69a3a54c9c43da380760 /test/functional/mempool_package_limits.py
parenta5d00d4baff27b4185ea086af571142af17c32e4 (diff)
parente6998838e5548991274ad2bf1697d862905b8837 (diff)
Merge bitcoin/bitcoin#22079: zmq: Add support to listen on IPv6 addresses
e6998838e5548991274ad2bf1697d862905b8837 doc: Add IPv6 address to zmq example (nthumann) 8abe5703a9bb76bc92204a6f69775790e96208fa test: Add IPv6 test to zmq (nthumann) ded449b726e47f35798ef1c4b1e59123a0dc2b61 zmq: Enable IPv6 on listening socket (nthumann) Pull request description: This PR adds support for listening on IPv6 addresses with bitcoinds ZMQ interface, just like the RPC server. Currently, it is not possible to specify an IPv6 address, as the `ZMQ_IPV6` [socket option](http://api.zeromq.org/master:zmq-setsockopt#toc27) is not set and therefore the ZMQ initialization fails, if one does so. The absence of this option has also been noted [here](https://github.com/bitcoin/bitcoin/issues/15198#issuecomment-617378512). With this PR one can e.g. set `-zmqpubhashblock=tcp://[::1]:28333` to listen on the IPv6 loopback address. ACKs for top commit: laanwj: Code review ACK e6998838e5548991274ad2bf1697d862905b8837 theStack: Tested ACK e6998838e5548991274ad2bf1697d862905b8837 🌱 Tree-SHA512: 43c3043d8d5c79794d475926259c1be975b694db4fcc1f7750a9a28e242f0fa1b531735a63ea5777498003aa5834f6243f39742d0f3941f2f37593d0c7890700
Diffstat (limited to 'test/functional/mempool_package_limits.py')
0 files changed, 0 insertions, 0 deletions