--- Day changed Wed Nov 15 2017
00:00 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
00:00 -!- windsok [~windsok@45.63.59.8] has joined #bitcoin-core-dev     
00:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]     
00:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
00:05 -!- meshcoll- [meshcollid@gateway/shell/elitebnc/x-qfmjfirebdnaqply] has joined #bitcoin-core-dev     
00:07 -!- JackH [~laptop@alvira.static.korbank.pl] has quit [Ping timeout: 248 seconds]     
00:08 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has quit []     
00:09 < kallewoof> After running for awhile, things got faster. I don't know what was going on but it seems to have been temporary.
00:10 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
00:11 < jonasschnelli> kallewoof: anyways,.. that datadir split PR is still welcome. :)
00:11 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:12 < bitcoin-git> [bitcoin] eklitzke opened pull request #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it (master...desktop-file) https://github.com/bitcoin/bitcoin/pull/11690
00:13 < kallewoof> OK! I'll see what I can do. :) Related: I wanted to make a PR that lets you have a readonly "cache" of the blockchain in a separate folder. You can spin up more than one node very easily without having to copy entire chain if you have access to the filesystem of the first one. Would be helpful for testing things I think.
00:16 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 268 seconds]     
00:19 -!- andytosh1 [~apoelstra@wpsoftware.net] has quit [Ping timeout: 240 seconds]     
00:19 -!- JackH [~laptop@91.189.61.70] has joined #bitcoin-core-dev     
00:20 -!- meshcoll- is now known as mesh_     
00:24 -!- JackH [~laptop@91.189.61.70] has quit [Ping timeout: 248 seconds]     
00:24 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit []     
00:25 < meshcollider> You can already move conf file with -conf and #11466 splits walletdir out so soon there'll be nothing left in the datadir itself ;)
00:25 < gribble> https://github.com/bitcoin/bitcoin/issues/11466 | Specify custom wallet directory with -walletdir param by MeshCollider · Pull Request #11466 · bitcoin/bitcoin · GitHub
00:29 -!- JackH [~laptop@91.189.61.70] has joined #bitcoin-core-dev     
00:31 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
00:32 -!- andytoshi [~apoelstra@wpsoftware.net] has joined #bitcoin-core-dev     
00:38 < kallewoof> Huh... 2017-11-15 08:37:57       - Connect 1802 transactions: 156296.66ms (86.735ms/tx, 25.606ms/txin) [270.35s]
00:40 < kallewoof> WOuld this benefit from having only blocks on external drive? I am not sure what part of the fs is used for the tx connect stuff. *checking*
00:42 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds]     
00:43 < wumpus> where you put chainstate is going to have the most influence there
00:43 < jonasschnelli> Yeah.. I guess the lag comes from leveldb internals
00:43 < wumpus> the blocks directory has the block data and block index, which are relatively rarely accessed (unless -txindex)
00:44 < kallewoof> Okay, testing ln -s solution to see if it helps.
00:44 < wumpus> (and unless you're reindexing, at which point it has to go through all blocks twice, but stilll chainstate drive will be much, much more busy)
00:45 < kallewoof> I'm not
00:48 < kallewoof> Yay! 2017-11-15 08:47:24       - Connect 2033 transactions: 2525.99ms (1.242ms/tx, 0.515ms/txin) [9.74s]
00:50 < jonasschnelli> kallewoof: that's with chainstate on internal drive an ln -s of your blocks to your ext drive?
00:51 < kallewoof> Yeah
00:52 < kallewoof> 4.7GB on internal and the rest on external
00:52 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev     
00:53 < wumpus> nice!
00:55 -!- cbag [4d397228@gateway/web/freenode/ip.77.57.114.40] has joined #bitcoin-core-dev     
00:56 -!- cbag [4d397228@gateway/web/freenode/ip.77.57.114.40] has left #bitcoin-core-dev []     
00:57 -!- laurentmt [~Thunderbi@92.154.68.134] has joined #bitcoin-core-dev     
00:57 -!- Emcy [~MC@unaffiliated/emcy] has quit [Quit: Leaving]     
00:57 -!- cbag [4d397228@gateway/web/freenode/ip.77.57.114.40] has joined #bitcoin-core-dev     
01:00 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
01:06 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Quit: Leaving]     
01:06 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev     
01:20 -!- indistylo [~indistylo@119.82.105.106] has joined #bitcoin-core-dev     
01:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
01:26 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #bitcoin-core-dev     
01:26 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
01:29 -!- cl0uding [~cl0uding@79.109.241.185.dyn.user.ono.com] has quit [Ping timeout: 248 seconds]     
01:31 < bitcoin-git> [bitcoin] practicalswift opened pull request #11691: rpc: Add missing lock in getblocktemplate(...). Work around Clang thread safety analysis quirks. (master...rpc-locking) https://github.com/bitcoin/bitcoin/pull/11691
01:31 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 255 seconds]     
01:33 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection]     
01:34 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #bitcoin-core-dev     
01:36 < wumpus> gah, we sould create a separate issue for WFL issues
01:37 -!- Caroline6Von [~Caroline6@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has joined #bitcoin-core-dev     
01:39 -!- wxss [~chatzilla@82.221.112.213] has quit [Remote host closed the connection]     
01:40 -!- halform [~halform@38.95.108.163] has joined #bitcoin-core-dev     
01:40 -!- cl0uding [~cl0uding@79.109.241.185.dyn.user.ono.com] has joined #bitcoin-core-dev     
01:41 -!- wxss [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev     
01:41 -!- Caroline6Von [~Caroline6@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has quit [Remote host closed the connection]     
01:42 -!- vicenteH [~user@195.235.96.150] has joined #bitcoin-core-dev     
01:42 -!- halform [~halform@38.95.108.163] has quit [Client Quit]     
01:43 -!- checksauce [~checksauc@38.95.108.163] has joined #bitcoin-core-dev     
01:46 -!- checksauce [~checksauc@38.95.108.163] has quit [Remote host closed the connection]     
01:46 -!- checksauce [~checksauc@38.95.108.163] has joined #bitcoin-core-dev     
01:48 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Ping timeout: 248 seconds]     
01:48 -!- checksauce [~checksauc@38.95.108.163] has quit [Client Quit]     
01:49 -!- l4ng1t [b6fd03b4@gateway/web/freenode/ip.182.253.3.180] has joined #bitcoin-core-dev     
01:49 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev     
01:50 -!- l4ng1t is now known as Guest27291     
01:51 < Guest27291> hi     
01:51 -!- checksauce [~checksauc@38.95.108.163] has joined #bitcoin-core-dev     
01:52 < Guest27291> can someone confirm segiwit2x is still execute?
01:52 -!- checksauce [~checksauc@38.95.108.163] has quit [Remote host closed the connection]     
01:52 < timothy> Guest27291: OT
01:52 < meshcollider> Guest27291: this is not the place, but segwit2x was called off https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html
01:53 < Guest27291> thanks.. but i still heard a lot of rumour about segwit2x which is make me confuse
01:53 -!- checksauce [~checksauc@38.95.108.163] has joined #bitcoin-core-dev     
01:53 < meshcollider> You should probably discuss it in #bitcoin not this channel
01:55 < Guest27291> sorry.. thanks anyway
01:55 < meshcollider> No problem :)
02:00 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Quit: Leaving.]     
02:02 -!- m8tion03 [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev     
02:03 -!- roconnor_ [~roconnor@host-45-58-247-46.dyn.295.ca] has quit [Ping timeout: 240 seconds]     
02:05 -!- m8tion01 [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Ping timeout: 240 seconds]     
02:11 < bitcoin-git> [bitcoin] practicalswift opened pull request #11692: Remove unused Boost include. Move Boost include. (master...remove-boost-includes) https://github.com/bitcoin/bitcoin/pull/11692
02:12 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 248 seconds]     
02:15 -!- yange [3af63782@gateway/web/freenode/ip.58.246.55.130] has joined #bitcoin-core-dev     
02:27 -!- Guest27291 [b6fd03b4@gateway/web/freenode/ip.182.253.3.180] has quit [Quit: Page closed]     
02:38 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
02:39 < promag> meshcollider: hi
02:39 < meshcollider> promag: Hey :)
02:39 < promag> I'm not familiar with the dumpwallet test
02:39 < promag> let me read it
02:40 < meshcollider> The dumpwallet test basically counts the number of keys present in the file and makes sure that is the number that were generated in the wallet
02:40 < meshcollider> For the scripts part which I added, it relies on the comment to find which scripts correspond to which P2SH address we generated
02:41 < meshcollider> and then reimports to make sure the script was valid
02:42 < meshcollider> I'm looking into the GetAllReserveKeys() comment you wrote now, I'm unsure on that as I didn't change that part of it 
02:42 < promag> +1 on the test
02:43 < promag> dunno why there is no lock in the RPC
02:43 < meshcollider> there is a lock on cs_wallet
02:43 < meshcollider> I commented on the PR, its on line 630
02:43 < meshcollider> https://github.com/bitcoin/bitcoin/pull/11667/files#diff-522490d83dce5375d423b23886e4125eR630
02:44 < meshcollider> Unless I misunderstood what you're referring to
02:44 < promag> f*** sorry!
02:44 < meshcollider> Heh all good :)
02:44 < promag> Missed one expand in gh
02:45 < meshcollider> So do you suggest modifying GetAllReserveKeys or is it ok since it is locked?
02:46 < meshcollider> This is the only place in the entire codebase which that function is called iirc
02:46 < promag> yes, it is fine the way it is
02:46 < meshcollider> Sweet, thanks :)
02:51 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 248 seconds]     
02:57 < meshcollider> promag: lol I like your thumbs_up reaction to that random "O" comment
02:57 < promag> hehe
02:57 < promag> meshcollider: I think you can remove ::GetCScripts
02:57 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...]     
02:57 < promag> why not return a const reference to mapScripts?
02:58 < promag> that way you avoid a bunch of copies, set sorts and map lookups?
02:59 < meshcollider> mmm yeah true, that function is basically a C+P of CBasicKeyStore::GetKeys()
03:00 < meshcollider> Is there any disadvantage to that?
03:00 < promag> meshcollider: the only one I can see is that `cs_KeyStore` must be locked
03:01 < promag> while using/iterating the mapScripts
03:01 < promag> I would wait for someone with deeper knowledge there
03:02 < promag> but the idea is the same as GetAllReserveKeys()
03:03 < promag> but that one is protected by cs_wallet I think
03:03 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev     
03:03 < meshcollider> Yeah
03:05 < meshcollider> Ok maybe just post the idea on the PR so others can weigh in on it when they see it 👍 
03:07 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
03:09 < bitcoin-git> [bitcoin] practicalswift closed pull request #11692: Remove unused Boost include. Move Boost include. (master...remove-boost-includes) https://github.com/bitcoin/bitcoin/pull/11692
03:11 -!- kgc [9f94a4c9@gateway/web/freenode/ip.159.148.164.201] has joined #bitcoin-core-dev     
03:11 < kgc> Hi! I have a question, sorry for interrupting, is it planned in the foreseeable future to change signrawtransaction rpc method to successfully sign an output that was sent to a P2SH-P2WSH address? I tried doing so resulted in failure.
03:13 -!- Jadyn10Hagenes [~Jadyn10Ha@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has joined #bitcoin-core-dev     
03:15 -!- cbag [4d397228@gateway/web/freenode/ip.77.57.114.40] has quit [Ping timeout: 260 seconds]     
03:17 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
03:20 -!- Khunbish [~Khunbish@213.108-247-81.adsl-dyn.isp.belgacom.be] has joined #bitcoin-core-dev     
03:22 -!- Jadyn10Hagenes [~Jadyn10Ha@LFbn-1-936-126.w86-247.abo.wanadoo.fr] has quit [Remote host closed the connection]     
03:22 -!- Flavio25Buckridg [~Flavio25B@ns334669.ip-5-196-64.eu] has quit [Remote host closed the connection]     
03:24 < wumpus> kgc: hrm, I think that should just work?
03:27 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
03:28 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
03:30 -!- Kirstin82Ledner [~Kirstin82@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev     
03:30 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 250 seconds]     
03:31 < meshcollider> kgc wumpus: yep should just work, tested on 0.15.0.1
03:32 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 255 seconds]     
03:32 < wumpus> thanks for testing meshcollider
03:33 < wumpus> kgc: so you need to be a bit more specific about the steps you followed and the result you get
03:39 < kgc> ok, I'll give you a json request I made, give me a sec
03:40 < kgc> {     "jsonrpc": "1.0",     "id": "requestId",     "method": "signrawtransaction",     "params": [         "0200000001d6b67546a418331a5e3877d103e7c95b2e0c69a2e289ddca75383dcca53128120100000000ffffffff0198929800000000001976a914423ffad905158d1d472f5fcd5fbc6916c2fb031f88ac00000000",         [             {                 "txid": "122831a5cc3d3875cadd89e2a2690c2e5bc9e703d177385e1a3318a44675b6d6",                 "vout": 1,      
03:40 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
03:40 < kgc> ok, not the best idea...
03:41 < kgc> https://pastebin.com/2apuckBk
03:41 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
03:41 < wumpus> better use a pastebi.. yea
03:42 -!- Giszmo [~leo@pc-166-83-100-190.cm.vtr.net] has joined #bitcoin-core-dev     
03:43 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
03:45 < kgc> this is the response from that request
03:45 < kgc> https://pastebin.com/SsszYS2w
03:47 < kgc> are there some undocumented parameters I should be passing in?
03:51 -!- limpkin is now known as limpkin_irc     
03:51 -!- yange [3af63782@gateway/web/freenode/ip.58.246.55.130] has quit [Ping timeout: 260 seconds]     
03:52 < wumpus> no, there are no further parameters. Sounds like the transaction is missing the witness somehow?
03:57 -!- andre1 [5ed30a8e@gateway/web/freenode/ip.94.211.10.142] has joined #bitcoin-core-dev     
03:57 -!- andre1 [5ed30a8e@gateway/web/freenode/ip.94.211.10.142] has left #bitcoin-core-dev []     
03:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
03:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
04:01 -!- dcousens [~dcousens@CPE-101-181-100-58.lnse5.cha.bigpond.net.au] has quit [Ping timeout: 255 seconds]     
04:02 -!- dcousens [~dcousens@CPE-120-144-136-90.lnse5.lon.bigpond.net.au] has joined #bitcoin-core-dev     
04:02 < meshcollider> oh hrm
04:03 -!- spinza [~spin@196.212.164.26] has joined #bitcoin-core-dev     
04:03 < kgc> well, it's slightly weird because if I create corresponding deposit address and import it inside bitcoin core wallet, I can send to and spend funds without anyproblems
04:04 < meshcollider> Yeah that's what I thought you were asking about initially
04:05 < wumpus> it looks like the witness was stripped from the transaction
04:06 < meshcollider> Does signtrawtransaction need a witness transaction with empty witness?
04:06 < meshcollider> Or will it add the witness itself
04:07 -!- dcousens [~dcousens@CPE-120-144-136-90.lnse5.lon.bigpond.net.au] has quit [Ping timeout: 240 seconds]     
04:07 < kgc> Hmm, are you suggesting that createrawtransaction method somehow cut out the witness part?
04:07 -!- dcousens [~dcousens@CPE-101-181-95-243.lnse5.cha.bigpond.net.au] has joined #bitcoin-core-dev     
04:08 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
04:09 < meshcollider> createrawtransaction would not create a witness transaction because it would not know it was a P2WSH address would it
04:10 < kgc> yeah, sounds legit, are there any workarounds for this except for realizing serialization myself (which I would much rather avoid)
04:11 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev     
04:11 < meshcollider> Well it shouldn't be hard to make it into a witness transaction right
04:11 < meshcollider> `02000000000101d6b67546a418331a5e3877d103e7c95b2e0c69a2e289ddca75383dcca5312812010000002322002016a91e58e02069f95ea6defba7436199658573c34d384c69779779f4500d7cacffffffff0198929800000000001976a914423ffad905158d1d472f5fcd5fbc6916c2fb031f88ac0000000000`
04:11 < meshcollider> just added marker, flag and empty witness
04:12 < wumpus> it's strange if that is needed though
04:12 < meshcollider> indeed
04:12 < wumpus> so I think we're missing something
04:12 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 248 seconds]     
04:16 < meshcollider> Ideally signrawtransaction should just convert the raw transaction to a witness transaction itself if the input is a witness input right
04:17 < kgc> that would be the desired behavior I guess
04:17 < wumpus> maybe reading the test code helps: https://github.com/bitcoin/bitcoin/blob/master/test/functional/segwit.py
04:18 < wumpus> send_to_witness and create_witness_tx
04:19 < meshcollider> I looked into that, but there are no tests for P2SH-P2WSH it seems 
04:19 < meshcollider> using signrawtransaction
04:20 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
04:20 < meshcollider> because L251-L264 notice that encode_p2sh is False
04:21 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
04:22 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection]     
04:25 < meshcollider> Hmm actually how does it know what the redeemscript is for the P2WSH part
04:25 < meshcollider> you only pass in the P2SH redeemscript aye
04:28 < kgc> these are the parameters I've available: https://pastebin.com/TE1LrR44 should I be passing in as a redeem script something other than: 002016a91e58e02069f95ea6defba7436199658573c34d384c69779779f4500d7cac
04:30 < meshcollider> Yeah see you give it `002016a91e58e02069f95ea6defba7436199658573c34d384c69779779f4500d7cac` which is the redeemScript for the P2SH wrapper, but then it must not know what the redeemscript for the internal `16a91e58e02069f95ea6defba7436199658573c34d384c69779779f4500d7cac` is
04:30 < meshcollider> which is what hex=...
04:30 < meshcollider> but I don't know how to pass that in, no :/
04:30 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev     
04:32 < kgc> I'm confused, then what is it expecting as the redeem script parameter
04:34 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 255 seconds]     
04:34 < meshcollider> I would think what you did was correct, maybe it really isn't supported without importing the script into the wallet... I would wait for someone more experienced than me to say for sure though
04:37 < kgc> well the very least I got the address generation part right :D hopefully someone can shed some light on it, because implementing tx serialization/deserialization/signing and maintaining it would be painful for me
04:37 < kgc> then I might as well start contributing to bitcoinj project on my spare time (which I don't have)
04:38 < aj> MarcoFalke: #11646 was merged, so it shouldn't be labelled up for grabs, should it?
04:38 < gribble> https://github.com/bitcoin/bitcoin/issues/11646 | Require a steady clock for bench with at least micro precision by TheBlueMatt · Pull Request #11646 · bitcoin/bitcoin · GitHub
04:39 < meshcollider> aj: might be related to the comment
04:39 -!- roconnor_ [~roconnor@host-45-78-201-152.dyn.295.ca] has joined #bitcoin-core-dev     
04:39 < kgc> should I open an issue on the github so it doesn't get lost?
04:39 < meshcollider> kgc: someone like sipa will probably be able to clarify things when he is online :)
04:40 < meshcollider> Yes I think an issue is a good idea
04:40 < kgc> ok, will do that, thank you for helping out :)
04:42 < meshcollider> There should be a way to pass scripts in as well as private keys
04:43 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Remote host closed the connection]     
04:43 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has joined #bitcoin-core-dev     
04:46 < meshcollider> kgc: in the mean time, you could just import the witness redeem script into your wallet I think :)
04:52 < wumpus> aj: I see now, it's merged but there was a mistake in it
04:56 < bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4db82b7aab4a...aca77a4d58c6
04:56 < bitcoin-git> bitcoin/master 63c2d83 practicalswift: Explicitly state assumption that state.m_chain_sync.m_work_header != nullptr in ConsiderEviction...
04:56 < bitcoin-git> bitcoin/master aca77a4 Wladimir J. van der Laan: Merge #11655: net: Assert state.m_chain_sync.m_work_header in ConsiderEviction...
04:56 < bitcoin-git> [bitcoin] laanwj closed pull request #11655: net: Assert state.m_chain_sync.m_work_header in ConsiderEviction (master...m_chain_sync.m_work_header) https://github.com/bitcoin/bitcoin/pull/11655
04:57 < JackH> how can I dump privkey on segwit addresses? I get an error when doing dumpprivkey
04:59 < JackH> from the one topic I read, since it is a p2sh script, there is no address, thus I cannot dump privkey? but how can I otherwise get the privkey for the inputs? 
04:59 < wumpus> you probably added the witness address using addwitnessaddress?
04:59 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]     
04:59 < wumpus> that won't add a private key
05:00 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev     
05:00 < JackH> so how do I get access to the inputs? basically I am looking to do a child pays for parent for some stuck txs
05:00 < JackH> and I wanted to import the privkey into electrum
05:00 < JackH> or is there a better way?
05:02 < wumpus> I think you need the address you called addwitnessaddress with, and use dumpprivkey with that
05:03 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
05:08 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has joined #bitcoin-core-dev     
05:10 < wumpus> that would give you a private key, though importing it in other software is not going to be easy I expect, e.g. just importing the key isn't going to make it recognize the transaction
05:12 -!- prestonparris [~prestonpa@c-69-181-105-116.hsd1.ca.comcast.net] has quit [Ping timeout: 240 seconds]     
05:15 -!- Giszmo [~leo@pc-166-83-100-190.cm.vtr.net] has quit [Ping timeout: 240 seconds]     
05:28 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
05:32 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 240 seconds]     
05:34 -!- LeMiner2 [LeMiner@5ED1AFBF.cm-7-2c.dynamic.ziggo.nl] has joined #bitcoin-core-dev     
05:34 -!- Leminer [LeMiner@unaffiliated/leminer] has quit [Ping timeout: 248 seconds]     
05:34 -!- LeMiner2 is now known as Leminer     
05:56 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit []     
06:04 -!- was [b968b974@gateway/web/freenode/ip.185.104.185.116] has joined #bitcoin-core-dev     
06:05 < was> hello
06:05 < was> is someone can help me ?
06:05 < wumpus> just ask your question in the channel and if someone can help you they'll answer (or tell you where it's better to ask it)
06:06 < was> i have a wallet btc core
06:06 < was> i save wallet.dat
06:06 < was> for change another pc
06:06 < was> now how can getback ?
06:06 < was> i have wallet.dat and my password
06:10 < was> you know ?
06:12 < sipa> try #bitcoin
06:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev     
06:18 -!- DigitalSwell [c28cfe53@gateway/web/freenode/ip.194.140.254.83] has joined #bitcoin-core-dev     
06:20 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
06:21 -!- DigitalSwell [c28cfe53@gateway/web/freenode/ip.194.140.254.83] has quit [Client Quit]     
06:23 -!- checksauce [~checksauc@38.95.108.163] has quit [Remote host closed the connection]     
06:24 -!- checksauce [~checksauc@38.95.108.163] has joined #bitcoin-core-dev     
06:24 -!- aruns [~indistylo@119.82.105.106] has joined #bitcoin-core-dev     
06:26 -!- indistylo [~indistylo@119.82.105.106] has quit [Ping timeout: 255 seconds]     
06:27 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev     
06:28 -!- checksauce [~checksauc@38.95.108.163] has quit [Ping timeout: 255 seconds]     
06:36 -!- Khunbish [~Khunbish@213.108-247-81.adsl-dyn.isp.belgacom.be] has quit [Remote host closed the connection]     
06:41 < promag> Are CBlockTreeDB/CDBWrapper member functions thread safe?
06:42 < wumpus> no     
06:44 -!- was [b968b974@gateway/web/freenode/ip.185.104.185.116] has quit [Quit: Page closed]     
06:45 -!- alreadylate [~textual@217-209-128-92-no94.tbcn.telia.com] has joined #bitcoin-core-dev     
06:46 < wumpus> though leveldb itself is thread safe
06:46 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
06:47 < wumpus> we make use of that only in one place, for the Cursor in GetUTXOStats, to iterate over a snapshot of the database while the rest of the process continues
06:52 < wumpus> but none of the caching and buffering we do on top of leveldb is thread-safe
06:52 -!- alreadylate [~textual@217-209-128-92-no94.tbcn.telia.com] has quit [Ping timeout: 248 seconds]     
06:52 < bitcoin-git> [bitcoin] practicalswift closed pull request #11691: rpc: Add missing lock in getblocktemplate(...). Work around Clang thread safety analysis quirks. (master...rpc-locking) https://github.com/bitcoin/bitcoin/pull/11691
06:53 -!- aruns [~indistylo@119.82.105.106] has quit [Ping timeout: 240 seconds]     
06:57 < promag> wumpus: ty
07:08 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
07:09 -!- felco [~felco@unaffiliated/felco] has quit [Quit: All your IRC are belong to ZNC]     
07:21 < bitcoin-git> [bitcoin] practicalswift opened pull request #11694: rpc: Add missing cs_main lock in getblocktemplate(...) (master...missing-lock-in-getblocktemplate) https://github.com/bitcoin/bitcoin/pull/11694
07:24 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Quit: Leaving]     
07:24 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev     
07:26 < bitcoin-git> [bitcoin] laanwj pushed 13 new commits to master: https://github.com/bitcoin/bitcoin/compare/aca77a4d58c6...927a1d7d088e
07:26 < bitcoin-git> bitcoin/master a7d3936 Matt Corallo: Add a CValidationInterface::TransactionRemovedFromMempool...
07:26 < bitcoin-git> bitcoin/master 0343676 Matt Corallo: Call TransactionRemovedFromMempool in the CScheduler thread...
07:26 < bitcoin-git> bitcoin/master 2b4b345 Matt Corallo: Add ability to assert a lock is not held in DEBUG_LOCKORDER
07:26 < bitcoin-git> [bitcoin] laanwj closed pull request #10286: Call wallet notify callbacks in scheduler thread (without cs_main) (master...2017-01-wallet-cache-inmempool-4) https://github.com/bitcoin/bitcoin/pull/10286
07:27 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev     
07:29 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
07:30 < promag> is practicalswift around?
07:33 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 268 seconds]     
07:37 -!- felco [~felco@unaffiliated/felco] has joined #bitcoin-core-dev     
07:38 -!- boreddanman1 [~daniel@ool-182cec5f.dyn.optonline.net] has quit [Ping timeout: 248 seconds]     
07:40 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-vhverfnnceiolawe] has quit [Quit: Connection closed for inactivity]     
07:45 -!- Khunbish [~Khunbish@213.108-247-81.adsl-dyn.isp.belgacom.be] has joined #bitcoin-core-dev     
07:59 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds]     
08:14 -!- gustav [570a65bf@gateway/web/cgi-irc/kiwiirc.com/ip.87.10.101.191] has joined #bitcoin-core-dev     
08:14 < gustav> hello
08:16 < promag> guess not
08:16 < promag> luke-jr: friendly reminder https://github.com/bitcoin/bitcoin/pull/11660#discussion_r150875214
08:20 < gustav> i have one app where users are given 1 bitcoin address A, they deposit btc on A and later on they withdraw on their address B. I'd like to use segwit addresses to cut down expenses on network fees (if im getting this right). now i use getnewaddress, sendmany and rawtransactions functions. would it be possible to use $addr = getnewaddress(); $segwit
08:20 < gustav> addr = addwitnessaddress($addr); to "move into segwit addresses usage"? if so would users be able to send to my app segwit address, and will my existing code be able to send payments to user addresses (non segwit and segwit)? thank you very much for all the work. now fees are insane this is why im asking. if wrong irc please tell me where to ask.
08:21 < gustav> reading online on stackoverflow and similar leads me to believe it can be done but im not sure about compatibility (user sends from non-segwit to segwit, needs to receive from segwit to non-segwit) and if addwitnessaddress is all i need. again thanks and sorry for wall of texts
08:22 < gustav> oopsie, using bitcoin-core latest version on linux (rpc, with php)
08:26 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 268 seconds]     
08:27 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds]     
08:30 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev     
08:37 -!- JackH [~laptop@91.189.61.70] has quit [Ping timeout: 255 seconds]     
08:51 -!- JackH [~laptop@alvira.static.korbank.pl] has joined #bitcoin-core-dev     
08:53 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
08:53 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds]     
08:57 < sturles> Yes, this will make an address into a segwit address (P2SH-P2WPKH).  There are multiple kinds of segwit addresses.  To get the highest nenefit, you can make a P2PKWH address like this: addwitnessaddress($addr,true)
08:58 -!- gustav [570a65bf@gateway/web/cgi-irc/kiwiirc.com/ip.87.10.101.191] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]     
08:58 -!- carlitos [b50d16b4@gateway/web/freenode/ip.181.13.22.180] has joined #bitcoin-core-dev     
08:58 < sturles> The P2PKWH address will begin with bc1... (Bech32 format), and the sending wallet must be segwit aware to use it.
08:59 -!- shesek [~shesek@bzq-84-110-176-175.red.bezeqint.net] has joined #bitcoin-core-dev     
08:59 -!- shesek [~shesek@bzq-84-110-176-175.red.bezeqint.net] has quit [Changing host]     
08:59 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev     
08:59 < sturles> You can only convert your own addresses.  Do not attempt to convert addresses you get from other people.
09:03 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
09:07 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
09:10 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
09:15 < BlueMatt> note to anyone with open wallet-rpc PRs: ##10286 will likely cause a silent conflict - you will need to add calls to BlockUntilSyncedToCurrentChain!
09:15 < gribble> https://github.com/bitcoin/bitcoin/issues/10286 | Call wallet notify callbacks in scheduler thread (without cs_main) by TheBlueMatt · Pull Request #10286 · bitcoin/bitcoin · GitHub
09:16 -!- LumberCartel [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds]     
09:22 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev     
09:29 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
09:29 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
09:30 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-qstjmknpocyplxie] has joined #bitcoin-core-dev     
09:34 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 258 seconds]     
09:36 -!- aruns [~indistylo@122.171.189.175] has joined #bitcoin-core-dev     
09:37 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev     
09:51 -!- carlitos [b50d16b4@gateway/web/freenode/ip.181.13.22.180] has quit [Quit: Page closed]     
09:52 < bitcoin-git> [bitcoin] MarcoFalke pushed 4 new commits to master: https://github.com/bitcoin/bitcoin/compare/927a1d7d088e...4ed818060ecf
09:52 < bitcoin-git> bitcoin/master 7c4f009 Russell Yanofsky: [trivial] Rename feebumper variables according to project code style...
09:52 < bitcoin-git> bitcoin/master 37bdcca Russell Yanofsky: [refactor] Make feebumper namespace...
09:52 < bitcoin-git> bitcoin/master aed1d90 Russell Yanofsky: [wallet] Change feebumper from class to functions...
09:53 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #10600: Make feebumper class stateless (master...pr/ipc-bump) https://github.com/bitcoin/bitcoin/pull/10600
10:01 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
10:04 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection]     
10:04 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
10:08 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
10:21 -!- laurentmt [~Thunderbi@92.154.68.134] has quit [Quit: laurentmt]     
10:26 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-mbqpgzolekltktkm] has joined #bitcoin-core-dev     
10:31 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection]     
10:32 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
10:35 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 248 seconds]     
10:54 < jonasschnelli> Thanks BlueMatt for the info
11:03 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-gbdofvznxcnpvcaa] has joined #bitcoin-core-dev     
11:04 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...]     
11:04 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
11:07 -!- sanada [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has quit []     
11:08 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
11:08 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
11:10 < luke-jr> BlueMatt: I wonder if there's a good way to make builds fail if they're incompatible
11:10 < luke-jr> though I can't think of anything obvious
11:11 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds]     
11:12 < BlueMatt> I mean its kinda a manual thing to figure out if a given RPC needs the block
11:25 -!- wunpunch [~Alli@176.27.129.249] has joined #bitcoin-core-dev     
11:27 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
11:29 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in]     
11:31 -!- wunpunch [~Alli@176.27.129.249] has quit [Read error: Connection reset by peer]     
11:40 < luke-jr> BlueMatt: right, but we could fail everything until some change is made to indicate one way or the other
11:40 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-qstjmknpocyplxie] has quit [Quit: Connection closed for inactivity]     
11:42 < BlueMatt> that seems like overkill? I mean as long as people pay attention when merging wallet rpc changes in the same way that we will need to in the future
11:42 < luke-jr> dunno
11:42 < luke-jr> incompatible changes breaking stuff is generally a good idea to avoid bug
11:42 < BlueMatt> I mean if you want to write one I'd be happy to see it, but I dont think its a huge risk
11:42 < BlueMatt> just gotta educate =D
11:52 -!- warxhead [warxhead@c-73-243-180-191.hsd1.co.comcast.net] has joined #bitcoin-core-dev     
11:56 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-yvcfubwysvydzuyy] has quit [Ping timeout: 276 seconds]     
12:02 < jonasschnelli> BlueMatt: re: https://github.com/bitcoin/bitcoin/pull/10387/commits/005fafdaa99b900d4a3ed0320e73e0a4863abf87
12:03 < jonasschnelli> Do you recommend to keep MayHaveUsefulAddressDB() as it is and add the HasAllDesirableServiceFlags() at another place?
12:03 < jonasschnelli> IMO NODE_NETWORK_LIMITED  should conform to MayHaveUsefulAddressDB()... or why not?
12:04 < BlueMatt> hmm?
12:04 < BlueMatt> yes, no, I was not objecting to the code changes there
12:04 < BlueMatt> at all
12:04 < BlueMatt> my complaint was about the commit message and the confusion it implies
12:04 < BlueMatt> an easy fix for which would be to change net_processing's addr handling
12:05 < BlueMatt> to check MayHaveUsefulAddressDB(services) || HasAllDesirableServiceFlags(services)
12:05 < BlueMatt> as the condition for getting an address into *our* addr db
12:05 < BlueMatt> (which, as indicated in the comment, would also not be a change in behavior, but it'd make things much clearer)
12:06 -!- kewde[m] [kewdematri@gateway/shell/matrix.org/x-cbkltrspzmsvygkb] has joined #bitcoin-core-dev     
12:07 < jonasschnelli> I see..
12:07 < jonasschnelli> BlueMatt: but we should also do feeler to NODE_NETWORK_LIMITED, right?
12:07 < jonasschnelli> That's why I have changed MayHaveUsefulAddressDB()
12:07 < BlueMatt> correct
12:07 < BlueMatt> again, I think the *code* in that commit is right, the changes I was talking about would change no behavior against what you already have
12:07 < jonasschnelli> Okay with just rewording the commit message to mention the feeler thing?
12:07 < BlueMatt> wait, huh?
12:08 < BlueMatt> ohoh, yes
12:08 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]     
12:08 < BlueMatt> so the function is named MayHaveUsefulAddressDB because its primary use is "should i do a feeler to this connection"
12:08 < jonasschnelli> Or do you think adding "HasAllDesirableServiceFlags(services)" in net_processing would make the code more readable (not an acctual change)
12:08 < BlueMatt> the fact that acceptance into our addr db relies on that function is purely because its a superset of HasAllDesirableServiceFlags
12:08 < BlueMatt> my request was that you do both
12:09 < jonasschnelli> okay... got it
12:11 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 255 seconds]     
12:13 < jonasschnelli> BlueMatt: wait,... but HasAllDesirableServiceFlags() changes over time. Should we not add NODE_NETWORK_LIMITED to our addr man even during IBD?
12:14 < jonasschnelli> A check in net_processing (MayHaveUsefulAddressDB(services) || HasAllDesirableServiceFlags(services)) would lead to not adding NODE_NETWORK_LIMITED during IBD, right? Is that desirable?
12:14 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
12:19 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
12:23 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 260 seconds]     
12:24 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
12:25 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
12:29 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
12:35 < BlueMatt> jonasschnelli: I mean MayHaveUsefulAddressDB will always return true for either NODE_NETWORK{,_LIMITED}
12:35 < BlueMatt> jonasschnelli: so it should be fine?
12:36 < jonasschnelli> Yes. Your right...
12:40 < rabidus> no, that's your left
12:40 < rabidus> sry.
12:41 < sipa> it's your right to be left on the left
12:41 < sipa> sry.
12:42 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
12:42 < jonasschnelli> lol     
12:51 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]     
12:54 < jonasschnelli> Anyone willing to review https://github.com/bitcoin/bitcoin/pull/11281/files?w=1 ?
12:54 < jonasschnelli> #11281
12:54 < gribble> https://github.com/bitcoin/bitcoin/issues/11281 | Avoid pemanent cs_main/cs_wallet lock during RescanFromTime by jonasschnelli · Pull Request #11281 · bitcoin/bitcoin · GitHub
12:54 < jonasschnelli> (use ?w=1)
12:54 -!- mmgen [~mmgen@gateway/tor-sasl/mmgen] has quit [Quit: (https://github.com/mmgen) leaving]     
13:01 -!- wxss_ [~chatzilla@82.221.112.213] has joined #bitcoin-core-dev     
13:02 -!- wxss [~chatzilla@82.221.112.213] has quit [Ping timeout: 250 seconds]     
13:02 -!- wxss_ is now known as wxss     
13:11 -!- aruns__ [~indistylo@122.171.202.159] has joined #bitcoin-core-dev     
13:13 -!- aruns [~indistylo@122.171.189.175] has quit [Ping timeout: 240 seconds]     
13:14 -!- tess_ [d85fec03@gateway/web/freenode/ip.216.95.236.3] has joined #bitcoin-core-dev     
13:14 -!- tess_ [d85fec03@gateway/web/freenode/ip.216.95.236.3] has quit [Client Quit]     
13:15 -!- indistylo [~indistylo@122.171.212.5] has joined #bitcoin-core-dev     
13:16 < bitcoin-git> [bitcoin] jnewbery opened pull request #11697: [trivial] remove trailing whitespace in streams.h (master...streams_trailing_whitespace) https://github.com/bitcoin/bitcoin/pull/11697
13:16 < meshcollider> wumpus: #11651 is ready to merge I think
13:16 -!- aruns__ [~indistylo@122.171.202.159] has quit [Ping timeout: 250 seconds]     
13:16 < gribble> https://github.com/bitcoin/bitcoin/issues/11651 | refactor: Make all #includes relative to project root (laanwj, MeshCollider, ryanofsky) by MeshCollider · Pull Request #11651 · bitcoin/bitcoin · GitHub
13:26 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds]     
13:39 -!- _parts [~tonedef@104.236.96.151] has joined #bitcoin-core-dev     
13:39 -!- JackH [~laptop@alvira.static.korbank.pl] has quit [Ping timeout: 248 seconds]     
13:39 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
13:41 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4ed818060ecf...f0c1f8abb018
13:41 < bitcoin-git> bitcoin/master b077fe9 Evan Klitzke: fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it
13:41 < bitcoin-git> bitcoin/master f0c1f8a MarcoFalke: Merge #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it...
13:41 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11690: [trivial] Fix the StartupWMClass for bitoin-qt, so gnome-shell can recognize it (master...desktop-file) https://github.com/bitcoin/bitcoin/pull/11690
13:56 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 268 seconds]     
14:07 < bitcoin-git> [bitcoin] lmlsna opened pull request #11698: [Docs] [Qt] RPC-Console nested commands documentation  (master...doc-rpc-console) https://github.com/bitcoin/bitcoin/pull/11698
14:11 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
14:13 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
14:14 -!- Aaronva__ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
14:16 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
14:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]     
14:17 -!- indistylo [~indistylo@122.171.212.5] has quit [Ping timeout: 255 seconds]     
14:18 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 248 seconds]     
14:19 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
14:23 < go1111111> I'm experiencing a fairly painful UX issue with Core. I'm probably "using it wrong", but I wanted to describe my problem in case it influences development, and also see if there's a workaround: 
14:23 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
14:23 -!- Aaronva__ is now known as AaronvanW     
14:25 < go1111111> I have several different wallet files, with different passwords. I rename them 'wallet.dat' as needed. I also recently started pruning my node. These two things don't work together well, as whenever the node is given a wallet with new addresses and it thinks it might be missing info, it wants to re-download the entire blockchain
14:25 < go1111111> so, i essentially have to redownload and revalidate the entire blockchain for every wallet (it is possible to be smarter about this by taking snapshots, but it's cumbersome). Is there a workaround to that?
14:26 < sipa> are you using multiwallet? you can load all wallets at once
14:28 < bitcoin-git> [bitcoin] jnewbery opened pull request #11699: [travis-ci] Only run linters on Pull Requests (master...lint_only_prs) https://github.com/bitcoin/bitcoin/pull/11699
14:28 < bitcoin-git> [bitcoin] jnewbery closed pull request #11697: [trivial] remove trailing whitespace in streams.h (master...streams_trailing_whitespace) https://github.com/bitcoin/bitcoin/pull/11697
14:28 < go1111111> Oh, wasn't aware of that. I'll look into it -- thanks!   My other problem: I'm about 40% of the way through validating the blockchain, but all the inputs I want to spend have already been seen by the node, so I'd like to be able to broadcast a tx even though the node itself doesn't know that inputs are unspent. Is there a better way to do this other than using createrawtransaction?
14:29 < go1111111> I'd like to take advantage of the transaction construction of the UI to avoid errors, but also don't want to wait another 6 hours.. 
14:30 < sipa> you can construct a transaction as soon as your node knows about the outputs
14:30 < sipa> however, if you would construct a transaction that spends inputs which happen to be already spent in the chain, the result will be invalid (and you'll need to use abandontransaction to fix things)
14:34 < go1111111> interesting. that's how I wanted it to work, but when I construct my tx in the UI and click 'send', the UI doesn't respond at all. I expect to be prompted for my pw. Now that I know this is unexpected i'll try some variations to see if I can get it to work. thanks
14:35 < sipa> i'm unfamiliar with the GUI, but that does sound like a bug
14:36 < sipa> or at least something that requires more accurate information
14:38 -!- jay_ [465f0af0@gateway/web/freenode/ip.70.95.10.240] has joined #bitcoin-core-dev     
14:38 -!- jay_ [465f0af0@gateway/web/freenode/ip.70.95.10.240] has quit [Client Quit]     
14:41 < go1111111> it seems to relate to coin-control. I get the expected behavior when I don't manually select the inputs
14:43 < go1111111> wait no, that's wrong.. I'll be back when/if I have a proper bug report. thanks for the help.
14:43 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/f0c1f8abb018...54aedc013744
14:43 < bitcoin-git> bitcoin/master ea3f363 Matt Corallo: Make ISSUE_TEMPLATE a bit shorter, mention hardware tests
14:43 < bitcoin-git> bitcoin/master 54aedc0 MarcoFalke: Merge #11686: Make ISSUE_TEMPLATE a bit shorter, mention hardware tests...
14:43 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #11686: Make ISSUE_TEMPLATE a bit shorter, mention hardware tests (master...2017-11-shorter-default-issue) https://github.com/bitcoin/bitcoin/pull/11686
14:45 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit []     
14:50 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
14:54 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
15:11 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
15:51 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 248 seconds]     
15:52 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
15:58 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
16:02 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-gbdofvznxcnpvcaa] has quit [Quit: Connection closed for inactivity]     
16:11 -!- grio_ [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev     
16:12 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Read error: Connection reset by peer]     
16:12 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
16:13 -!- Khunbish [~Khunbish@213.108-247-81.adsl-dyn.isp.belgacom.be] has quit [Quit: Khunbish]     
16:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 255 seconds]     
16:22 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hjojabgfvtcxamsj] has joined #bitcoin-core-dev     
16:23 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed]     
16:31 < bitcoin-git> [bitcoin] willyko opened pull request #11700: Add gitian PGP key: willyko (master...master) https://github.com/bitcoin/bitcoin/pull/11700
16:40 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 255 seconds]     
16:45 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has joined #bitcoin-core-dev     
16:48 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in]     
16:49 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
16:53 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Client Quit]     
16:54 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 248 seconds]     
16:54 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
16:58 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev     
17:04 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in]     
17:05 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
17:15 -!- Kirstin82Ledner [~Kirstin82@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 240 seconds]     
17:21 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in]     
17:21 -!- Antoinette31Kuhl [~Antoinett@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev     
17:21 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
17:22 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
17:23 -!- Netsplit *.net <-> *.split quits: warxhead, Ylbam, bordeaux_facile, wolfspraul, Squidicuz, NielsvG, pindarhk_, profall, earlz, mesh_,  (+196 more, use /NETSPLIT to show all of them)
17:28 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
17:28 -!- Cory [~Cory@unaffiliated/cory] has quit [Max SendQ exceeded]     
17:28 -!- BGL [thirty@75-149-171-58-Washington.hfc.comcastbusiness.net] has quit [Max SendQ exceeded]     
17:28 -!- Netsplit over, joins: luke-jr, wumpus, warren, BlueMatt, jl2012, kallewoof, BashCo, midnightmagic, GAit, jonasschnelli (+195 more)
17:30 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in]     
17:31 -!- shtirlic [~shtirlic@ec2-35-158-173-101.eu-central-1.compute.amazonaws.com] has joined #bitcoin-core-dev     
17:35 -!- Cory [~Cory@unaffiliated/cory] has joined #bitcoin-core-dev     
17:39 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev     
17:40 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev     
17:40 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Client Quit]     
17:40 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 240 seconds]     
17:42 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 255 seconds]     
17:45 -!- sanada [~bitktn@36-2-119-80.chiba.ap.gmo-isp.jp] has joined #bitcoin-core-dev     
17:49 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-mbqpgzolekltktkm] has quit [Quit: Connection closed for inactivity]     
17:58 -!- chartractegg [~chartract@gateway/vpn/privateinternetaccess/chartractegg] has joined #bitcoin-core-dev     
17:59 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev     
18:03 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #bitcoin-core-dev     
18:06 -!- chartractegg [~chartract@gateway/vpn/privateinternetaccess/chartractegg] has quit [Quit: Textual IRC Client: www.textualapp.com]     
18:08 -!- chartractegg [~chartract@gateway/vpn/privateinternetaccess/chartractegg] has joined #bitcoin-core-dev     
18:14 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds]     
18:15 < meshcollider> sipa: re #11693 do you know if there is any way to currently signrawtransaction for P2SH-P2WSH ? Or should I open a PR to add a witness program key to that call
18:15 < gribble> https://github.com/bitcoin/bitcoin/issues/11693 | Signing raw transaction that has p2sh-p2wsh input · Issue #11693 · bitcoin/bitcoin · GitHub
18:15 -!- chartractegg [~chartract@gateway/vpn/privateinternetaccess/chartractegg] has left #bitcoin-core-dev ["Textual IRC Client: www.textualapp.com"]     
18:15 < meshcollider> Or is there something else planned
18:18 < sipa> meshcollider: hmm, that is surprising
18:19 < sipa> meshcollider: maybe we should just automatically add the p2sh version of each script passed to signrawtransaction
18:19 < sipa> that should work without api break
18:19 < meshcollider> Mmm so you would just pass the internal WSH script in the scriptSig?
18:21 -!- jsfour [~jsfour@cpe-76-90-140-31.socal.res.rr.com] has quit [Ping timeout: 255 seconds]     
18:22 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 248 seconds]     
18:24 -!- Murch [~murch@96-82-80-28-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]     
18:27 -!- BGL [twenty@75-149-171-58-Washington.hfc.comcastbusiness.net] has joined #bitcoin-core-dev     
18:27 -!- owowo [ovovo@gateway/vpn/mullvad/x-zmbwdaczelwhusoz] has joined #bitcoin-core-dev     
18:27 -!- owowo [ovovo@gateway/vpn/mullvad/x-zmbwdaczelwhusoz] has quit [Changing host]     
18:27 -!- owowo [ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev     
18:27 -!- owowo [ovovo@unaffiliated/ovovo] has quit [Changing host]     
18:27 -!- owowo [ovovo@gateway/vpn/mullvad/x-zmbwdaczelwhusoz] has joined #bitcoin-core-dev     
18:37 < meshcollider> JSON*
18:38 < sipa> right
18:38 < sipa> hmm, but it would need to guess the witness version
18:38 < meshcollider> sipa: it's already a JASON object so adding an extra key wouldn't break it anyway would it
18:38 < meshcollider> Oops did that resend
18:42 < sipa> okay
18:42 < sipa> good
18:42 < gmaxwell> from a usability perspective, having to have some extra key isn't super friendly, if it can be reasonably avoided.
18:42 < gmaxwell> (these interfaces do exist for thigns other than driving test harnesses, you know)
18:46 < meshcollider> I don't know how it could be avoided without instead passing in the witness version, like sipa mentioned
18:47 -!- LumberCartel [~randolf@96.53.47.42] has joined #bitcoin-core-dev     
18:49 < sipa> or alternatively, doing it automatically for all known witness types and versions
18:50 < meshcollider> Why does the signrawtransaction help text already say "redeemScript": "hex",   (string, required for P2SH or P2WSH) redeem script
18:50 < meshcollider> Oh don't worry, that's P2WSH not P2SH-P2WSH
18:51 -!- go1111111 [~elliot@199.231.240.191] has quit [Quit: Leaving]     
18:52 < gmaxwell> whatever we do, it should be the case the you can form a valid signraw line using nothing other than a simple reformatting of listunspent's output.
18:56 < meshcollider> What is the redeemScript output from listunspent for P2SH-P2WSH
18:57 < meshcollider> I assume it doesn't currently output the witness script at all, which will need to be modified too
18:57 < sipa> gmaxwell: that's not really possible, and already not true for P2SH
18:58 < sipa> at least not for watch-only outputs
18:59 < gmaxwell> sipa: if you've imported the script it should be possible (I have no watch only p2sh so I don't know if it does)
18:59 < sipa> gmaxwell: it won't work
18:59 < gmaxwell> We should fix that then.
19:00 < sipa> i mean it won't work when passing in explicit private keys
19:00 < sipa> because then it uses the keystore consteucted from the rpc arguments rather than your wallet's keystore
19:00 < sipa> part of this confusion is solved by finally splitting up signrawtransaction into a wallet version and a utility version (achow has a pr i think)
19:01 < gmaxwell> the flaw here is that our private key encodings don't represent (or imply) the redeemscript.
19:01 < sipa> in the wallet version, things already work fine and nothing is needed for p2sh-p2wsk
19:01 < sipa> in the non-wallet version you inherently need to pass in the solving information somehow
19:02 < sipa> indeed one way is to encode it in the private key
19:02 < gmaxwell> or just declare that it's already encoded in the private key, and expand each private key all known ways; but that doesn't work e.g. for multisig.
19:02 < sipa> but that's not generally possible for all output types (and specifically won't work for.any multisig kinda thing, which is exactly where p2wsh is used), so other ways must exist as well
19:02 < sipa> right
19:03 < gmaxwell> e.g. current private keys = {p2pk,p2pkh,p2sh-one-key,p2wpkhv0,p2wpkhv0-p2sh}
19:04 < gmaxwell> we have the redeemscript for each input we're going to sign as an argument, so it could meet in the middle with the private keys. ugh.
19:05 < sipa> yeah
19:06 < sipa> whatwver encoding is used for the solving information, listunspent should probably be made to report it
19:06 < sipa> if known
19:08 < Chris_Stewart_5> gmaxwell: So basically this would look like attaching an extra byte of data to the current format to indicate the script it corresponds to>
19:08 < Chris_Stewart_5> ?     
19:09 < Chris_Stewart_5> and some sort of standardized scheme for standard script types I guess
19:17 -!- m8tion01 [~m8tion@81-65-53-254.rev.numericable.fr] has joined #bitcoin-core-dev     
19:20 -!- m8tion03 [~m8tion@81-65-53-254.rev.numericable.fr] has quit [Ping timeout: 248 seconds]     
19:25 -!- checksauce [~checksauc@182.232.172.197] has joined #bitcoin-core-dev     
19:25 < meshcollider> So if I just made listunspent just report witness script for P2SH-P2WSH outputs and then signrawtransaction accept it that would be simple right
19:26 < meshcollider> That's the cleanest way i can see to ensure P2SH-P2WSH multisig works for example, which is what brought on this discussion
19:26 < sipa> while you're at it, also add redeemscript for P2SH?
19:30 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev     
19:32 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds]     
19:38 < meshcollider> To listunspent?
19:39 < sipa> yes, it's also needed in signrawtransaction when giving private keys manually
19:39 < meshcollider> sipa: I thought listunspent already had it
19:42 < sipa> oh, indeed!
20:01 -!- checksauce [~checksauc@182.232.172.197] has quit [Read error: Connection reset by peer]     
20:08 -!- checksauce [~checksauc@96.30.100.143] has joined #bitcoin-core-dev     
20:13 -!- go1111111 [~elliot@199.231.240.191] has joined #bitcoin-core-dev     
20:26 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
20:26 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit]     
20:26 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
20:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 268 seconds]     
20:28 -!- lex11 [~Mutter@2607:fb90:525b:bd27:c8e7:c3c4:2970:edd2] has joined #bitcoin-core-dev     
20:31 -!- lex11 [~Mutter@2607:fb90:525b:bd27:c8e7:c3c4:2970:edd2] has quit [Quit: Mutter: www.mutterirc.com]     
20:32 -!- grio_ [~grio@ip68-102-158-172.ks.ok.cox.net] has quit [Ping timeout: 248 seconds]     
20:32 -!- BCBot [~BCBot@46.101.246.115] has quit [Ping timeout: 255 seconds]     
20:49 -!- checksauce [~checksauc@96.30.100.143] has quit [Remote host closed the connection]     
20:49 -!- checksauce [~checksauc@96.30.101.181] has joined #bitcoin-core-dev     
20:50 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 240 seconds]     
20:51 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev     
21:00 < bitcoin-git> [bitcoin] jamesob opened pull request #11702: [build] Add a script for installing db4 (master...install-db4-script) https://github.com/bitcoin/bitcoin/pull/11702
21:00 -!- grio [~grio@ip68-102-158-172.ks.ok.cox.net] has joined #bitcoin-core-dev     
21:08 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds]     
21:11 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has joined #bitcoin-core-dev     
21:23 -!- BCBot [~BCBot@46.101.246.115] has joined #bitcoin-core-dev     
21:27 -!- checksauce [~checksauc@96.30.101.181] has quit [Read error: Connection reset by peer]     
21:32 -!- go1111111 [~elliot@199.231.240.191] has quit [Ping timeout: 248 seconds]     
21:38 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]     
21:39 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
22:05 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 248 seconds]     
22:08 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev     
22:09 -!- go1111111 [~elliot@199.231.240.191] has joined #bitcoin-core-dev     
22:14 -!- Taco [62ea5718@gateway/web/freenode/ip.98.234.87.24] has joined #bitcoin-core-dev     
22:19 -!- Taco [62ea5718@gateway/web/freenode/ip.98.234.87.24] has quit [Ping timeout: 260 seconds]     
22:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-dhwbzyaiztrjsgvr] has joined #bitcoin-core-dev     
22:35 -!- checksauce [~checksauc@110.78.145.159] has joined #bitcoin-core-dev     
22:41 -!- indistylo [~indistylo@119.82.105.106] has joined #bitcoin-core-dev     
23:21 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-zmhxcaxxjeimnrdm] has quit [Ping timeout: 252 seconds]     
23:23 -!- sugarpuff [sid92283@gateway/web/irccloud.com/x-cqdafmiwrzlzfqtw] has quit [Ping timeout: 255 seconds]     
23:25 -!- sugarpuff [sid92283@gateway/web/irccloud.com/x-ntnvhezktwvemzjr] has joined #bitcoin-core-dev     
23:33 -!- Victor_sueca is now known as Victorsueca     
23:44 -!- jsfour [~jsfour@cpe-45-50-168-164.socal.res.rr.com] has quit [Ping timeout: 268 seconds]     
23:51 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds]     
23:51 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds]     
23:53 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev     
23:55 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]     
23:56 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev     
23:56 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev     
23:58 -!- checksauce [~checksauc@110.78.145.159] has quit [Ping timeout: 248 seconds]