< fanquake>
adam_ asdfasdf Yes, this channel is used for discussion specific to core development, as well as dev meetings. See https://botbot.me/freenode/bitcoin-core-dev/ for logs.
< fanquake>
Could someone send some testnet coins to 2MxhnRfjqjps8CSsUgp1US51q555Js5mUMr . Cheers.
< echeveria>
has there been any discussion recently about improving the methods for low-latency GBT updates?
< echeveria>
the pool software that's publicly available at the moment seems to use a variety of methods for detecting when there's a new block, -blocknotify calling a script that sends an interrupt to send an RPC call, polling the RPC in a tight loop, or even attempting to build an empty block template from the ZMQ socket raw block output. the RPC interface has a long polling option but that's pretty hacky as well.
< echeveria>
most ideally there'd be a mode for the ZMQ socket which emits a GetBlockTemplate response on UpdateTip, and at some configurable interval. eliminates any polling misses, any latency from spawming a new shell just to send an interrupt.
< bitcoin-git>
[bitcoin] fanquake opened pull request #11936: [build] Warn that only libconsensus can be built without Boost (master...libcon-boost) https://github.com/bitcoin/bitcoin/pull/11936
< echeveria>
jonasschnelli: long polling is really difficult to deal with in a reliable way. there's software out there which calls GBT every 100ms, holding cs_main for who knows what portion of the time; as preferable to using long polling.
< promag>
echeveria: jonasschnelli: both zmq notification and long polling have a problem: missed data
< promag>
if you need reliability IMO you have to poll
< echeveria>
promag: if you're losing ZMQ frames with a unix domain socket you've got other issues. there's sequence numbers in the messages that Bitcoin Core emits too, so you should be able to detect if you're getting messages lost.
< promag>
I know that
< promag>
just saying that generally ZMQ is not reliable, you have to work around the reliability
< echeveria>
at any rate, the main uncomfortable feature is that JSON is still the most logical output.
< bitcoin-git>
[bitcoin] hsjoberg opened pull request #11937: GUI: Setting for deciding address type (legacy, p2sh or bech32) (master...segwitwalletguioption) https://github.com/bitcoin/bitcoin/pull/11937
< bigboytimmyc>
hey guys got a quick code question
< bigboytimmyc>
if anyones around
< provoostenator>
bigboytimmyc: this place is like New York City. No need to see hi, just ask :-)