1 2017-12-18 00:15:22	0|adam_|yeah same
 2 2017-12-18 00:15:23	0|adam_|lol
 3 2017-12-18 00:17:31	0|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.
 4 2017-12-18 01:09:23	0|fanquake|Could someone send some testnet coins to 2MxhnRfjqjps8CSsUgp1US51q555Js5mUMr . Cheers.
 5 2017-12-18 01:09:58	0|BlueMatt|fanquake: done
 6 2017-12-18 01:12:21	0|fanquake|BlueMatt Thanks
 7 2017-12-18 03:59:18	0|BGL|https://i.imgur.com/mTR70FX.jpg
 8 2017-12-18 04:03:19	0|fanquake|BGL See https://github.com/bitcoin/bitcoin/issues/9860
 9 2017-12-18 04:04:30	0|fanquake|It's an upstream issue with Qt, and won't affect running core. Are you running windows?
10 2017-12-18 04:04:59	0|BGL|yes
11 2017-12-18 04:58:15	0|mryandao|quick question, where can I find code on how AES encryption is applied to the encrypted private keys in wallet.dat?
12 2017-12-18 04:58:47	0|mryandao|alternatively, a grep regex will be sufficient ;)
13 2017-12-18 04:58:53	0|phantomcircuit|mryandao, maybe just in the code
14 2017-12-18 04:59:09	0|mryandao|yeah, I mean in the core source.
15 2017-12-18 05:01:27	0|phantomcircuit|mryandao, src/wallet/crypter.cpp
16 2017-12-18 05:01:51	0|mryandao|phantomcircuit: wonderful, thanks.
17 2017-12-18 05:52:55	0|echeveria|has there been any discussion recently about improving the methods for low-latency GBT updates?
18 2017-12-18 05:53:56	0|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.
19 2017-12-18 06:11:35	0|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.
20 2017-12-18 06:40:39	0|bitcoin-git|[13bitcoin] 15fanquake opened pull request #11936: [build] Warn that only libconsensus can be built without Boost (06master...06libcon-boost) 02https://github.com/bitcoin/bitcoin/pull/11936
21 2017-12-18 06:40:57	0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #11806: [Build]: Modify error if boost lib is not found (06master...06boost) 02https://github.com/bitcoin/bitcoin/pull/11806
22 2017-12-18 06:42:27	0|bitcoin-git|[13bitcoin] 15fanquake closed pull request #11920: Trivial: Spelling fix, python → Python (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/11920
23 2017-12-18 06:51:09	0|echeveria|to exemplify that, CreateNewBlock() takes 26ms, sending it down RPC takes 90ms.
24 2017-12-18 07:48:09	0|jonasschnelli|echeveria: maybe have a look at https://github.com/bitcoin/bitcoin/pull/9919?
25 2017-12-18 07:48:47	0|jonasschnelli|Why is the longpolling hacky?
26 2017-12-18 08:38:43	0|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.
27 2017-12-18 12:07:34	0|promag|echeveria: jonasschnelli: both zmq notification and long polling have a problem: missed data
28 2017-12-18 12:08:34	0|promag|if you need reliability IMO you have to poll
29 2017-12-18 12:11:12	0|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.
30 2017-12-18 12:12:05	0|promag|I know that
31 2017-12-18 12:12:56	0|promag|just saying that generally ZMQ is not reliable, you have to work around the reliability
32 2017-12-18 12:24:50	0|echeveria|at any rate, the main uncomfortable feature is that JSON is still the most logical output.
33 2017-12-18 15:27:35	0|bitcoin-git|[13bitcoin] 15hsjoberg opened pull request #11937: GUI: Setting for deciding address type (legacy, p2sh or bech32)  (06master...06segwitwalletguioption) 02https://github.com/bitcoin/bitcoin/pull/11937
34 2017-12-18 16:08:23	0|bigboytimmyc|hey guys got a quick code question
35 2017-12-18 16:08:29	0|bigboytimmyc|if anyones around
36 2017-12-18 16:28:44	0|provoostenator|bigboytimmyc: this place is like New York City. No need to see hi, just ask :-)
37 2017-12-18 17:50:35	0|bitcoin-git|[13bitcoin] 15Gerjan77 opened pull request #11939: Update build-windows.md (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/11939
38 2017-12-18 17:56:31	0|bitcoin-git|[13bitcoin] 15Gerjan77 closed pull request #11939: Update build-windows.md (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/11939
39 2017-12-18 18:24:15	0|nedn|I am trying to build bitcoin on Mac, stuck at running "autogen.sh" step. Anyone knows what may be missing here? https://pastebin.com/4ndyXPz7
40 2017-12-18 18:26:15	0|sipa|looks like you don't have libtool
41 2017-12-18 18:28:12	0|nedn|thanks! "brew link libtool" fixed it for me
42 2017-12-18 19:25:29	0|jonasschnelli|In SignCompact (message signing), we do: vchSig[0] = 27 + rec + (fCompressed ? 4 : 0);  can someone explain that? There is no specs?
43 2017-12-18 19:25:55	0|jonasschnelli|Is that just appending the recovery id with a flag if its compressed or not in 4 bits?
44 2017-12-18 19:28:42	0|sipa|yes
45 2017-12-18 19:29:24	0|sipa|the + 27 was just a random number to prevent it being confusable with public keys
46 2017-12-18 19:29:37	0|sipa|the +4 was added later for compressed pubkeys
47 2017-12-18 19:29:50	0|sipa|we'll probably need to extend it further for P2WPKH and P2SH-P2WPKH
48 2017-12-18 19:43:54	0|phantomcircuit|heyyy
49 2017-12-18 19:43:56	0|phantomcircuit|500k blocks
50 2017-12-18 19:44:06	0|phantomcircuit|i feel this should involve cake
51 2017-12-18 19:44:30	0|andytoshi|;;bc,blocks
52 2017-12-18 19:44:31	0|gribble|{"blockcount":500008}
53 2017-12-18 19:48:18	0|sipa|phantomcircuit: it's also the 4y anniversary of the term 'hodl'
54 2017-12-18 19:49:03	0|contrapumpkin|screw the price, that's the real milestone
55 2017-12-18 19:59:14	0|jonasschnelli|thanks sipa
56 2017-12-18 20:13:27	0|cluelessperson|phantomcircuit: but you already have lots of cake on your face.
57 2017-12-18 20:16:23	0|phantomcircuit|heh
58 2017-12-18 20:31:07	0|jtimon|for people who care about decimal anyway
59 2017-12-18 20:33:47	0|phantomcircuit|jtimon, i suggested cake
60 2017-12-18 20:38:15	0|jtimon|phantomcircuit: cake is poison, but I'm afraid my beer replacement isn't more healthy
61 2017-12-18 20:38:57	0|phantomcircuit|jtimon, delicious poison
62 2017-12-18 20:44:26	0|meshcollider|Happy half million \o/
63 2017-12-18 21:02:01	0|meshcollider|ryanofsky: thanks for all the reviews today!
64 2017-12-18 21:07:16	0|blaster|I wonder which block size limit we'd be at by 500k if satoshi's idea got added as per https://bitcointalk.org/index.php?topic=1347.msg15366#msg15366
65 2017-12-18 21:18:33	0|ryanofsky|meshcollider, no problem. nice easy reviews