12016-03-29T00:00:42  *** p15 has quit IRC
  22016-03-29T00:06:08  *** Thireus has quit IRC
  32016-03-29T00:08:42  *** Thireus has joined #bitcoin-core-dev
  42016-03-29T00:14:01  *** Alopex has quit IRC
  52016-03-29T00:15:07  *** Alopex has joined #bitcoin-core-dev
  62016-03-29T00:42:43  *** fengling has joined #bitcoin-core-dev
  72016-03-29T00:46:29  *** Thireus has quit IRC
  82016-03-29T00:47:54  *** Thireus has joined #bitcoin-core-dev
  92016-03-29T00:50:33  *** wumpus has quit IRC
 102016-03-29T00:50:43  *** afk11 has quit IRC
 112016-03-29T00:51:01  *** Ylbam has quit IRC
 122016-03-29T00:51:48  *** wumpus has joined #bitcoin-core-dev
 132016-03-29T00:52:11  *** afk11 has joined #bitcoin-core-dev
 142016-03-29T00:53:20  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 152016-03-29T00:59:52  *** jouke has quit IRC
 162016-03-29T01:06:53  *** jouke has joined #bitcoin-core-dev
 172016-03-29T01:10:19  *** p15 has joined #bitcoin-core-dev
 182016-03-29T01:26:20  *** frankenmint has joined #bitcoin-core-dev
 192016-03-29T01:28:21  *** Chris_Stewart_5 has quit IRC
 202016-03-29T01:43:50  *** Thireus has quit IRC
 212016-03-29T01:44:15  *** Thireus has joined #bitcoin-core-dev
 222016-03-29T01:46:24  *** afk11 has quit IRC
 232016-03-29T01:48:46  *** afk11 has joined #bitcoin-core-dev
 242016-03-29T01:56:36  *** fengling has quit IRC
 252016-03-29T02:03:13  *** fengling has joined #bitcoin-core-dev
 262016-03-29T02:10:40  *** johnwhitton has quit IRC
 272016-03-29T02:11:39  *** johnwhitton has joined #bitcoin-core-dev
 282016-03-29T02:14:13  *** frankenmint has quit IRC
 292016-03-29T02:35:56  *** belcher has quit IRC
 302016-03-29T02:54:57  *** achow101 has quit IRC
 312016-03-29T03:09:01  *** Alopex has quit IRC
 322016-03-29T03:09:35  *** hsmiths2 has joined #bitcoin-core-dev
 332016-03-29T03:09:35  *** hsmiths has quit IRC
 342016-03-29T03:10:07  *** Alopex has joined #bitcoin-core-dev
 352016-03-29T03:25:48  *** moli has joined #bitcoin-core-dev
 362016-03-29T03:27:04  *** molz has quit IRC
 372016-03-29T03:47:57  *** frankenmint has joined #bitcoin-core-dev
 382016-03-29T04:14:31  *** johnwhitton has quit IRC
 392016-03-29T04:15:09  *** johnwhitton has joined #bitcoin-core-dev
 402016-03-29T04:22:39  *** dermoth has quit IRC
 412016-03-29T04:23:32  *** dermoth has joined #bitcoin-core-dev
 422016-03-29T04:48:37  *** pavel_ has quit IRC
 432016-03-29T04:48:48  *** paveljanik has joined #bitcoin-core-dev
 442016-03-29T05:00:32  *** molz has joined #bitcoin-core-dev
 452016-03-29T05:01:17  *** Giszmo has quit IRC
 462016-03-29T05:03:28  *** moli has quit IRC
 472016-03-29T05:38:16  *** BCBot has quit IRC
 482016-03-29T06:11:46  *** Ylbam has joined #bitcoin-core-dev
 492016-03-29T06:24:16  *** Thireus has quit IRC
 502016-03-29T06:36:01  *** Alopex has quit IRC
 512016-03-29T06:36:02  *** davec has quit IRC
 522016-03-29T06:36:21  *** davec has joined #bitcoin-core-dev
 532016-03-29T06:37:06  *** Alopex has joined #bitcoin-core-dev
 542016-03-29T07:04:03  *** Don_John has quit IRC
 552016-03-29T07:13:02  *** Alopex has quit IRC
 562016-03-29T07:14:07  *** Alopex has joined #bitcoin-core-dev
 572016-03-29T07:22:08  *** abritoid has joined #bitcoin-core-dev
 582016-03-29T07:27:50  *** BCBot has joined #bitcoin-core-dev
 592016-03-29T07:29:01  *** Alopex has quit IRC
 602016-03-29T07:30:07  *** Alopex has joined #bitcoin-core-dev
 612016-03-29T07:33:32  <GitHub191> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/84370d58ffc6...26794d4645e4
 622016-03-29T07:33:33  <GitHub191> bitcoin/master fa3fafc MarcoFalke: [qa] wallet: Wait for reindex to catch up
 632016-03-29T07:33:33  <GitHub191> bitcoin/master 26794d4 Wladimir J. van der Laan: Merge #7757: [qa] wallet: Wait for reindex to catch up...
 642016-03-29T07:33:39  <GitHub5> [bitcoin] laanwj closed pull request #7757: [qa] wallet: Wait for reindex to catch up (master...Mf1603-qaWalletReindex) https://github.com/bitcoin/bitcoin/pull/7757
 652016-03-29T07:46:55  *** xiangfu has quit IRC
 662016-03-29T08:03:02  <jonasschnelli> wumpus: awesome idea with the "bc-monitor"!
 672016-03-29T08:03:16  <jonasschnelli> Would it only require to connect over ZMQ or also over RPC?
 682016-03-29T08:03:22  <wumpus> thanks :)
 692016-03-29T08:03:29  <jonasschnelli> The later would probably require two stunnels?
 702016-03-29T08:03:41  <wumpus> it requires both, eventually I want to make zmq optional
 712016-03-29T08:04:03  <jonasschnelli> With RPC long poll? Or how would you update the stat?
 722016-03-29T08:04:05  <wumpus> but I'm most interested in the zmq stats myself so that's the priority for what I'm currently buildlng :)
 732016-03-29T08:04:19  <wumpus> just poll, updates will be slower and some things will be missing (like the actiity log)
 742016-03-29T08:04:52  <jonasschnelli> Hmm... the polling is kinda lame/hacky and also I don't like the JSON/http overhead...
 752016-03-29T08:04:53  <wumpus> so the eventual plan is: zmq is *nice*, rpc is required to get the base info
 762016-03-29T08:05:14  <jonasschnelli> I had similar ideas for a new GUI (monitor).
 772016-03-29T08:05:33  <wumpus> JSON and http overhead doesn't matter for things that never change (say the name and version of the node)
 782016-03-29T08:05:45  <jonasschnelli> right..
 792016-03-29T08:05:50  <wumpus> as well as the max size of the mempool
 802016-03-29T08:05:50  <wumpus> etc
 812016-03-29T08:06:28  <wumpus> also things can be updated asynchronously, you don't have to hang the GUI while an RPC request is underway
 822016-03-29T08:06:31  <jonasschnelli> I think we should definitively add a sequence number for each zmq notification.
 832016-03-29T08:07:07  <jonasschnelli> This is at tiny cost...
 842016-03-29T08:07:13  <wumpus> yes I'm not sure why that wasn't done in the first place
 852016-03-29T08:07:24  <jonasschnelli> Right. It would be an API break now.
 862016-03-29T08:07:30  <jonasschnelli> But we might risk that...
 872016-03-29T08:07:33  <wumpus> would need to be a sequence number per notifier, not a global one, you can't expect people to be listening for everything
 882016-03-29T08:07:35  <jonasschnelli> or optionally allow to enable it.
 892016-03-29T08:07:38  <wumpus> right.
 902016-03-29T08:07:50  <jonasschnelli> Right. It should be per message type.
 912016-03-29T08:07:59  <jonasschnelli> A uint64 per message type.
 922016-03-29T08:08:28  <wumpus> nah a uint64 is not necessary
 932016-03-29T08:08:35  <wumpus> you just need to check that next packet is prevpacket+1
 942016-03-29T08:08:39  <wumpus> even a byte woulddo :)
 952016-03-29T08:09:15  <jonasschnelli> Indeed. A "skip" > 256 would be extremely rare.
 962016-03-29T08:09:27  <wumpus> hm  you're right... well ok, 2 bytes then
 972016-03-29T08:09:49  <wumpus> if you miss 65k packets, well, I'd say you're screwed anyway...
 982016-03-29T08:10:04  <jonasschnelli> Hah. True.
 992016-03-29T08:10:08  <jonasschnelli> Let me know when you have your bc-monitor ready for testing..
1002016-03-29T08:10:13  <wumpus> sure!
1012016-03-29T08:10:34  *** jannes has joined #bitcoin-core-dev
1022016-03-29T08:17:42  <wumpus> <jonasschnelli> Hmm... the polling is kinda lame/hacky and also I don't like the JSON/http overhead... <- what about encoding univalues as cbor (http://cbor.io/) instead  *ducks*
1032016-03-29T08:19:37  <wumpus> not actualy convinced how much it would help, but for huge structures like the output of e.g. getrawmempool true it may save a few bytes
1042016-03-29T08:19:39  <jonasschnelli> wumpus: hah! More hacky! But i like it. :)
1052016-03-29T08:19:57  <jonasschnelli> The polling is just not in-sync with thread synchro.
1062016-03-29T08:20:12  <jonasschnelli> The notification approach would scale better IMO
1072016-03-29T08:20:19  <wumpus> I do think json parsing can be made very fast too
1082016-03-29T08:20:35  <wumpus> (e.g. univalue is already plenty faster than the boost thing)
1092016-03-29T08:20:55  <jonasschnelli> I kinda like zmq and I have also though about a channel into the other direction,.. but I'm also aware of the risks.
1102016-03-29T08:21:01  <wumpus> sure, notification is good fo things that change, especially at high frequency
1112016-03-29T08:21:06  <wumpus> it's not a replacement for a command/response system
1122016-03-29T08:21:57  <jonasschnelli> What would speak against accepting requests over zmq (bitcoind listens) and process it async and response with some events (similar to p2p)? Bad design?
1132016-03-29T08:22:03  *** paveljanik has quit IRC
1142016-03-29T08:22:23  <jonasschnelli> With requests I mean: "give me some informations about connected peers",... just some basic stuff.
1152016-03-29T08:22:29  <jonasschnelli> Auth would be a problem.
1162016-03-29T08:22:35  <wumpus> why not use rest instead?
1172016-03-29T08:22:53  <wumpus> we already have an unauthenticated information interface
1182016-03-29T08:22:58  <jonasschnelli> I just don't like having multiple port connected for one purpose (a monitor)
1192016-03-29T08:23:10  <wumpus> (and rest doesn't need to be necessarily json)
1202016-03-29T08:23:45  <jonasschnelli> It would be very difficult to connect a "monitor" app to your remove node.
1212016-03-29T08:23:52  <jonasschnelli> *remote
1222016-03-29T08:24:03  <wumpus> I'd like zmq events for some P2P events though
1232016-03-29T08:24:12  <wumpus> like 'new node connected' 'node disconnected' etc
1242016-03-29T08:24:13  *** PRab has quit IRC
1252016-03-29T08:24:43  <wumpus> jonasschnelli: I'm mostly aiming at local usage right now, that's why I use ncurses in the first place
1262016-03-29T08:25:27  <wumpus> I could split it into two components, one that connects to a local RPC and ZMQ, the other that connects to the tool, and one TCP connection in between. But meh, that's not a priority :)
1272016-03-29T08:25:30  <jonasschnelli> wumpus: Yes. This makes sense. I though about a GUI tool that is also process separated.
1282016-03-29T08:25:31  *** PRab has joined #bitcoin-core-dev
1292016-03-29T08:25:35  <jonasschnelli> And this would require RPC and ZMQ.
1302016-03-29T08:26:03  <wumpus> zmq is not very suitable for over-the-internet usage, if you're considering that
1312016-03-29T08:26:11  <jonasschnelli> Maybe someone could write a proxy-python script that sits behind apache/ngix and bundles the channels, do the SSL, etc.
1322016-03-29T08:26:39  <jonasschnelli> (bundles the channels = RPC & ZMQ)
1332016-03-29T08:26:39  <wumpus> something like websocket notification would work better for that. Wouldn't be too difficult to roll a zmq-to-websocket adapter.
1342016-03-29T08:26:52  <jonasschnelli> right.
1352016-03-29T08:27:18  <wumpus> initialliy I'd have preferred using a streaming http socket for notifications, but zmq is more 'standard'
1362016-03-29T08:27:45  <jonasschnelli> Yes.
1372016-03-29T08:28:43  <jonasschnelli> I think if one likes to connect over the inet with a monitor app, a CGI python script would be sufficient. You could use SSL and http digest from apache/httpd
1382016-03-29T08:29:14  <jonasschnelli> But lets first focus on the monitor locally connected!
1392016-03-29T08:29:31  <wumpus> if it's for over the internet a whole new world of authentication, security, etc opens up... scope creep etc :)
1402016-03-29T08:29:55  *** ebfull has quit IRC
1412016-03-29T08:30:08  <wumpus> I do agree it'd be nice though
1422016-03-29T08:31:37  <jonasschnelli> I really dream of re-usign an old computer as "monitor center" for a couple of nodes... mempool, peers, blocks
1432016-03-29T08:31:39  *** ebfull has joined #bitcoin-core-dev
1442016-03-29T08:32:19  <wumpus> what about snmp support? *sorry, troll mode today*
1452016-03-29T08:32:44  <jonasschnelli> Is that still alive.. :)
1462016-03-29T08:33:01  <jonasschnelli> But yes. Would allow to attach multiple tools.
1472016-03-29T08:33:08  <btcdrak> OMG wumpus.
1482016-03-29T08:33:21  <wumpus> I dont't actually know, I played around with it >10 years ago when I did something with *gasp* servers
1492016-03-29T08:33:32  <jonasschnelli> haha...
1502016-03-29T08:34:07  <btcdrak> mind you, it's probably not a bad idea...
1512016-03-29T08:34:15  <wumpus> the protocol is terrible and the implementations are even worse, brittle and old (think: openssl but worse)
1522016-03-29T08:34:21  <jonasschnelli> I still use it to create some stats from my servers though. I guess "munin" still uses snmp.
1532016-03-29T08:34:45  *** Guyver2 has joined #bitcoin-core-dev
1542016-03-29T08:34:58  <wumpus> you could make a snmp-to-RPC adapter though, if you come up with enough OIDs and learn to speak ASN.1
1552016-03-29T08:35:24  <jonasschnelli> lol
1562016-03-29T08:36:04  <wumpus> jonasschnelli: sure, lots of enterprise equipment still uses it, and the big monitor tools support it. It's just not very internet-ready, unless you use it over a secure monitoring VPN or such.
1572016-03-29T08:36:44  <jonasschnelli> Agree.
1582016-03-29T08:38:59  *** Thireus has joined #bitcoin-core-dev
1592016-03-29T08:47:39  *** MarcoFalke has joined #bitcoin-core-dev
1602016-03-29T08:53:10  <GitHub151> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/597494f5a90c...a0cea89456f8
1612016-03-29T08:53:10  <GitHub151> bitcoin/0.12 c0fe2c9 BtcDrak: Mark p2p alert system as deprecated....
1622016-03-29T08:53:10  <GitHub110> [bitcoin] laanwj closed pull request #7741: [0.12] Mark p2p alert system as deprecated (0.12...alert0) https://github.com/bitcoin/bitcoin/pull/7741
1632016-03-29T08:53:11  <GitHub151> bitcoin/0.12 a0cea89 Wladimir J. van der Laan: Merge #7741: [0.12] Mark p2p alert system as deprecated...
1642016-03-29T08:56:07  <sipa> wumpus: if we need to fix the serialization for gettxoutsetinfo... maybe we can replace it with a merkleized version?
1652016-03-29T08:57:21  <wumpus> sipa: you mean a 6-month masters project for someone? :) or isn't it that bad to do?
1662016-03-29T08:57:34  <sipa> wumpus: i don't mean UTXO commitments
1672016-03-29T08:57:39  <wumpus> ohh!
1682016-03-29T08:58:01  <wumpus> sure, would be good to have a better format
1692016-03-29T08:58:32  <wumpus> I'm everything but married to the current one, and apparently we already broke it once without anyone noticing, so (as long as we mention it in the release notes) I'm not against breaking it again
1702016-03-29T08:58:52  <sipa> but we can iterate over the utxo entries in order like now, but use an incremental merkle tree hasher (similar to the algorithm used by ComputeMerkleRoot and friends now)
1712016-03-29T08:58:58  <wumpus> cool
1722016-03-29T08:59:34  <sipa> the overhead would be the same, and you could make it answer queries for specific entries... and it could later just be converted to a commitment structure
1732016-03-29T08:59:45  <wumpus> yes, after  the memory improvement for the merkle tree hasher it doesn't have to store all the data in meory
1742016-03-29T09:03:03  *** AaronvanW has quit IRC
1752016-03-29T09:06:14  *** johnwhitton has quit IRC
1762016-03-29T09:06:33  *** AaronvanW has joined #bitcoin-core-dev
1772016-03-29T09:08:44  <GitHub100> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/26794d4645e4...aa0d2b263186
1782016-03-29T09:08:44  <GitHub100> bitcoin/master f11c5a3 Wladimir J. van der Laan: devtools: make github-merge.py use py3...
1792016-03-29T09:08:45  <GitHub100> bitcoin/master aa0d2b2 Wladimir J. van der Laan: Merge #7737: devtools: make github-merge.py use py3...
1802016-03-29T09:08:49  <GitHub80> [bitcoin] laanwj closed pull request #7737: devtools: make github-merge.py use py3 (master...2016_03_python_3_github_merge) https://github.com/bitcoin/bitcoin/pull/7737
1812016-03-29T09:11:29  <GitHub88> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/aa0d2b263186...2676e12016db
1822016-03-29T09:11:29  <GitHub88> bitcoin/master cef8bdf Jonas Schnelli: [Wallet][RPC] add missing abandon status documentation
1832016-03-29T09:11:30  <GitHub88> bitcoin/master 2676e12 Wladimir J. van der Laan: Merge #7742: [Wallet][RPC] add missing abandon status documentation...
1842016-03-29T09:11:34  <GitHub177> [bitcoin] laanwj closed pull request #7742: [Wallet][RPC] add missing abandon status documentation (master...2016/03/ab_doc) https://github.com/bitcoin/bitcoin/pull/7742
1852016-03-29T09:15:52  <GitHub34> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/2676e12016db...b35a59179359
1862016-03-29T09:15:53  <GitHub34> bitcoin/master 7eb7029 instagibbs: Add importprunedfunds rpc call
1872016-03-29T09:15:53  <GitHub34> bitcoin/master f1bb13c instagibbs: Added companion removeprunedfunds call.
1882016-03-29T09:15:54  <GitHub34> bitcoin/master b35a591 Wladimir J. van der Laan: Merge #7558: [RPC] Add import/removeprunedfunds rpc call...
1892016-03-29T09:15:58  <GitHub96> [bitcoin] laanwj closed pull request #7558: [RPC] Add import/removeprunedfunds rpc call (master...prunedforport) https://github.com/bitcoin/bitcoin/pull/7558
1902016-03-29T09:25:22  <GitHub90> [bitcoin] jonasschnelli opened pull request #7761: [Qt] remove trailing output-index from transaction-id (master...2016/03/ui_txid) https://github.com/bitcoin/bitcoin/pull/7761
1912016-03-29T09:45:36  *** Guyver2 has quit IRC
1922016-03-29T09:51:49  *** rubensayshi has joined #bitcoin-core-dev
1932016-03-29T10:25:56  *** fengling has quit IRC
1942016-03-29T10:30:59  *** laurentmt has joined #bitcoin-core-dev
1952016-03-29T10:32:10  *** Guyver2 has joined #bitcoin-core-dev
1962016-03-29T10:39:51  *** BCBot_ has joined #bitcoin-core-dev
1972016-03-29T10:43:39  *** laurentmt has quit IRC
1982016-03-29T10:54:50  *** anttea has joined #bitcoin-core-dev
1992016-03-29T10:59:28  *** randy-waterhouse has quit IRC
2002016-03-29T12:01:39  *** dermoth_ has joined #bitcoin-core-dev
2012016-03-29T12:02:05  *** dermoth has quit IRC
2022016-03-29T12:02:07  *** dermoth_ is now known as dermoth
2032016-03-29T12:23:47  *** jtimon has joined #bitcoin-core-dev
2042016-03-29T12:24:13  *** fengling_ has joined #bitcoin-core-dev
2052016-03-29T12:28:56  *** fengling_ has quit IRC
2062016-03-29T12:33:21  <jonasschnelli> wumpus: what about adding a github label "ZMQ"?
2072016-03-29T12:33:29  *** laurentmt has joined #bitcoin-core-dev
2082016-03-29T12:33:52  <jonasschnelli> Maybe each IO should have its label
2092016-03-29T12:33:53  <wumpus> hmm maybe, I generally prefer to keep anything that is about communicating with applications under 'RPC'
2102016-03-29T12:34:06  <jonasschnelli> okay.
2112016-03-29T12:34:15  <wumpus> but I'm not against it, we have some more zmq specific issues now
2122016-03-29T12:34:44  <wumpus> there is a compromise somewhere between general enough labels for sorting, and specific enough
2132016-03-29T12:34:51  <MarcoFalke> what about adding a github label 'easy'?
2142016-03-29T12:35:04  <wumpus> not a bad idea
2152016-03-29T12:36:02  *** abritoid has left #bitcoin-core-dev
2162016-03-29T12:39:36  <GitHub188> [bitcoin] jonasschnelli opened pull request #7762: [ZMQ] append a message sequence number to every ZMQ notification (master...2016/03/zmq_seq) https://github.com/bitcoin/bitcoin/pull/7762
2172016-03-29T12:39:57  <jonasschnelli> MarcoFalke: "Easy" would stand for "trivial"? "Easy" to review?
2182016-03-29T12:43:43  <MarcoFalke> Easy just for issues
2192016-03-29T12:44:25  <MarcoFalke> So when someone want to "try out" patching something in bitcoin, they can jsut grab an easy issue
2202016-03-29T12:44:55  <MarcoFalke> But fixing an issue tagged with easy usually implies the review is easy as well.
2212016-03-29T12:48:00  <wumpus> easy to implement, not so much 'trivial'
2222016-03-29T12:48:21  <wumpus> trivial was used for comment and message changes
2232016-03-29T12:48:38  <wumpus> this can be somewhat more beefy, but not requires deep understanding of bitcoin core itself
2242016-03-29T12:49:00  <wumpus> and indeed for PRs it makes no sense :)
2252016-03-29T13:04:16  <jonasschnelli> maybe we could rename "RPC" to "RPC/ZMQ/REST"?
2262016-03-29T13:04:29  <jonasschnelli> and remove "REST"
2272016-03-29T13:04:59  <jonasschnelli> For "Easy" we could use "easy to implement" (so interpretation is more clean than)
2282016-03-29T13:05:07  <jonasschnelli> *clear
2292016-03-29T13:07:28  *** belcher has joined #bitcoin-core-dev
2302016-03-29T13:11:17  *** Giszmo has joined #bitcoin-core-dev
2312016-03-29T13:18:51  *** Chris_Stewart_5 has joined #bitcoin-core-dev
2322016-03-29T13:45:09  *** laurentmt has quit IRC
2332016-03-29T13:55:33  <wumpus> jonasschnelli: yes, let's do that
2342016-03-29T13:57:51  <wumpus> done
2352016-03-29T13:59:46  <jonasschnelli> Looks good!
2362016-03-29T14:27:26  *** fengling_ has joined #bitcoin-core-dev
2372016-03-29T14:31:24  <morcos> wumpus: 7648 is actually relatively simple code wise, i believe it has gotten a lot of review.  i believe at least one of petertodd's comments were about testing of the consensus code in bip68 which is tested fairly heavily by the new rpc test.
2382016-03-29T14:32:16  *** fengling_ has quit IRC
2392016-03-29T14:37:04  *** p15 has quit IRC
2402016-03-29T14:48:12  <GitHub125> [bitcoin] sipa opened pull request #7763: Reformat version in UpdateTip and other messages (master...hexver) https://github.com/bitcoin/bitcoin/pull/7763
2412016-03-29T14:50:38  <GitHub140> [bitcoin] MarcoFalke opened pull request #7764: [qa] Don't run pruning.py twice (master...Mf1603-qaPruningTwice) https://github.com/bitcoin/bitcoin/pull/7764
2422016-03-29T14:57:54  *** Amnez777 has quit IRC
2432016-03-29T15:07:43  <GitHub4> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/b35a59179359...a65b36ce354a
2442016-03-29T15:07:43  <GitHub4> bitcoin/master faa9f01 MarcoFalke: [qa] Don't run pruning.py twice
2452016-03-29T15:07:44  <GitHub4> bitcoin/master a65b36c Wladimir J. van der Laan: Merge #7764: [qa] Don't run pruning.py twice...
2462016-03-29T15:07:54  <GitHub58> [bitcoin] laanwj closed pull request #7764: [qa] Don't run pruning.py twice (master...Mf1603-qaPruningTwice) https://github.com/bitcoin/bitcoin/pull/7764
2472016-03-29T15:09:51  *** Amnez777 has joined #bitcoin-core-dev
2482016-03-29T15:15:14  *** Amnez777 has quit IRC
2492016-03-29T15:15:14  *** Amnez777 has joined #bitcoin-core-dev
2502016-03-29T15:16:52  <GitHub161> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/a65b36ce354a...d8e862a5a753
2512016-03-29T15:16:53  <GitHub161> bitcoin/master 018b60c Wladimir J. van der Laan: test_framework: detect failure of bitcoind startup...
2522016-03-29T15:16:53  <GitHub161> bitcoin/master d8e862a Wladimir J. van der Laan: Merge #7744: test_framework: detect failure of bitcoind startup...
2532016-03-29T15:17:02  <GitHub133> [bitcoin] laanwj closed pull request #7744: test_framework: detect failure of bitcoind startup (master...2016_03_detect_startup_failure) https://github.com/bitcoin/bitcoin/pull/7744
2542016-03-29T15:23:09  <GitHub11> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/d8e862a5a753...5131005e5b26
2552016-03-29T15:23:10  <GitHub11> bitcoin/master 18f05c7 Wladimir J. van der Laan: build: python 3 compatibility...
2562016-03-29T15:23:10  <GitHub11> bitcoin/master 5131005 Wladimir J. van der Laan: Merge #7723: build: python 3 compatibility...
2572016-03-29T15:23:17  <GitHub163> [bitcoin] laanwj closed pull request #7723: build: python 3 compatibility (master...2016_03_build_python_3) https://github.com/bitcoin/bitcoin/pull/7723
2582016-03-29T15:25:40  *** davec has quit IRC
2592016-03-29T15:26:10  *** davec has joined #bitcoin-core-dev
2602016-03-29T15:32:40  *** Amnez777 has quit IRC
2612016-03-29T15:44:20  *** Amnez777 has joined #bitcoin-core-dev
2622016-03-29T15:45:33  *** frankenmint has quit IRC
2632016-03-29T15:46:08  *** frankenmint has joined #bitcoin-core-dev
2642016-03-29T15:50:45  *** frankenmint has quit IRC
2652016-03-29T15:54:02  *** Amnez777 has quit IRC
2662016-03-29T15:54:02  *** Amnez777 has joined #bitcoin-core-dev
2672016-03-29T15:54:20  *** zooko has joined #bitcoin-core-dev
2682016-03-29T15:57:15  *** laurentmt has joined #bitcoin-core-dev
2692016-03-29T15:57:28  *** laurentmt has quit IRC
2702016-03-29T16:21:52  *** JeromeLegoupil has joined #bitcoin-core-dev
2712016-03-29T16:30:56  *** fengling_ has joined #bitcoin-core-dev
2722016-03-29T16:35:36  *** fengling_ has quit IRC
2732016-03-29T16:43:46  *** droark has quit IRC
2742016-03-29T16:46:42  *** frankenmint has joined #bitcoin-core-dev
2752016-03-29T16:48:32  *** [_smitty] has joined #bitcoin-core-dev
2762016-03-29T16:49:34  *** [_smitty] is now known as roidster
2772016-03-29T16:50:56  *** paveljanik has joined #bitcoin-core-dev
2782016-03-29T16:51:51  *** frankenmint has quit IRC
2792016-03-29T17:07:42  *** lightningbot has joined #bitcoin-core-dev
2802016-03-29T17:07:46  *** teward has joined #bitcoin-core-dev
2812016-03-29T17:07:48  *** dgenr8 has joined #bitcoin-core-dev
2822016-03-29T17:08:06  *** gavinandresen is now known as Guest27562
2832016-03-29T17:08:35  *** cfields has joined #bitcoin-core-dev
2842016-03-29T17:08:40  *** amiller has joined #bitcoin-core-dev
2852016-03-29T17:08:44  *** amiller is now known as Guest26461
2862016-03-29T17:09:28  *** molz has joined #bitcoin-core-dev
2872016-03-29T17:10:49  *** Guest26461 has quit IRC
2882016-03-29T17:10:49  *** Guest26461 has joined #bitcoin-core-dev
2892016-03-29T17:10:49  *** Guest26461 is now known as amiller
2902016-03-29T17:12:33  *** molly has quit IRC
2912016-03-29T17:15:26  *** nsh has joined #bitcoin-core-dev
2922016-03-29T17:16:16  *** sipa_ is now known as sipa
2932016-03-29T17:16:46  *** sipa is now known as Guest47312
2942016-03-29T17:16:46  *** zooko has quit IRC
2952016-03-29T17:17:01  *** binns has joined #bitcoin-core-dev
2962016-03-29T17:17:10  *** Guest47312 is now known as sipax
2972016-03-29T17:18:08  *** mturquette has joined #bitcoin-core-dev
2982016-03-29T17:18:48  *** michagogo has joined #bitcoin-core-dev
2992016-03-29T17:19:40  *** eragmus has joined #bitcoin-core-dev
3002016-03-29T17:21:04  *** jannes has quit IRC
3012016-03-29T17:47:28  *** frankenmint has joined #bitcoin-core-dev
3022016-03-29T17:52:47  *** frankenmint has quit IRC
3032016-03-29T18:05:42  <GitHub158> [bitcoin] laanwj opened pull request #7766: rpc: Register calls where they are defined (master...2016_03_separate_rpc_registration) https://github.com/bitcoin/bitcoin/pull/7766
3042016-03-29T18:12:25  *** JeromeLegoupil has quit IRC
3052016-03-29T18:30:05  *** laurentmt has joined #bitcoin-core-dev
3062016-03-29T18:33:41  *** fengling_ has joined #bitcoin-core-dev
3072016-03-29T18:33:58  *** laurentmt has quit IRC
3082016-03-29T18:38:36  *** fengling_ has quit IRC
3092016-03-29T18:48:52  *** JeromeLegoupil has joined #bitcoin-core-dev
3102016-03-29T18:49:39  *** frankenmint has joined #bitcoin-core-dev
3112016-03-29T18:53:08  *** achow101 has joined #bitcoin-core-dev
3122016-03-29T18:54:17  *** frankenmint has quit IRC
3132016-03-29T19:02:34  <jonasschnelli> Right? importaddress leads to ISMINE_WATCH_UNSOLVABLE? and importpubkey to ISMINE_WATCH_SOLVABLE? (at least for P2PKH outputs)
3142016-03-29T19:03:01  <sipax> yes
3152016-03-29T19:03:26  <jonasschnelli> Is there no internal ripemd(hash()) cache that could map an P2PKH output to a given private key?
3162016-03-29T19:03:49  <jonasschnelli> Or why is importing and address "UNSOLVABLE"?
3172016-03-29T19:05:20  <jonasschnelli> I guess privkey->pubke->hash->hash160->base58c, then compare against required scriptsig pkh and sign...
3182016-03-29T19:10:45  *** moli has joined #bitcoin-core-dev
3192016-03-29T19:12:40  *** molz has quit IRC
3202016-03-29T19:14:02  *** molz has joined #bitcoin-core-dev
3212016-03-29T19:15:32  *** Taek42 is now known as Taek
3222016-03-29T19:16:06  <btcdrak> meeting recap for anyone that missed it https://bitcoincore.org/en/meetings/2016/03/24/
3232016-03-29T19:17:01  *** moli has quit IRC
3242016-03-29T19:18:20  <instagibbs> I was going to check for mediantimepast violations, but I don't have an unpruned node...
3252016-03-29T19:18:35  * instagibbs really should get a larger ssd
3262016-03-29T19:29:05  <jonasschnelli> instagibbs: use a spinning disk?!
3272016-03-29T19:29:25  <instagibbs> what am I, a cave man
3282016-03-29T19:29:35  <gmaxwell> 1tb SSDs can be had for $200-$300 now.
3292016-03-29T19:35:53  <jonasschnelli> instagibbs: lol!
3302016-03-29T19:36:10  <jonasschnelli> use 7200rpm. :)
3312016-03-29T19:37:09  <jonasschnelli> or try: http://www.extremetech.com/wp-content/uploads/2012/12/ibm-3390-hard-drive-teardown-640x353.jpg
3322016-03-29T19:42:49  <btcdrak> jonas 10k rpm or nuthin'
3332016-03-29T19:43:49  <sipax> jonasschnelli: it's unsolvable because it doesn't know what scriptPubKey to construct.
3342016-03-29T19:45:09  <jonasschnelli> sipax: but couldn't it look through all provided/available private keys and generate the pubkey in a temp. keystore and does a lookup?
3352016-03-29T19:45:45  <sipax> jonasschnelli: the point is that it shouldn't
3362016-03-29T19:46:22  <jonasschnelli> hah. ok.
3372016-03-29T19:46:27  <sipax> wallets should not try to guess how to spend coins
3382016-03-29T19:46:51  <sipax> that only leads to confused behaviour, as it makes you forget under what circumstances it works
3392016-03-29T19:46:53  <jonasschnelli> okay. This makes sense.
3402016-03-29T19:47:18  <gmaxwell> for example, say someone pays a 1 of 2, me and you... and you 'guess' correctly that you can spend it, show it in your wallet... then LOL 8 confirms in I claw the funds back.
3412016-03-29T19:47:43  *** d_t has joined #bitcoin-core-dev
3422016-03-29T19:47:47  <sipax> it's like saying "how do you mean, you didn't get my money? oh, i took your pubkey and added 21/7 times the generator to it! that's easy rightz your wallet should have guessed that that was possible and look for it!"
3432016-03-29T19:49:27  <sipax> if you import an address, you're telling the wallet "treat this address as mine, regardless of whether you know how to spend it or not"
3442016-03-29T19:49:53  <sipax> if you want it to be able to solve, you should tell it what it needs to be able to solve (by importing the keys and scripts)
3452016-03-29T19:50:29  *** frankenmint has joined #bitcoin-core-dev
3462016-03-29T19:55:01  *** frankenmint has quit IRC
3472016-03-29T19:55:31  <jonasschnelli> sipax: Agreed.
3482016-03-29T19:56:07  <jonasschnelli> I was just thinking about separating key from the wallet but still use the wallets coinselection, etc.
3492016-03-29T19:56:43  <jonasschnelli> You could do this by impoting the addresses/pubkey and use fundrawtransaction to create your transactions.
3502016-03-29T19:56:55  <sipax> yes, then you need to import the keys, not just the addresses
3512016-03-29T19:57:05  <jonasschnelli> Then sign it locally (in my case over the hardware wallet app), then send it back for broadcasting.
3522016-03-29T19:57:22  <jonasschnelli> Right... I see now the point with the keys instead of the addresses.
3532016-03-29T19:58:10  <jonasschnelli> First I though "addresses could include less risks to 'pass around'". But agree with your statement "wallets should not try to guess how to spend coins".
3542016-03-29T20:07:30  *** Don_John has joined #bitcoin-core-dev
3552016-03-29T20:20:25  *** supasonic has joined #bitcoin-core-dev
3562016-03-29T20:33:01  *** anchow101 has joined #bitcoin-core-dev
3572016-03-29T20:35:32  *** achow101 has quit IRC
3582016-03-29T20:37:45  *** zooko has joined #bitcoin-core-dev
3592016-03-29T20:41:17  <sdaftuar> instagibbs: gmaxwell: i don't see any blocks mined from 12/1/15 to 3/13/16 that include transactions which fail MTP
3602016-03-29T20:41:42  <sdaftuar> however there are very few transactions that use time based locktimes, and only a small fraction of those appear to use times that are remotely relevant
3612016-03-29T20:42:03  <sipax> maybe we should try creating some?
3622016-03-29T20:42:10  <sdaftuar> yeah i think that would be great
3632016-03-29T20:42:31  <gmaxwell> Indeed, for MTP thats the next thing to do.. conduct the test.
3642016-03-29T20:45:13  <gmaxwell> what we're trying to do is avoid a hot cut of MTP, causing block orphaning. (again, this doesn't block deployment; but if there are miners still mining these things they'll need to be actively nagged to stop mining them before the soft fork)
3652016-03-29T20:54:17  *** anchow101 has quit IRC
3662016-03-29T20:54:35  *** achow101 has joined #bitcoin-core-dev
3672016-03-29T21:05:00  *** zooko has quit IRC
3682016-03-29T21:07:23  *** frankenmint has joined #bitcoin-core-dev
3692016-03-29T21:12:14  <cfields> anyone happen to know why bitcoind always uses ATYP DOMAINNAME when connecting to a proxy, even when using ipv4/ipv6 ?
3702016-03-29T21:15:03  *** roidster has quit IRC
3712016-03-29T21:30:40  *** d_t has quit IRC
3722016-03-29T21:33:18  *** Don_John has quit IRC
3732016-03-29T21:46:50  *** cryptapus has joined #bitcoin-core-dev
3742016-03-29T21:57:11  <MarcoFalke> passing getblock(., False) into deserialize of mininode should not fail?
3752016-03-29T22:00:52  *** JeromeLegoupil has quit IRC
3762016-03-29T22:03:29  *** Guyver2 has quit IRC
3772016-03-29T22:04:49  *** PaulCapestany has quit IRC
3782016-03-29T22:05:30  *** PaulCapestany has joined #bitcoin-core-dev
3792016-03-29T22:05:54  *** PaulCapestany has quit IRC
3802016-03-29T22:07:20  *** PaulCapestany has joined #bitcoin-core-dev
3812016-03-29T22:08:06  *** gevs_ has joined #bitcoin-core-dev
3822016-03-29T22:11:34  *** gevs has quit IRC
3832016-03-29T22:15:55  <GitHub186> [bitcoin] MarcoFalke opened pull request #7767: [qa] add test: Deserialize getblock result (master...Mf1603-qaMininodeDeser) https://github.com/bitcoin/bitcoin/pull/7767
3842016-03-29T22:21:31  *** sipax is now known as sipa
3852016-03-29T22:21:34  *** sipa has joined #bitcoin-core-dev
3862016-03-29T22:22:34  *** cryptapus is now known as cryptapus_afk
3872016-03-29T22:25:34  *** Don_John has joined #bitcoin-core-dev
3882016-03-29T22:28:47  *** laurentmt has joined #bitcoin-core-dev
3892016-03-29T22:29:11  *** laurentmt has quit IRC
3902016-03-29T22:39:11  *** fengling_ has joined #bitcoin-core-dev
3912016-03-29T22:43:57  *** fengling_ has quit IRC
3922016-03-29T22:54:42  <GitHub10> [bitcoin] MarcoFalke closed pull request #7767: [qa] add test: Deserialize getblock result (master...Mf1603-qaMininodeDeser) https://github.com/bitcoin/bitcoin/pull/7767
3932016-03-29T23:05:14  *** anttea has quit IRC
3942016-03-29T23:21:47  *** MarcoFalke has quit IRC
3952016-03-29T23:27:25  *** roidster has joined #bitcoin-core-dev
3962016-03-29T23:52:24  *** gijensen has quit IRC
3972016-03-29T23:54:46  *** laurentmt has joined #bitcoin-core-dev
3982016-03-29T23:56:33  *** laurentmt has quit IRC