12017-11-29T00:01:15  <promag> my point is that there should be one line for each file
  22017-11-29T00:02:38  <promag> and:
  32017-11-29T00:02:48  <meshcollider> mmm yeah, ok
  42017-11-29T00:02:50  <promag> * wallets/db.log; since 0.16.0 for fresh installs
  52017-11-29T00:03:04  <meshcollider> Yep that sounds sensible
  62017-11-29T00:03:05  <meshcollider> Thanks :)
  72017-11-29T00:03:13  <promag> err, don't know, I'm bad at copy..
  82017-11-29T00:03:29  <promag> np
  92017-11-29T00:05:56  *** ctya has quit IRC
 102017-11-29T00:06:26  *** archaeal has joined #bitcoin-core-dev
 112017-11-29T00:06:28  *** JamesAU has quit IRC
 122017-11-29T00:06:44  *** JamesAU has joined #bitcoin-core-dev
 132017-11-29T00:07:15  *** hoge_ has quit IRC
 142017-11-29T00:07:25  *** merehap has joined #bitcoin-core-dev
 152017-11-29T00:11:19  <bitcoin-git> [bitcoin] MoneyMakerLTD opened pull request #11784: Update README.md (master...master) https://github.com/bitcoin/bitcoin/pull/11784
 162017-11-29T00:15:49  *** ctya has joined #bitcoin-core-dev
 172017-11-29T00:18:48  *** JamesAU has quit IRC
 182017-11-29T00:19:08  <promag> fanquake: 11784 why?
 192017-11-29T00:19:23  *** JamesAU has joined #bitcoin-core-dev
 202017-11-29T00:20:03  <fanquake> progmag it's replacing the readme with one line about some money maker coin?
 212017-11-29T00:21:14  <meshcollider> heh trivial ACK to that, sounds like a necessary upgrade
 222017-11-29T00:22:07  <promag> fanquake: sounds legit
 232017-11-29T00:22:47  <promag> meshcollider: files.md is almost sorted, wallets/* should be on the bottom?
 242017-11-29T00:23:10  *** wunpunch has quit IRC
 252017-11-29T00:23:29  *** roadcrap has joined #bitcoin-core-dev
 262017-11-29T00:23:54  <meshcollider> oops that should be database/* not wallets/* lol
 272017-11-29T00:23:57  <meshcollider> nice catch
 282017-11-29T00:24:52  <promag> that too
 292017-11-29T00:25:55  <promag> line 10 should move to line 18?
 302017-11-29T00:26:06  *** quantbot has quit IRC
 312017-11-29T00:26:17  <promag> line 12 too
 322017-11-29T00:26:22  *** ctya has quit IRC
 332017-11-29T00:28:42  *** quantbot has joined #bitcoin-core-dev
 342017-11-29T00:30:33  *** quantbot_ has joined #bitcoin-core-dev
 352017-11-29T00:30:55  <meshcollider> done
 362017-11-29T00:31:00  *** Krellan_ is now known as Krellan
 372017-11-29T00:31:36  *** mrios has joined #bitcoin-core-dev
 382017-11-29T00:32:07  *** promag has quit IRC
 392017-11-29T00:32:59  *** ctya has joined #bitcoin-core-dev
 402017-11-29T00:33:03  *** quantbot has quit IRC
 412017-11-29T00:33:35  *** Randolf has quit IRC
 422017-11-29T00:37:36  *** promag has joined #bitcoin-core-dev
 432017-11-29T00:38:28  *** baltakatei has quit IRC
 442017-11-29T00:38:32  *** DvdKhl has quit IRC
 452017-11-29T00:38:41  *** baltakatei has joined #bitcoin-core-dev
 462017-11-29T00:39:40  <promag> meshcollider: wallets/database/*: BDB database environment; only used for wallet since 0.8.0; since 0.16.0
 472017-11-29T00:39:53  *** mrios has quit IRC
 482017-11-29T00:39:53  <promag> should be wallets/database/*: BDB database environment; only used for wallet since 0.16.0?
 492017-11-29T00:40:31  *** AaronvanW has quit IRC
 502017-11-29T00:41:07  *** AaronvanW has joined #bitcoin-core-dev
 512017-11-29T00:45:05  *** AaronvanW has quit IRC
 522017-11-29T00:46:52  <luke-jr> new wallets*
 532017-11-29T00:48:34  *** Victorsueca has quit IRC
 542017-11-29T00:49:18  *** ctya has quit IRC
 552017-11-29T00:49:53  *** Victorsueca has joined #bitcoin-core-dev
 562017-11-29T00:52:30  <promag> that too
 572017-11-29T00:55:24  *** promag has quit IRC
 582017-11-29T00:56:35  *** Emcy_ has quit IRC
 592017-11-29T00:57:16  *** Emcy has joined #bitcoin-core-dev
 602017-11-29T01:01:33  *** hoge_ has joined #bitcoin-core-dev
 612017-11-29T01:01:53  *** Masterboy has quit IRC
 622017-11-29T01:06:51  *** promag has joined #bitcoin-core-dev
 632017-11-29T01:08:03  *** Masterboy has joined #bitcoin-core-dev
 642017-11-29T01:10:35  *** Chris_Stewart_5 has joined #bitcoin-core-dev
 652017-11-29T01:13:04  *** arubi has quit IRC
 662017-11-29T01:22:48  *** Giszmo has joined #bitcoin-core-dev
 672017-11-29T01:24:01  *** Giszmo has quit IRC
 682017-11-29T01:25:38  *** Randolf has joined #bitcoin-core-dev
 692017-11-29T01:26:44  *** fanquake has quit IRC
 702017-11-29T01:26:46  *** Giszmo has joined #bitcoin-core-dev
 712017-11-29T01:28:25  *** ctya has joined #bitcoin-core-dev
 722017-11-29T01:30:22  *** Randolf has quit IRC
 732017-11-29T01:31:29  *** Randolf has joined #bitcoin-core-dev
 742017-11-29T01:33:02  *** hoge_ has quit IRC
 752017-11-29T01:33:30  *** Masterboy has quit IRC
 762017-11-29T01:34:50  *** AaronvanW has joined #bitcoin-core-dev
 772017-11-29T01:37:41  *** Giszmo has quit IRC
 782017-11-29T01:38:45  *** Giszmo has joined #bitcoin-core-dev
 792017-11-29T01:43:34  *** goatpig has quit IRC
 802017-11-29T01:45:54  *** promag has quit IRC
 812017-11-29T02:00:10  *** Chris_Stewart_5 has quit IRC
 822017-11-29T02:05:51  *** Randolf has quit IRC
 832017-11-29T02:06:31  *** fanquake has joined #bitcoin-core-dev
 842017-11-29T02:09:00  <mlz> Hello Core devs, 10000!!! Congratulations and thank you for all your hard work, the price didn't happen without your help! So thank you!  :)
 852017-11-29T02:15:21  *** Randolf has joined #bitcoin-core-dev
 862017-11-29T02:17:03  *** bule has quit IRC
 872017-11-29T02:17:20  *** bule has joined #bitcoin-core-dev
 882017-11-29T02:28:28  *** Ylbam has quit IRC
 892017-11-29T02:37:23  *** Randolf has quit IRC
 902017-11-29T02:45:56  *** dqx has quit IRC
 912017-11-29T02:50:09  *** bule has quit IRC
 922017-11-29T02:51:10  *** wxss has quit IRC
 932017-11-29T02:57:49  *** JamesAU has quit IRC
 942017-11-29T02:58:52  *** AaronvanW has quit IRC
 952017-11-29T02:59:28  *** AaronvanW has joined #bitcoin-core-dev
 962017-11-29T03:04:29  *** AaronvanW has quit IRC
 972017-11-29T03:04:47  *** ctya has quit IRC
 982017-11-29T03:08:09  *** JamesAU has joined #bitcoin-core-dev
 992017-11-29T03:08:14  *** dabura667 has joined #bitcoin-core-dev
1002017-11-29T03:20:07  *** Krellan has quit IRC
1012017-11-29T03:23:04  *** AaronvanW has joined #bitcoin-core-dev
1022017-11-29T03:32:40  *** AaronvanW has quit IRC
1032017-11-29T03:33:15  *** AaronvanW has joined #bitcoin-core-dev
1042017-11-29T03:34:47  *** JamesAU has quit IRC
1052017-11-29T03:36:06  *** AaronvanW has quit IRC
1062017-11-29T03:36:46  *** AaronvanW has joined #bitcoin-core-dev
1072017-11-29T03:56:44  *** AaronvanW has quit IRC
1082017-11-29T03:57:22  *** Giszmo has quit IRC
1092017-11-29T03:58:14  *** Mahesh has joined #bitcoin-core-dev
1102017-11-29T04:00:08  <Mahesh> Mahesh/dchsjzumck/web/886659427
1112017-11-29T04:01:12  *** Randolf has joined #bitcoin-core-dev
1122017-11-29T04:01:53  *** Mahesh has quit IRC
1132017-11-29T04:02:44  *** ctya has joined #bitcoin-core-dev
1142017-11-29T04:15:11  *** Giszmo has joined #bitcoin-core-dev
1152017-11-29T04:18:41  *** Giszmo has quit IRC
1162017-11-29T04:20:46  *** fanquake has quit IRC
1172017-11-29T04:29:01  *** cysm has quit IRC
1182017-11-29T04:31:22  *** JamesAU has joined #bitcoin-core-dev
1192017-11-29T04:34:07  *** cysm has joined #bitcoin-core-dev
1202017-11-29T04:35:27  *** JamesAU has quit IRC
1212017-11-29T04:41:29  *** Giszmo has joined #bitcoin-core-dev
1222017-11-29T04:44:54  *** ctya has quit IRC
1232017-11-29T04:53:40  *** Sinclair6 has quit IRC
1242017-11-29T04:58:36  *** Sinclair6 has joined #bitcoin-core-dev
1252017-11-29T05:07:18  *** Emcy_ has joined #bitcoin-core-dev
1262017-11-29T05:10:01  *** Emcy has quit IRC
1272017-11-29T05:15:09  *** musalbas has quit IRC
1282017-11-29T05:17:09  *** JamesAU has joined #bitcoin-core-dev
1292017-11-29T05:21:32  *** JamesAU has quit IRC
1302017-11-29T05:21:46  *** JamesAU has joined #bitcoin-core-dev
1312017-11-29T05:26:43  <bitcoin-git> [bitcoin] vii opened pull request #11785: Prevent file-descriptor exhaustion from RPC layer (master...master) https://github.com/bitcoin/bitcoin/pull/11785
1322017-11-29T05:54:08  *** Victorsueca has quit IRC
1332017-11-29T05:55:24  *** Victorsueca has joined #bitcoin-core-dev
1342017-11-29T06:26:07  *** shesek has quit IRC
1352017-11-29T06:35:49  *** meshcollider has quit IRC
1362017-11-29T06:38:34  *** shesek has joined #bitcoin-core-dev
1372017-11-29T06:38:34  *** shesek has joined #bitcoin-core-dev
1382017-11-29T06:41:16  *** arubi has joined #bitcoin-core-dev
1392017-11-29T06:43:34  *** meshcollider has joined #bitcoin-core-dev
1402017-11-29T06:47:27  *** davec has quit IRC
1412017-11-29T06:56:13  *** miker_ has joined #bitcoin-core-dev
1422017-11-29T06:56:31  *** miker_ has quit IRC
1432017-11-29T06:58:33  *** Krellan has joined #bitcoin-core-dev
1442017-11-29T06:58:55  *** davec has joined #bitcoin-core-dev
1452017-11-29T06:58:57  *** Krellan has joined #bitcoin-core-dev
1462017-11-29T07:00:00  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
1472017-11-29T07:17:29  *** qrestlove has joined #bitcoin-core-dev
1482017-11-29T07:18:48  *** qrestlove has quit IRC
1492017-11-29T07:19:54  *** qrestlove has joined #bitcoin-core-dev
1502017-11-29T07:22:39  *** JamesAU has quit IRC
1512017-11-29T07:36:26  *** BashCo has quit IRC
1522017-11-29T07:37:04  *** BashCo has joined #bitcoin-core-dev
1532017-11-29T07:38:08  *** photonclock_ has quit IRC
1542017-11-29T07:41:27  *** BashCo has quit IRC
1552017-11-29T08:07:37  *** photonclock_ has joined #bitcoin-core-dev
1562017-11-29T08:20:38  *** qrestlove has quit IRC
1572017-11-29T08:20:51  <wumpus> jonasschnelli: have tried it on odroid C2, was a bit disappointed at the perfomrance - I don't have a XU4
1582017-11-29T08:22:02  <wumpus> jonasschnelli: do have a i.mx8 evaluation board prototype, which seems to be really fast, but don't really dare run a bitcoind sync on it, afraid it will overheat
1592017-11-29T08:22:13  *** twistedline has quit IRC
1602017-11-29T08:23:00  *** twistedline has joined #bitcoin-core-dev
1612017-11-29T08:28:20  <wumpus> regarding storage on the odroid C2 there's not that much options, only USB2.0, and no SATA
1622017-11-29T08:29:51  <wumpus> I eventually used network block device and a SSD w/ the 1GB ethernet, but that's kind of cheating, and it still wasn't really fast, I didn't have time to investigate further
1632017-11-29T08:30:08  <wumpus> also the thing overheats like crazy
1642017-11-29T08:31:06  <sipa> the debug.log on my c2 is weird
1652017-11-29T08:31:18  <sipa> it seems like it stopped doing anything for about 8 hours
1662017-11-29T08:31:45  <jonasschnelli> eMMC would perform better?
1672017-11-29T08:33:11  *** qrestlove has joined #bitcoin-core-dev
1682017-11-29T08:33:44  <wumpus> sipa: mine didn't stop for 8 hours but there were lots of unexplained pauses during block validtion
1692017-11-29T08:36:02  <wumpus> jonasschnelli: not sure about eMMC speeds, I don't think they're much higher than general MMC ones
1702017-11-29T08:36:35  <jonasschnelli> wumpus: referring to http://www.hardkernel.com/main/_Files/prdt/2016/201602/201506301616277586.jpg
1712017-11-29T08:36:41  <wumpus> at least it's just a dumb flash card (but embedded) not a real SSD
1722017-11-29T08:39:09  *** quin_ has joined #bitcoin-core-dev
1732017-11-29T08:40:05  <wumpus> ah yes eMMC5.0 is a lot faster
1742017-11-29T08:41:09  *** kabaum has joined #bitcoin-core-dev
1752017-11-29T08:41:22  <wumpus> <wumpus> 14763950080 bytes (15 GB, 14 GiB) copied, 127.03 s, 116 MB/s <- read benchmark from a eMMC on i.MX8, don't know the write speed
1762017-11-29T08:42:03  <kallewoof> Does gitian require you to run inside a VM or is it possible to run it directly? I keep having issues with lxc. ("lxc-execute: start.c: lxc_spawn: 1094 Failed to find gateway addresses. / Failed to spawn container "gitian".")
1772017-11-29T08:42:44  <jonasschnelli> kallewoof: I run it directly host -> LXC
1782017-11-29T08:42:48  <wumpus> you don't need to run gitian in a VM but it will always spawn one level of VM at least
1792017-11-29T08:43:48  <kallewoof> OK, great! At least I'm not trying to do the impossible.
1802017-11-29T08:45:04  <wumpus> re: eMMC speed the problem is that this doesn't really tell how it will perform under our typical leveldb load, which is seek-heavy, not linear-write/read heavy
1812017-11-29T08:45:18  <jonasschnelli> wumpus: indeed...
1822017-11-29T08:45:20  *** Jochem has quit IRC
1832017-11-29T08:45:34  <kallewoof> Gitian sidenote: is there a reason why it doesn't have #!/bin/bash at the top? I use zsh, which explodes.
1842017-11-29T08:45:40  <kallewoof> (gitian-build.sh)
1852017-11-29T08:46:03  <kallewoof> Running "bash bitcoin/contrib/gitian-build.sh" works fine so no biggie, just annoying.
1862017-11-29T08:46:14  <wumpus> dunno, feel free to add it, shellscripting always suffers from the many different kinds of shells with slightly different syntax
1872017-11-29T08:46:39  <kallewoof> OK
1882017-11-29T08:49:49  <wumpus> if you use any kind of looping or conditionals please contribute a python script instead, not a shell script, it's always at least 5 iterations of bash-this-syntax-back-to-the-eighties. But anyhow we have this one and it, more or less, works.
1892017-11-29T08:51:30  *** BashCo has joined #bitcoin-core-dev
1902017-11-29T08:55:49  <gmaxwell> wumpus: imx6 has an internal thermal cut, it'll shut off if you overheat it.  I assume the same for the imx8?  you could put a fan on it
1912017-11-29T08:58:34  <wumpus> gmaxwell: I think so! but as I only have it temporarily (to do reverse-engineering to add GC7000 support to etnaviv) I don't want to take too much risk
1922017-11-29T09:01:31  *** laurentmt has joined #bitcoin-core-dev
1932017-11-29T09:01:50  <Provoostenator> I've been syncing a Xiaomi A1 Android phone using ABCore for the past week or so (with a few interruptions, but I didn't want the battery to explode while I was away). When it's done, I can mail the logs to anyone who's interested.
1942017-11-29T09:03:25  <wumpus> Provoostenator: what SoC does that have?
1952017-11-29T09:05:53  <gmaxwell> wumpus: awesome that you're working on it. imx8 looks pretty exciting.
1962017-11-29T09:06:15  <gmaxwell> I hope someone does a novena like board with imx8, would be a lot more interesting than the original novena.
1972017-11-29T09:06:39  <Provoostenator> It's at height 469K taking about 2 seconds per block. wumpus: https://en.wikipedia.org/wiki/Xiaomi_Mi_A1 (Octa-core (8x2.0GHz Cortex-A53)?)
1982017-11-29T09:07:25  <Provoostenator> I doubt my wifi or home internet is a bottleneck.
1992017-11-29T09:08:26  <wumpus> gmaxwell: it's great hw, it seems really fast, rendering at 4k seems to be around the speed it was with 1080p on i.mx6q
2002017-11-29T09:09:53  <wumpus> Provoostenator: two seconds per block at height 496K is pretty good for ARM
2012017-11-29T09:10:01  *** ula has quit IRC
2022017-11-29T09:11:17  *** Krellan has quit IRC
2032017-11-29T09:11:28  <wumpus> gmaxwell: at least solidrun (from cubox) has plans to make a i.mx8 variant, also purism/librem is looking at it for their phone
2042017-11-29T09:11:53  <midnightmagic> i wish linux supported the solid-run stuff more
2052017-11-29T09:11:58  *** Krellan has joined #bitcoin-core-dev
2062017-11-29T09:12:20  <wumpus> but I think it will be quite popular, I had some link to some other planned board as well but can't find it right now
2072017-11-29T09:12:27  <gmaxwell> wumpus: the fact that its a53 is nice... for a long time I wondered if they'd ever existed.
2082017-11-29T09:12:40  <wumpus> midnightmagic: which one? i.mx6 is fully upstream supported, as one of the few ARM SoCs?
2092017-11-29T09:12:57  <gmaxwell> oh nevermind I'm confused. a57 is the out of order one.
2102017-11-29T09:13:28  <gmaxwell> and imx8 is a72 which is a newer out of order one.
2112017-11-29T09:17:06  <wumpus> midnightmagic: that's the cubox-i variant, I've been running stock debian on mine for years. Their first board was based on Marvell Armada 510, not sure that made it upstream.
2122017-11-29T09:19:35  *** Dummbatz has joined #bitcoin-core-dev
2132017-11-29T09:20:12  <midnightmagic> wumpus: The clearfog pro; the ECC version doesn't exist (in spite of saying it's available on their website) but apparently a pile of the onboard interfaces are glitchy under linux for that board.
2142017-11-29T09:21:27  <wumpus> i.MX8 seems to be 4xA53, 2xA72, for the top range model
2152017-11-29T09:21:58  *** JackH has quit IRC
2162017-11-29T09:23:40  <wumpus> midnightmagic: ah another Armada-based one, yes I wouldn't expect anything but pain :)
2172017-11-29T09:24:52  *** Victorsueca has quit IRC
2182017-11-29T09:24:55  <midnightmagic> wumpus: due to NDA restrictions on the documentation?
2192017-11-29T09:25:23  *** Victorsueca has joined #bitcoin-core-dev
2202017-11-29T09:27:18  <wumpus> midnightmagic: there's that problem, but my experience with their hw is also sort of flakey
2212017-11-29T09:28:24  <wumpus> I also remember a glitchy USB interface on one of their SoCs
2222017-11-29T09:28:24  *** timothy has joined #bitcoin-core-dev
2232017-11-29T09:29:33  <wumpus> it's not impossible that it's a driver issue, but their stance toward upstreaming drivers pretty much means you're stuck with the ancient vendor kernel forever
2242017-11-29T09:32:18  *** AaronvanW has joined #bitcoin-core-dev
2252017-11-29T09:34:28  *** JackH has joined #bitcoin-core-dev
2262017-11-29T09:34:54  *** arubi has quit IRC
2272017-11-29T09:35:03  *** laurentmt1 has joined #bitcoin-core-dev
2282017-11-29T09:35:19  *** arubi has joined #bitcoin-core-dev
2292017-11-29T09:36:36  *** laurentmt has quit IRC
2302017-11-29T09:36:36  *** laurentmt1 is now known as laurentmt
2312017-11-29T09:37:37  *** Emcy_ has quit IRC
2322017-11-29T09:38:22  *** Guyver2 has joined #bitcoin-core-dev
2332017-11-29T09:44:28  *** shadow_walker has joined #bitcoin-core-dev
2342017-11-29T09:44:42  <shadow_walker> hi Guys
2352017-11-29T09:44:42  *** vicenteH has joined #bitcoin-core-dev
2362017-11-29T09:44:57  <shadow_walker> I need some help to create a bitcoin web wallet
2372017-11-29T09:45:03  *** aserc has joined #bitcoin-core-dev
2382017-11-29T09:45:09  <shadow_walker> I am trying to understand what is the best approach for the same
2392017-11-29T09:45:29  <shadow_walker> should I use the bitcoincore.io or https://github.com/bitcoin/bitcoin
2402017-11-29T09:45:39  <shadow_walker> if any one can suggest ?
2412017-11-29T09:47:18  <wumpus> #bitcoin please
2422017-11-29T09:48:54  <aserc> hi need assistance - was sent some transaction few days ago from  old wallet and transaction is not  visible on explorer. Some cborg here told me to upgrade to new node and now have new node and all blockchain was rescaned or not know what was node doing. That transaction is not visible again now what is best option in node to get back that coins. could click abandon transaction but will coins than be in wallet again?
2432017-11-29T09:50:20  <wumpus> yes, you try abandoning the transaction and re-spending the coins. Likely it was sent with too little fee.
2442017-11-29T09:50:32  <wumpus> but ask in #bitcoin please this is not a help channel
2452017-11-29T09:50:38  <aserc> not cborg but cberg
2462017-11-29T09:53:27  <aserc> hi
2472017-11-29T09:53:59  <aserc> after abandon transaction coins are in wallet no need for assistance for now
2482017-11-29T09:54:02  <aserc> :)
2492017-11-29T09:54:11  *** Aaronvan_ has joined #bitcoin-core-dev
2502017-11-29T09:56:25  *** Aaronvan_ has joined #bitcoin-core-dev
2512017-11-29T09:57:09  *** dabura667 has quit IRC
2522017-11-29T09:57:30  *** Aaronva__ has joined #bitcoin-core-dev
2532017-11-29T09:57:58  *** AaronvanW has quit IRC
2542017-11-29T10:00:44  *** Aaronvan_ has quit IRC
2552017-11-29T10:19:19  <wumpus> great!
2562017-11-29T10:35:00  *** shadow_walker has quit IRC
2572017-11-29T10:38:33  *** Cogito_Ergo_Sum has quit IRC
2582017-11-29T10:53:34  *** goatpig has joined #bitcoin-core-dev
2592017-11-29T10:59:41  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/26efc220a13a...e97039605e0d
2602017-11-29T10:59:42  <bitcoin-git> bitcoin/master e1a8ec5 Andras Elso: Fix: Open files read only if requested
2612017-11-29T10:59:42  <bitcoin-git> bitcoin/master e970396 Wladimir J. van der Laan: Merge #11747: Fix: Open files read only if requested...
2622017-11-29T11:02:09  <wumpus> strange, it looks like commits are still notified here by github but not pulls opening/closing
2632017-11-29T11:03:43  <aj> "<bitcoin-git> [bitcoin] vii opened pull request #11785: ..." came through earlier
2642017-11-29T11:03:44  <gribble> https://github.com/bitcoin/bitcoin/issues/11785 | Prevent file-descriptor exhaustion from RPC layer by vii · Pull Request #11785 · bitcoin/bitcoin · GitHub
2652017-11-29T11:05:14  <wumpus> yes, but not the close for 11747, nor the one I closed before that
2662017-11-29T11:05:50  *** meshcollider has quit IRC
2672017-11-29T11:05:55  <wumpus> it seems unreliable lately
2682017-11-29T11:09:05  *** kabaum has quit IRC
2692017-11-29T11:20:12  <wumpus> just merged two PRs without anything appearing here.
2702017-11-29T11:20:21  <bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/46d1ebfcf854...32c9b570fcea
2712017-11-29T11:20:21  <bitcoin-git> bitcoin/master 8b2c733 Gregory Sanders: clarify abortrescan rpc use
2722017-11-29T11:20:22  <bitcoin-git> bitcoin/master 32c9b57 Wladimir J. van der Laan: Merge #11753: clarify abortrescan rpc use...
2732017-11-29T11:20:49  <wumpus> oh, that one it does, but not the one before it (#11737)
2742017-11-29T11:20:50  <gribble> https://github.com/bitcoin/bitcoin/issues/11737 | Document partial validation in ConnectBlock() by sdaftuar · Pull Request #11737 · bitcoin/bitcoin · GitHub
2752017-11-29T11:21:49  *** wxss has joined #bitcoin-core-dev
2762017-11-29T11:22:34  *** fanquake has joined #bitcoin-core-dev
2772017-11-29T11:23:04  <fanquake> wumpus clearly someone is playing tricks :p
2782017-11-29T11:23:45  <wumpus> or the bot is on strike
2792017-11-29T11:24:22  <fanquake> Hopefully it's not that smart just yet
2802017-11-29T11:24:55  <fanquake> If someone on Windows could test #9254, that'd be great. It's now fixed up, and ready for review.
2812017-11-29T11:24:57  <gribble> https://github.com/bitcoin/bitcoin/issues/9254 | [depends] ZeroMQ 4.2.2 by fanquake · Pull Request #9254 · bitcoin/bitcoin · GitHub
2822017-11-29T11:25:03  *** Krellan has quit IRC
2832017-11-29T11:26:23  *** Krellan has joined #bitcoin-core-dev
2842017-11-29T11:26:54  <wumpus> the chance of someone testing it on windows is much higher if we merge it
2852017-11-29T11:27:31  <wumpus> as the risk is limited to zeromq support, I think it's acceptable
2862017-11-29T11:28:32  <fanquake> wumpus If the changes look ok to you, then I think that's fine. The one thing I was going to look at was adding --disable-curve-keygen to our build options. But that doesn't really matter if you'd just like to merge it now.
2872017-11-29T11:29:17  <wumpus> fanquake: there's no rush, if you still want to make changes I'll wait
2882017-11-29T11:30:08  <wumpus> we don't use curve-keygen so disabling it mgiht speed up the build by a little bit
2892017-11-29T11:30:30  <fanquake> Yes, that was my thinking. I'll push that change up now.
2902017-11-29T11:40:27  *** Ayiezamhri has joined #bitcoin-core-dev
2912017-11-29T11:41:03  *** Ayiezamhri has left #bitcoin-core-dev
2922017-11-29T12:04:35  *** pbase has joined #bitcoin-core-dev
2932017-11-29T12:08:23  <pbase> is there an alternative way to keep the chain synced? it is painfully slow!
2942017-11-29T12:13:27  *** pbase has quit IRC
2952017-11-29T12:18:04  *** Aaronva__ is now known as AaronvanW
2962017-11-29T12:20:54  *** kabaum has joined #bitcoin-core-dev
2972017-11-29T12:58:38  *** kabaum has quit IRC
2982017-11-29T13:01:15  *** arubi has quit IRC
2992017-11-29T13:01:25  *** aserc has quit IRC
3002017-11-29T13:01:34  *** arubi has joined #bitcoin-core-dev
3012017-11-29T13:21:03  *** JackH has quit IRC
3022017-11-29T13:28:23  *** skyfire has joined #bitcoin-core-dev
3032017-11-29T13:30:02  *** skyfire is now known as skyfirecctv
3042017-11-29T13:39:58  *** wxss has quit IRC
3052017-11-29T13:41:46  *** skyfirecctv has quit IRC
3062017-11-29T13:41:55  *** Krellan has quit IRC
3072017-11-29T13:42:45  *** Krellan has joined #bitcoin-core-dev
3082017-11-29T13:47:21  *** wxss has joined #bitcoin-core-dev
3092017-11-29T13:55:09  *** larafale has joined #bitcoin-core-dev
3102017-11-29T13:57:16  *** LampTreadStone07 has joined #bitcoin-core-dev
3112017-11-29T14:04:01  <larafale> Hey folks, is it possible for my `bitcoind` to emit only `unconfirmed` tx via ZMQ? currently I received all tx, and when a block arrive I receive the same tx again. I'd like to filter this at the bitcoind level. thx for the feedback guys
3122017-11-29T14:05:20  *** larafale has quit IRC
3132017-11-29T14:05:46  *** larafale has joined #bitcoin-core-dev
3142017-11-29T14:07:53  *** Victorsueca has quit IRC
3152017-11-29T14:09:09  *** Victorsueca has joined #bitcoin-core-dev
3162017-11-29T14:09:27  *** jtimon has quit IRC
3172017-11-29T14:14:11  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
3182017-11-29T14:14:11  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
3192017-11-29T14:17:42  *** promag has joined #bitcoin-core-dev
3202017-11-29T14:19:40  <promag> larafale: not currently possible
3212017-11-29T14:20:09  <larafale> hum, thx :)
3222017-11-29T14:22:05  <promag> larafale: you might be interested in #8549
3232017-11-29T14:22:07  <gribble> https://github.com/bitcoin/bitcoin/issues/8549 | zmq: mempool notifications by jmcorgan · Pull Request #8549 · bitcoin/bitcoin · GitHub
3242017-11-29T14:22:39  <larafale> great, thx
3252017-11-29T14:22:45  <promag> wumpus: not int the roadmap right?
3262017-11-29T14:22:51  <promag> *in
3272017-11-29T14:23:57  <larafale> I also don't get why when I list 2 recent utxo via rpc on my tesnet node, I get one utxo that has a height way above chain height.
3282017-11-29T14:24:03  <larafale> { chainHeight: 1249987,
3292017-11-29T14:24:03  <larafale>   chaintipHash: '00000000000014a8d77d839efc2221d4956e1a6b755b43b551800a3077e0ee05',
3302017-11-29T14:24:03  <larafale>   bitmap: '11',
3312017-11-29T14:24:05  <larafale>   utxos:
3322017-11-29T14:24:07  <larafale>    [ { height: 1249944, value: 0.08333, scriptPubKey: [Object] },
3332017-11-29T14:24:09  <larafale>      { height: 2147483647, value: 0.01839147, scriptPubKey: [Object] } ] }
3342017-11-29T14:24:45  *** dgenr8 has joined #bitcoin-core-dev
3352017-11-29T14:24:49  <promag> larafale: in the future don't paste stuff here, use pastebin or github gist for instance
3362017-11-29T14:25:12  <larafale> ok no prob, I'm new i don't know the rules :)
3372017-11-29T14:26:57  <promag> larafale: you mean REST?
3382017-11-29T14:27:19  <larafale> no I made the call from rpc
3392017-11-29T14:27:37  <promag> what call?
3402017-11-29T14:28:23  <larafale> I'm issuing a getUnspentTransactionOutputs command passing 2 tx hash, above is the result i get
3412017-11-29T14:28:46  <larafale> but my concern is why one of the returned utxo has a height way above chain tip
3422017-11-29T14:31:06  <promag> I guess that coin is not in a block
3432017-11-29T14:33:08  <larafale> you are right, now that the tx got included in a block I get a valid height. But how would you explain the height: 2147483647 when it was not included? if it's not included in a block yet what does height represent and how did that number got there?
3442017-11-29T14:34:24  <promag> larafale: that value is 31 bits
3452017-11-29T14:35:10  <promag> https://github.com/bitcoin/bitcoin/blob/master/src/coins.h#L38-L39
3462017-11-29T14:35:43  <promag> all nHeight bits are 1
3472017-11-29T14:36:40  <promag> so, if height is that value then the corresponding transaction is not in the chain
3482017-11-29T14:36:56  <promag> jnewbery: ping
3492017-11-29T14:37:42  <larafale> really appreciate the feedback, thanks promag
3502017-11-29T14:37:52  <promag> no problem
3512017-11-29T14:38:01  <promag> larafale: btw, what client are you using
3522017-11-29T14:38:19  <larafale> ZMQ client ?
3532017-11-29T14:39:18  <promag> no, I mean, getUnspentTransactionOutputs belongs to which library?
3542017-11-29T14:39:27  <larafale> I'm building my own client over bitcoind
3552017-11-29T14:39:58  <larafale> https://github.com/ruimarinho/bitcoin-core
3562017-11-29T14:40:14  <larafale> and that the client I issue RPC command with
3572017-11-29T14:41:07  <promag> ah yes, so you are issuing a REST call
3582017-11-29T14:41:40  <promag> https://github.com/ruimarinho/bitcoin-core/blob/6d558a486d783d73bd8087e55d42592ff7a3b3ee/src/index.js#L215-L234
3592017-11-29T14:41:45  *** wxss has quit IRC
3602017-11-29T14:43:27  <larafale> is UnspentTransactionOutputs only available throught REST ? I can also run that command throught bitcoin-cli I guess?
3612017-11-29T14:43:30  <larafale> I will try
3622017-11-29T14:44:32  <promag> you have RPC listunspents
3632017-11-29T14:44:50  <promag> listunspent (singular)
3642017-11-29T14:45:02  <larafale> yes ok.
3652017-11-29T14:54:09  *** kabaum has joined #bitcoin-core-dev
3662017-11-29T15:04:24  *** JackH has joined #bitcoin-core-dev
3672017-11-29T15:07:27  *** jack__ has joined #bitcoin-core-dev
3682017-11-29T15:10:25  *** Randolf has quit IRC
3692017-11-29T15:11:24  *** archaeal has quit IRC
3702017-11-29T15:15:20  *** Randolf has joined #bitcoin-core-dev
3712017-11-29T15:32:48  <jnewbery> promag: no need to ping. What's the question?
3722017-11-29T15:44:49  *** SopaXorzTaker has quit IRC
3732017-11-29T15:52:19  <BlueMatt> sipa: if you get particularly bored, I went down a way-too-deep rabbit hole reading mapBlocksUnlinked and pruning logic, and ended up with a few teaks to help my understanding and fix some tiny edge cases as I go....care to take a look at all but the top commit on https://github.com/TheBlueMatt/bitcoin/commits/2017-11-unlinked-blockx-fixes and tell me if its worth upstreaming?
3742017-11-29T15:52:45  *** SopaXorzTaker has joined #bitcoin-core-dev
3752017-11-29T15:53:49  *** BashCo has quit IRC
3762017-11-29T15:57:49  *** dcousens has quit IRC
3772017-11-29T15:58:19  *** dcousens has joined #bitcoin-core-dev
3782017-11-29T15:59:08  *** Krellan has quit IRC
3792017-11-29T16:00:07  *** Krellan has joined #bitcoin-core-dev
3802017-11-29T16:18:14  *** BashCo has joined #bitcoin-core-dev
3812017-11-29T16:24:11  *** SopaXorzTaker has quit IRC
3822017-11-29T16:24:51  *** SopaXorzTaker has joined #bitcoin-core-dev
3832017-11-29T16:29:39  *** Murch has joined #bitcoin-core-dev
3842017-11-29T16:38:03  *** Emcy has joined #bitcoin-core-dev
3852017-11-29T16:42:02  <bitcoin-git> [bitcoin] rawodb closed pull request #11787: Support for SegWit addresses, change addresses and UI request payment (master...pr/segwit_addresses_master) https://github.com/bitcoin/bitcoin/pull/11787
3862017-11-29T16:42:40  *** LampTreadStone07 has quit IRC
3872017-11-29T16:47:57  *** wafa has joined #bitcoin-core-dev
3882017-11-29T16:51:17  *** Randolf has quit IRC
3892017-11-29T16:51:49  *** wafa has quit IRC
3902017-11-29T16:53:19  *** jack__ has quit IRC
3912017-11-29T16:56:58  <promag> jnewbery: how could I test parallel rescans? so that I know they are really parallel executions server side?
3922017-11-29T16:57:25  <promag> related to #11281
3932017-11-29T16:57:28  <gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
3942017-11-29T16:59:37  <promag> I mean add a test in test/functional
3952017-11-29T17:06:20  *** ossifrage has quit IRC
3962017-11-29T17:08:17  *** ossifrage has joined #bitcoin-core-dev
3972017-11-29T17:10:06  *** ossifrage has quit IRC
3982017-11-29T17:12:10  *** musalbas has joined #bitcoin-core-dev
3992017-11-29T17:15:54  *** ossifrage has joined #bitcoin-core-dev
4002017-11-29T17:19:03  *** erichCompSci has joined #bitcoin-core-dev
4012017-11-29T17:20:51  <erichCompSci> Hello, I was wondering about the following problem.  Miners in bitcoin verify transactions in the blockchain by hashing the previous blocks header, transaction data and a nonce value.  However, the block is only considered a legitimate block
4022017-11-29T17:21:03  <erichCompSci> if the final hash
4032017-11-29T17:21:09  <erichCompSci> is below a certain threshold
4042017-11-29T17:21:23  <erichCompSci> So...when that hash becomes as low as it can go
4052017-11-29T17:21:37  <erichCompSci> how do new transactions get verified?
4062017-11-29T17:21:45  <erichCompSci> ?
4072017-11-29T17:24:11  <Murch> That question is better suited for Bitcoin.stackexchange.com than for this channel. However, the difficulty scales on a range of 2^256, so that scenario is pretty far-fetched.
4082017-11-29T17:28:39  <erichCompSci> Well, I'll move over there then, but I'm afraid I don't understand.  At some point, it will become nearly impossible to create new blocks, hence miners will be unable to mine new bitcoins...so then how are transactions verified?  After all, miners mine by creating the blocks in the blockchain that also verify transactions...so if miners will eventually be unable to mine new coins they must be unable to create new bloc
4092017-11-29T17:28:44  <erichCompSci> I'm asking on the developer forum
4102017-11-29T17:29:15  <erichCompSci> someone must be thinking of this...how are you going to do the hashing post mining era so that transactions still only take 10 min
4112017-11-29T17:29:30  <erichCompSci> new blocks in the chain only take 10 min
4122017-11-29T17:29:32  <erichCompSci> sorry
4132017-11-29T17:29:41  <erichCompSci> otherwise you have to revisit other things like
4142017-11-29T17:30:17  *** roadcrap has quit IRC
4152017-11-29T17:30:43  <erichCompSci> block chain lengths can no longer be used for consensus as the hashes don't have a specific value they have to be under...what will the new rule be?
4162017-11-29T17:30:44  <Murch> erichCompSci: The sun will go out before our capacity to increase the difficulty runs out. Also, we could just make the difficulty field bigger.
4172017-11-29T17:31:25  <erichCompSci> But then there won't be a fixed amount of bitcoins?
4182017-11-29T17:31:35  <erichCompSci> if you increase the difficulty field?
4192017-11-29T17:31:52  <Murch> erichCompSci: The difficulty is not related to the reward schedule
4202017-11-29T17:32:11  <erichCompSci> Okay, thats something I didn't know...I'll look into that thanks
4212017-11-29T17:32:13  <jnewbery> promag: not sure what you mean by parallel executions server side
4222017-11-29T17:32:34  *** erichCompSci has quit IRC
4232017-11-29T17:37:40  *** DvdKhl has joined #bitcoin-core-dev
4242017-11-29T17:41:08  *** Dizzle has joined #bitcoin-core-dev
4252017-11-29T17:47:06  *** jtimon has joined #bitcoin-core-dev
4262017-11-29T17:53:31  *** timothy has quit IRC
4272017-11-29T17:57:16  *** bitcoincore-slac has joined #bitcoin-core-dev
4282017-11-29T18:00:19  <jonasschnelli> promag: wumpus: I'm currently overhauling #11281 ... The parallel rescans can best be tested with an artificial temp. sleep in the inner rescan loop
4292017-11-29T18:00:21  <gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid permanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
4302017-11-29T18:00:39  <jonasschnelli> Need also to rebase because 11281 does not cover "rescanblockchain" (new RPC) yet.
4312017-11-29T18:00:48  <bitcoincore-slac> Just wanted to let everyone who has committed code to bitcoin core that there are A LOT of shout-outs and appreciation to all of you the past few days on Slack, Twitter, etc.  We know what you have done and continuing to do and can't thank you enough!
4322017-11-29T18:01:04  *** bitcoincore-slac has left #bitcoin-core-dev
4332017-11-29T18:09:37  *** laurentmt has quit IRC
4342017-11-29T18:10:00  *** Victorsueca has quit IRC
4352017-11-29T18:10:12  *** bule has joined #bitcoin-core-dev
4362017-11-29T18:10:24  <instagibbs> can anyone point to where the wallet magic value is in the repo, if any
4372017-11-29T18:11:23  *** Victorsueca has joined #bitcoin-core-dev
4382017-11-29T18:13:49  *** intcat has quit IRC
4392017-11-29T18:16:29  *** Krellan has quit IRC
4402017-11-29T18:17:42  *** Krellan has joined #bitcoin-core-dev
4412017-11-29T18:18:20  *** intcat has joined #bitcoin-core-dev
4422017-11-29T18:18:53  *** intcat has quit IRC
4432017-11-29T18:19:07  <Provoostenator> In case we still want to discuss this tomorrow: Google Summer of Code rules archived from last year: http://web.archive.org/web/20170211133438/https://summerofcode.withgoogle.com/rules/
4442017-11-29T18:19:40  *** intcat has joined #bitcoin-core-dev
4452017-11-29T18:20:04  <Provoostenator> One issue might be that they seem to require a real organization, with legacy world stuff like someone being able to legally represent it. So sounds like this would have to go through some random related foundation.
4462017-11-29T18:21:43  <Varunram>  Provoostenator: I think organisation means anything, like even a Github organisation
4472017-11-29T18:22:07  <Varunram> Because every year, there are baby orgs that get a chance at SoC
4482017-11-29T18:23:00  <Varunram> If we do discuss about this tomorrow, I can pitch in more info if you'd like :)
4492017-11-29T18:23:50  <Provoostenator> The terms and conditions are pretty specific about legal representation though.
4502017-11-29T18:26:14  <Varunram> Most probably, that's only in place to accept stuff, I'll ask around and come back though
4512017-11-29T18:27:03  *** intcat has quit IRC
4522017-11-29T18:28:09  *** intcat has joined #bitcoin-core-dev
4532017-11-29T18:32:00  <aj> the software freedom conservancy seems to be the recommended umbrella org so you don't have to setup your own -- https://developers.google.com/open-source/gsoc/help/org-payments
4542017-11-29T18:34:05  <aj> i think software in the public interest also works and is used by debian and others (spi-inc.org)
4552017-11-29T18:36:02  *** Murch has quit IRC
4562017-11-29T18:36:27  *** vicenteH has quit IRC
4572017-11-29T18:43:27  *** Murch has joined #bitcoin-core-dev
4582017-11-29T18:47:15  <Provoostenator> aj: that might get controversial quickly. A single individual accepting and forwarding payments seems better. Ideally someone in a jurisdiction where this wouldn't have weird tax implications.
4592017-11-29T18:48:00  <bitcoin-git> [bitcoin] jnewbery opened pull request #11789: [tests] [travis-ci] Combine logs on failure (master...pr11779.2) https://github.com/bitcoin/bitcoin/pull/11789
4602017-11-29T18:48:30  *** intcat has quit IRC
4612017-11-29T18:49:18  *** intcat has joined #bitcoin-core-dev
4622017-11-29T18:52:56  <phantomcircuit> instagibbs, what magic value?
4632017-11-29T18:53:27  <instagibbs> phantomcircuit, was just wondering how Core knows it's reading hte "right" bdb, talking with sipa about it now
4642017-11-29T18:54:07  <instagibbs> I want to make a wallet that simply won't open with Core master, or anything in the near future
4652017-11-29T18:54:37  <sipa> but still want it to be BDB?
4662017-11-29T18:55:52  <instagibbs> yes
4672017-11-29T18:56:50  <sipa> yes, use minversion
4682017-11-29T18:57:26  <instagibbs> yeah, that's what I did for now, removed the footgun surface until its maxed out
4692017-11-29T19:19:52  *** intcat has quit IRC
4702017-11-29T19:21:06  *** intcat has joined #bitcoin-core-dev
4712017-11-29T19:31:56  *** intcat has quit IRC
4722017-11-29T19:32:49  *** intcat has joined #bitcoin-core-dev
4732017-11-29T19:38:42  *** Cogito_Ergo_Sum has quit IRC
4742017-11-29T19:46:32  *** dcousens has quit IRC
4752017-11-29T19:46:43  *** dcousens has joined #bitcoin-core-dev
4762017-11-29T19:54:05  *** kexkey has joined #bitcoin-core-dev
4772017-11-29T19:54:25  *** laurentmt has joined #bitcoin-core-dev
4782017-11-29T19:54:55  *** promag has quit IRC
4792017-11-29T19:56:20  *** ula has joined #bitcoin-core-dev
4802017-11-29T20:05:39  *** SopaXorzTaker has quit IRC
4812017-11-29T20:06:30  *** wxss has joined #bitcoin-core-dev
4822017-11-29T20:14:10  *** intcat has quit IRC
4832017-11-29T20:14:53  *** intcat has joined #bitcoin-core-dev
4842017-11-29T20:19:30  *** arubi_ has joined #bitcoin-core-dev
4852017-11-29T20:20:32  *** Chris_Stewart_5 has joined #bitcoin-core-dev
4862017-11-29T20:20:34  *** commavir has joined #bitcoin-core-dev
4872017-11-29T20:21:32  *** arubi has quit IRC
4882017-11-29T20:26:56  *** Cheeseo has joined #bitcoin-core-dev
4892017-11-29T20:28:39  *** bule has quit IRC
4902017-11-29T20:29:21  *** Emcy has quit IRC
4912017-11-29T20:29:54  *** intcat has quit IRC
4922017-11-29T20:30:42  *** intcat has joined #bitcoin-core-dev
4932017-11-29T20:31:58  *** Krellan has quit IRC
4942017-11-29T20:33:26  *** Krellan has joined #bitcoin-core-dev
4952017-11-29T20:41:10  *** vicenteH has joined #bitcoin-core-dev
4962017-11-29T20:43:48  *** Randolf has joined #bitcoin-core-dev
4972017-11-29T20:44:37  <jimpo> How do people typically profile/time the code on live nodes? eg. Avg validation time for the past N blocks?
4982017-11-29T20:44:49  <BlueMatt> -debug=bench
4992017-11-29T20:45:15  <BlueMatt> (and -logtimemicros)
5002017-11-29T20:45:46  <jimpo> Ah, cool
5012017-11-29T20:57:32  *** veleiro has joined #bitcoin-core-dev
5022017-11-29T20:57:55  *** frostbyte1982 has joined #bitcoin-core-dev
5032017-11-29T20:58:37  *** bule has joined #bitcoin-core-dev
5042017-11-29T21:08:56  *** veleiro has left #bitcoin-core-dev
5052017-11-29T21:13:11  *** dqx has joined #bitcoin-core-dev
5062017-11-29T21:13:25  *** Ylbam has joined #bitcoin-core-dev
5072017-11-29T21:14:45  *** intcat has quit IRC
5082017-11-29T21:15:36  *** intcat has joined #bitcoin-core-dev
5092017-11-29T21:17:54  *** intcat has quit IRC
5102017-11-29T21:18:52  *** intcat has joined #bitcoin-core-dev
5112017-11-29T21:19:33  <eck> are there pixmaps for bitcoin testnet? i'd like to create .desktop file for bitcoin-qt -testnet=1 that uses the green logo, instead of the orange one
5122017-11-29T21:21:55  *** larafale has quit IRC
5132017-11-29T21:29:36  <eck> nevermind, I found the code that shifts the hue in src/qt/networkstyle.cpp, I will probably submit a PR seeing if I can get testnet and regtest pixmaps checked in for this purpose
5142017-11-29T21:30:20  <sipa> seems reasonable to me
5152017-11-29T21:32:54  *** intcat has quit IRC
5162017-11-29T21:34:05  *** intcat has joined #bitcoin-core-dev
5172017-11-29T21:38:50  *** intcat has quit IRC
5182017-11-29T21:39:36  *** intcat has joined #bitcoin-core-dev
5192017-11-29T21:53:47  *** dqx has quit IRC
5202017-11-29T21:54:04  *** laurentmt has quit IRC
5212017-11-29T21:56:53  *** Emcy has joined #bitcoin-core-dev
5222017-11-29T21:58:44  *** kexkey has quit IRC
5232017-11-29T22:00:01  *** meshcollider has joined #bitcoin-core-dev
5242017-11-29T22:00:02  *** Randolf has quit IRC
5252017-11-29T22:01:23  <bitcoin-git> [bitcoin] eklitzke opened pull request #11790: Add pixmaps for testnet and regtest (master...pixmaps) https://github.com/bitcoin/bitcoin/pull/11790
5262017-11-29T22:11:22  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
5272017-11-29T22:11:22  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev
5282017-11-29T22:12:29  *** dqx has joined #bitcoin-core-dev
5292017-11-29T22:13:04  *** promag has joined #bitcoin-core-dev
5302017-11-29T22:15:35  *** Randolf has joined #bitcoin-core-dev
5312017-11-29T22:17:08  <bitcoin-git> [bitcoin] jnewbery opened pull request #11791: [tests] Rename NodeConn and NodeConnCB (master...rename_node_conn) https://github.com/bitcoin/bitcoin/pull/11791
5322017-11-29T22:19:00  *** promag has quit IRC
5332017-11-29T22:19:00  *** intcat has quit IRC
5342017-11-29T22:20:08  *** intcat has joined #bitcoin-core-dev
5352017-11-29T22:33:05  <jonasschnelli> eck: pixmaps? for the application icons?
5362017-11-29T22:33:29  <jonasschnelli> Some years ago we moved from pixmaps to the dynamic generated icons via networkstyle.cpp
5372017-11-29T22:35:11  *** Randolf has quit IRC
5382017-11-29T22:35:17  *** promag has joined #bitcoin-core-dev
5392017-11-29T22:43:08  *** Guyver2 has quit IRC
5402017-11-29T22:46:52  *** Krellan has quit IRC
5412017-11-29T22:48:05  *** Krellan has joined #bitcoin-core-dev
5422017-11-29T22:48:56  *** intcat has quit IRC
5432017-11-29T22:49:00  <eck> they're still used on linux (and i imagine on os x and windows) to provide an application icon
5442017-11-29T22:50:19  *** dqx has quit IRC
5452017-11-29T22:50:25  *** intcat has joined #bitcoin-core-dev
5462017-11-29T22:50:50  <eck> specifically via the Icon= entry in the .desktop file
5472017-11-29T22:51:44  *** dqx has joined #bitcoin-core-dev
5482017-11-29T22:51:59  *** cheese_ has joined #bitcoin-core-dev
5492017-11-29T22:52:11  <jonasschnelli> eck: Yes. Windows has that direct link to testnet. That's true.
5502017-11-29T22:52:18  <jonasschnelli> Not sure about linux
5512017-11-29T22:52:29  <jonasschnelli> Maybe via contrib/
5522017-11-29T22:56:15  *** RoyceX has joined #bitcoin-core-dev
5532017-11-29T22:58:41  *** cheese_ has quit IRC
5542017-11-29T23:06:04  *** Dizzle has quit IRC
5552017-11-29T23:06:43  *** Chris_Stewart_5 has quit IRC
5562017-11-29T23:08:03  *** intcat has quit IRC
5572017-11-29T23:08:22  *** Cogito_Ergo_Sum has quit IRC
5582017-11-29T23:08:50  *** intcat has joined #bitcoin-core-dev
5592017-11-29T23:10:37  *** RoyceX has quit IRC
5602017-11-29T23:17:18  <jimpo> leveldb docs say that DB is safe for concurrent access by multiple threads: https://github.com/bitcoin/bitcoin/blob/master/src/leveldb/include/leveldb/db.h#L42. Is it assumed that CDBWrapper is as well or no?
5612017-11-29T23:19:35  <sipa> i believe so, but i don't think we ever use that
5622017-11-29T23:19:47  <sipa> CCoinsCache certainly isn't
5632017-11-29T23:19:56  *** intcat has quit IRC
5642017-11-29T23:20:43  *** intcat has joined #bitcoin-core-dev
5652017-11-29T23:23:13  <jimpo> I'm looking into building the tx index in it's own thread instead of ConnectBlock. Do you think 1) it's a bad idea altogether 2) it's safe to keep the txindex data in the blocktree database or 3) the txindex should be rebuilt in its own DB?
5662017-11-29T23:23:43  *** Cory has quit IRC
5672017-11-29T23:24:09  <sipa> i think the txindex should be modified to use the signal mechanism the wallet uses too
5682017-11-29T23:24:30  <jimpo> in case 2, multiple threads would most likely access the same CBlockTreeDB, though alternately there could be multiple wrapper objects with a shared pointer to the same underlying leveldb::DB
5692017-11-29T23:24:35  <sipa> which afaik matt is moving to support multiple threads
5702017-11-29T23:24:56  <sipa> and yes, a separate db sounds right to me - we'd have lower consistency guarantees then, though
5712017-11-29T23:25:00  *** Cheeseo has quit IRC
5722017-11-29T23:25:30  <sipa> which i'm not sure will be acceptable
5732017-11-29T23:25:51  <jonasschnelli> Anyone up for a quick review: https://github.com/bitcoin/bitcoin/pull/11616/files?
5742017-11-29T23:26:03  <jimpo> consistency for RPC calls? couldn't it just block until the txindex is in sync?
5752017-11-29T23:26:21  <jimpo> GetRawTransaction RPC, specifically
5762017-11-29T23:26:35  <sipa> jimpo: perhaps
5772017-11-29T23:27:00  <bitcoin-git> [bitcoin] aaron-hanson opened pull request #11792: Trivial: fix comments for ZeroMQ bitcoind args (master...trivial-zeromq-arguments-comments) https://github.com/bitcoin/bitcoin/pull/11792
5782017-11-29T23:27:07  <sipa> ideally i'd say there is a separate 'indexing subsystem' which is something you talk to explicitly (perhaps using a separate endpoint like the wallet)
5792017-11-29T23:27:37  <sipa> in that case you can easily guarantee consisntency within the subsystem (e.g. you could ask what its best block is, and that would be in sync with its indexing results)
5802017-11-29T23:28:02  <sipa> making the rpc block until it's caught up is probably the right approach initially but feels much less clean
5812017-11-29T23:28:37  <jimpo> That might make sense for possible future indexes, but would break compatibility for GetRawTransaction, no?
5822017-11-29T23:28:41  *** twistedline has quit IRC
5832017-11-29T23:28:41  *** Randolf has joined #bitcoin-core-dev
5842017-11-29T23:28:55  *** Cheeseo has joined #bitcoin-core-dev
5852017-11-29T23:30:25  *** Cory has joined #bitcoin-core-dev
5862017-11-29T23:31:40  *** twistedline has joined #bitcoin-core-dev
5872017-11-29T23:33:49  <jimpo> As far as the separate DB instead of a separate key prefix within the same DB (the current design), it would require a migration, which could be avoided if we were comfortable with concurrent access to CBlockTreeDB.
5882017-11-29T23:35:01  *** dqx has quit IRC
5892017-11-29T23:39:25  *** dqx has joined #bitcoin-core-dev
5902017-11-29T23:39:34  *** Cogito_Ergo_Sum has joined #bitcoin-core-dev