--- Day changed Mon Nov 27 2017 00:05 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 00:11 -!- digifis [~sin@x590f2af8.dyn.telefonica.de] has quit [Ping timeout: 240 seconds] 00:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 00:16 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 255 seconds] 00:16 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 00:17 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 00:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 00:43 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 00:45 -!- sanjeev_ [~sanjeev@118.185.49.106] has quit [Read error: Connection reset by peer] 00:52 -!- sanjeev [~sanjeev@118.185.49.106] has joined #bitcoin-core-dev 01:09 -!- atroxes [~atroxes@unaffiliated/atroxes] has quit [Ping timeout: 240 seconds] 01:14 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 01:21 -!- laurentmt [~Thunderbi@78.84.98.113] has joined #bitcoin-core-dev 01:23 -!- laurentmt [~Thunderbi@78.84.98.113] has quit [Client Quit] 01:25 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 01:29 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 01:41 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 01:43 -!- atroxes [~atroxes@unaffiliated/atroxes] has joined #bitcoin-core-dev 01:57 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 02:05 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-wakdopuvrocbjwrf] has quit [Quit: Connection closed for inactivity] 02:11 -!- Ayana59Smitham [~Ayana59Sm@ns334669.ip-5-196-64.eu] has quit [Remote host closed the connection] 02:24 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has joined #bitcoin-core-dev 02:27 -!- promag [~promag@bl6-24-70.dsl.telepac.pt] has quit [Remote host closed the connection] 02:35 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev 02:45 < wallet42> What are the counter arguments to have a switch where the miner can set a couple of vbytes (10-50K) aside in a getblocktemplate that will include lowfee, oldest first transactions instead of highest paying? 02:59 -!- AndyS2 [~noname@static.74.88.9.5.clients.your-server.de] has joined #bitcoin-core-dev 03:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 03:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 03:08 < sipa> wallet42: complicates the block construction code significantly, would likely not be used by a significant portion of the hashrate 03:09 < sipa> further, having it available even if it was used wouldn't really benefit anyone; it's essentially introducing a lottery in the mining construction from the perspective of wallets 03:13 < Provoostenator> I was thinking about creating an RPC method to add a new destination + amount to an existing RBF transaction. Or to add a "append-tx" argument to sendtoaddress. Has anyone worked on that in past? 03:13 < Provoostenator> (or explained why that's a terrible idea) 03:14 < sipa> Provoostenator: i've thought a bit about a more invasive idea that's related 03:14 < sipa> i think it would be nice to have in the wallet, independent from the sendtoaddress/sendmany/... RPCs, a list of "outputs i would like to pay to" (with address/amount) 03:15 < sipa> and any time that list is changed, or a transaction confirms, a new single transaction is constructed that pays out to all the entries in that list that haven't been paid to already 03:15 < Provoostenator> And then have the wallet figure out if a new transaction is cheaper than amending one? 03:15 < sipa> no, there is always just a single outstanding unconfirmed transaction 03:16 < sipa> for any change, that transaction is modified 03:16 < Provoostenator> That makes sense. 03:16 < sipa> the cost of bumping for RBF reasons is usually trivial compared to its actual fee 03:16 < sipa> (just add 1sat/vbyte) 03:17 < Provoostenator> Right, unless it's a very large transaction. But that would be trivial to check. 03:17 < sipa> there are complications to this... for example you need coin selection that guarantees conflicts with all previously attempted unconfirmed transaction 03:17 < sipa> or you may need to pre-sign multiple candidate follow-up transactions based on which of your earlier attempts confirms 03:17 < sipa> (as you can't automatically get access to encrypted keys later) 03:18 < sipa> and it likely conflicts with how people actually use bitcoin in the real world now - where they expect a txid to be something you can track 03:18 < Provoostenator> Oh, so in that case you'd use SIGHASH flags? 03:18 < sipa> just predict the possible sceniarios, and sign a full follow-up transaction for each (or at least for the few most likely ones) 03:22 < aj> sipa, wallet42: can't you just use prioritisetransaction rpc on the 50 oldest/whatever transactions to get that behaviour anyway? 03:22 -!- qrestlove [~qrestlove@2605:6000:eb4a:ef00:5c35:64d9:a8e4:fdd2] has quit [Ping timeout: 255 seconds] 03:23 < Provoostenator> Although it sounds more elegant, I don't think I can pull that off, yet :-) 03:24 < sipa> aj: yes 03:24 < aj> sipa: predict the possible scenarios? should be called fund-xanatos-transaction... 03:24 < sipa> xanatos? 03:25 < aj> http://tvtropes.org/pmwiki/pmwiki.php/Main/XanatosGambit 03:27 < sipa> Provoostenator: well i think this would be pretty much independent from all existing transaction logic 03:27 < sipa> it'd reuse coin selection, but that's it :) 03:29 -!- mumux [~mix@ip-79-111-95-71.bb.netbynet.ru] has joined #bitcoin-core-dev 03:30 -!- mumux [~mix@ip-79-111-95-71.bb.netbynet.ru] has quit [Quit: Leaving] 03:30 -!- mumux [~mix@ip-79-111-95-71.bb.netbynet.ru] has joined #bitcoin-core-dev 03:30 < wallet42> sipa: are the wallet RPC capabilities currently enough to pull of something like that with an external python app? 03:31 < wallet42> As a prototype 03:31 < sipa> yes, just use prioritisetransaction 03:32 < sipa> and getrawmempool 03:35 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-gdjycrkmphpvgtpc] has joined #bitcoin-core-dev 03:40 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 276 seconds] 03:41 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 03:41 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 03:41 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 03:41 -!- qrestlove [~qrestlove@cpe-66-69-225-126.austin.res.rr.com] has joined #bitcoin-core-dev 03:42 < sipa> ugh, master allocates enormous amounts of memory for me while syncing from scratch from network 03:42 < sipa> 0.15.1 with the same configuration works fine 03:43 < sipa> (it made my system with 32G RAM OOM) 03:44 < Provoostenator> sipa: any way Travis could catch something like that? 03:44 < Provoostenator> Or does it take too long before memory usage gets out of hand? 03:45 < sipa> it OOMed when my debug.log said the dbcache was 1.7G 03:45 < sipa> which is substantial but not excessive 03:45 < sipa> and the overhead on top of what the dbcache predicts should only be a few 100 MB 03:51 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Remote host closed the connection] 03:52 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 03:53 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-rwashhaabydsevoj] has quit [Read error: Connection reset by peer] 03:53 -!- Muis [sid26074@gateway/web/irccloud.com/x-cvxlefzowwqvgxbs] has quit [Ping timeout: 250 seconds] 03:54 -!- michagogo [uid14316@wikia/Michagogo] has quit [Ping timeout: 264 seconds] 03:54 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-jctzynzlxesysxaw] has quit [Ping timeout: 240 seconds] 03:54 -!- aspect_ [sid151486@gateway/web/irccloud.com/x-gkmuwnjivgxyujyd] has joined #bitcoin-core-dev 03:54 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-wgcshzttlkcvspys] has quit [Ping timeout: 255 seconds] 03:54 -!- nejon [uid38993@gateway/web/irccloud.com/x-rmswzrrevowmefar] has quit [Ping timeout: 264 seconds] 03:55 -!- Muis [sid26074@gateway/web/irccloud.com/x-ytxowvqicflhxlwi] has joined #bitcoin-core-dev 03:55 -!- nejon [uid38993@gateway/web/irccloud.com/x-ktjyaqfajnicfjsi] has joined #bitcoin-core-dev 03:55 -!- michagogo [uid14316@wikia/Michagogo] has joined #bitcoin-core-dev 03:56 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 248 seconds] 03:56 -!- lifeofguenter [~lifeofgue@bnc.pro.to.co.ls] has quit [Ping timeout: 260 seconds] 03:58 -!- cyber55 [~cyber55@unaffiliated/cyber55] has quit [Quit: Leaving] 03:59 -!- cyber55 [~cyber55@unaffiliated/cyber55] has joined #bitcoin-core-dev 03:59 -!- cyber55 [~cyber55@unaffiliated/cyber55] has quit [Read error: Connection reset by peer] 03:59 -!- lifeofguenter [~lifeofgue@bnc.pro.to.co.ls] has joined #bitcoin-core-dev 04:00 -!- go1111111 [~go1111111@gateway/vpn/privateinternetaccess/go1111111] has joined #bitcoin-core-dev 04:08 -!- wxss [~user@91.236.116.83] has joined #bitcoin-core-dev 04:09 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 04:10 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 04:11 -!- isis [~isis@abulafia.patternsinthevoid.net] has quit [Ping timeout: 240 seconds] 04:11 -!- isis [~isis@abulafia.patternsinthevoid.net] has joined #bitcoin-core-dev 04:13 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 252 seconds] 04:13 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 04:14 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 264 seconds] 04:18 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 04:19 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 04:24 < Provoostenator> sipa: the second log link in the channel topic seems a bit stale... 04:24 < aj> Provoostenator: yeah, the cron job broke and i haven't updated it since botbot seems better 04:28 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 268 seconds] 04:32 < Provoostenator> Any idea why "test/functional/test_runner.py --loglevel=INFO bumpfee" doesn't result in "Mining blocks..." appearing my console? 04:33 < Provoostenator> It should according to: https://github.com/bitcoin/bitcoin/blob/master/test/functional/bumpfee.py#L52 04:34 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Remote host closed the connection] 04:35 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has joined #bitcoin-core-dev 04:38 < aj> Provoostenator: okay cron job fixed, that wasn't so hard 04:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:39 < Provoostenator> aj: nice, that seems to work 04:39 -!- quantbot [~quantbot@ool-2f125d98.dyn.optonline.net] has quit [Ping timeout: 248 seconds] 04:41 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 04:42 < Provoostenator> Is anyone timestamping them? 04:48 < aj> Provoostenator: each line has a timestamp :) but if you mean cryptographically, no 04:49 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 04:53 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 240 seconds] 05:09 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 05:14 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 248 seconds] 05:16 < morcos> sipa: that sounds bad 05:17 < morcos> re: wallet replacement, i think privacy concerns would also be substantial 05:17 < morcos> you can assume chain analysis companies would start tracking unconfirmed txs, and use that to further group outputs as related 05:19 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 05:20 < Provoostenator> That's one reason I would make this RPC-only initially. 05:22 < Provoostenator> morcos: but does it really matter much privacy wise if you spend the next transaction from your change or by amending the original transaction? 05:23 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 260 seconds] 05:24 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 05:26 < morcos> Provoostenator: well if you spend from your change, it MAY be unclear that it was your change or the person you paid spending (agreed that right now change is probably pretty easily identifiable though) 05:26 < morcos> also if you spend unconfirmed, then you have a good point 05:28 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 252 seconds] 05:28 < Provoostenator> I can see a use case for low priority and smaller transactions, e.g. paying back friends, where you intentionally set the fee too low, so you can keep amending it. A poor mans payment channel. Obviously there's a privacy cost. 05:29 < morcos> or rich mans payment channel as the case may be. :) 05:29 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 05:31 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 05:33 < Provoostenator> "TestFramework (INFO): Mining blocks..." does show up in the test log file. 05:35 -!- hoge_ [~hoge@ngn9-ppp85.tokyo.sannet.ne.jp] has joined #bitcoin-core-dev 05:35 < Provoostenator> Even stranger given that the default is INFO. 05:43 < Provoostenator> Ah, so I need to call "test/functional/bumpfee.py --loglevel=INFO" for this to work. 05:49 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 240 seconds] 05:50 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-hrqmjnqngzxcldyq] has joined #bitcoin-core-dev 05:51 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 248 seconds] 05:51 -!- hsmiths [uid95325@gateway/web/irccloud.com/x-ieceermpktuwxjbq] has joined #bitcoin-core-dev 05:52 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 05:52 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 05:52 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 05:55 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-gdjycrkmphpvgtpc] has quit [Quit: Connection closed for inactivity] 06:00 -!- kbgg_ [Elite20763@gateway/shell/elitebnc/x-zmhlxmhgoqkkvafu] has joined #bitcoin-core-dev 06:03 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 06:06 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has joined #bitcoin-core-dev 06:12 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 264 seconds] 06:12 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:13 -!- hoge_ [~hoge@ngn9-ppp85.tokyo.sannet.ne.jp] has quit [Remote host closed the connection] 06:19 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 06:19 -!- JamesAU_ [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 06:20 -!- quantbot [~quantbot@38.101.106.141] has quit [Remote host closed the connection] 06:20 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 06:20 -!- quantbot [~quantbot@38.101.106.141] has joined #bitcoin-core-dev 06:23 -!- JamesAU_ [~JamesAU@120.146.9.99] has quit [Ping timeout: 240 seconds] 06:24 -!- JamesAU_ [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 06:25 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has joined #bitcoin-core-dev 06:25 -!- Cogito_Ergo_Sum [~Myself@80.107.149.55] has quit [Changing host] 06:25 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 06:29 -!- JamesAU_ [~JamesAU@120.146.9.99] has quit [Ping timeout: 276 seconds] 06:32 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 06:32 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev 06:35 -!- sanjeev [~sanjeev@118.185.49.106] has quit [Ping timeout: 248 seconds] 06:36 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:48 < bitcoin-git> [bitcoin] joemphilips opened pull request #11770: [REST] add a rest endpoint for estimatesmartfee, docs, and test (master...rest_fee) https://github.com/bitcoin/bitcoin/pull/11770 06:55 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev 07:00 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 264 seconds] 07:01 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 07:27 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 248 seconds] 07:35 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 07:36 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 07:52 -!- archaeal_ [60462f91@gateway/web/freenode/ip.96.70.47.145] has joined #bitcoin-core-dev 07:53 -!- tim [b89e5ed2@gateway/web/freenode/ip.184.158.94.210] has joined #bitcoin-core-dev 07:53 -!- tim [b89e5ed2@gateway/web/freenode/ip.184.158.94.210] has quit [Client Quit] 07:53 -!- dcousens [~dcousens@CPE-101-181-112-6.lnse5.cha.bigpond.net.au] has quit [Ping timeout: 250 seconds] 07:54 -!- dcousens [~dcousens@CPE-101-181-17-139.lnse4.cha.bigpond.net.au] has joined #bitcoin-core-dev 07:55 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Ping timeout: 246 seconds] 07:55 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 07:55 -!- StopAndDecrypt [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has quit [Changing host] 07:55 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 08:00 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 08:04 < promag> archaeal_: it it was me, I would have the PR title: Add REST endpoint blockhash 08:05 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 08:05 < promag> then one commit for the implementation, one for the test and other for the doc 08:05 -!- satwo [~textual@pool-173-76-23-167.bstnma.fios.verizon.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 08:06 < promag> ^ 11765 08:07 < archaeal_> i see...yeah that makes sense 08:07 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds] 08:09 < Lauda> sipa I can confirm very high memory usage. I had a fresh sync (albeit a fork of 0.15.x) and it was using over 6 GB with 4GB dbcache and swap was 100% utilized. 08:18 -!- RoyceX [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 248 seconds] 08:25 -!- zaxar [4f6ba610@gateway/web/freenode/ip.79.107.166.16] has joined #bitcoin-core-dev 08:25 -!- zaxar [4f6ba610@gateway/web/freenode/ip.79.107.166.16] has quit [Client Quit] 08:31 -!- zaxaar [zaxaar@adsl-16.79.107.166.tellas.gr] has joined #bitcoin-core-dev 08:33 -!- zaxaar [zaxaar@adsl-16.79.107.166.tellas.gr] has quit [Client Quit] 08:33 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 08:33 -!- DvdKhl [~Arokh@ip-37-201-211-111.hsi13.unitymediagroup.de] has joined #bitcoin-core-dev 08:35 < bitcoin-git> [bitcoin] jnewbery opened pull request #11771: [tests] Change invalidtxrequest to use BitcoinTestFramework (master...refactor_invalidtxrequest) https://github.com/bitcoin/bitcoin/pull/11771 08:35 -!- Randolf [~randolf@207.81.117.86] has joined #bitcoin-core-dev 08:36 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 08:36 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 268 seconds] 08:37 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 08:37 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 08:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 08:40 -!- RoyceX [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 240 seconds] 08:40 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-yxfueodttfpnlmwa] has joined #bitcoin-core-dev 08:41 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 240 seconds] 08:43 -!- satwo [~textual@pool-173-76-23-167.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 08:43 -!- satwo [~textual@pool-173-76-23-167.bstnma.fios.verizon.net] has quit [Client Quit] 08:50 -!- cheese_ [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 248 seconds] 08:54 -!- Randolf [~randolf@207.81.117.86] has quit [Ping timeout: 260 seconds] 09:01 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 09:02 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 09:05 -!- Khunbish [~Khunbish@28.62-136-217.adsl-dyn.isp.belgacom.be] has joined #bitcoin-core-dev 09:05 -!- Khunbish [~Khunbish@28.62-136-217.adsl-dyn.isp.belgacom.be] has quit [Client Quit] 09:09 -!- JackH [~laptop@212.78.169.180] has joined #bitcoin-core-dev 09:11 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has joined #bitcoin-core-dev 09:11 -!- musalbas [~musalbas@2001:bc8:30c2:ff00::] has joined #bitcoin-core-dev 09:18 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 09:21 -!- Randolf [~randolf@207.81.117.206] has joined #bitcoin-core-dev 09:22 -!- cheese_ [~Cheeseo@unaffiliated/cheeseo] has quit [Ping timeout: 248 seconds] 09:24 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev 09:25 -!- Randolf [~randolf@207.81.117.206] has quit [Ping timeout: 240 seconds] 09:26 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 09:30 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:31 -!- JackH [~laptop@212.78.169.180] has quit [Ping timeout: 260 seconds] 09:33 -!- Chasity76Ortiz [~Chasity76@ns334669.ip-5-196-64.eu] has joined #bitcoin-core-dev 09:37 < bitcoin-git> [bitcoin] jnewbery closed pull request #11047: [tests] rename functional tests (master...rename_functional_tests) https://github.com/bitcoin/bitcoin/pull/11047 09:40 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 09:41 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 09:41 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:42 -!- archaeal_ [60462f91@gateway/web/freenode/ip.96.70.47.145] has quit [Ping timeout: 260 seconds] 09:42 < morcos> sipa: have a second to talk about SW wallet? 09:42 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:43 < morcos> i thought one of the cases we wanted to cover (which is mostly a version of 2 i think) is that you have a backup of a 0.15.0 wallet now, and you addwitnessaddress, but then later you have to restore from backup 09:43 < morcos> this is what the 2(a) case was meant to handle 09:43 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 248 seconds] 09:44 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:44 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:44 < morcos> i dont think i particularly care if we don't handle that in 0.16, but it does seem like at some point we should handle that... with SW out, people are going to be doing that work flow. 09:45 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 09:46 < morcos> never mind, i didn't read carefully enough.. the 1(a) case handles that if you are running 0.16, its only the downgrade case that isn't handled 09:46 < morcos> i think that is good enough 09:47 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 09:48 < sipa> morcos: ok 09:48 < morcos> i'm fine with 1(a), 2(c), 3(a). But I wonder if there is some way we can warn the user about Problem 2, like could the backup have a higher walelt version (ick) 09:48 < sipa> right, that would be one solution 09:49 < sipa> but it's hard to prevent backups by just file copying 09:50 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:50 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:51 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #bitcoin-core-dev 09:51 < sipa> you could have some system where a wallet is 'loaded' into a node, and the wallet file itself becomes marked as a backup, but something else in the node's configuration contains knowledge to avoid treating it as a backup 09:51 < sipa> but... yuck 09:51 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 09:51 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 09:54 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 09:54 < morcos> well the good thing is there is a workaround right.. so maybe warnings are enough, saying that if you want to downgrade and you only have a backup, you first need to run 0.16 with the backup and make a fresh backup, and then you can downgrade 09:55 < morcos> and that is true regardless of whether you backup is from 0.15 or 0.16 10:04 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has quit [Ping timeout: 276 seconds] 10:07 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 10:07 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 10:09 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 10:09 -!- timothy [~tredaelli@redhat/timothy] has quit [Quit: Konversation terminated!] 10:11 < BlueMatt> sipa: I really cant say I'm a fan of 2c 10:14 < sipa> the alternatives aren't great either though 10:15 -!- Jochem [525e2acb@gateway/web/freenode/ip.82.94.42.203] has joined #bitcoin-core-dev 10:17 < BlueMatt> sipa: what did you think of my suggestion of a segwit-wallet-bestblockhash field 10:17 < BlueMatt> in addition to wallet-bestblockhash 10:17 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Quit: Leaving] 10:17 < BlueMatt> which allows you to rescan for segwit addresses if you downgraded to 15 for a while (and havent fully pruned those blocks) 10:19 < sipa> BlueMatt: sounds doable, but it's not really something we can continue 10:20 < sipa> it's a bit of an accident that segwit was introduced in 0.13.1, but will only be actually supported 3 major versions later 10:20 < BlueMatt> hmm? 10:21 < sipa> i don't think we should continue to expect that it's at all feasible that a new feature introduced will actually work at all after downgrading 10:21 < BlueMatt> I didnt claim it would/should? 10:21 < sipa> right, but the approach you suggest really only works for segwit 10:21 < sipa> not for anything later 10:21 < sipa> (likely) 10:21 < BlueMatt> yes, this is specifically a segwit thing in large part cause we're not doing a full -walletupgrade for it 10:22 < BlueMatt> if we were doing a -walletupgrade (which I still think is the "right" way to do this, but obviously with a ton more complication) then I dont think we'd need to do this 10:22 -!- Giszmo [~leo@pc-204-28-214-201.cm.vtr.net] has joined #bitcoin-core-dev 10:22 < BlueMatt> a non-default clear statement of "I'm moving my wallet to 0.16" should be sufficient, but absent that, we should be more careful to handle some downgrade cases 10:24 < gmaxwell> how is walletupgrade right when it leaves current wallets people are using today unrecoverable? 10:24 < BlueMatt> hmm? 10:24 < gmaxwell> people use addwitnessaddress, then their backups are instantly no good-- no lookahead, no nothing. 10:25 < gmaxwell> that screup is fixed by 'upgrading' by default 10:25 < sipa> gmaxwell: i don't see how that has anything to do with explicit upgrade or not 10:25 < BlueMatt> I mean addwitnessaddress is barely supported and largely unsupportable, at least without something like upgradewallet 10:25 < BlueMatt> I mean you can auto-upgrade a user if they've previously used addwitnessaddress 10:25 < BlueMatt> cause an addwitnessaddress wallet is already a mess (at least wrt backups) 10:26 < sipa> explicit upgrade just guarantees that old versions will give you an error rather than silently missing things _for addresses generated in the future_ 10:26 < sipa> obviously any addresses generated in the must should always continue to work 10:26 < BlueMatt> of course, but explicit upgrade also has a clear definition for the user: you cannot open this wallet anymore in old versions 10:27 < BlueMatt> which if we *dont* do an explicit upgrade, we end up in this quagmire of backward compatibility/downgrade hell 10:27 < gmaxwell> BlueMatt: if you don't autoupgrade someone then you won't make their backups good again. 10:27 < BlueMatt> "make their backups good again"? 10:28 < BlueMatt> I do not think we should *ever* auto-upgrade someone, with the possible exception of folks who've previously addwitnessaddress'd, cause they're kinda fucked if we dont, or at least we should nag them 10:28 < sipa> i think at some point we should do a required uograde 10:28 < gmaxwell> Right now, joe blow believes our claims of supporting segwit, runs the software, follows instructions to use it... unknown to him, his backup will miss coins if recovered. Post upgrading to a release that autoupgrades his backup will no longer miss coins when recovered. 10:28 < gmaxwell> _You cannot tell if they've used addwitnessaddress because they could be loading a backup which hasn't seen it_ 10:29 < sipa> well 1a solves that 10:30 < gmaxwell> if you try, you get even more awesome effects like one backup works for address X and another doesn't for reasons entirely unrelated to address X. 10:30 < BlueMatt> yes, I think for that reason 1a is probably good 10:30 < sipa> the only case that is not covered is downgrading + restoring a backup simuktaneously 10:31 < sipa> which is inherently impossible to solve completely 10:31 < BlueMatt> yes, and hence my suggestion to do a segwit-wallet-bestblockhash, cause then we at least fix it for non-pruned or only-briefly-run-as-downgraded nodes 10:31 < sipa> but some solutions are possible for the case where the backup was made after uograding 10:31 < BlueMatt> sidestepping the version rabbithole 10:32 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 10:32 * BlueMatt would also like to further discuss 2a 10:32 < BlueMatt> whats default keypool size? its not *that* bad 10:32 < sipa> 2000 keys 10:32 < BlueMatt> and, when we go to do things "the right way", we can clean those out, maybe 10:32 < sipa> + more logic and edge cases 10:33 < BlueMatt> with a -walletupgrade can clean out those entries 10:33 < sipa> = something that still only works as long as you don't actually use the wallet too much after downgrading 10:34 < BlueMatt> hmm? no? 10:34 < BlueMatt> your backups will still work cause they have the witnesses added 10:35 < BlueMatt> and the upgraded wallet obviously wont cause you set the version to be un-openable with the old version 10:35 < sipa> right 10:36 < sipa> but if the wallet was used a lot in the new version after the backup was made, you'll hit problems when the backup's keypool runs out 10:36 < BlueMatt> yes, but that is always true 10:36 < BlueMatt> if your keypool runs out you cant run from a backup or you lose funds 10:36 < BlueMatt> period. 10:37 < BlueMatt> (I suppose with the exception of HD, but....ugh) 10:37 < sipa> no, not period 10:37 < sipa> this is exactly the assumption we don't need to make with HD wallets anymore 10:38 < sipa> relying on the keypool to deal with downgraded backups reintroduces that assumption 10:38 < BlueMatt> yes, with the exception of HD 10:38 < sipa> that's not a small exception 10:38 < sipa> that's the norm 10:39 < BlueMatt> ok, so now we're back to segwit-wallet-bestblockhash 10:39 < BlueMatt> thats the only way to fix that issue 10:39 < wallet42> sipa: ah yes. prioritisetransaction is exactly what im looking for. 10:40 < sipa> BlueMatt: right, but only in the case the user actually uogrades again 10:40 < BlueMatt> well if they dont upgrade again there is literally nothing we can do 10:40 < sipa> that's my point 10:40 < wallet42> spia: my python prototype question was in the context of the output list wallet amend tx amend idea you talked about with provoost 10:40 < BlueMatt> (and I think thats reasonable, if you use segwit in a version with a headline of "SegWit Wallet" and then downgrade, you'd kinda expect to not have your segwit funds) 10:41 < sipa> BlueMatt: so why do we need to support the downgrade + restore case again? 10:41 < BlueMatt> well the current proposal does *not* fully work in the case you upgrade again, without a rescan 10:41 < sipa> it's without guarantees at best 10:41 < BlueMatt> if you are non-pruned its guaranteed 10:41 < sipa> in whatever case 10:41 < sipa> it's without guarantees at best as long as you don't upgrade 10:41 < BlueMatt> huh? 10:42 < sipa> don't upgrade after downgrading, i mean 10:42 < BlueMatt> yes, if you dont ever switch back to 0.16+, then you are maybe not safe in this case 10:42 < sipa> not maybe 10:42 < BlueMatt> but so what? we can still improve things 10:43 < sipa> in that case nothing can be guaranteed 10:43 < BlueMatt> doing a partial-rescan is a very, very big improvement for many of the cases we're talking about 10:43 < BlueMatt> even if its not a guarantee 10:43 < BlueMatt> assuming you may never upgrade to 0.16+ and trying to support that seems like nonsense 10:43 < BlueMatt> but thats not what I'm arguing here 10:43 < sipa> ok, so let's walk through yhis 10:43 < sipa> you upgrade to 0.16 10:43 < sipa> there is no segwitwallet record 10:44 < sipa> you do what? assume that the existing non-segwit wallet bestblock record is accurate? 10:45 < BlueMatt> a) ignore, b) rescan from segwit activation date if you have P2SH-P2WPKH entries c) always rescan from segwit activation date 10:45 < sipa> b assumes the file is recent enough to have those records 10:46 < BlueMatt> d) rescan in case -findmissingsegwitoutputs=true is set 10:46 < BlueMatt> indeed, b kinda sucks 10:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:46 < sipa> i think the best solution is just telling people to run with 0.16 and -rescan in that case 10:46 < BlueMatt> do we have a rescan from date rpc? 10:46 < BlueMatt> i think we do now, right? 10:47 < sipa> unsure 10:47 < BlueMatt> I mean in that case we also need 2a, I think 10:48 < sipa> how so? 10:48 < sipa> 1a solves everything during a rescan 10:48 -!- windsok [~windsok@unaffiliated/windsok] has quit [Quit: No Ping reply in 180 seconds.] 10:48 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 10:49 < BlueMatt> yea, sorry, 1a obviously fixes it for rescan, maybe I'm just more worried about problem 2 10:49 < gmaxwell> unrelated to this, through some combination of multiwallet, -rescan, restarting my node.. I ended up in a situation with a bunch of wallets that lost all their transactions but think they're in sync. 10:49 < BlueMatt> more like "oops, da server with wallet blew up, bring in the one we upgraded from last week, running 0.15.1, will have to do for now" 10:50 < BlueMatt> gmaxwell: thats....frightening....is it 0.15.1 with the copied-db issue? 10:50 < morcos> i basically agree with sipa 10:50 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 10:50 < sipa> my solution to problem 2 is tell people to avoid downgrading and restoring, and if in exceptional cases that misses something, rescan 10:50 < gmaxwell> w/ recent-ish master. 10:50 < BlueMatt> sipa: but that doesnt solve the problem of not upgrading right away? at least 2a will help significantly 10:50 < morcos> i think 1a, 3a and a guide for acceptable workflows and how to recover is the way to go.. we should not make things too difficult. 10:51 < morcos> however i think we will need to do something like 2a when we have the upgrade wallet option for 0.17. but then it will i think be fully optional as to whether you upgrade or not. 10:51 < gmaxwell> I _think_ what I did was start with two dozen -wallets and -rescan then realized it would sequentially rescan each, killed the process, then went on to try using them directly. 10:52 -!- digifis [~sin@x4dbe3ea2.dyn.telefonica.de] has joined #bitcoin-core-dev 10:52 < sipa> BlueMatt: but even if we do 2a, there is no solution for 4a 10:52 -!- windsok [~windsok@unaffiliated/windsok] has joined #bitcoin-core-dev 10:52 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 10:52 < sipa> recovery options are great, but they exist 10:52 < BlueMatt> yea, issue 4 is unsolveable, I agree 10:52 < morcos> sorry, not actually 2a for 0.17, but something that takes all your keys in your keypool and stores them as things that implicitly might have any style address 10:52 < BlueMatt> with the exception of 1a + rescan 10:53 < sipa> 2a is essentially trying to avoid a recovery procedure in a situation which already is something that should never be part of normal workflow 10:54 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #bitcoin-core-dev 10:54 < gmaxwell> if we make rescan faster we could be more liberal in expecting its use. 10:55 < gmaxwell> not tooo liberal, since pruned nodes can't rescan... 10:55 < BlueMatt> gmaxwell: do you have an intuition in why rescan is slow? I havent looked into it 10:56 < sipa> BlueMatt: we should do a benchmark for reindex with and without wallet 10:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:58 < sipa> if there is a significant different between the two, there is a totally obvious improvement from not calling Solver on each output in order to match it with the wallet 10:58 < sipa> (which construct a vector of vectors ffs) 10:58 < gmaxwell> well we fully read and deseralize each block and each transaction then pass them through the wallet code, so that implhes 1001 memory allocations plus sha256ing each transaction (and reserializing to do so)... looking at IO we also seem to create a lot of excess IO with opening the file, seeking to the block closing it. 10:59 < sipa> then indeed there is the cost of just loading blocks, which could be improved by having a block deserializer that doesn't build/verify the merkle tree 10:59 < gmaxwell> at least from rough looking at it, we do both a bunch of dump computation and IO and all of it serialized. 11:00 < gmaxwell> it's worth noting that it's not remarkably faster with the blockchain all in cache. 11:01 < BlueMatt> sipa: ok, so I guess I feel a lot more comfortable about things if we do #11281 and recommend rescanblockchain segwit_activation_height 11:01 < 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 11:02 < BlueMatt> sipa: I'd still be more comfortable with 2a...its far from a hard guarantee of anything, but I really could see someone ending up in the state where that'd save them 11:02 < BlueMatt> if for no other reason than someone restoring a backup may load in 0.15, realize they need 0.16, then open in 0.16 right away 11:02 < BlueMatt> and end up screwing themselves 11:04 < BlueMatt> the segwit-wallet-best-block-hash would also similarly solve the same issue even if you do my option a where you just ignore it if it isnt there 11:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 11:04 < BlueMatt> though I agree that kinda feels gross given its solving such a specific edge case without any hard guarantees 11:04 -!- windsok [~windsok@unaffiliated/windsok] has quit [Quit: No Ping reply in 180 seconds.] 11:06 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 11:08 -!- windsok [~windsok@45.63.59.8] has joined #bitcoin-core-dev 11:08 -!- windsok [~windsok@45.63.59.8] has quit [Changing host] 11:08 -!- windsok [~windsok@unaffiliated/windsok] has joined #bitcoin-core-dev 11:08 < BlueMatt> can we at least high-priority #11281 for 0.16? 11:08 < 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 11:08 < BlueMatt> so that rescan is at least slightly less painful from the qt command window 11:08 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 11:09 < sipa> sgtm 11:09 < BlueMatt> and add a "I lost my segwit coins" button in the debug window 11:09 * BlueMatt *ducks* 11:10 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 264 seconds] 11:10 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 240 seconds] 11:13 < gmaxwell> any kind of scanning uncertanty will cause untold amounts of prophylactic scanning. 11:13 -!- bobl [d0f8aeaf@gateway/web/freenode/ip.208.248.174.175] has joined #bitcoin-core-dev 11:13 < BlueMatt> yea, but I dont think we can really solve that...... 11:13 -!- digifis [~sin@x4dbe3ea2.dyn.telefonica.de] has quit [Quit: Verlassend] 11:14 < BlueMatt> in part cause 0.16 docs are going to have to have a bunch of "in case you did X, do this rescan" 11:14 -!- bobl [d0f8aeaf@gateway/web/freenode/ip.208.248.174.175] has quit [Client Quit] 11:15 < gmaxwell> thats partly why I was commenting about making rescanning faster. 11:15 < BlueMatt> yes, though dunno about making that a requirement for 0.16 :p 11:15 < gmaxwell> oh another point on speed-- I opened an issue for this-- right now if you load up a dozen wallets and -rescan. ... it rescans a dozen times, one for each wallet by itself... 11:15 < BlueMatt> yes, that should be fixed as well 11:16 < gmaxwell> my first idea about not spending the rest of my life rescanning was thwarted by that. 11:22 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 240 seconds] 11:28 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 11:30 < bitcoin-git> [bitcoin] TheBlueMatt opened pull request #11775: Move fee estimator into validationinterface/cscheduler thread (master...2017-09-background-feeest) https://github.com/bitcoin/bitcoin/pull/11775 11:33 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 11:34 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 11:47 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 11:48 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wjfffutfezyosced] has joined #bitcoin-core-dev 11:48 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 255 seconds] 12:03 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev 12:06 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 12:07 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 12:11 < jonasschnelli> BlueMatt: added 11281 to the project 7 12:11 -!- Chasity76Ortiz [~Chasity76@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 276 seconds] 12:13 < BlueMatt> jonasschnelli: thanks! 12:15 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has quit [Remote host closed the connection] 12:15 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has joined #bitcoin-core-dev 12:17 < cluelessperson> BlueMatt: are you updating the fee estimator? 12:17 -!- ekrok_ [~ekrok@85.200.34.95.customer.cdi.no] has joined #bitcoin-core-dev 12:17 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has quit [Read error: Connection reset by peer] 12:18 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 12:20 < BlueMatt> cluelessperson: it doesnt change the fee estimator logic, except to handle a few edge cases better 12:33 -!- Sinclair6 [~sinclair6@2602:306:c4b1:2570:24c5:35df:bedb:ce4b] has joined #bitcoin-core-dev 12:37 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt] 12:42 < sipa> Lauda: using 6GB with 4GB dbcache sounds bad but not nearly the same thing i was seeing 12:43 < sipa> i was seeing 32GB usage with 1.7G dbcache 12:43 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 240 seconds] 13:07 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Read error: Connection reset by peer] 13:07 < Lauda> Well, add 4 gb of SWAP to that so probably ~10ish (I think I allocated 7 maximum for the VM). However, yes. That is much worse :< 13:07 < Lauda> Any ideas as to what is causing that? 13:10 < sipa> by "using" i mean RSS size, not physical usage 13:10 < sipa> it's pretty hard to map VM usage to physical usage, as processes can share memory etc 13:11 < sipa> (by VM i mean virtual memory, not virtual machine - it's probably confusing in this context) 13:12 < Lauda> Oh, then 6 GB yeah. 13:13 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has joined #bitcoin-core-dev 13:14 < Lauda> Your behavior is only in current master, not in 0.15.1? 13:14 < sipa> indeed 13:15 < sipa> in 0.15.1 memory usage stayed nicely within a few 100 MB of the cache size 13:15 < sipa> though i now fail to reproduce with master 13:16 < Lauda> That's strange. 13:27 -!- Randolf [~randolf@24.244.32.238] has joined #bitcoin-core-dev 13:35 -!- Randolf [~randolf@24.244.32.238] has quit [Ping timeout: 276 seconds] 13:36 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has joined #bitcoin-core-dev 13:36 -!- cryptapus_ [~cryptapus@jupiter.osmus.org] has quit [Changing host] 13:36 -!- cryptapus_ [~cryptapus@unaffiliated/cryptapus] has joined #bitcoin-core-dev 13:36 -!- cryptapus [~cryptapus@unaffiliated/cryptapus] has quit [Read error: Connection reset by peer] 13:36 -!- cryptapus_ is now known as cryptapus 13:39 -!- Dizzle [~dizzle@108.171.182.16] has joined #bitcoin-core-dev 13:45 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 13:55 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 13:57 -!- archaeal_ [60462f91@gateway/web/freenode/ip.96.70.47.145] has joined #bitcoin-core-dev 13:59 < cluelessperson> BlueMatt: do you know who might be best to redo the logic? 13:59 < cluelessperson> reason being that fees seem to jump up faster than volume 13:59 < cluelessperson> https://jochen-hoenicke.de/queue/#2h 13:59 < gribble> https://github.com/bitcoin/bitcoin/issues/2 | Long-term, safe, store-of-value · Issue #2 · bitcoin/bitcoin · GitHub 14:00 < BlueMatt> cluelessperson: if there were a clear and easy fix it would have been done already :/ 14:00 < BlueMatt> sadly good fee estimation is super non-trivial 14:01 < BlueMatt> *especially* for the non-economical (eg doing non-rbf so want high confidence) case 14:01 < cluelessperson> BlueMatt: agreed. I could only recommend experimenting with "lower estimates slightly" and see how the mempool responds. 14:01 -!- pgupta [~pgupta@193.60.220.253] has joined #bitcoin-core-dev 14:01 < cluelessperson> that would take >years to tune. 14:01 < BlueMatt> doing it with rbf in economical mode could probably get improvements and go down faster, etc 14:02 < BlueMatt> "lower estimates slightly"? what does that mean? 14:02 < BlueMatt> in steady-state the fee estimator does incredibly well, it also happens to do incredibly well for very-high-confidence-of-inclusion 14:02 < cluelessperson> BlueMatt: (existing_fee_estimate) - 1 sat, -5 sat, -10 sat 14:02 * cluelessperson chuckles at the absurdity 14:02 < BlueMatt> though fee estimation also ends up being a bit of a self-fuffilling prophecy 14:03 < BlueMatt> yea, I dont think that is a good approach :p 14:05 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 268 seconds] 14:06 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has joined #bitcoin-core-dev 14:06 < cluelessperson> BlueMatt: I'm taking classes. Hopefully I can help in the future, but right now I'm a moronw. :/ 14:06 -!- ekrok_ [~ekrok@85.200.34.95.customer.cdi.no] has quit [Read error: Connection reset by peer] 14:08 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has joined #bitcoin-core-dev 14:16 -!- ekrok [~ekrok@85.200.34.95.customer.cdi.no] has quit [Read error: Connection reset by peer] 14:16 -!- ekrok_ [~ekrok@85.200.34.95.customer.cdi.no] has joined #bitcoin-core-dev 14:18 < mlz> lol 14:28 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wjfffutfezyosced] has quit [Quit: Connection closed for inactivity] 14:48 -!- Cheeseo [~Cheeseo@gateway/vpn/privateinternetaccess/cheeseo] has quit [Ping timeout: 240 seconds] 14:49 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 14:52 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 14:58 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 14:59 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-ftrbfowlmtwkdbvj] has joined #bitcoin-core-dev 15:02 -!- cyber55 [~cyber55@unaffiliated/cyber55] has joined #bitcoin-core-dev 15:07 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wadiombjhvvjpemi] has joined #bitcoin-core-dev 15:10 -!- pgupta [~pgupta@193.60.220.253] has quit [Remote host closed the connection] 15:11 -!- js___ [8004384e@gateway/web/freenode/ip.128.4.56.78] has joined #bitcoin-core-dev 15:11 -!- pgupta [~pgupta@193.60.220.253] has joined #bitcoin-core-dev 15:11 -!- js___ [8004384e@gateway/web/freenode/ip.128.4.56.78] has quit [Client Quit] 15:12 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 15:14 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:14 -!- quantbot [~quantbot@38.101.106.141] has quit [Ping timeout: 248 seconds] 15:15 -!- pgupta [~pgupta@193.60.220.253] has quit [Ping timeout: 276 seconds] 15:19 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 276 seconds] 15:19 -!- shesek [~shesek@bzq-84-110-53-47.red.bezeqint.net] has joined #bitcoin-core-dev 15:19 -!- shesek [~shesek@bzq-84-110-53-47.red.bezeqint.net] has quit [Changing host] 15:19 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 15:19 -!- Randolf [~randolf@24.244.32.173] has joined #bitcoin-core-dev 15:22 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #11779: qa: Combine logs on travis by default (master...Mf1711-travisQaLogs) https://github.com/bitcoin/bitcoin/pull/11779 15:23 -!- pgupta [~pgupta@109.246.173.160] has joined #bitcoin-core-dev 15:26 -!- Randolf [~randolf@24.244.32.173] has quit [Ping timeout: 268 seconds] 15:28 -!- pgupta [~pgupta@109.246.173.160] has quit [Ping timeout: 268 seconds] 15:29 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 15:35 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has quit [] 15:35 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 260 seconds] 15:38 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Ping timeout: 264 seconds] 15:40 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 15:46 -!- esotericnonsense [~esotericn@unaffiliated/esotericnonsense] has joined #bitcoin-core-dev 15:48 -!- brianhoffman_ [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has joined #bitcoin-core-dev 15:50 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 15:50 -!- brianhoffman [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has quit [Ping timeout: 268 seconds] 15:50 -!- brianhoffman_ is now known as brianhoffman 15:56 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:56 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Remote host closed the connection] 15:56 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 15:58 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 15:59 -!- Dizzle [~dizzle@108.171.182.16] has quit [Quit: Leaving...] 16:01 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:ae96:a3a2:7ac2:9390] has joined #bitcoin-core-dev 16:01 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 16:03 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 276 seconds] 16:03 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 248 seconds] 16:04 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 16:06 -!- jb55 [~jb55@208.98.200.100] has joined #bitcoin-core-dev 16:08 -!- archaeal_ [60462f91@gateway/web/freenode/ip.96.70.47.145] has quit [Quit: Page closed] 16:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 16:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 16:34 -!- dqx__ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 16:37 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 248 seconds] 16:38 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 16:41 -!- JamesAU_ [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 16:42 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 240 seconds] 16:43 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Ping timeout: 276 seconds] 16:43 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 16:46 -!- JamesAU_ [~JamesAU@203.210.69.68] has quit [Ping timeout: 240 seconds] 16:51 -!- tigana [~tiganasec@197.237.160.185] has joined #bitcoin-core-dev 16:51 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 16:57 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 16:58 -!- dqx_ [~dqx@unaffiliated/dqx] has joined #bitcoin-core-dev 16:58 -!- tigana [~tiganasec@197.237.160.185] has quit [Quit: Leaving] 16:59 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has quit [Read error: Connection reset by peer] 17:00 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has quit [Read error: Connection reset by peer] 17:00 -!- PaulCapestany [~PaulCapes@ip68-100-207-91.dc.dc.cox.net] has joined #bitcoin-core-dev 17:01 -!- Squidicuz [~squid@pool-173-48-82-37.bstnma.fios.verizon.net] has joined #bitcoin-core-dev 17:01 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:01 -!- dqx__ [~dqx@unaffiliated/dqx] has quit [Ping timeout: 260 seconds] 17:01 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:01 -!- victorSN [~victorSN@ec2-18-221-184-249.us-east-2.compute.amazonaws.com] has quit [Quit: Ping timeout (120 seconds)] 17:02 -!- Ge0rges [~Ge0rges@104.236.151.200] has quit [Ping timeout: 260 seconds] 17:03 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 17:03 -!- Ge0rges [~Ge0rges@104.236.151.200] has joined #bitcoin-core-dev 17:05 -!- dqx_ [~dqx@unaffiliated/dqx] has quit [Quit: .] 17:06 -!- isis [~isis@abulafia.patternsinthevoid.net] has quit [Ping timeout: 240 seconds] 17:08 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 240 seconds] 17:11 -!- isis [~isis@abulafia.patternsinthevoid.net] has joined #bitcoin-core-dev 17:13 -!- mumux [~mix@ip-79-111-95-71.bb.netbynet.ru] has quit [Remote host closed the connection] 17:15 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:16 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-ftrbfowlmtwkdbvj] has quit [Quit: Connection closed for inactivity] 17:16 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:20 -!- Randolf [~randolf@96.53.47.42] has quit [Ping timeout: 276 seconds] 17:23 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:24 -!- quantbot [~quantbot@cpe-74-73-138-18.nyc.res.rr.com] has joined #bitcoin-core-dev 17:25 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:31 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:ae96:a3a2:7ac2:9390] has quit [Ping timeout: 276 seconds] 17:32 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:ec69:f:8974:72a4] has joined #bitcoin-core-dev 17:33 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:35 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:37 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 17:38 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:ec69:f:8974:72a4] has quit [Remote host closed the connection] 17:38 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:3eef:933d:a2bd:9fd8] has joined #bitcoin-core-dev 17:41 -!- nickler [~nickler@185.12.46.130] has quit [Ping timeout: 268 seconds] 17:46 -!- Randolf [~randolf@96.53.47.42] has joined #bitcoin-core-dev 17:47 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:48 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:49 -!- nickler [~nickler@185.12.46.130] has joined #bitcoin-core-dev 17:50 -!- ekrion [~ff@adsl201-232-238-252.epm.net.co] has quit [Quit: Lost terminal] 17:53 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 17:55 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 17:57 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-yxfueodttfpnlmwa] has quit [Quit: Connection closed for inactivity] 18:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 18:01 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 18:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 18:01 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:3eef:933d:a2bd:9fd8] has quit [Remote host closed the connection] 18:02 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 18:02 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:e115:4c0:dd8b:ae23] has joined #bitcoin-core-dev 18:04 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 18:09 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 18:11 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 18:12 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 18:13 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 248 seconds] 18:17 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Remote host closed the connection] 18:17 -!- bule2 [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 18:18 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 264 seconds] 18:20 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has joined #bitcoin-core-dev 18:21 -!- kallewoof [~karl@67.205.138.199] has quit [Ping timeout: 260 seconds] 18:22 -!- kallewoof [~karl@67.205.138.199] has joined #bitcoin-core-dev 18:23 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 18:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 1.7.1] 18:24 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 18:25 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 268 seconds] 18:26 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 18:26 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 18:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Client Quit] 18:27 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 18:29 -!- wxss [~user@91.236.116.83] has quit [Quit: leaving] 18:32 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 18:33 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 18:33 -!- brianhoffman_ [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has joined #bitcoin-core-dev 18:35 -!- gmurf [8102b573@gateway/web/freenode/ip.129.2.181.115] has joined #bitcoin-core-dev 18:35 -!- brianhoffman [~brianhoff@pool-96-231-163-68.washdc.fios.verizon.net] has quit [Ping timeout: 240 seconds] 18:35 -!- brianhoffman_ is now known as brianhoffman 18:37 -!- Emcy_ [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 18:39 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 18:39 -!- Emcy [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 18:40 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 18:41 < gmurf> any good places to learn how to use Bitcoin api 18:42 -!- gmurf [8102b573@gateway/web/freenode/ip.129.2.181.115] has quit [Quit: Page closed] 18:51 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 18:52 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 18:58 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:00 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:03 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 19:03 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 19:06 -!- DigitalDank [DigitalDan@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:06 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 19:06 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 19:07 -!- goatpig [56f75683@gateway/web/freenode/ip.86.247.86.131] has quit [Quit: Page closed] 19:08 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:10 -!- jtimon [~quassel@164.31.134.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds] 19:10 -!- Ehruv [2a6a3cce@gateway/web/freenode/ip.42.106.60.206] has joined #bitcoin-core-dev 19:11 -!- awright [4738b6f2@gateway/web/freenode/ip.71.56.182.242] has joined #bitcoin-core-dev 19:13 -!- Ehruv [2a6a3cce@gateway/web/freenode/ip.42.106.60.206] has quit [Client Quit] 19:16 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:17 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:23 -!- awright [4738b6f2@gateway/web/freenode/ip.71.56.182.242] has quit [Quit: Page closed] 19:24 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:25 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:27 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has joined #bitcoin-core-dev 19:27 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wadiombjhvvjpemi] has quit [Quit: Connection closed for inactivity] 19:32 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:32 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:38 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:40 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:45 -!- wangyuan [276d7d44@gateway/web/freenode/ip.39.109.125.68] has joined #bitcoin-core-dev 19:47 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 19:47 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has quit [Read error: Connection reset by peer] 19:47 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 19:48 -!- DigitalDank [~Satoshi41@ip72-207-116-245.sd.sd.cox.net] has joined #bitcoin-core-dev 19:52 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 19:52 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Ping timeout: 240 seconds] 19:56 -!- BRokq [c630c534@gateway/web/freenode/ip.198.48.197.52] has joined #bitcoin-core-dev 19:59 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 19:59 -!- Chris_Stewart_5 [~chris@gateway/vpn/privateinternetaccess/chrisstewart5/x-62865615] has quit [Ping timeout: 276 seconds] 20:00 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 20:03 -!- BRokq [c630c534@gateway/web/freenode/ip.198.48.197.52] has quit [Ping timeout: 260 seconds] 20:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #bitcoin-core-dev 20:13 < rusty> Latest master branch, bitcoind in regtest mode: bitcoind: validation.cpp:4203: void CheckBlockIndex(const Consensus::Params&): Assertion `(pindexFirstNeverProcessed != nullptr) == (pindex->nChainTx == 0)' failed. 20:16 -!- Emcy_ [~Emcy@unaffiliated/emcy] has quit [Ping timeout: 240 seconds] 20:16 < rusty> Pretty sure that was a .bitcoind dir from an older bitcoind. 20:16 -!- Emcy [~Emcy@unaffiliated/emcy] has joined #bitcoin-core-dev 20:36 -!- archaeal [62ce095e@gateway/web/freenode/ip.98.206.9.94] has quit [Quit: Page closed] 20:46 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 20:48 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 20:48 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 20:48 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 20:52 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 276 seconds] 20:53 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev 21:03 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 21:08 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 21:12 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Ping timeout: 240 seconds] 21:14 -!- StopAndDecrypt_ [~StopAndDe@c-73-248-248-9.hsd1.nj.comcast.net] has joined #bitcoin-core-dev 21:14 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 248 seconds] 21:18 -!- JackH [~laptop@2a02:a210:2e00:300:655a:7cbf:d627:81fb] has quit [Ping timeout: 264 seconds] 21:32 -!- Sinclair6 [~sinclair6@2602:306:c4b1:2570:24c5:35df:bedb:ce4b] has quit [Remote host closed the connection] 21:47 < aj> rusty: hey, i can duplicate that 21:48 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 21:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 21:50 -!- bule2 [~bule@gateway/tor-sasl/bule] has quit [Ping timeout: 248 seconds] 21:50 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 21:57 < aj> rusty: try https://pastebin.com/QfjsEHFK to reproduce -- bug seems to be in validation.cpp::RewindBlockIndex where pindexIter->nTx or nChainTx gets set to 0, but not real sure what the fix should be 21:59 -!- btcdrak [uid234579@gateway/web/irccloud.com/x-gdhklivdhraqigsk] has joined #bitcoin-core-dev 22:11 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-dowkwmlclhffdslb] has joined #bitcoin-core-dev 22:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 22:19 -!- Leminer [LeMiner@unaffiliated/leminer] has quit [Read error: Connection reset by peer] 22:20 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has quit [Remote host closed the connection] 22:21 -!- d9b4bef9 [~d9b4bef9@web501.webfaction.com] has joined #bitcoin-core-dev 22:22 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Remote host closed the connection] 22:24 -!- windsok [~windsok@unaffiliated/windsok] has quit [Quit: No Ping reply in 180 seconds.] 22:25 < wangyuan> test 22:25 -!- wangyuan [276d7d44@gateway/web/freenode/ip.39.109.125.68] has quit [Quit: Page closed] 22:26 -!- JamesAU [~JamesAU@203.210.69.68] has joined #bitcoin-core-dev 22:27 -!- windsok [~windsok@unaffiliated/windsok] has joined #bitcoin-core-dev 22:29 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 22:30 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 22:31 -!- pgupta [~pgupta@109.246.173.160] has joined #bitcoin-core-dev 22:32 -!- LeMiner [LeMiner@unaffiliated/leminer] has joined #bitcoin-core-dev 22:32 -!- JamesAU [~JamesAU@203.210.69.68] has quit [Ping timeout: 240 seconds] 22:32 -!- pgupta [~pgupta@109.246.173.160] has quit [Client Quit] 22:36 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 22:37 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 22:52 -!- esotericnonsense is now known as triggered 22:52 -!- triggered is now known as esotericnonsense 22:59 -!- hoge_ [~hoge@p6763012-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 23:06 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 23:10 -!- JamesAU [~JamesAU@120.146.9.99] has quit [Ping timeout: 240 seconds] 23:12 -!- Cogito_Ergo_Sum [~Myself@unaffiliated/cogito-ergo-sum/x-7399460] has joined #bitcoin-core-dev 23:13 < Varunram> rusty: aj: had the bugs few days back, turned out to be exactly what rusty specified, there'd be another .bitcoin directory somewhere. Once I changed home directories, it went well 23:16 < Varunram> bug* 23:23 < aj> Varunram: yeah, i think it'd be triggered by an old regtest blockchain from before #11389 got merged 23:23 < gribble> https://github.com/bitcoin/bitcoin/issues/11389 | Support having SegWit always active in regtest (sipa, ajtowns, jnewbery) by sipa · Pull Request #11389 · bitcoin/bitcoin · GitHub 23:23 -!- JamesAU [~JamesAU@120.146.9.99] has joined #bitcoin-core-dev 23:24 < Varunram> aj: Thanks! I was looking for that commit, couldn't find it 23:26 -!- hellxcode [~hellxcode@2607:fcc8:6d42:e700:e115:4c0:dd8b:ae23] has quit [Quit: WeeChat 1.9.1] 23:40 < bitcoin-git> [bitcoin] laanwj closed pull request #11722: Switched sync.{cpp,h} to std threading primitives. (master...tjps_sync_antiboost) https://github.com/bitcoin/bitcoin/pull/11722 23:41 -!- bule [~bule@gateway/tor-sasl/bule] has quit [Read error: Connection reset by peer] 23:41 -!- bule [~bule@gateway/tor-sasl/bule] has joined #bitcoin-core-dev 23:41 < wumpus> I'm completely lost with regard to PRs once again - anything ready for merge? 23:45 < jonasschnelli> wumpus: I think a lot of "unfinished" PRs right now... 23:45 < wumpus> yes... 23:45 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev 23:45 < fanquake> A few that could probably just be closed as well 23:46 < jonasschnelli> fanquake: BTW. Thanks for your awesome work on closing / pinging on PRs! 23:46 < fanquake> wumpus probably lost in that wormhole from earlier :p 23:46 < wumpus> yes thanks fanquake :) 23:46 < fanquake> jonasschnelli I try and keep on top of it. Have been wanting to ask you about your place for the coredev-tech site. Saw you put it up on GH? 23:47 < jonasschnelli> fanquake: Yeah, The site is ugly (but simple). jnewbery will probably do some changes for the NY meeting. 23:47 < jonasschnelli> (Which you are very welcome to join) 23:48 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection] 23:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 23:48 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #bitcoin-core-dev 23:49 < fanquake> jonasschnelli when is that, might see if I can come along? I'm waiting for a meetup down here heh 23:49 < jonasschnelli> fanquake: Australia is on the list,.. :) I'm not sure about the NY one... you need to ask jnewbery. Not sure if the exact date stays.. Guess it's in March 18 23:49 < jonasschnelli> Not announce yet 23:50 < fanquake> jonasschnelli cool. Good chance to discuss any potential iOS development work as well. 23:51 < aj> "next one in NYC the week of March 5th 2018" 23:53 < jonasschnelli> aj: Thanks! 23:53 < jonasschnelli> fanquake: Yeah. Though, I won't attend. Schedule-colision. 23:54 < wumpus> this is what we should avoid: https://github.com/bitcoin/bitcoin/pull/11747 the person posts a straightforward two-line fix for an actual issue, when well-meaning but overly zealous review comments get them to refactor things in a questionable way resulting in much more discussion and doubt of correctness 23:55 < fanquake> jonasschnelli no worries 23:55 < wumpus> if something fixes a problem, please just utACK it, if you want to refactor it to your personal taste later then go ahead but that's not part of review 23:55 < wumpus> now we have yet another PR that is stuck... 23:56 < jonasschnelli> wumpus: indeed. 23:57 < bitcoin-git> [bitcoin] fanquake closed pull request #9859: Make TestBlockValidity optional in CreateNewBlock (master...tbv-optional) https://github.com/bitcoin/bitcoin/pull/9859 23:58 < fanquake> I've always wondered how best we could keep tracked of post merge nits/minor fixups. Maybe another tag that we can add to PRs post merge which have any todos remaining in the comments? Then occasionally someone can sweep through and "clean up" stuff. 23:58 < wumpus> fanquake: I think MarcoFalke added the "up for grabs" tag for that 23:58 < fanquake> If GitHub search was a bit better it mightn't be such as issue. 23:59 < aj> commits that sweep through and clean up stuff are generally pretty painful though, aren't they? 23:59 < wumpus> yes, they are 23:59 < fanquake> wumpus I mean PRs that have been merged, but with outstanding todos. Rather than just abandoned. I guess they are somewhat the same. 23:59 -!- raheel_ [67ff054a@gateway/web/freenode/ip.103.255.5.74] has joined #bitcoin-core-dev 23:59 < wumpus> fanquake: if they have important TODOs that warrants an issue of its own, if not, better to forget about it sometimes