--- Log opened Sun Nov 11 00:00:18 2018 00:02 -!- bzb [~bzb@135-23-193-53.cpe.pppoe.ca] has joined #bitcoin-core-dev 00:02 -!- bzb [~bzb@135-23-193-53.cpe.pppoe.ca] has quit [Client Quit] 00:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 00:16 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 00:17 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 00:18 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 00:19 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 00:20 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds] 00:25 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 00:26 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: Connection reset by peer] 00:26 -!- owowo [~ovovo@unaffiliated/ovovo] has quit [Ping timeout: 245 seconds] 00:26 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 00:28 -!- leishman [~leishman@2604:5500:c225:c500:805:476d:d282:a7f3] has joined #bitcoin-core-dev 00:28 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: Connection reset by peer] 00:28 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 00:32 -!- leishman [~leishman@2604:5500:c225:c500:805:476d:d282:a7f3] has quit [Ping timeout: 250 seconds] 00:45 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: Connection reset by peer] 00:46 -!- deaunapaul [~recover@180.190.52.175] has quit [Remote host closed the connection] 00:46 -!- deaunapaul [~recover@180.190.52.74] has joined #bitcoin-core-dev 00:47 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 01:05 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: No route to host] 01:05 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 01:11 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 01:33 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 01:46 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: No route to host] 01:47 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 01:52 -!- rex4539 [~rex4539@ppp-2-84-165-183.home.otenet.gr] has quit [Quit: rex4539] 02:02 -!- leishman [~leishman@2604:5500:c225:c500:e51c:22cc:beff:5171] has joined #bitcoin-core-dev 02:07 -!- leishman [~leishman@2604:5500:c225:c500:e51c:22cc:beff:5171] has quit [Ping timeout: 250 seconds] 02:14 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #bitcoin-core-dev 02:14 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: No route to host] 02:15 -!- shesek` [~shesek@185.3.147.193] has joined #bitcoin-core-dev 02:20 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:34 < wumpus> luke-jr: I know you're joking but it makes me think, I don't think I've heard heard of *anything* using QtNetwork, let alone hardened P2P code 02:35 -!- timothy [~tredaelli@redhat/timothy] has joined #bitcoin-core-dev 02:35 < wumpus> phantomcircuit: I think we should still move to libevent at some point, but first things first, I suppose this refactoring will move in the right direction for that 02:37 < wumpus> the thing I'm most worried about, is the same when switching over the P2P layer to libevent: how can we test this enough to be confident enough to merge this, without running into random trouble for users or suddenly losing connectable nodes etc 02:37 -!- leishman [~leishman@2604:5500:c225:c500:44f6:2c14:55e2:bb9c] has joined #bitcoin-core-dev 02:38 < wumpus> I think the whitelisting was a good idea at least, it means we're not exposed to issues for platforms it hasn't been tested on 02:42 -!- leishman [~leishman@2604:5500:c225:c500:44f6:2c14:55e2:bb9c] has quit [Ping timeout: 250 seconds] 02:47 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 02:47 -!- deaunapaul [~recover@180.190.52.74] has quit [Remote host closed the connection] 02:47 -!- deaunapaul [~recover@180.190.52.74] has joined #bitcoin-core-dev 02:49 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev 03:09 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 252 seconds] 03:10 -!- leishman [~leishman@2604:5500:c225:c500:143a:36ba:5b62:2e1e] has joined #bitcoin-core-dev 03:14 -!- leishman [~leishman@2604:5500:c225:c500:143a:36ba:5b62:2e1e] has quit [Ping timeout: 252 seconds] 03:15 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Ping timeout: 256 seconds] 03:17 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev 03:20 -!- bitconner [~conner@203.221.127.245] has joined #bitcoin-core-dev 03:22 -!- shesek` [~shesek@185.3.147.193] has quit [Read error: Connection reset by peer] 03:23 -!- shesek [~shesek@185.3.147.193] has joined #bitcoin-core-dev 03:23 -!- shesek [~shesek@185.3.147.193] has quit [Changing host] 03:23 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 03:32 -!- mistergold [~mistergol@77.243.25.254] has joined #bitcoin-core-dev 03:33 -!- timothy [~tredaelli@redhat/timothy] has quit [Ping timeout: 272 seconds] 03:35 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has quit [Read error: Connection reset by peer] 03:36 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 03:51 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 03:52 -!- shesek [~shesek@185.3.147.193] has joined #bitcoin-core-dev 03:52 -!- shesek [~shesek@185.3.147.193] has quit [Changing host] 03:52 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:01 -!- rex4539 [~rex4539@ppp-2-84-165-183.home.otenet.gr] has joined #bitcoin-core-dev 04:02 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:02 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 04:33 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 04:49 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 04:54 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:05 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [] 05:16 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:19 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 05:21 -!- alextes [~alextes@59.5.206.21] has joined #bitcoin-core-dev 05:21 -!- alextes [~alextes@59.5.206.21] has quit [Remote host closed the connection] 05:24 -!- math_ [~mario@p4FCB3DE6.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 05:24 -!- drygol5 [~drygol@156.196.242.255] has joined #bitcoin-core-dev 05:27 -!- drygol5 [~drygol@156.196.242.255] has quit [Remote host closed the connection] 05:27 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 05:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 264 seconds] 05:31 -!- lukedashjr is now known as luke-jr 05:41 -!- rabidus [~rabidus@85-23-137-40.bb.dnainternet.fi] has quit [Ping timeout: 240 seconds] 05:43 -!- rabidus [~rabidus@85-23-137-40.bb.dnainternet.fi] has joined #bitcoin-core-dev 05:55 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 05:56 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:08 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 06:09 -!- deaunapaul [~recover@180.190.52.74] has quit [Remote host closed the connection] 06:09 -!- deaunapaul [~recover@180.190.52.175] has joined #bitcoin-core-dev 06:11 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:11 -!- shesek [~shesek@185.3.147.193] has joined #bitcoin-core-dev 06:11 -!- shesek [~shesek@185.3.147.193] has quit [Changing host] 06:11 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:14 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 06:14 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: No route to host] 06:17 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:21 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 06:23 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 06:26 -!- lukedashjr is now known as luke-jr 06:31 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 06:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds] 06:35 -!- lukedashjr is now known as luke-jr 06:42 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:43 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 06:48 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection] 07:09 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 07:12 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 07:13 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 07:13 -!- bralyclow [~bralyclow@195.242.213.119] has joined #bitcoin-core-dev 07:15 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 07:33 -!- hsmiths_ [uid95325@gateway/web/irccloud.com/x-wygouiramxtdvtgk] has joined #bitcoin-core-dev 07:43 -!- Giszmo [~leo@190.162.241.129] has joined #bitcoin-core-dev 07:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev 08:04 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 252 seconds] 08:30 -!- bitconner [~conner@203.221.127.245] has joined #bitcoin-core-dev 08:35 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 272 seconds] 08:37 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 240 seconds] 08:38 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 08:39 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev 08:43 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has quit [Ping timeout: 250 seconds] 08:45 -!- TheFuzzStone [~TheFuzzSt@194.99.105.76] has joined #bitcoin-core-dev 08:50 -!- CodeBlue1776 [~CodeBlue1@107-215-134-60.lightspeed.cicril.sbcglobal.net] has joined #bitcoin-core-dev 08:57 -!- TheFuzzStone [~TheFuzzSt@194.99.105.76] has quit [Quit: Konversation terminated!] 09:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [] 09:10 -!- deaunapaul [~recover@180.190.52.175] has quit [Ping timeout: 252 seconds] 09:11 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 09:16 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 09:21 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 272 seconds] 09:21 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 09:43 -!- deaunapaul [~recover@180.190.37.101] has joined #bitcoin-core-dev 09:43 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-pjqjbykstugzcuoh] has joined #bitcoin-core-dev 10:16 < phantomcircuit> wumpus, any opinion on setting the default maxconnections higher on systems with high limits 10:17 < phantomcircuit> the reason not to is that each connection uses memory 10:17 < phantomcircuit> (which reminds me we should have a -maxmemory flag that sets all the other ones) 10:18 < gmaxwell> because memory, and because there currently isn't a need... hosts aren't getting maxed out. 10:22 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:26 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 244 seconds] 10:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 10:48 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 10:50 < stevenroose> gettxoutsetinfo reports on the totals about the utxo set, right? (about total value, f.e.) 10:50 < stevenroose> Does that mean that provably unspent outputs (like OP_RETURN) are not included? 10:52 < sipa> exactlyu 10:52 < sipa> *exactly 10:53 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds] 10:54 < phantomcircuit> stevenroose, probably unspendable* 10:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 10:55 < sipa> phantomcircuit: no, provably 10:55 < sipa> OP_RETURN outputs cannot be spent 10:55 < sipa> ah 10:55 < sipa> you're correcting the "unspent", not the "provably" :D 10:57 < phantomcircuit> derp 10:57 < phantomcircuit> i misspelled provably 10:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 244 seconds] 10:59 < kabaum> probably unspendable = bernanke ascii art 11:03 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 11:08 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 250 seconds] 11:11 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jvygaaazflmpqviw] has joined #bitcoin-core-dev 11:11 < bitcoin-git> [bitcoin] practicalswift opened pull request #14706: Fix icc (Intel C++ compiler) warnings (master...icc) https://github.com/bitcoin/bitcoin/pull/14706 11:11 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-jvygaaazflmpqviw] has left #bitcoin-core-dev [] 11:34 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 11:44 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 272 seconds] 12:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 12:18 -!- bralyclow [~bralyclow@195.242.213.119] has quit [Ping timeout: 252 seconds] 12:21 -!- bralyclow [~bralyclow@195.242.213.119] has joined #bitcoin-core-dev 12:43 -!- bralyclow [~bralyclow@195.242.213.119] has quit [Remote host closed the connection] 12:55 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 13:00 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 246 seconds] 13:03 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 13:07 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 245 seconds] 13:14 < phantomcircuit> gmaxwell, aight i wont touch that 13:16 -!- mistergo1d [~mistergol@77.243.25.254] has joined #bitcoin-core-dev 13:19 -!- mistergold [~mistergol@77.243.25.254] has quit [Ping timeout: 245 seconds] 13:24 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 268 seconds] 13:34 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 13:39 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 244 seconds] 13:39 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 245 seconds] 13:45 -!- grafcaps [~haroldbr@047-227-079-209.res.spectrum.com] has joined #bitcoin-core-dev 13:55 -!- grafcaps [~haroldbr@047-227-079-209.res.spectrum.com] has quit [Ping timeout: 240 seconds] 14:11 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has quit [Read error: Connection reset by peer] 14:12 -!- grafcaps [~haroldbr@75.112.211.230] has joined #bitcoin-core-dev 14:16 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 252 seconds] 14:19 -!- ap4lmtree [~ap4lmtree@unaffiliated/ap4lmtree] has joined #bitcoin-core-dev 14:20 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)] 14:22 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has joined #bitcoin-core-dev 14:27 -!- Krellan [~Krellan@2601:640:4000:a876:d0e2:dc41:93ee:b128] has quit [Ping timeout: 252 seconds] 14:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:44 -!- mistergo1d [~mistergol@77.243.25.254] has quit [Read error: Connection reset by peer] 14:54 -!- nuss [5b153e4a@gateway/web/freenode/ip.91.21.62.74] has joined #bitcoin-core-dev 14:54 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 14:56 -!- nuss [5b153e4a@gateway/web/freenode/ip.91.21.62.74] has quit [Client Quit] 15:04 -!- bitconner [~conner@203.213.82.158] has joined #bitcoin-core-dev 15:05 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 15:18 -!- irc_viewer_test [irc_viewer@gateway/vpn/privateinternetaccess/ircviewertest/x-06412631] has quit [Ping timeout: 252 seconds] 15:21 -!- leishman [~leishman@50.237.29.22] has joined #bitcoin-core-dev 15:30 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 252 seconds] 15:43 -!- bitconner [~conner@220-244-36-124.static.tpgi.com.au] has joined #bitcoin-core-dev 15:59 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 244 seconds] 16:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev 16:17 -!- deaunapaul [~recover@180.190.37.101] has quit [Ping timeout: 246 seconds] 16:19 -!- deaunapaul [~recover@180.190.37.101] has joined #bitcoin-core-dev 16:25 -!- deaunapaul [~recover@180.190.37.101] has quit [Ping timeout: 268 seconds] 16:27 < gmaxwell> https://bitcoin.stackexchange.com/questions/80926/update-to-0-17-0-broke-several-rpc-api-calls-that-worked-under-0-16-3-how-to-mi 16:31 < sipa> i think one of those is a known issue 16:31 < sipa> for which a PR exists to fix it 16:31 -!- deaunapaul [~recover@180.190.37.101] has joined #bitcoin-core-dev 16:31 < meshcollider> this one #14602 ? 16:31 < gribble> https://github.com/bitcoin/bitcoin/issues/14602 | Bugfix: Correctly calculate balances when min_conf is used, and for getbalance("*") by luke-jr · Pull Request #14602 · bitcoin/bitcoin · GitHub 16:34 < meshcollider> it should probably be backported then right 16:36 -!- Krellan [~Krellan@2601:640:4000:a876:3c50:d658:d864:898] has joined #bitcoin-core-dev 16:36 < sipa> meshcollider: yes 16:37 < gmaxwell> yep, I thought I saw that one. The other one is less clear to me... "invalid amount" makes me wonder what php is doing with 0.00005. 16:37 < gmaxwell> meshcollider: yes, that a pretty serious behavior change. 16:39 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Read error: Connection reset by peer] 16:46 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 16:49 -!- Toby [0c1ca695@gateway/web/freenode/ip.12.28.166.149] has joined #bitcoin-core-dev 16:49 < Toby> Hello there. 16:49 -!- Toby is now known as Guest9346 16:49 < Guest9346> Is anybody there? 16:50 < Guest9346> How can I contribute to bitcoin development 16:54 -!- Guest9346 [0c1ca695@gateway/web/freenode/ip.12.28.166.149] has quit [Ping timeout: 256 seconds] 16:55 -!- Krellan [~Krellan@2601:640:4000:a876:3c50:d658:d864:898] has quit [Ping timeout: 276 seconds] 16:59 -!- Krellan [~Krellan@2601:640:4000:a876:3c50:d658:d864:898] has joined #bitcoin-core-dev 17:14 < meshcollider> Yeah the listunspent one is weird, I don't think theres been any changes to how it works in 0.17? And I can't replicate the issue using the command line, I suspect you're right about it being a weird PHP thing 17:44 < gmaxwell> meshcollider: a while back (not in 0.17.0) we changes from accepting .00005 to only accepting 0.00005 who knows how it stringifies that value... 18:02 -!- shesek [~shesek@unaffiliated/shesek] has joined #bitcoin-core-dev 18:13 -!- grafcaps [~haroldbr@75.112.211.230] has joined #bitcoin-core-dev 18:17 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 252 seconds] 18:17 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-core-dev 18:20 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-evxuyeyqokcjnwie] has joined #bitcoin-core-dev 18:20 < bitcoin-git> [bitcoin] andrewtoth opened pull request #14707: [RPC] Add include_coinbase option to receiveby RPCs (master...receivedby-coinbase) https://github.com/bitcoin/bitcoin/pull/14707 18:20 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-evxuyeyqokcjnwie] has left #bitcoin-core-dev [] 18:23 -!- ken2812221 [~ken281222@110.50.135.219] has quit [Ping timeout: 272 seconds] 19:13 -!- bitconner [~conner@220-244-36-124.static.tpgi.com.au] has quit [Ping timeout: 272 seconds] 19:14 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev 19:16 < phantomcircuit> gmaxwell, almost certainly bad things 19:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 245 seconds] 19:18 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds] 19:20 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev 19:24 -!- Aaronvan_ [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 244 seconds] 19:29 -!- _cryptosignal_me [~John@91.245.74.93] has joined #bitcoin-core-dev 19:35 -!- leishman [~leishman@50.237.29.22] has quit [Remote host closed the connection] 19:36 -!- leishman [~leishman@50.237.29.22] has joined #bitcoin-core-dev 19:40 -!- leishman [~leishman@50.237.29.22] has quit [Ping timeout: 252 seconds] 19:53 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has quit [Ping timeout: 244 seconds] 19:59 -!- sanket1729 [62d49a0a@gateway/web/freenode/ip.98.212.154.10] has joined #bitcoin-core-dev 20:03 -!- _cryptosignal_me [~John@91.245.74.93] has quit [Ping timeout: 252 seconds] 20:04 < sanket1729> What do you think about the following? Prior to RBF, nodes discarded all the transactions after the first transaction thereby guarding CPU validation resources by not validating other transactions. After RBF, nodes need to validate all subsequent transactions with higher sequence number if they pay higher fee. 20:04 < sanket1729> In peak fees times, fees have been around 1000sat/byte(Jan 2018) whereas rbf only requires fees be more than minTxRelay fees(currently 1say/byte in bitcoin core) than the previous transaction. An attacker could start with 1 sat/byte fees and send 1000 RBF transactions with increasing fees 1sat/byte, 2 .... and so on. Thereby wasting node CPU validation resources 1000 times. This is not a big problem since fees are around 20:04 < sanket1729> Or maybe this is the expected behavior? 20:06 < gmaxwell> sanket1729: they could do the same thing without replacement at all, simply by chaining low fee transactions. 20:07 < gmaxwell> the whole design of the RBF rules was to limit resource expendature to be approximately equal to the worst case you could achieve without using replacement. 20:08 < sanket1729> Yes, but I read somewhere that mempool increases the minimum fees to tx to enter into mempool incase there is spam. But this is not spam since we are replacing things from mempool. So, it is kindof different 20:10 < sanket1729> From pwuille from bitcoin stackexchange: Nodes on the network maintain unconfirmed transactions in their mempool, and when the mempool grows too big, they will raise the minimum fee necessary to enter the mempool 20:10 < gmaxwell> sanket1729: the minimum relay fee goes up when your nodes local mempool is full (e.g. 300MB of txdata), that value has never gone much over 10s/b IIRC FWIW. 20:12 < phantomcircuit> gmaxwell, isn't the replacement increase also based on the mempool inclusion? 20:15 < gmaxwell> phantomcircuit: yes well kinda. The replcement must meet the new minimum and must be greater than the replaced by the incremental feerate. They used to be one in the same, but I believe they were split because it made predicting the incremental minimum too hard. 20:15 < esotericnonsense> gmaxwell: isn't it the case that without replacement there's a limit to chaining 20:15 < esotericnonsense> (it could well be the case that the limit is newer than RBF) 20:16 < gmaxwell> esotericnonsense: kinda. but if you fan out pessimally (to hit the worst case) it's enormous, so not a praticial limit on your ability to make many transactions. 20:17 < gmaxwell> that limit is just there to avoid computational blow up in things like CPFP. 20:17 < sipa> the incremental feerate for replacement doesn't go up when the mempool gets full 20:17 < sipa> only the minimum relay feerate 20:17 < sipa> sanket1729: hi, pieter here 20:18 < esotericnonsense> ah yes i suppose that's right. 20:18 < esotericnonsense> hadn't thought about fanning. lol. 20:18 < gmaxwell> sipa: which is technically a violation of BIP125. 20:19 < esotericnonsense> anyway I pasted this just now in -forks but thought someone here might care as it's core dev. 20:19 < esotericnonsense> https://bitcoin.electronrelocation.com/ force refresh if you've seen it before cos I have some issues with caching. 20:19 < esotericnonsense> prettified. i have receiving working but not sending cause I sit and think properly about authentication. 20:19 < esotericnonsense> I need to* 20:20 < esotericnonsense> (i have no bloody idea why my port forwarding has stopped working and need to investigate). 20:21 < gmaxwell> (that was changed in PR#9615 FWIW, though it doesn't really make much difference in any case) 20:21 < gribble> https://github.com/bitcoin/bitcoin/issues/9615 | Wallet incremental fee by morcos · Pull Request #9615 · bitcoin/bitcoin · GitHub 20:23 < gmaxwell> esotericnonsense: nice! (your link) 20:23 < esotericnonsense> gmaxwell: thank you :) 20:24 < gmaxwell> esotericnonsense: block template view could show some stats like total weight, and total fees + subsidy. 20:24 < esotericnonsense> yeah. i think it can actually be the same as the mempool table or roughly the same anyway 20:26 < gmaxwell> esotericnonsense: on the peers table, take care to avoid displaying the random port number on one side of the connection (looks like you don't right now), it's basically of zero use but knowing it makes TCP RST attacks much easier. 20:27 < gmaxwell> esotericnonsense: chaintips might be an interesting thing to show. and maybe some limited 'block explorer' like stuff. 20:27 < esotericnonsense> i think everything that's in bitcoind-ncurses can go in there 20:29 < esotericnonsense> it's not that simple to reason about not DoSing my own node though on the public version, if it were auth gated it would be a lot easier :p 20:29 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has joined #bitcoin-core-dev 20:29 < esotericnonsense> e.g. caching responses works if you have a limited subset of responses, if someone can arbitrarily query a txid I need to actually think about things :P 20:31 < gmaxwell> well you could just apply some rate limiter, perhaps with some per-IP bucketing so a DOSer doesn't block all webaccess. 20:31 < esotericnonsense> yeah, it just has to be thought about per query I think because it simplifies the design to not care about rate limiting in the general case (e.g. only certain paths are vulnerable) 20:32 < esotericnonsense> (I mean, _really_ rate limiting like 1-5/s as opposed to 'no-one needs to hit me at 100/s go away' 20:33 < esotericnonsense> i think i'm going to build it in to the whitelist on the backend 20:34 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has quit [Ping timeout: 244 seconds] 20:39 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection] 20:44 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev 20:56 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-rvlhnsrxiwimmkpw] has joined #bitcoin-core-dev 20:56 < bitcoin-git> [bitcoin] kallewoof closed pull request #12508: IsAllFromMe (master...feature-isallfromme) https://github.com/bitcoin/bitcoin/pull/12508 20:56 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-rvlhnsrxiwimmkpw] has left #bitcoin-core-dev [] 20:58 -!- Giszmo [~leo@190.162.241.129] has quit [Ping timeout: 246 seconds] 21:21 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 21:24 -!- Giszmo [~leo@ip-213-236-219-201.nextelmovil.cl] has joined #bitcoin-core-dev 21:25 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Ping timeout: 246 seconds] 21:28 -!- atomicthumbs_ [~atomicthu@179.34.162.22] has joined #bitcoin-core-dev 21:28 -!- atomicthumbs_ [~atomicthu@179.34.162.22] has quit [Remote host closed the connection] 21:29 -!- instagibbs [~instagibb@pool-100-15-135-248.washdc.fios.verizon.net] has joined #bitcoin-core-dev 21:47 -!- bitconner [~conner@175.45.73.99] has joined #bitcoin-core-dev 21:49 -!- Giszmo [~leo@ip-213-236-219-201.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 21:51 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 22:00 -!- spinza [~spin@155.93.246.187] has joined #bitcoin-core-dev 22:08 -!- Giszmo [~leo@190.162.241.129] has joined #bitcoin-core-dev 22:12 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection] 22:13 -!- tryphe_ [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev 22:14 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-core-dev 22:18 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection] 22:19 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev 22:19 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-dasblpcyoopneprl] has joined #bitcoin-core-dev 22:19 < bitcoin-git> [bitcoin] AkioNak opened pull request #14708: Warn unrecognised sections in the config file (master...warn_unrecognized_section) https://github.com/bitcoin/bitcoin/pull/14708 22:19 -!- bitcoin-git [bitcoin-gi@gateway/service/github.com/x-dasblpcyoopneprl] has left #bitcoin-core-dev [] 22:23 -!- murrayn [~murrayn@unaffiliated/murrayn] has quit [Ping timeout: 268 seconds] 22:24 -!- bitconner [~conner@175.45.73.99] has quit [Ping timeout: 264 seconds] 22:24 -!- bitconner [~conner@175.45.73.99] has joined #bitcoin-core-dev 22:29 -!- bitconner [~conner@175.45.73.99] has quit [Ping timeout: 252 seconds] 22:29 -!- Ga1aCt1Cz00__ [~Ga1aCt1Cz@p2003005F6E1F7C11B84A57F2B4346D02.dip0.t-ipconnect.de] has joined #bitcoin-core-dev 22:32 -!- Ga1aCt1Cz00_ [~Ga1aCt1Cz@p2003005F6E1F7C83346384DDAD6DBAF5.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds] 22:34 -!- martinus [53a499e2@gateway/web/freenode/ip.83.164.153.226] has joined #bitcoin-core-dev 22:35 -!- martinus [53a499e2@gateway/web/freenode/ip.83.164.153.226] has quit [Client Quit] 23:01 -!- grafcaps [~haroldbr@75.112.211.230] has joined #bitcoin-core-dev 23:01 -!- a5m0_ [~a5m0@unaffiliated/a5m0] has quit [Remote host closed the connection] 23:07 -!- a5m0 [~a5m0@unaffiliated/a5m0] has joined #bitcoin-core-dev 23:08 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 240 seconds] 23:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 23:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #bitcoin-core-dev 23:22 -!- deaunapaul [~recover@180.190.37.101] has quit [Remote host closed the connection] 23:22 -!- deaunapaul [~recover@180.190.37.26] has joined #bitcoin-core-dev 23:57 -!- kalle [~kalle@2a00:801:e0:30:8987:49c1:c531:fb11] has quit [Quit: Leaving] --- Log closed Mon Nov 12 00:00:18 2018