< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #22102: Remove `Warning:` from warning message printed for unknown new rules (master...warning-msg) https://github.com/bitcoin/bitcoin/pull/22102
< elichai2>
Are the binaries from bitcoin.org compiled with zmq support?
< fanquake>
yes
< elichai2>
oh I apparently forgot that zmq addresses need to have a protocol prefix (eg "tcp://IP:PORT"), and bitcoin core didn't complain about it
< elichai2>
which channel is best for asking about details on the zmq interface? #bitcoin? (I remembered there was a #bitcoin-dev, but I can't join it) or is here also fine?
< elichai2>
I'm sometimes getting big jumps in (zmq) sequence numbers, for example, I was listening to `hashtx` with a buffer of 20 on the bitcoin core side, and suddenly I got a message with sequence number 4139 while the one before it had 3038
< fanquake>
elichai2: could also just be worthwhile opening an issue
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22232: refactor: Pass interpreter flags as uint32_t instead of signed int (master...2106-refactorFlags) https://github.com/bitcoin/bitcoin/pull/22232
< bitcoin-git>
bitcoin/master faf7623 MarcoFalke: fuzz: Call const member functions in addrman fuzz test only once
< bitcoin-git>
bitcoin/master d75a1df MarcoFalke: Merge bitcoin/bitcoin#21941: fuzz: Call const member functions in addrman ...
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #21941: fuzz: Call const member functions in addrman fuzz test only once (master...2105-fuzzAddrConst) https://github.com/bitcoin/bitcoin/pull/21941
< bitcoin-git>
[bitcoin] josibake opened pull request #22235: script: add script to generate example bitcoin.conf (master...josibake-auto-generate-example-bitcoin-conf-file) https://github.com/bitcoin/bitcoin/pull/22235