--- Day changed Sat Feb 18 2017
00:01 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has joined #bitcoin-core-dev     
00:03 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nbjlguyfbhosukos] has joined #bitcoin-core-dev     
00:04 -!- Kexkey [~kexkey@23.227.207.22] has quit [Ping timeout: 255 seconds]     
00:05 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has quit [Ping timeout: 255 seconds]     
00:13 -!- goksinen [~goksinen@2604:2000:c591:8400:9d10:d1e1:fc88:8a61] has joined #bitcoin-core-dev     
00:14 -!- goksinen [~goksinen@2604:2000:c591:8400:9d10:d1e1:fc88:8a61] has quit [Remote host closed the connection]     
00:16 -!- goksinen [~goksinen@2604:2000:c591:8400:b493:810e:1fb2:205e] has joined #bitcoin-core-dev     
00:23 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev     
00:26 -!- goksinen [~goksinen@2604:2000:c591:8400:b493:810e:1fb2:205e] has quit [Remote host closed the connection]     
00:27 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 255 seconds]     
00:55 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has joined #bitcoin-core-dev     
00:59 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has quit [Ping timeout: 240 seconds]     
01:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]     
01:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev     
01:22 < wumpus> luke-jr: I fixed that assertion problem recently
01:22 < luke-jr> ?     
01:22 < luke-jr> oh     
01:23 < wumpus> https://github.com/bitcoin/bitcoin/pull/9735
01:24 < luke-jr> thanks
01:26 < wumpus> apparently my for gitian output for linux mismatches
01:26 < wumpus> windows matches, and osx too (except for achow101)
01:30 < wumpus> linux: looks like only the x86_64 output mismatches - aarch64, arm, i686 are the same
01:32 < wumpus> cfields: your gitian assert package overview has "Reading package lists..." ""Building dependency tree..." apt command output in it
01:34 < wumpus> my assert has *three* versions of g++-4.8 in it:g++-4.8_4.8.2-19ubuntu1_amd64.deb, g++-4.8_4.8.4-2ubuntu1~14.04.1_amd64.deb, g++-4.8_4.8.4-2ubuntu1~14.04.3_amd64.deb  ... that seems overkill
01:35 < wumpus> that almost must be the problem, will try to clean it up
01:35 < wumpus> the base image that is, not the assert file :)
01:40 -!- myyao_ [~myyao@219.135.155.120] has joined #bitcoin-core-dev     
01:40 -!- myyao__ [~myyao@219.135.155.120] has quit [Ping timeout: 240 seconds]     
01:49 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has joined #bitcoin-core-dev     
01:53 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has quit [Ping timeout: 240 seconds]     
02:17 -!- MarcoFalke [~marco@host10-2.natpool.mwn.de] has joined #bitcoin-core-dev     
02:32 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/50a226563cd8...8efd1c820b9a
02:32 < bitcoin-git> bitcoin/master a432aa0 Takashi Mitsuta: Remove unused module from rpc-tests
02:32 < bitcoin-git> bitcoin/master 8efd1c8 MarcoFalke: Merge #9744: Remove unused module from rpc-tests...
02:32 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #9744: Remove unused module from rpc-tests (master...remove-unused-modules-from-rpc-tests) https://github.com/bitcoin/bitcoin/pull/9744
02:43 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has joined #bitcoin-core-dev     
02:47 -!- goksinen [~goksinen@2604:2000:c591:8400:55fd:582a:f3f3:a276] has quit [Ping timeout: 240 seconds]     
02:55 -!- cannon-c [ccc23f04@gateway/web/freenode/ip.204.194.63.4] has quit [Quit: Page closed]     
03:00 < bitcoin-git> [bitcoin] MarcoFalke opened pull request #9795: doc: Update manpages for master (laanwj) (master...Mf1602-docManMaster) https://github.com/bitcoin/bitcoin/pull/9795
03:06 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev     
03:14 < bitcoin-git> [bitcoin] MarcoFalke pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/8efd1c820b9a...aa5fa642b0e7
03:14 < bitcoin-git> bitcoin/master 0c9b9b7 practicalswift: [trivial] Fix recently introduced typos in comments
03:14 < bitcoin-git> bitcoin/master aa5fa64 MarcoFalke: Merge #9696: [trivial] Fix recently introduced typos in comments...
03:14 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #9696: [trivial] Fix recently introduced typos in comments (master...fix-recently-introduced-typos) https://github.com/bitcoin/bitcoin/pull/9696
03:19 -!- str4d [~str4d@host-78-145-29-21.as13285.net] has joined #bitcoin-core-dev     
03:36 -!- goksinen [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has joined #bitcoin-core-dev     
03:40 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Quit: Leaving]     
03:40 -!- goksinen [~goksinen@cpe-74-71-4-175.nyc.res.rr.com] has quit [Ping timeout: 240 seconds]     
04:29 -!- myyao_ [~myyao@219.135.155.120] has quit [Quit: Leaving]     
04:42 -!- norotartagen [~norotarta@71-89-76-184.dhcp.bycy.mi.charter.com] has quit [Remote host closed the connection]     
04:44 -!- norotartagen [~norotarta@71-89-76-184.dhcp.bycy.mi.charter.com] has joined #bitcoin-core-dev     
05:09 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has joined #bitcoin-core-dev     
05:09 < wumpus> ok, above gitian issue was solved by rebuildling with a new base image
05:42 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 240 seconds]     
05:50 -!- Arvidt [~Arvidt@p5B2AB21C.dip0.t-ipconnect.de] has quit [Quit: leaving]     
06:06 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev     
06:30 < bitcoin-git> [bitcoin] MarcoFalke pushed 6 new commits to master: https://github.com/bitcoin/bitcoin/compare/aa5fa642b0e7...7ff4a538a868
06:30 < bitcoin-git> bitcoin/master 1581ecb John Newbery: Use configparser in rpc-tests.py...
06:30 < bitcoin-git> bitcoin/master 91bffff John Newbery: Use argparse in rpc_tests.py...
06:30 < bitcoin-git> bitcoin/master afd38e7 John Newbery: Improve rpc-tests.py arguments...
06:30 < bitcoin-git> [bitcoin] MarcoFalke closed pull request #9657: Improve rpc-tests.py (master...improvepytests2) https://github.com/bitcoin/bitcoin/pull/9657
06:51 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev     
06:54 < cfields> wumpus: so your sigs match mine now?
06:54 < achow101> I'm going to be away from my build computer today so I won't be able to help
06:56 < cfields> ok     
06:56 < cfields> i guess if we have 3 matches we can go with that one, but we really need to figure out why we're getting 2 different results
06:57 < achow101> I tried remaking the base vm and rebuilding before I left but I was having issues with making it
06:59 < cfields> achow101: thanks for trying
07:02 < cfields> wumpus: please confirm if you'd like me to go ahead and push the sigs for the one we've got. the fact that achow101 and fanquake have matching mismatches for osx is a bit worrisome
07:13 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
07:13 -!- Giszmo [~leo@pc-240-13-215-201.cm.vtr.net] has quit [Quit: Leaving.]     
07:13 -!- Giszmo1 [~leo@pc-240-13-215-201.cm.vtr.net] has joined #bitcoin-core-dev     
07:13 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]     
07:22 -!- goksinen [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev     
07:28 < MarcoFalke> "matching mismatches", heh.
07:28 < MarcoFalke> going to run the osx gitian, lets see what my result is...
07:31 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev     
07:32 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
07:35 -!- lclc [~lclc@unaffiliated/lclc] has quit [Ping timeout: 255 seconds]     
07:35 -!- moli_ [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds]     
08:06 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 268 seconds]     
08:19 -!- Arvidt [~Arvidt@p5B2AB21C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev     
08:37 -!- lclc [~lclc@unaffiliated/lclc] has joined #bitcoin-core-dev     
08:39 -!- jtimon [~quassel@245.30.134.37.dynamic.jazztel.es] has joined #bitcoin-core-dev     
08:40 < cfields> ok, i'm going to go ahead and push
08:41 < cfields> we need to try to figure out what the discrepancy is before rc2, though
08:57 -!- str4d [~str4d@host-78-145-29-21.as13285.net] has quit [Ping timeout: 240 seconds]     
08:59 < cfields> gitian builders: detached osx/win sigs for 0.14.0rc1 pushed.
09:00 < cfields> achow101 / fanquake: not sure what to tell you yet, i'll keep trying to get it pinned down
09:29 < wumpus> cfields: yes, let's try to continue. It's strange that macosx apparently isn't determinstic, but that's no reason to not go on with the other platforms for rc1
09:29 < wumpus> would be nice to sort this out before final, of course
10:07 -!- bsm117532 [~mcelrath@135.84.167.210] has joined #bitcoin-core-dev     
10:12 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev     
10:35 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #bitcoin-core-dev     
10:37 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds]     
10:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds]     
11:18 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
12:08 -!- moli_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection]     
12:08 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
13:03 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #bitcoin-core-dev     
13:03 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]     
13:35 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has quit [Remote host closed the connection]     
13:35 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has joined #bitcoin-core-dev     
13:49 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has quit [Disconnected by services]     
13:50 < luke-jr> [13:09:35] <wumpus> ok, above gitian issue was solved by rebuildling with a new base image <-- eh, not sure this is a good resolution :|
13:50 -!- shesek [~shesek@bzq-84-110-60-48.red.bezeqint.net] has joined #bitcoin-core-dev     
13:51 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has joined #bitcoin-core-dev     
13:59 -!- goksinen [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Remote host closed the connection]     
13:59 -!- JackH [~laptop@79-73-188-131.dynamic.dsl.as9105.com] has joined #bitcoin-core-dev     
14:00 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev     
14:01 -!- goksinen [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has joined #bitcoin-core-dev     
14:05 -!- goksinen [~goksinen@rrcs-50-75-193-138.nyc.biz.rr.com] has quit [Ping timeout: 240 seconds]     
15:02 < luke-jr> thoughts on a GUI screen showing what #bitcoin-watch used to? https://en.bitcoin.it/wiki/Bitcoin-Watch
15:03 < luke-jr> (minus the trade info I guess)
15:42 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]     
15:53 -!- goksinen [~goksinen@2604:2000:c591:8400:2d4b:14ad:5a1a:4358] has joined #bitcoin-core-dev     
15:54 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 240 seconds]     
16:02 -!- isle2983 [~isle2983@gateway/vpn/privateinternetaccess/isle2983] has quit [Ping timeout: 240 seconds]     
16:04 -!- isle2983 [~isle2983@162.216.46.109] has joined #bitcoin-core-dev     
16:07 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #bitcoin-core-dev     
16:12 -!- isle2983 [~isle2983@162.216.46.109] has quit [Ping timeout: 260 seconds]     
16:23 -!- goksinen [~goksinen@2604:2000:c591:8400:2d4b:14ad:5a1a:4358] has quit [Remote host closed the connection]     
16:45 -!- handlex [~handlex@2804:14c:658f:4dc7:c8b2:52f4:9796:36d6] has joined #bitcoin-core-dev     
16:49 -!- handlex [~handlex@2804:14c:658f:4dc7:c8b2:52f4:9796:36d6] has quit [Client Quit]     
17:01 -!- aburan_ [~root@2602:304:ce71:a8f0:95c7:dcb1:104f:7b53] has quit [Ping timeout: 240 seconds]     
17:02 -!- Arvidt [~Arvidt@p5B2AB21C.dip0.t-ipconnect.de] has quit [Quit: leaving]     
17:08 -!- aburan_ [~root@2602:304:ce71:a8f0:95c7:dcb1:104f:7b53] has joined #bitcoin-core-dev     
17:08 -!- Arvidt [~Arvidt@p5B2AB21C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev     
17:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]     
18:00 -!- aburan_ [~root@2602:304:ce71:a8f0:95c7:dcb1:104f:7b53] has quit [Remote host closed the connection]     
18:15 < bitcoin-git> [bitcoin] fanquake closed pull request #8660: txoutsbyaddress index (take 2) (master...cozz8) https://github.com/bitcoin/bitcoin/pull/8660
18:17 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection]     
18:18 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev     
18:32 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev     
18:33 < fanquake> cfields pushed my signed sigs up. Can try help debug gitian issues during today.
18:33 < fanquake> Also noticed that zlib doesn't currently build with osx depends builder
18:34 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nbjlguyfbhosukos] has quit [Quit: Connection closed for inactivity]     
18:45 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Ping timeout: 255 seconds]     
19:02 < luke-jr> re "About Qt": we're using "About %1" now anyway, so the translation issue is presumably gone, and Qt might actually be worth promoting anyway; thinking perhaps what would be an improvement there is to add an "About Bitcoin" :p
19:10 < gmaxwell> luke-jr: It might be better to put the QT link though on the about bitcoin core page though.
19:10 < gmaxwell> the about qt thing is really uninteresting.
19:10 < luke-jr> hmm     
19:10 < luke-jr> so the menu would have About Bitcoin Core and About Bitcoin; and the former's dialog have a link for About Qt?
19:13 < gmaxwell> I think that would be dandy. I dunno what about Bitcoin would say.
19:14 < gmaxwell> I think all this is kind of pointless, user use of bitcoin is dying because of sync resource requirements.
19:16 < luke-jr> true, better things to spend time on esp since the translation issue is basically fixed
19:22 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 260 seconds]     
19:24 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev     
19:25 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit [Client Quit]     
19:31 < gmaxwell> I'd be happy to ack a patch to improve the about messages but I think it's a waste of time to work on that.
19:37 -!- moli_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection]     
19:37 -!- chjj [~chjj@unaffiliated/chjj] has joined #bitcoin-core-dev     
19:37 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
19:39 -!- moli_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection]     
19:39 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
19:51 -!- Giszmo1 [~leo@pc-240-13-215-201.cm.vtr.net] has quit [Quit: Leaving.]     
20:23 -!- JackH [~laptop@79-73-188-131.dynamic.dsl.as9105.com] has quit [Ping timeout: 240 seconds]     
20:24 -!- moli_ [~molly@unaffiliated/molly] has quit [Remote host closed the connection]     
20:33 -!- chris2000 [~chris2000@p5082A630.dip0.t-ipconnect.de] has joined #bitcoin-core-dev     
20:35 -!- IRCFrEAK [~gk.1wm.su@2a03:4a80:2:2d3:2d3:9c14:a427:77be] has joined #bitcoin-core-dev     
20:36 -!- chris200_ [~chris2000@p5DCB5C30.dip0.t-ipconnect.de] has quit [Ping timeout: 240 seconds]     
20:37 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev     
20:41 -!- IRCFrEAK [~gk.1wm.su@2a03:4a80:2:2d3:2d3:9c14:a427:77be] has left #bitcoin-core-dev []     
20:41 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds]     
20:48 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 240 seconds]     
20:50 < BlueMatt> <conman> do you understand the whitelist v addnode thing btw?
20:50 < BlueMatt> <conman> if I whitelist an IP address and addnode it, when I see it listed in the debug window it has the addnode'd IP there as not whitelisted
20:51 < gmaxwell> ugh, whitelist is not something conman should want for pratically anything. Addnode (in 0.14 at least) prevents banning, whitelisting adds to that near blindly and redundantly relaying transactions, which is not desirable for him, unless he's now become an armory developer. :P
20:52 < BlueMatt> yes, i figured, but also it is a strange thing that it doesnt whitelist for outbound
20:55 -!- fengling [~fengling@223.223.187.142] has quit [Ping timeout: 252 seconds]     
20:55 -!- xiangfu_ [~xiangfu@223.223.187.142] has quit [Ping timeout: 245 seconds]     
21:00 < BlueMatt> hum, yea, looks like addnode will only consider itself "connected" if IP:Port matches, not just IP, so if you, eg, addnode bidirectionally you're guaranteed to have two connections (unless the source uses 8333 for source port, which it wont)
21:00 < BlueMatt> afaict
21:01 < gmaxwell> yea, bidi results in two connections, I think I had believed there was no strong way to avoid it-- in any case, it's always been true.
21:02 < BlueMatt> i mean why do we only consider an addnode connected if its the same port?
21:02 < BlueMatt> might as well just filter by ip?
21:02 < gmaxwell> now I'm not sure why I was thinking it was hard to avoid. maybe just that being connected to the same IP is not the same as connecting to that IP due to the existance of NATs.
21:02 < BlueMatt> indeed, though if you addnode its probably fine
21:02 < gmaxwell> E.g. if you addnode my office, but have some random laptop at my office connected to you, you have not achieved your goal.
21:03 < gmaxwell> but perhaps it's close enough that the default should be to avoid the duplicate connection...
21:03 < BlueMatt> yes, that would be my vote
21:03 < gmaxwell> the other thing is that the addnode connection is privledged in ways that the inbound isn't. 
21:04 < BlueMatt> true, but if the connection gets killed it'll re-open
21:04 < BlueMatt> possibly as -addnode
21:04 < BlueMatt> and we can do the same set-host-on-lookup thing we do for other connections and set the addnode flag if we find an applicable inbound connection
21:06 < gmaxwell> well as I said, inbound != addnode.  This would be much better with authentication keys, since you would know if it was who you thought it was.
21:07 < BlueMatt> yup, that
21:09 < gmaxwell> We could have some other kind of cookie based dedupe that worked more robustly.
21:09 < BlueMatt> true, though im no fan of encouraging more places where you can tie two nodes together as the same one
21:09 < BlueMatt> i know we have a few places with that and just added more, buttttt
21:11 < gmaxwell> well kinda hopeless, we should set a bar that we'd like to meet there. Like you shouldn't be able to correlate tor/ipv4+ipv6 as much as we can but otherwise we don't care. And especially shouldn't be able to correlate across restarts as much as we can.
21:11 < gmaxwell> the current informal method is not working well.
21:11 < BlueMatt> true
21:12 < gmaxwell> BlueMatt: and yea, we just added a _smoking hot_ identifier... so kinda moot. without a good framework we're just going to keep undermining ourselves while also missing good functionality.
21:12 < BlueMatt> i mean where all do we have that? double spend-based net splitting, compact blocks, addr stuff, what else?
21:12 < BlueMatt> i mean the compact block one is easy to split-by-netgroup
21:13 < gmaxwell> well lets ask the question, would we want to 'logically' behave like we had two mempools for ipv4 vs tor,  or just give up and say that the strongest property we try to achieve is unlinkablity across restarts?
21:13 < gmaxwell> Because thats the first choice there, if we're unwilling to do that then the best I think we can do is unlinkability across restarts.
21:13 < BlueMatt> heh, +/- saving mempool on disk :p
21:13 < gmaxwell> yea, well peers.dat is the big limitation on restarts right now, in fact. much more than mempool.
21:14 < BlueMatt> yea, ok
21:15 < BlueMatt> yea, its a shame keeping multiple peers.dat per-netgroup would kinda defeat the purpose of peers.dat :/
21:15 < gmaxwell> One of the open questions about mempool sync is do we want to make mempools convergent ... e.g. that you would switch to doublespends under some criteria.  Without that, I think our worst case synchronization bandwidth will always be quadratic.
21:16 < BlueMatt> yea, good question...i mean we could do some kind of lowest-hash metric, but that seems to amount to a not-by-fee-rbf
21:16 < BlueMatt> which also sucks, though i suppose the bw usage could be mitigated
21:16 < gmaxwell> BlueMatt: well the sorting criteria can be {fee,hash} which is basically what I menat by convergent.
21:17 < BlueMatt> yes, i assumed that
21:17 < gmaxwell> (or in particular, fee,H(salt,hash)  where salt is a random beacon to avoid being able to grind preferable txn.)
21:17 -!- moli_ [~molly@unaffiliated/molly] has joined #bitcoin-core-dev     
21:17 < gmaxwell> and the fact that it's non-fee based replacement is actually not harmful... so long as the sync process rate limits itself.
21:18 < BlueMatt> random how? wouldnt it have to be network-wide? which would mean grindable
21:18 < BlueMatt> yesyes, generally agreed there
21:18 < gmaxwell> I think I can show that the bandwidth of that is polylog.
21:18 < gmaxwell> BlueMatt: e.g. using block hashes, so it would be network wide but your grindablity would be a finite window. 
21:19 < BlueMatt> heh, well you only need to grind a lower hash...that shouldnt take you 10 minutes
21:20 < BlueMatt> anyway, just means an attacker can always create infinite amount of mempool divergence in a single tx, though they'd have to spend fee to actually put it in a higher-sync-rate-bucket
21:20 -!- fengling [~fengling@223.223.187.142] has joined #bitcoin-core-dev     
21:23 -!- xiangfu [~xiangfu@223.223.187.142] has joined #bitcoin-core-dev     
21:31 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev     
21:35 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has quit [Ping timeout: 240 seconds]     
21:35 < BlueMatt> lol, recaptcha wasnt working so i tried the "audio version" and it just said "we're sorry, your computer may be sending automated queries, so we cannot process your request"
21:35 < BlueMatt> fuckers
21:36 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds]     
21:39 < gmaxwell> better than the google search captcha that just sends you really hard captchas and doesn't let you through no matter what.
21:39 < BlueMatt> thats what it was doing for the non-audio form, though
21:39 < BlueMatt> it just kept saying "try again"
21:40 < gmaxwell> yea, I think google does that intentionally on search... so perhaps they also do on recaptcha.
21:41 < BlueMatt> yea, likely, except they give it away if you try to switch to audio
21:42 < gmaxwell> Same shadowbanning BS that reddit does, so profoundly anti-social. The hope is to make spammers waste their time/money, and it ignores the people they harm when there is a false positive.
21:42 < BlueMatt> hum, im thinking its just straight up broken, doesnt work on a different browser/ip either
22:01 -!- asoltys [~adam@115.96.198.104.bc.googleusercontent.com] has joined #bitcoin-core-dev     
22:19 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has quit [Remote host closed the connection]     
22:20 -!- d9b4bef9 [~d9b4bef9@web419.webfaction.com] has joined #bitcoin-core-dev     
22:20 -!- harrymm [~wayne@104.207.83.19] has joined #bitcoin-core-dev     
22:26 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev     
22:27 -!- aalex [~aalex@64.187.177.58] has joined #bitcoin-core-dev     
22:30 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds]     
22:34 -!- aalex [~aalex@64.187.177.58] has quit [Ping timeout: 268 seconds]     
22:39 < achow101> cfields: I fixed the osx build. I finally fixed the fucking osx build. All I had to do was make a new base vm. it only took me the better part of the last 3-4 hours to figure out that vmbuilder has a bug and that I had a zombie vm screwing things up
22:53 -!- jtimon [~quassel@245.30.134.37.dynamic.jazztel.es] has quit [Ping timeout: 268 seconds]     
22:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 240 seconds]     
23:20 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has joined #bitcoin-core-dev     
23:24 -!- goksinen [~goksinen@2604:2000:c591:8400:8d3e:9aa9:1628:cfc6] has quit [Ping timeout: 240 seconds]