--- Day changed Wed Nov 29 2017
00:07 -!- photonclock_ [~photonclo@47.37.153.193] has joined #bitcoin-core-dev     
00:20 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00::1] has quit [Ping timeout: 252 seconds]     
00:20 < wumpus> jonasschnelli: have tried it on odroid C2, was a bit disappointed at the perfomrance - I don't have a XU4
00:22 < 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
00:22 -!- twistedline [~quassel@unaffiliated/twistedline] has quit [Read error: Connection reset by peer]     
00:23 -!- twistedline [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev     
00:28 < wumpus> regarding storage on the odroid C2 there's not that much options, only USB2.0, and no SATA
00:29 < 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
00:30 < wumpus> also the thing overheats like crazy
00:31 < sipa> the debug.log on my c2 is weird
00:31 < sipa> it seems like it stopped doing anything for about 8 hours
00:31 < jonasschnelli> eMMC would perform better?
00:33 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:454f:112b:9095:f0ea] has joined #bitcoin-core-dev     
00:33 < wumpus> sipa: mine didn't stop for 8 hours but there were lots of unexplained pauses during block validtion
00:36 < wumpus> jonasschnelli: not sure about eMMC speeds, I don't think they're much higher than general MMC ones
00:36 < jonasschnelli> wumpus: referring to http://www.hardkernel.com/main/_Files/prdt/2016/201602/201506301616277586.jpg
00:36 < wumpus> at least it's just a dumb flash card (but embedded) not a real SSD
00:39 -!- quin_ [63392209@gateway/web/freenode/ip.99.57.34.9] has joined #bitcoin-core-dev     
00:40 -!- quin_ [63392209@gateway/web/freenode/ip.99.57.34.9] has quit [Client Quit]     
00:40 < wumpus> ah yes eMMC5.0 is a lot faster
00:41 -!- kabaum [~kalle@178.132.75.146] has joined #bitcoin-core-dev     
00:41 < 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
00:42 < 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".")
00:42 < jonasschnelli> kallewoof: I run it directly host -> LXC
00:42 < wumpus> you don't need to run gitian in a VM but it will always spawn one level of VM at least
00:43 < kallewoof> OK, great! At least I'm not trying to do the impossible.
00:45 < 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
00:45 < jonasschnelli> wumpus: indeed... 
00:45 -!- Jochem [525e2acb@gateway/web/freenode/ip.82.94.42.203] has quit [Ping timeout: 260 seconds]     
00:45 < kallewoof> Gitian sidenote: is there a reason why it doesn't have #!/bin/bash at the top? I use zsh, which explodes.
00:45 < kallewoof> (gitian-build.sh)
00:46 < kallewoof> Running "bash bitcoin/contrib/gitian-build.sh" works fine so no biggie, just annoying.
00:46 < wumpus> dunno, feel free to add it, shellscripting always suffers from the many different kinds of shells with slightly different syntax
00:46 < kallewoof> OK     
00: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.
00:51 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:55 < 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
00:58 < 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
01:01 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev     
01:01 < 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. 
01:03 < wumpus> Provoostenator: what SoC does that have?
01:05 < gmaxwell> wumpus: awesome that you're working on it. imx8 looks pretty exciting.
01:06 < gmaxwell> I hope someone does a novena like board with imx8, would be a lot more interesting than the original novena.
01:06 < 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)?)
01:07 < Provoostenator> I doubt my wifi or home internet is a bottleneck.
01:08 < 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
01:09 < wumpus> Provoostenator: two seconds per block at height 496K is pretty good for ARM
01:10 -!- ula [~ula@b2b-78-94-9-226.unitymedia.biz] has quit [Ping timeout: 250 seconds]     
01:11 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
01:11 < 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
01:11 < midnightmagic> i wish linux supported the solid-run stuff more
01:11 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
01:12 < 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
01:12 < gmaxwell> wumpus: the fact that its a53 is nice... for a long time I wondered if they'd ever existed.
01:12 < wumpus> midnightmagic: which one? i.mx6 is fully upstream supported, as one of the few ARM SoCs?
01:12 < gmaxwell> oh nevermind I'm confused. a57 is the out of order one.
01:13 < gmaxwell> and imx8 is a72 which is a newer out of order one.
01:17 < 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.
01:19 -!- Dummbatz [~dummy@89.126.196.178.dynamic.wline.res.cust.swisscom.ch] has joined #bitcoin-core-dev     
01:20 < 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.
01:21 < wumpus> i.MX8 seems to be 4xA53, 2xA72, for the top range model
01:21 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 264 seconds]     
01:23 < wumpus> midnightmagic: ah another Armada-based one, yes I wouldn't expect anything but pain :)
01:24 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
01:24 < midnightmagic> wumpus: due to NDA restrictions on the documentation?
01:25 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
01:27 < wumpus> midnightmagic: there's that problem, but my experience with their hw is also sort of flakey
01:28 < wumpus> I also remember a glitchy USB interface on one of their SoCs
01:28 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev     
01:29 < 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
01:32 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
01:34 -!- JackH [~laptop@212.78.169.180] has joined #bitcoin-core-dev     
01:34 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
01:35 -!- laurentmt1 [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev     
01:35 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
01:36 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Ping timeout: 255 seconds]     
01:36 -!- laurentmt1 is now known as laurentmt     
01:37 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds]     
01:38 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
01:44 -!- shadow_walker [ca36fcc9@gateway/web/freenode/ip.202.54.252.201] has joined #bitcoin-core-dev     
01:44 < shadow_walker> hi Guys
01:44 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev     
01:44 < shadow_walker> I need some help to create a bitcoin web wallet
01:45 -!- aserc [5d8843ff@gateway/web/freenode/ip.93.136.67.255] has joined #bitcoin-core-dev     
01:45 < shadow_walker> I am trying to understand what is the best approach for the same
01:45 < shadow_walker> should I use the bitcoincore.io or https://github.com/bitcoin/bitcoin
01:45 < shadow_walker> if any one can suggest ?
01:47 < wumpus> #bitcoin please
01:48 < 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? 
01:50 < wumpus> yes, you try abandoning the transaction and re-spending the coins. Likely it was sent with too little fee.
01:50 < wumpus> but ask in #bitcoin please this is not a help channel
01:50 < aserc> not cborg but cberg
01:53 < aserc> hi     
01:53 < aserc> after abandon transaction coins are in wallet no need for assistance for now
01:54 < aserc> :)     
01:54 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
01:54 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Client Quit]     
01:56 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
01:57 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Quit: Leaving]     
01:57 -!- Aaronva__ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
01:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 264 seconds]     
02:00 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]     
02:19 < wumpus> great!
02:34 -!- shadow_walker [ca36fcc9@gateway/web/freenode/ip.202.54.252.201] has quit [Ping timeout: 260 seconds]     
02:38 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []     
02:53 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev     
02:59 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/26efc220a13a...e97039605e0d
02:59 < bitcoin-git> bitcoin/master e1a8ec5 Andras Elso: Fix: Open files read only if requested
02:59 < bitcoin-git> bitcoin/master e970396 Wladimir J. van der Laan: Merge #11747: Fix: Open files read only if requested...
03:02 < wumpus> strange, it looks like commits are still notified here by github but not pulls opening/closing
03:03 < aj> "<bitcoin-git> [bitcoin] vii opened pull request #11785: ..." came through earlier
03:03 < gribble> https://github.com/bitcoin/bitcoin/issues/11785 | Prevent file-descriptor exhaustion from RPC layer by vii · Pull Request #11785 · bitcoin/bitcoin · GitHub
03:05 < wumpus> yes, but not the close for 11747, nor the one I closed before that
03:05 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tnqquspxmzycmjwz] has quit [Quit: Connection closed for inactivity]     
03:05 < wumpus> it seems unreliable lately
03:09 -!- kabaum [~kalle@178.132.75.146] has quit [Ping timeout: 240 seconds]     
03:20 < wumpus> just merged two PRs without anything appearing here.
03:20 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/46d1ebfcf854...32c9b570fcea
03:20 < bitcoin-git> bitcoin/master 8b2c733 Gregory Sanders: clarify abortrescan rpc use
03:20 < bitcoin-git> bitcoin/master 32c9b57 Wladimir J. van der Laan: Merge #11753: clarify abortrescan rpc use...
03:20 < wumpus> oh, that one it does, but not the one before it (#11737)
03:20 < gribble> https://github.com/bitcoin/bitcoin/issues/11737 | Document partial validation in ConnectBlock() by sdaftuar · Pull Request #11737 · bitcoin/bitcoin · GitHub
03:21 -!- wxss [~user@89.34.96.100] has joined #bitcoin-core-dev     
03:22 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev     
03:23 < fanquake> wumpus clearly someone is playing tricks :p
03:23 < wumpus> or the bot is on strike
03:24 < fanquake> Hopefully it's not that smart just yet
03:24 < fanquake> If someone on Windows could test #9254, that'd be great. It's now fixed up, and ready for review.
03:24 < gribble> https://github.com/bitcoin/bitcoin/issues/9254 | [depends] ZeroMQ 4.2.2 by fanquake · Pull Request #9254 · bitcoin/bitcoin · GitHub
03:25 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
03:26 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
03:26 < wumpus> the chance of someone testing it on windows is much higher if we merge it
03:27 < wumpus> as the risk is limited to zeromq support, I think it's acceptable
03:28 < 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.
03:29 < wumpus> fanquake: there's no rush, if you still want to make changes I'll wait
03:30 < wumpus> we don't use curve-keygen so disabling it mgiht speed up the build by a little bit
03:30 < fanquake> Yes, that was my thinking. I'll push that change up now.
03:40 -!- Ayiezamhri [71d2f79e@gateway/web/freenode/ip.113.210.247.158] has joined #bitcoin-core-dev     
03:41 -!- Ayiezamhri [71d2f79e@gateway/web/freenode/ip.113.210.247.158] has left #bitcoin-core-dev []     
04:04 -!- pbase [~pbase@unaffiliated/pbase] has joined #bitcoin-core-dev     
04:08 < pbase> is there an alternative way to keep the chain synced? it is painfully slow!
04:13 -!- pbase [~pbase@unaffiliated/pbase] has quit [Ping timeout: 240 seconds]     
04:18 -!- Aaronva__ is now known as AaronvanW     
04:20 -!- kabaum [~kalle@62.119.166.1] has joined #bitcoin-core-dev     
04:58 -!- kabaum [~kalle@62.119.166.1] has quit [Ping timeout: 255 seconds]     
05:01 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
05:01 -!- aserc [5d8843ff@gateway/web/freenode/ip.93.136.67.255] has quit [Ping timeout: 260 seconds]     
05:01 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
05:21 -!- JackH [~laptop@212.78.169.180] has quit [Ping timeout: 248 seconds]     
05:28 -!- skyfire [~skyfire@185.159.156.6] has joined #bitcoin-core-dev     
05:30 -!- skyfire is now known as skyfirecctv     
05:39 -!- wxss [~user@89.34.96.100] has quit [Ping timeout: 264 seconds]     
05:41 -!- skyfirecctv [~skyfire@185.159.156.6] has quit [Ping timeout: 264 seconds]     
05:41 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
05:42 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
05:47 -!- wxss [~user@89.34.96.100] has joined #bitcoin-core-dev     
05:55 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev     
05:57 -!- LampTreadStone07 [~androirc@198.208.72.10] has joined #bitcoin-core-dev     
06:04 < 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
06:05 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Quit: Leaving...]     
06:05 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #bitcoin-core-dev     
06:07 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
06:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
06:09 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 250 seconds]     
06:14 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has joined #bitcoin-core-dev     
06:14 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has quit [Changing host]     
06:14 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev     
06:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
06:19 < promag> larafale: not currently possible
06:20 < larafale> hum, thx :)
06:22 < promag> larafale: you might be interested in #8549
06:22 < gribble> https://github.com/bitcoin/bitcoin/issues/8549 | zmq: mempool notifications by jmcorgan · Pull Request #8549 · bitcoin/bitcoin · GitHub
06:22 < larafale> great, thx 
06:22 < promag> wumpus: not int the roadmap right?
06:22 < promag> *in     
06:23 < 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.
06:24 < larafale> { chainHeight: 1249987,
06:24 < larafale>   chaintipHash: '00000000000014a8d77d839efc2221d4956e1a6b755b43b551800a3077e0ee05',
06:24 < larafale>   bitmap: '11',
06:24 < larafale>   utxos:
06:24 < larafale>    [ { height: 1249944, value: 0.08333, scriptPubKey: [Object] },
06:24 < larafale>      { height: 2147483647, value: 0.01839147, scriptPubKey: [Object] } ] }
06:24 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev     
06:24 < promag> larafale: in the future don't paste stuff here, use pastebin or github gist for instance
06:25 < larafale> ok no prob, I'm new i don't know the rules :)
06:26 < promag> larafale: you mean REST?
06:27 < larafale> no I made the call from rpc
06:27 < promag> what call?
06:28 < larafale> I'm issuing a getUnspentTransactionOutputs command passing 2 tx hash, above is the result i get
06:28 < larafale> but my concern is why one of the returned utxo has a height way above chain tip
06:31 < promag> I guess that coin is not in a block
06:33 < 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?
06:34 < promag> larafale: that value is 31 bits
06:35 < promag> https://github.com/bitcoin/bitcoin/blob/master/src/coins.h#L38-L39
06:35 < promag> all nHeight bits are 1
06:36 < promag> so, if height is that value then the corresponding transaction is not in the chain
06:36 < promag> jnewbery: ping
06:37 < larafale> really appreciate the feedback, thanks promag
06:37 < promag> no problem
06:38 < promag> larafale: btw, what client are you using
06:38 < larafale> ZMQ client ?
06:39 < promag> no, I mean, getUnspentTransactionOutputs belongs to which library?
06:39 < larafale> I'm building my own client over bitcoind
06:39 < larafale> https://github.com/ruimarinho/bitcoin-core
06:40 < larafale> and that the client I issue RPC command with
06:41 < promag> ah yes, so you are issuing a REST call
06:41 < promag> https://github.com/ruimarinho/bitcoin-core/blob/6d558a486d783d73bd8087e55d42592ff7a3b3ee/src/index.js#L215-L234
06:41 -!- wxss [~user@89.34.96.100] has quit [Quit: leaving]     
06:43 < larafale> is UnspentTransactionOutputs only available throught REST ? I can also run that command throught bitcoin-cli I guess? 
06:43 < larafale> I will try
06:44 < promag> you have RPC listunspents
06:44 < promag> listunspent (singular)
06:45 < larafale> yes ok.
06:54 -!- kabaum [~kalle@h-13-35.A163.priv.bahnhof.se] has joined #bitcoin-core-dev     
07:04 -!- JackH [~laptop@ip-213-127-58-112.ip.prioritytelecom.net] has joined #bitcoin-core-dev     
07:07 -!- jack__ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has joined #bitcoin-core-dev     
07:10 -!- Randolf [~randolf@96.53.47.38] has quit [Ping timeout: 248 seconds]     
07:11 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has quit [Quit: Page closed]     
07:15 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
07:32 < jnewbery> promag: no need to ping. What's the question?
07:44 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
07:52 < 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?
07:52 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev     
07:53 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
07:57 -!- dcousens [~dcousens@CPE-101-181-17-139.lnse4.cha.bigpond.net.au] has quit [Ping timeout: 268 seconds]     
07:58 -!- dcousens [~dcousens@CPE-101-181-19-104.lnse4.cha.bigpond.net.au] has joined #bitcoin-core-dev     
07:59 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
08:00 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
08:18 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
08:24 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
08:24 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev     
08:29 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
08:38 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
08:42 < 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
08:42 -!- LampTreadStone07 [~androirc@198.208.72.10] has quit [Read error: Connection reset by peer]     
08:47 -!- wafa [5da930b7@gateway/web/freenode/ip.93.169.48.183] has joined #bitcoin-core-dev     
08:51 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 276 seconds]     
08:51 -!- wafa [5da930b7@gateway/web/freenode/ip.93.169.48.183] has quit [Client Quit]     
08:53 -!- jack__ [~jack@66-188-250-34.dhcp.eucl.wi.charter.com] has quit [Ping timeout: 268 seconds]     
08:56 < promag> jnewbery: how could I test parallel rescans? so that I know they are really parallel executions server side? 
08:57 < promag> related to #11281
08:57 < 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
08:59 < promag> I mean add a test in test/functional
09:06 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Quit: Leaving]     
09:08 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev     
09:10 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has quit [Client Quit]     
09:12 -!- musalbas [~musalbas@2001:bc8:30c2:ff00::] has joined #bitcoin-core-dev     
09:15 -!- ossifrage [~ossifrage@unaffiliated/ossifrage] has joined #bitcoin-core-dev     
09:19 -!- erichCompSci [6cea5edc@gateway/web/freenode/ip.108.234.94.220] has joined #bitcoin-core-dev     
09:20 < 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
09:21 < erichCompSci> if the final hash
09:21 < erichCompSci> is below a certain threshold
09:21 < erichCompSci> So...when that hash becomes as low as it can go
09:21 < erichCompSci> how do new transactions get verified?
09:21 < erichCompSci> ?     
09:24 < 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.
09:28 < 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
09:28 < erichCompSci> I'm asking on the developer forum
09:29 < 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
09:29 < erichCompSci> new blocks in the chain only take 10 min
09:29 < erichCompSci> sorry
09:29 < erichCompSci> otherwise you have to revisit other things like
09:30 -!- roadcrap [~roadcrypt@unaffiliated/roadcrap] has quit [Ping timeout: 276 seconds]     
09:30 < 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?
09:30 < 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.
09:31 < erichCompSci> But then there won't be a fixed amount of bitcoins?
09:31 < erichCompSci> if you increase the difficulty field?
09:31 < Murch> erichCompSci: The difficulty is not related to the reward schedule
09:32 < erichCompSci> Okay, thats something I didn't know...I'll look into that thanks
09:32 < jnewbery> promag: not sure what you mean by parallel executions server side
09:32 -!- erichCompSci [6cea5edc@gateway/web/freenode/ip.108.234.94.220] has quit [Quit: Page closed]     
09:37 -!- DvdKhl [~Arokh@ip-37-201-211-111.hsi13.unitymediagroup.de] has joined #bitcoin-core-dev     
09:41 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev     
09:47 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
09:53 -!- timothy [tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!]     
09:57 -!- bitcoincore-slac [a7730f03@gateway/web/freenode/ip.167.115.15.3] has joined #bitcoin-core-dev     
10:00 < 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
10:00 < 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
10:00 < jonasschnelli> Need also to rebase because 11281 does not cover "rescanblockchain" (new RPC) yet.
10:00 < 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!
10:01 -!- bitcoincore-slac [a7730f03@gateway/web/freenode/ip.167.115.15.3] has left #bitcoin-core-dev []     
10:09 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt]     
10:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
10:10 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
10:10 < instagibbs> can anyone point to where the wallet magic value is in the repo, if any
10:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
10:13 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
10:16 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
10:17 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
10:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
10:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
10:19 < 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/
10:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
10:20 < 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. 
10:21 < Varunram>  Provoostenator: I think organisation means anything, like even a Github organisation 
10:22 < Varunram> Because every year, there are baby orgs that get a chance at SoC
10:23 < Varunram> If we do discuss about this tomorrow, I can pitch in more info if you'd like :)
10:23 < Provoostenator> The terms and conditions are pretty specific about legal representation though.
10:26 < Varunram> Most probably, that's only in place to accept stuff, I'll ask around and come back though
10:27 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
10:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
10:31 < 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
10:34 < aj> i think software in the public interest also works and is used by debian and others (spi-inc.org)
10:36 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]     
10:36 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 240 seconds]     
10:43 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
10:47 < 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.
10:48 < 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
10:48 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
10:49 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
10:52 < phantomcircuit> instagibbs, what magic value?
10:53 < instagibbs> phantomcircuit, was just wondering how Core knows it's reading hte "right" bdb, talking with sipa about it now
10:54 < instagibbs> I want to make a wallet that simply won't open with Core master, or anything in the near future
10:54 < sipa> but still want it to be BDB?
10:55 < instagibbs> yes     
10:56 < sipa> yes, use minversion
10:57 < instagibbs> yeah, that's what I did for now, removed the footgun surface until its maxed out
11:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
11:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
11:31 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
11:32 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
11:38 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []     
11:46 -!- dcousens [~dcousens@CPE-101-181-19-104.lnse4.cha.bigpond.net.au] has quit [Ping timeout: 240 seconds]     
11:46 -!- dcousens [~dcousens@CPE-101-181-109-10.lnse5.cha.bigpond.net.au] has joined #bitcoin-core-dev     
11:54 -!- kexkey [~kexkey@67.215.11.14] has joined #bitcoin-core-dev     
11:54 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
11:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
11:56 -!- ula [~ula@b2b-78-94-11-194.unitymedia.biz] has joined #bitcoin-core-dev     
12:05 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
12:06 -!- wxss [~user@185.153.179.7] has joined #bitcoin-core-dev     
12:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
12:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
12:19 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
12:20 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
12:20 -!- commavir [vir@2604:180::502b:135a] has joined #bitcoin-core-dev     
12:21 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
12:26 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev     
12:28 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection]     
12:29 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds]     
12:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
12:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
12:31 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
12:33 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
12:41 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
12:43 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
12:44 < jimpo> How do people typically profile/time the code on live nodes? eg. Avg validation time for the past N blocks?
12:44 < BlueMatt> -debug=bench
12:45 < BlueMatt> (and -logtimemicros)
12:45 < jimpo> Ah, cool
12:57 -!- veleiro [~sleeper@fsf/member/veleiro] has joined #bitcoin-core-dev     
12:57 -!- frostbyte1982 [18f845a2@gateway/web/freenode/ip.24.248.69.162] has joined #bitcoin-core-dev     
12:58 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
13:08 -!- veleiro [~sleeper@fsf/member/veleiro] has left #bitcoin-core-dev []     
13:13 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
13:13 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-uylxslcrwquyqnbe] has joined #bitcoin-core-dev     
13:14 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
13:15 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
13:17 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
13:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
13:19 < 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
13:21 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection]     
13:29 < 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
13:30 < sipa> seems reasonable to me
13:32 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
13:34 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
13:38 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
13:39 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
13:53 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
13:54 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]     
13:56 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
13:58 -!- kexkey [~kexkey@67.215.11.14] has quit [Ping timeout: 276 seconds]     
14:00 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tieifxashleptdfe] has joined #bitcoin-core-dev     
14:00 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 276 seconds]     
14:01 < bitcoin-git> [bitcoin] eklitzke opened pull request #11790: Add pixmaps for testnet and regtest (master...pixmaps) https://github.com/bitcoin/bitcoin/pull/11790
14:11 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has joined #bitcoin-core-dev     
14:11 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has quit [Changing host]     
14:11 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev     
14:12 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
14:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
14:15 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
14:17 < bitcoin-git> [bitcoin] jnewbery opened pull request #11791: [tests] Rename NodeConn and NodeConnCB (master...rename_node_conn) https://github.com/bitcoin/bitcoin/pull/11791
14:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
14:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
14:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
14:33 < jonasschnelli> eck: pixmaps? for the application icons?
14:33 < jonasschnelli> Some years ago we moved from pixmaps to the dynamic generated icons via networkstyle.cpp
14:35 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds]     
14:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
14:43 -!- Guyver2 [~Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]     
14:46 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
14:48 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
14:48 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
14:49 < eck> they're still used on linux (and i imagine on os x and windows) to provide an application icon
14:50 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
14:50 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
14:50 < eck> specifically via the Icon= entry in the .desktop file
14:51 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
14:51 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev     
14:52 < jonasschnelli> eck: Yes. Windows has that direct link to testnet. That's true.
14:52 < jonasschnelli> Not sure about linux
14:52 < jonasschnelli> Maybe via contrib/
14:56 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev     
14:58 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds]     
15:06 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...]     
15:06 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 258 seconds]     
15:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
15:08 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []     
15:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
15:10 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 248 seconds]     
15:17 < 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?
15:19 < sipa> i believe so, but i don't think we ever use that
15:19 < sipa> CCoinsCache certainly isn't
15:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
15:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
15:23 < 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?
15:23 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 248 seconds]     
15:24 < sipa> i think the txindex should be modified to use the signal mechanism the wallet uses too
15:24 < 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
15:24 < sipa> which afaik matt is moving to support multiple threads
15:24 < sipa> and yes, a separate db sounds right to me - we'd have lower consistency guarantees then, though
15:25 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Read error: Connection reset by peer]     
15:25 < sipa> which i'm not sure will be acceptable
15:25 < jonasschnelli> Anyone up for a quick review: https://github.com/bitcoin/bitcoin/pull/11616/files?
15:26 < jimpo> consistency for RPC calls? couldn't it just block until the txindex is in sync?
15:26 < jimpo> GetRawTransaction RPC, specifically
15:26 < sipa> jimpo: perhaps
15:27 < 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
15:27 < 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)
15:27 < 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)
15:28 < sipa> making the rpc block until it's caught up is probably the right approach initially but feels much less clean
15:28 < jimpo> That might make sense for possible future indexes, but would break compatibility for GetRawTransaction, no?
15:28 -!- twistedline [~quassel@unaffiliated/twistedline] has quit [Ping timeout: 252 seconds]     
15:28 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
15:28 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev     
15:30 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev     
15:31 -!- twistedline [~quassel@unaffiliated/twistedline] has joined #bitcoin-core-dev     
15:33 < 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.
15:35 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
15:39 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
15:39 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev     
16:05 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
16:06 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
16:13 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
16:15 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
16:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1]     
16:23 -!- Peilin-Yang [0819c51a@gateway/web/freenode/ip.8.25.197.26] has joined #bitcoin-core-dev     
16:31 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 260 seconds]     
16:31 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
16:32 -!- DvdKhl [~Arokh@ip-37-201-211-111.hsi13.unitymediagroup.de] has quit [Ping timeout: 260 seconds]     
16:33 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
16:38 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds]     
16:41 -!- Peilin-Yang [0819c51a@gateway/web/freenode/ip.8.25.197.26] has quit [Quit: Page closed]     
16:50 -!- unholymachine [~quassel@2601:8c:c003:9f16:1ca7:d5b5:613c:ea93] has joined #bitcoin-core-dev     
16:54 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
16:54 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
16:57 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]     
17:14 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
17:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
17:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
17:21 -!- wxss [~user@185.153.179.7] has quit [Quit: leaving]     
17:23 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds]     
17:27 < promag> fanquake: extended tests too? https://github.com/bitcoin/bitcoin/pull/11791#issuecomment-348052591
17:30 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
17:31 < fanquake> promag I can run them also
17:36 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-uylxslcrwquyqnbe] has quit [Quit: Connection closed for inactivity]     
17:39 -!- roidster [~chatzilla@71-84-200-106.dhcp.nrwl.ca.charter.com] has joined #bitcoin-core-dev     
17:43 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
17:45 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []     
17:59 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
18:09 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
18:10 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
18:12 -!- fanquake [~fanquake@unaffiliated/fanquake] has left #bitcoin-core-dev []     
18:12 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed]     
18:17 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection]     
18:17 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
18:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
18:23 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
18:23 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]     
18:29 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tieifxashleptdfe] has quit [Quit: Connection closed for inactivity]     
18:48 -!- Cheeseo [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 248 seconds]     
18:55 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
19:07 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
19:08 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
19:15 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev     
19:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
19:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
19:23 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
19:27 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 268 seconds]     
19:31 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
19:35 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 268 seconds]     
19:35 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection]     
19:41 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 255 seconds]     
19:48 -!- Cory [~Cory@unaffiliated/cory] has quit [Ping timeout: 260 seconds]     
19:53 -!- Pasha [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev     
19:54 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
19:54 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
19:57 -!- Pasha is now known as Cory     
19:59 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
20:00 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
20:16 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
20:16 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
20:17 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
20:18 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 268 seconds]     
20:35 -!- roidster [~chatzilla@71-84-200-106.dhcp.nrwl.ca.charter.com] has quit [Ping timeout: 268 seconds]     
20:40 -!- roidster [~chatzilla@71-84-200-106.dhcp.nrwl.ca.charter.com] has joined #bitcoin-core-dev     
20:40 -!- roidster is now known as Guest70745     
20:40 -!- Guest70745 is now known as roidster     
20:44 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
20:46 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 260 seconds]     
21:02 -!- ula [~ula@b2b-78-94-11-194.unitymedia.biz] has quit [Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/]     
21:11 -!- jouke [~jouke@a80-100-203-151.adsl.xs4all.nl] has quit [Ping timeout: 240 seconds]     
21:11 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
21:13 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
21:13 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
21:14 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has joined #bitcoin-core-dev     
21:29 -!- murr4y [ali@100.94.211.130.bc.googleusercontent.com] has quit [Ping timeout: 246 seconds]     
21:29 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Read error: No route to host]     
21:30 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev     
21:30 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host]     
21:30 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev     
21:35 -!- roidster [~chatzilla@71-84-200-106.dhcp.nrwl.ca.charter.com] has quit [Quit: ChatZilla 0.9.93 [SeaMonkey 2.48/20170707010522]]     
21:46 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 276 seconds]     
21:51 -!- dqx [~dqx@unaffiliated/dqx] has quit [Ping timeout: 240 seconds]     
21:53 -!- dqx [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev     
22:03 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 268 seconds]     
22:04 < warren> MarcoFalke: https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-fedora.md  nice!  how recently did you test this btw?
22:04 -!- arubi_ [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
22:04 < warren> MarcoFalke: I have had python-vm-builder RPM packages for years but it broke sometime this year and couldn't figure out how to fix it. although I use only qemu-kvm, not lxc. 
22:07 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
22:08 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
22:09 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
22:10 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev     
22:19 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer]     
22:19 -!- jouke [~jouke@a80-100-203-151.adsl.xs4all.nl] has joined #bitcoin-core-dev     
22:19 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
22:20 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
22:21 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev     
22:24 -!- dqx [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection]     
22:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
22:26 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
22:28 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer]     
22:29 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev     
22:31 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vbbtkajcqlrtvmni] has joined #bitcoin-core-dev     
22:35 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer]     
22:36 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev     
22:37 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Client Quit]     
22:49 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-rhfgqlbziozzlake] has joined #bitcoin-core-dev     
22:50 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
23:00 -!- chirayu [cb58906d@gateway/web/freenode/ip.203.88.144.109] has joined #bitcoin-core-dev     
23:02 -!- chirayu [cb58906d@gateway/web/freenode/ip.203.88.144.109] has quit [Client Quit]     
23:10 -!- DvdKhl [~Arokh@ip-37-201-211-111.hsi13.unitymediagroup.de] has joined #bitcoin-core-dev     
23:10 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
23:17 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
23:17 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
23:18 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
23:19 < bitcoin-git> [bitcoin] Varunram opened pull request #11793: Docs: Bump OS X version to 10.13 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/11793
23:19 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
23:19 -!- Krellan [~krellan@2601:640:4000:ab47:208f:23df:4e27:a1c9] has quit [Read error: Connection reset by peer]     
23:19 < Varunram> ^ This needn't be a standalone PR in itself, can be merged with other fixes
23:20 -!- Krellan [~krellan@2601:640:4000:ab47:5841:9d8a:7994:5b02] has joined #bitcoin-core-dev     
23:23 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has quit [Quit: Plugging out.]     
23:25 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev     
23:27 -!- murr4y [ali@100.94.211.130.bc.googleusercontent.com] has joined #bitcoin-core-dev     
23:27 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
23:29 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
23:37 < bitcoin-git> [bitcoin] laanwj closed pull request #9254: [depends] ZeroMQ 4.2.2 (master...zeromq-4-2-0) https://github.com/bitcoin/bitcoin/pull/9254
23:38 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
23:48 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 248 seconds]     
23:53 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev     
23:55 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev     
23:57 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
23:58 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
23:59 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev