--- Log opened Thu Sep 20 00:00:14 2018
00:03 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev
00:15 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 240 seconds]
00:20 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev
00:25 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 272 seconds]
00:30 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev
00:37 -!- jungly [~quassel@79.8.200.97] has joined #bitcoin-core-dev
00:39 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-uybxshavvfqpwrdn] has joined #bitcoin-core-dev
00:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
00:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
01:00 -!- setpill [~setpill@unaffiliated/setpill] has joined #bitcoin-core-dev
01:26 -!- timothy [tredaelli@redhat/timothy] has joined #bitcoin-core-dev
01:37 -!- wpaulino [~wpaulino@unaffiliated/wpaulino] has joined #bitcoin-core-dev
01:38 -!- fanquake [~fanquake@unaffiliated/fanquake] has joined #bitcoin-core-dev
01:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
01:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
01:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
01:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
01:46 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
02:02 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has joined #bitcoin-core-dev
02:08 -!- adam3us [~adam3us@unaffiliated/adam3us] has quit [Ping timeout: 268 seconds]
02:08 -!- Lightsword [~Lightswor@2604:a880:1:20::1d3:9001] has quit [Quit: ZNC]
02:09 -!- adam3us [~adam3us@unaffiliated/adam3us] has joined #bitcoin-core-dev
02:09 -!- Lightsword [~Lightswor@2604:a880:1:20::1d3:9001] has joined #bitcoin-core-dev
02:12 -!- treebeardd [~treebeard@2601:19b:c601:7cf4:199:6910:e3ab:8e37] has joined #bitcoin-core-dev
02:40 -!- csknk [~csknk@unaffiliated/csknk] has joined #bitcoin-core-dev
02:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
02:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
02:47 -!- ott0disk [~smuxi@cd.85.7a9f.ip4.static.sl-reverse.com] has joined #bitcoin-core-dev
03:14 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
03:18 -!- emzy [~quassel@unaffiliated/emzy] has joined #bitcoin-core-dev
03:18 -!- treebeardd [~treebeard@2601:19b:c601:7cf4:199:6910:e3ab:8e37] has quit [Remote host closed the connection]
03:33 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 244 seconds]
03:35 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
03:36 -!- csknk [~csknk@unaffiliated/csknk] has quit [Quit: leaving]
03:37 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection]
03:38 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
03:44 -!- Arvidt [~Arvidt@p5DE6A8A7.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
03:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
03:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
03:46 -!- phantomcircuit [~phantomci@192.241.205.97] has quit [Ping timeout: 244 seconds]
03:47 < Arvidt> Is it on purpose, that the SHA256SUMs file in https://bitcoincore.org/bin/bitcoin-core-0.17.0/test.rc4/ is now named SHA256SUMS instead of SHA256SUMS.asc like it used to be named in the past? Because I have a download script and that looks for the file SHA256SUMS.asc to verfiy the download and the script does fail now because of missing signature file.
03:47 < wumpus> without libc you cannot expect any binaries for linux to work, I doubt something like flatpak or appimage would help
03:47 < wumpus> Arvidt: uhm, no, that's not on purpose, looks like I didn't upload the signed asc
03:47 < wumpus> Arvidt: thanks for the reminder
03:52 < Arvidt> wumpus: OK maybe there is missing a release algorithm documentation to be able to cleanly reproduce/make a release, to prevent something is forgotten/mistaken like in this case?
03:53 -!- phantomcircuit [~phantomci@192.241.205.97] has joined #bitcoin-core-dev
03:54 < wumpus> Arvidt: should be fixed now
03:58 < Arvidt> In the file there are signatures for bitcoin-0.10.4rc1 !
04:04 -!- treebeardd [~treebeard@23-30-129-3-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
04:04 < wumpus> right. now it has the correct ones.
04:10 < provoostenator> cfields: will sign as soon as I remember what the "please run gbuild --upgrade" error was about again...
04:15 -!- ott0disk [~smuxi@cd.85.7a9f.ip4.static.sl-reverse.com] has quit [Ping timeout: 245 seconds]
04:18 < Arvidt> wumpus: Issue is fixed now, download could be verified as usual.
04:21 -!- Arvidt [~Arvidt@p5DE6A8A7.dip0.t-ipconnect.de] has quit [Quit: leaving]
04:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
04:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
04:49 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has quit [Remote host closed the connection]
04:50 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has joined #bitcoin-core-dev
04:50 < fanquake> If anyone is interested, I've posted a simple guide to using gitian-builder directly on macOS: https://github.com/fanquake/core-review/tree/master/gitian-building
04:50 < fanquake> (follow up from a few days ago)
04:50 < fanquake> I've been using this method for all the recent builds.
04:52 < provoostenator> Nice, I'll try that after the Mojave update...
04:53 -!- yep555 [~yep555@p200300C99F1C2D003D7AE976B70E5450.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
04:54 -!- promag [~promag@119.70.114.89.rev.vodafone.pt] has quit [Ping timeout: 244 seconds]
04:54 < yep555> will there be an rc5?
04:58 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #bitcoin-core-dev
05:00 < fanquake> yep555 Should be, as there are still a few issues outstanding for 0.17.0 https://github.com/bitcoin/bitcoin/milestone/33
05:09 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 260 seconds]
05:18 -!- ken2812221_ [~ken281222@180.217.128.66] has joined #bitcoin-core-dev
05:18 -!- setpill [~setpill@unaffiliated/setpill] has quit [Quit: o/]
05:22 -!- ken2812221 [~ken281222@36-226-68-170.dynamic-ip.hinet.net] has quit [Quit: Leaving]
05:26 -!- ken2812221_ is now known as ken2812221
05:36 -!- emilengler [~emil@ip4d145229.dynamic.kabel-deutschland.de] has joined #bitcoin-core-dev
05:36 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection]
05:44 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Ping timeout: 240 seconds]
05:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
05:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
05:45 -!- ott0disk [~smuxi@d3.85.7a9f.ip4.static.sl-reverse.com] has joined #bitcoin-core-dev
05:47 -!- queip [~queip@unaffiliated/rezurus] has quit [Quit: bye, freenode]
05:52 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Remote host closed the connection]
06:08 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #bitcoin-core-dev
06:08 -!- emilengler [~emil@ip4d145229.dynamic.kabel-deutschland.de] has quit [Quit: Konversation terminated!]
06:15 -!- queip [~queip@unaffiliated/rezurus] has joined #bitcoin-core-dev
06:16 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
06:24 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
06:27 -!- owowo [~ovovo@unaffiliated/ovovo] has joined #bitcoin-core-dev
06:35 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev
06:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
06:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
06:46 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]
06:46 -!- jnewbery [~john@rrcs-67-251-193-154.nyc.biz.rr.com] has joined #bitcoin-core-dev
06:52 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has joined #bitcoin-core-dev
07:00 -!- games_ [sid99242@gateway/web/irccloud.com/x-vefnlqhjyljubnai] has joined #bitcoin-core-dev
07:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
07:16 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
07:19 < ott0disk> Hello is there a way to use the 'generate' RPC deterministically (during a functional test of course)?   
07:25 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #bitcoin-core-dev
07:26 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has joined #bitcoin-core-dev
07:27 < michagogo> provoostenator: I just always use —upgrade
07:27 < michagogo> And I have a script I run every so often to upgrade the base image
07:28 < provoostenator> I remember that not working a while ago, but will try again next time. This time I just nuked the images and ran it again.
07:28 < provoostenator> It would be nice if it just did that automatically.
07:28 < michagogo> Heh, I guess that works too…
07:29 < michagogo> Yeah, I guess maybe they think you might want to have a consistent environment and not upgrade any of the base packages unless you say so
07:30 < michagogo> Or maybe they assume you don’t want to spend the time to upgrade each time
07:30 < michagogo> Or something
07:30 < michagogo> 🤷
07:31 < michagogo> At this point I have the whole thing automated
07:34 < michagogo> I just kick off one script with the version and the targets (usually all) and it does it all, including creating the PR
07:34 -!- promag [~promag@83.223.235.33] has joined #bitcoin-core-dev
07:35 < provoostenator> 0.14.3 release notes (etc) ready for review in #14279
07:35 < gribble> https://github.com/bitcoin/bitcoin/issues/14279 | 0.14.3 release notes, manpage and version bump by Sjors · Pull Request #14279 · bitcoin/bitcoin · GitHub
07:42 < promag> jnewbery: do you think BitcoinTestFramework should be used/extended to support bitcoin-wallet-tool tests?
07:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
07:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
07:53 -!- Murch [~murch@172.56.38.5] has joined #bitcoin-core-dev
07:55 -!- rex4539 [~rex4539@185.220.102.8] has quit [Quit: rex4539]
07:55 -!- ott0disk [~smuxi@d3.85.7a9f.ip4.static.sl-reverse.com] has quit [Ping timeout: 244 seconds]
08:00 -!- promag [~promag@83.223.235.33] has quit [Remote host closed the connection]
08:11 -!- fanquake [~fanquake@unaffiliated/fanquake] has quit []
08:12 -!- Murch [~murch@172.56.38.5] has quit [Quit: Snoozing.]
08:31 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
08:32 -!- treebeardd [~treebeard@23-30-129-3-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection]
08:38 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 272 seconds]
08:41 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
08:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
08:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
08:46 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Remote host closed the connection]
08:47 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
08:52 < jnewbery> promag: I'd say it's probably better to keep them separate if possible. Take a look at the bitcoin-tx tests in test/util. Tests for bitcoin-wallet-tool should probably go in there.
09:14 -!- pipp8 [~pipp8@unaffiliated/pipp8] has joined #bitcoin-core-dev
09:17 -!- davex__ [~user@97-119-108-199.omah.qwest.net] has joined #bitcoin-core-dev
09:17 -!- davex__ [~user@97-119-108-199.omah.qwest.net] has quit [Remote host closed the connection]
09:18 -!- davex__ [~user@97-119-108-199.omah.qwest.net] has joined #bitcoin-core-dev
09:18 -!- davex__ [~user@97-119-108-199.omah.qwest.net] has quit [Remote host closed the connection]
09:19 -!- Krellan [~Krellan@2601:640:4000:9258:f4e2:f1d8:c681:21b4] has quit [Ping timeout: 240 seconds]
09:22 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 252 seconds]
09:30 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection]
09:32 -!- jarthur [~jarthur@207.114.244.5] has joined #bitcoin-core-dev
09:39 < wumpus> I agree
09:39 < wumpus> although, in this case you might need bitcoind to create/populate the wallet in the first place
09:40 < wumpus> so it integrates somewhat more closely with the existing tests that bitcoin-tx which is an independend utility 
09:40 < wumpus> and as soon as you need bitcoind and RPC, integrating it into the test framework makes much more sense
09:40 < wumpus> otherwise you'll end up duplicating functionality
09:41 < wumpus> promag isn't even here is he
09:42 -!- Tennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
09:44 -!- Krellan [~Krellan@2601:640:4000:9258:f4e2:f1d8:c681:21b4] has joined #bitcoin-core-dev
09:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
09:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
09:45 -!- promag [~promag@83.223.234.111] has joined #bitcoin-core-dev
09:46 < promag> wumpus: jnewbery: sorry, catching up
09:46 -!- MTennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
09:47 < promag> to test against running nodes I'm extending BitcoinTestFramework
09:50 -!- Tennis [~Tennis@unaffiliated/tennis] has quit [Ping timeout: 252 seconds]
09:50 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
09:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
10:12 < promag> bbl
10:13 -!- promag [~promag@83.223.234.111] has quit [Remote host closed the connection]
10:16 < wumpus>  * [new tag]                                                                           v0.14.3 -> v0.14.3
10:16 < midnightmagic> \o/
10:34 -!- rhyslindmark [~rhyslindm@209.6.69.135] has joined #bitcoin-core-dev
10:37 -!- rhyslindmark [~rhyslindm@209.6.69.135] has quit []
10:44 -!- rhyslindmark [~rhyslindm@209.6.69.135] has joined #bitcoin-core-dev
10:44 -!- rhyslindmark [~rhyslindm@209.6.69.135] has quit [Client Quit]
10:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
10:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
10:48 < jnewbery> wumpus: promag: yes, that makes sense. If you need a bitcoind to create the wallet, then it makes sense to incorporate the tests into the functional test framework
10:49 < jnewbery> (although I am a little concerned about the tendency for the functional test framework to keep on expanding forever)
10:55 < wumpus> I'm more concerned with adding more utilities to bitcoin core than the test framework expanding to test them
10:55 < wumpus> at least the tests should skip if built without the utility, I suppose
11:07 -!- Krellan [~Krellan@2601:640:4000:9258:f4e2:f1d8:c681:21b4] has quit [Remote host closed the connection]
11:10 < MarcoFalke> We can always try to refactor it later if it becomes an issue. Refactoring solves all issues I heard.
11:11 -!- rex4539 [~rex4539@nevada.tor-relay.host] has joined #bitcoin-core-dev
11:16 -!- TennisB [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
11:20 -!- timothy [tredaelli@redhat/timothy] has quit [Remote host closed the connection]
11:20 -!- MTennis [~Tennis@unaffiliated/tennis] has quit [Ping timeout: 246 seconds]
11:32 < wumpus> heh
11:32 -!- rex4539 [~rex4539@nevada.tor-relay.host] has quit [Quit: rex4539]
11:33 < wumpus> that explains the large amount of refactoring...
11:43 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection]
11:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
11:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
11:56 -!- jarthur [~jarthur@207.114.244.5] has quit []
11:57 < MarcoFalke> meeting in 3?
11:58 < luke-jr> no, 2
11:59 < sipa> no, 1
11:59 < luke-jr> I see you were just waiting for the minute to change for posting that!
11:59 < sipa> actually, no, i just switched to this terminal when the clock was already ":59"
11:59 < luke-jr> :p
12:00 < MarcoFalke> 0
12:00 < sdaftuar> hi
12:00  * luke-jr pokes wumpus
12:00 < jonasschnelli> hi
12:00 < luke-jr> don't make us off-by-one!
12:00 < MarcoFalke> off-by-negative-one
12:00 < luke-jr> :x
12:01 < MarcoFalke> topic proposals:
12:01 < MarcoFalke> short topic: Delete 0.10.* executables from bitcoincore.org
12:01 < MarcoFalke> short topic: Add GitHub pull request template
12:01 < sipa> wumpus: ^
12:01 < MarcoFalke> But I think first topic is 0.17.0?
12:01 < achow101> hi
12:02 < wumpus> #startmeeting
12:02 < lightningbot> Meeting started Thu Sep 20 19:02:24 2018 UTC.  The chair is wumpus. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:02 < lightningbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
12:02 < MarcoFalke> I think anyone can be the host that knows the commands for the meeting bot?
12:02 < MarcoFalke> ah
12:02 < wumpus> #topic 0.17.0
12:02 < meshcollider> Hi
12:03 < MarcoFalke> I think two of the issues in the milestone are just release-notes related
12:03 < wumpus> anything specific you want to discuss about it?
12:03 < wumpus> correct, the only real still-open issue is achow101 's PR
12:04 < gmaxwell> I think we should probably just get 0.17 out soon, and even slip the PSBT fix to 0.17.1 to be done soon after.
12:04 < wumpus> yes,agree
12:04 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
12:04 < gmaxwell> it's unfortunately that PSBT is hobbled in 0.17, but considering bugfix upgrades we'll be better off not delaying due to a new feature that is kinda expiremental in any case... and probably has other bugs.
12:04 < promag> hi
12:04 -!- rex4539 [~rex4539@tor-exit-node.pie-coop.net] has joined #bitcoin-core-dev
12:05 < sipa> i'm not sure it's a very common workflow that triggers (importing a p2sh-segwit address without known pubkey, and then trying to sign on an offline system)
12:06 < sipa> it just happened to be the first thing i tried
12:06 < gmaxwell> I think it's like _the_ obvious workflow... if you happen to be using embedded segwit. :P
12:06 < wumpus> so, all in all it depends on why people want to upgrade to 0.17.0
12:06 < gmaxwell> Can we provide workaround instructions that have people import the redeemscript?
12:06 < luke-jr> we just released 0.16.3; is there a reason to rush 0.17 now?
12:06 < wumpus> if a properly working PSBT is very important, we should delay the release for it
12:06 < luke-jr> people who really want it can always use a rc
12:06 < sipa> gmaxwell: or another roundtrip; i'll write up a workaround
12:07 < gmaxwell> luke-jr: It's 0.1 higher.
12:07 < wumpus> if PSBT is seen as an curious experimental feature, then not so much
12:07 < gmaxwell> Since PSBT is new I don't think it's important if it works at all.
12:07 < wumpus> I don't have a clear perspective on that
12:07 < sipa> gmaxwell: it's 0.7 higher :)
12:07 < sdaftuar> gmaxwell: i agree with that
12:08 < morcos> i also would rather document the shortcomings of PSBT and proceed with the release.   
12:08 < achow101> I think it is fine to release as is and do the fix for .1 later
12:08 < wumpus> don't really want complaints like 'so you released 0.17.0 but it's useless as the PSBT we've been waiting for is useless'
12:08 < gmaxwell> I think cosmically PSBT is important, but it's fine if we get it after another month delay or what not.. and it's not broken completely, there is a workaround, and that issue only applies to p2sh-segwit.
12:08 < achow101> this is fairly edge case imo
12:08 < MarcoFalke> so action: Merge release notes?
12:08 -!- clarkmoody [~clarkmood@47-218-248-206.bcstcmta04.res.dyn.suddenlink.net] has joined #bitcoin-core-dev
12:09 < wumpus> but that's not the gut feeling I have about it, and I'm okay with tagging 0.17.0 final next week when no new problems come up
12:09 < gmaxwell> It's also not the only shortcoming of PSBT as is... e.g. the txou-scan + spend workflow is kind of a mess for non-segwit outputs as I was lamenting in here a few weeks ago. (not as easily fixed)
12:09 < promag> make it experimental like scantxoutset?
12:09 < wumpus> right, PSBT is bound to have more problems that will come up when other users start using it
12:09 < gmaxwell> I don't think it needs to be marked more expiremental.
12:09 < wumpus> there will likely need to be a 0.17.1 for other reasons
12:10 < sipa> i don't think we should be waving 'experimental' as a label as a way to avoid responsibility in creating decent interfaces
12:10 < wumpus> we could disable it completely.
12:10 < sipa> it's there to indicate that changes are possible in the future
12:10 < gmaxwell> scantxoutset is marked expiremental in particular because the interface isn't stable.
12:10 < wumpus> just disable the methods, make PSBT entirely miss 0.17.0
12:10 < promag> rpc cycle experimental -> stable -> deprecated :P
12:10 < sipa> i think it's fine to release 0.17.0 as-is now
12:11 < wumpus> but only if you think releasing as-is is "avoiding responsibility"
12:11 < gmaxwell> wumpus: I don't see how doing that, in this case, would make anyone better off. I would agree if it was like "PSBT could surprise crash, or eat your coins" or whatnot.
12:11 < wumpus> gmaxwell: it was because of sipa's working
12:11 < wumpus> wording*
12:11 < luke-jr> [19:10:32] <wumpus> just disable the methods, make PSBT entirely miss 0.17.0 <-- IMO better to just delay 0.17 a bit
12:11 < gmaxwell> But in this case, it's just "this very specific sequence of actions in this specific use case just doesn't work"
12:11 < sipa> wumpus: no, i'm just a bit annoyed with the "we could always mark things experimental!" response to things that don't work - not specific to this issue
12:11 < achow101> I think 0.17 is fine to release as is
12:11 < sipa> this is minor enough
12:12 < wumpus> sipa: well it's quite common for software to have 'known issues' with releases
12:12 < morcos> we have a precedent of release notes with a Known Bugs section
12:12 < promag> luke-jr: remove features in RC?
12:12 < sipa> wumpus: right, that's far more honest :)
12:12 < morcos> damn i type too slow
12:12 < gmaxwell> yea, for this it's fine.
12:12 < wumpus> at some point ,a release needs to be cut, in spite of everything
12:12 -!- earlz [~earlz@earlz.net] has joined #bitcoin-core-dev
12:12 < luke-jr> promag: not necessarily in general, but in this specific case
12:12 < gmaxwell> Sometimes a known issue is severe enough you need to disable the functionality, but not here. And expiremental isn't the right concept: it's not that PSBT is going to change its interface in an incompatible way, it just has some bugs.
12:12 < luke-jr> promag: no reason to rush 0.17, and fixing it shouldn't delay long
12:13 < wumpus> but I agree removing features should be left for when something is dangerously broken
12:13 < wumpus> but the fact that this discussion keeps coming back indicates to me that most people just want 0.17.0 out, for other reasons than PSBT
12:13 < promag> we want people to try it+, but in a responsible way, so experimental sounds fine to me
12:13 < gmaxwell> For use we're using expiremental to get functionality out when the remaining issue is some debate (or incompleteness) in the interface, and where we figure people are better off having it, even if the interface isn't stable yet.
12:14 < sipa> psbt is not experimental; its workflows or interfaces aren't changing, nor is there a security issue
12:14 < gmaxwell> because we found that we were delaying good features because "interfaces-are-forever".
12:14 < wumpus> right
12:14 < sipa> there's just a bug that prevents it from working in an edge case that can be worked around, which will be fixed soon
12:15 < gmaxwell> and 0.17 has a lot of fantastic improvements that people should get their hands on.
12:15 < earlz> What's the best way to privately report a security problem in bitcoin core? 
12:15 < promag> sipa: experimental can also mean incomplete, or not entirely tested or finished?
12:15 < sipa> earlz: security@bitcoincore.org
12:15 < wumpus> earlz: gpg-signed mail to maintainers
12:15 < luke-jr> gpg encrypted, not signed.
12:15 < sipa> i care more about gpg-encrypted than signed :)
12:15 < earlz> Thanks
12:15 < wumpus> eh yes, sorry , encrypted
12:16 < gmaxwell> earlz: https://bitcoincore.org/en/contact/  has the info.
12:16  * luke-jr wonders if earlz's question should be considered in the context of the meeting topic
12:17 < gmaxwell> please don't discuss security issues on irc.
12:17 < wumpus> #topic Delete 0.10.* executables from bitcoincore.org
12:17 < MarcoFalke> Similar to how the branches were deleted from the GitHub git mirror (https://bitcoincore.org/en/meetings/2018/05/03/#delete-08-09-and-010-git-branches), we should delete executables that are long EOL.
12:17 < luke-jr> rather move than delete
12:17 < MarcoFalke> bitcoincore.org is mostly concerned about distributing working, tested and non-vulnerable software versions of Bitcoin Core. The site should not serve as an archive of binary blobs. Note that releases before 0.10.0 are already not offered as download on https://bitcoincore.org/bin/.
12:17 < wumpus> yes, would rather move to an "old_dont_use" directory
12:17 < gmaxwell> wumpus: it's really useful to have old executable archived somewhere. It's often hard to _build_ old versions because of @#$@ dependency changes.
12:17 < wumpus> gmaxwell: I agree
12:18 < wumpus> deleting isn't necssary, I think
12:18 < jonasschnelli> Agree
12:18 < MarcoFalke> Then, we should also put up the 0.8 and earlier versions?
12:18 < wumpus> we do!
12:18 < MarcoFalke> Oh I din't know
12:19 < luke-jr> https://bitcoincore.org/bin/insecure/ has back to 0.8.6
12:19 < luke-jr> …and copies of 0.10 it seems
12:19 < gmaxwell> probably anything that doesn't enforce all current consensus rules should be in a old_dont_use directory.
12:19 < sipa> so 0.13.1 ?
12:19 < wumpus> when bitcoincore.org started hosting executables I think I copied everything from bitcoin.org
12:20 < gmaxwell> sipa: has it been that long, ... I guess so.
12:20 < wumpus> ok with me
12:20 < sipa> nearly 2 years.
12:21 < MarcoFalke> Hmm https://bitcoincore.org/bin/bitcoin-core-0.10.4/ seems empty
12:21 < wumpus> MarcoFalke: yes, that version was never released
12:21 < MarcoFalke> But yeah, moving is fine if developers still use the binaries
12:21 < MarcoFalke> Oh I remember we had this chat
12:21 < luke-jr> FWIW, I do have various old versions archived on https://luke.dashjr.org/programs/bitcoin/files/bitcoind/
12:22 < wumpus> there was an rc for 0.10.4 at some point AFAIK that's why the directory exists
12:22 < MarcoFalke> Ah
12:22 < gmaxwell> in any case action is to move but don't delete old versions? and at least anything that isn't current with the current consensus rules?
12:22 < sdaftuar> 0.13 is past end-of-life, so i think it should be considered "old_dont_use" as well
12:22 < wumpus> gmaxwell: yes I think so
12:23 < wumpus> MarcoFalke: rcs for old releases used to be deleted because of disk space constraints on bitcoin.org, don't know if bitcoincore.org has the same problem
12:24 < gmaxwell> sdaftuar: also old don't use due to not having the crash fix.
12:25 < wumpus> isn't 0.14 the first release with the crash bug?
12:25 < sdaftuar> wumpus: yes
12:25 < wumpus> #topic Add GitHub pull request template (MarcoFalke)
12:26 < MarcoFalke> There are sometimes pull requests that do simple stylistic refactoring without obvious advantages to either users or developers. The GitHub pull request template would remind contributors that they need to provide clear rationale for these refactoring changes
12:26 < wumpus> yes please
12:26 < jnewbery> ACK
12:26 < sdaftuar> +1
12:26 < jamesob> +1. thoughts on test coverage requirements?
12:26 < cfields> and a benchmark if it's intended to be an optimization
12:26 < MarcoFalke> I'd just wanted to ask people to look at https://github.com/bitcoin/bitcoin/pull/14217
12:26 < MarcoFalke> and leave feedback
12:27 < sdaftuar> jamesob: i think it's always good to encourage PR openers and reviewers to ensure there's test coverage!
12:27 < gmaxwell> 12:26:44 < cfields> and a benchmark if it's intended to be an optimization
12:27 < MarcoFalke> jamesob: In the future, a bot could automatically close refactoring pull requests without rationale or missing test coverage.
12:27 < wumpus> cfields: right
12:27 < gmaxwell> I also worry about things that are intended to be 'cleanup' that make things slower.
12:27 < wumpus> #action review https://github.com/bitcoin/bitcoin/pull/14217
12:27 < MarcoFalke> At least we have some monitoring to detect obvious slowdowns after merge
12:28 < gmaxwell> See for example arvid's removal of INLINE that sipa commented on-- which actually seems to be okay, but its the sort of thing that could result in massive performance regressions.
12:28 < MarcoFalke> Though, would be good to get the signal before merge
12:28 < wumpus> gmaxwell: yes...
12:28 < gmaxwell> MarcoFalke: yes, but it looks like it wasn't running very frequently which also makes it hard to tell which commit(s) did it.
12:28 < gmaxwell> so perhaps my concern is best fixed by just improving the monitoring.
12:28 < MarcoFalke> It runs about once a day, but we had some downtime last month
12:28 < wumpus> that's another cleanup I really don't care for, for what it's worth
12:29 < jamesob> gmaxwell: bitcoinperf shouldn't be down that long again
12:29 < gmaxwell> OKAY
12:29 < gmaxwell> Would it be possible to get it to run on each PR merge even if it falls behind?
12:29 < MarcoFalke> The basic stuff for sure
12:29 < jamesob> that's a lotta compute, but it's something I'm thinking about - and will have time to work on after the next month or so
12:29 < MarcoFalke> IBD is the hardest
12:30 < wumpus> could at least check whether cpp/h files were changed !
12:30 < gmaxwell> I think it's silly for us to be bound on compute.
12:30 < wumpus> it seems completely unnecessary to run it after a documentation change
12:30 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev
12:30 < sdaftuar> gmaxwell: agreed
12:30 < gmaxwell> indeed, skipping pointless changes is good... but ultimately if we need a rack of computers to keep up with it, we should be able to get that.
12:31 < wumpus> no one is stopping anyone from doing that, no :)
12:31 < sipa> consistent performance numbers do need identical hardware etc
12:31 < wumpus> could even run it on PRs
12:32 < sipa> if you want to parallellize
12:32 < wumpus> yes
12:32 < gmaxwell> In absence of someone doing it we probably shouldn't just keep a commit flux that we can't adequately test though, and checking for perf regressions is part of it.
12:32 < wumpus> it's kind of more expensive than what travis does, VMs would be useless for this
12:32 < gmaxwell> indeed.
12:33 < wumpus> in any case, I'm all for discouraging useless refactoring changes
12:33 < wumpus> it sometimes feels like I'm the only person pushing back against them
12:34 < jonasschnelli> no.. i'm with you
12:35 < wumpus> any other topics?
12:37 < wumpus> if not, I'm going to close the meeting and go to bed, need to get up very early tomorrow for my flight
12:37 < cfields> I'm back full-time, still catching up. Please ping me if you have anything that was waiting for me or that I should get to quickly.
12:37 < sipa> wumpus: safe travels
12:37 < wumpus> cfields: welcome back !
12:37 < jonasschnelli> cfields: great to hear!
12:37 < wumpus> sipa: thank you
12:38 < promag> cheers
12:38 < MarcoFalke> safe travels!
12:38 < luke-jr> cfields: I think I have at least one PR wumpus wanted you to look at, but no rush
12:39 < MarcoFalke> proposed action: end meeting
12:39 < promag> regarding practicalswift (are you here?), I think he should build something like bitcoinacks.com
12:39 < sipa> ack
12:39 < wumpus> #endmeeting
12:39 < lightningbot> Meeting ended Thu Sep 20 19:39:35 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
12:39 < lightningbot> Minutes:        http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-09-20-19.02.html
12:39 < lightningbot> Minutes (text): http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-09-20-19.02.txt
12:39 < lightningbot> Log:            http://www.erisian.com.au/meetbot/bitcoin-core-dev/2018/bitcoin-core-dev.2018-09-20-19.02.log.html
12:39 < promag> but for his tools
12:40 < cfields> luke-jr: roger
12:41 < promag> jnewbery: should I open a PR to discuss the wallet tool test?
12:41 -!- treebeardd [~treebeard@173.13.103.65] has joined #bitcoin-core-dev
12:42 < provoostenator> Argh, timezones, sorry I missed the party/meeting.
12:43 < jnewbery> promag: I think you could just oen a PR for a test for bitcoin-wallet-tool, including the commit from 13926. I expect any test would be merged as part of the original PR, but discussion of the tests can be in your new PR.
12:44 -!- paracyst [paracyst@unaffiliated/paracyst] has quit [Quit: bye]
12:44 < promag> yap
12:44 -!- paracyst [paracyst@unaffiliated/paracyst] has joined #bitcoin-core-dev
12:45 < luke-jr> (I wish I could suggest new tools just get a new repo of their own, but I think in this case it's not practical :x )
12:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
12:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
12:50 < wumpus> indeed, that's not practical in this case, the whole point in this case is to share the low-level code with the wallet
12:51 < wumpus> and it makes sense to ship it, every database worth its salt also comes with at least one recovery tool
12:52 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
12:53 < provoostenator> Fwiw compiling back to 0.5 isn't that hard, last time I tried: https://gist.github.com/Sjors/70f14baf1f834f3547bf35553faff610 
12:55 < luke-jr> I wonder if the gitian sigs still match
12:56 < jcorgan> provoostenator: if you set the timezone for the meeting to Reykjavik it will always be correct. I think that's the only country that uses GMT all year.
12:56 < sipa> (nit: Reykjavik is not a country)
12:57 < jcorgan> sure, sure
12:58 < provoostenator> jcorgan: my calender worked fine, I just ignored it
12:58 < luke-jr> some calendar won't let you just set UTC?
12:58 < jcorgan> heh
12:58 < jcorgan> i don't think google does
12:58 < sipa> luke-jr: google calendar
13:00 < provoostenator> Can we get signed binaries for 0.15.2? 
13:00 -!- grubles [~grubles@gateway/tor-sasl/grubles] has quit [Remote host closed the connection]
13:01 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #bitcoin-core-dev
13:04 -!- treyzania [~treyzania@paphos.tr3y.io] has joined #bitcoin-core-dev
13:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
13:16 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #bitcoin-core-dev
13:22 < clarkmoody> exit
13:23 -!- clarkmoody [~clarkmood@47-218-248-206.bcstcmta04.res.dyn.suddenlink.net] has quit []
13:23 < treyzania> nice
13:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
13:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
13:46 < michagogo> Um, I'm looking at a `git diff v0.14.2..v0.14.3`
13:46 < michagogo> This version seems to introduce a whole bunch of typos o_O
13:48 < michagogo> Oh, looks like it's actually all in one file: https://www.irccloud.com/pastebin/r7TtkcBE/
14:02 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has quit [Ping timeout: 246 seconds]
14:13 -!- nullptr| [~nullptr|@ip-94-113-103-134.net.upcbroadband.cz] has joined #bitcoin-core-dev
14:14 -!- rh0nj [~rh0nj@136.243.139.96] has quit [Remote host closed the connection]
14:15 -!- rh0nj [~rh0nj@136.243.139.96] has joined #bitcoin-core-dev
14:19 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
14:20 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
14:26 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
14:41 -!- treebeardd [~treebeard@173.13.103.65] has quit [Remote host closed the connection]
14:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
14:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
14:46 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
14:50 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-uybxshavvfqpwrdn] has quit [Quit: Connection closed for inactivity]
14:50 -!- yep555 [~yep555@p200300C99F1C2D003D7AE976B70E5450.dip0.t-ipconnect.de] has quit [Quit: Leaving]
14:54 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
14:56 -!- gekmuth [~androirc@188.113.19.180] has joined #bitcoin-core-dev
15:14 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev
15:34 -!- hebasto [~hebasto@195.60.70.234] has quit [Remote host closed the connection]
15:39 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Read error: Connection reset by peer]
15:40 -!- Guyver2 [AdiIRC@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
15:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
15:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
15:47 -!- quer [~quer@unaffiliated/quer] has quit [Read error: Connection reset by peer]
15:48 -!- quer [~quer@unaffiliated/quer] has joined #bitcoin-core-dev
15:56 -!- gekmuth [~androirc@188.113.19.180] has quit [Quit: AndroIRC - Android IRC Client ( http://www.androirc.com )]
16:15 -!- hirish [~hirish@hirish.cloudns.org] has joined #bitcoin-core-dev
16:19 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
16:21 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
16:25 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
16:26 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
16:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 245 seconds]
16:31 -!- MTennis [~Tennis@unaffiliated/tennis] has joined #bitcoin-core-dev
16:34 -!- TennisB [~Tennis@unaffiliated/tennis] has quit [Ping timeout: 245 seconds]
16:35 -!- MTennis [~Tennis@unaffiliated/tennis] has quit [Client Quit]
16:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
16:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
17:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection]
17:01 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:02 -!- pipp8 [~pipp8@unaffiliated/pipp8] has quit [Quit: Leaving]
17:03 -!- Murch [~murch@50-200-105-218-static.hfc.comcastbusiness.net] has quit [Quit: Snoozing.]
17:06 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 246 seconds]
17:11 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
17:16 -!- VanCo [~VanCo@unaffiliated/vanco] has joined #bitcoin-core-dev
17:16 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]
17:16 -!- lnostdal [~lnostdal@77.70.119.51] has joined #bitcoin-core-dev
17:23 < gmaxwell> https://bitcoincore.org/en/2018/09/20/notice/
17:25 < luke-jr> this seems way too premature; only 2% of the network's upgraded :/
17:27 < gmaxwell> unfortunately, the issue was made public.
17:27 < luke-jr> :/
17:28 < gmaxwell> it wasn't clear if it would propagate or die out, but since it was moderatly easy to discover on your own, even just the rumors of it risked someone exploiting it.
17:30 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Read error: Connection reset by peer]
17:31 < achow101> gmaxwell: luke-jr: there's an r/btc thread about someone finding the bug
17:32 < gmaxwell> achow101: it's referenced in the message. 'circulating'
17:34 < jamesob> Wow, that was fast
17:36 -!- jarthur [~jarthur@2605:6000:1019:41ab:bcc0:73f9:3650:bafb] has joined #bitcoin-core-dev
17:40 < promag> jnewbery: fyi #14283
17:41 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
17:43 -!- VanCo [~VanCo@unaffiliated/vanco] has quit [Quit: Leaving]
17:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
17:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
17:46 -!- VanCo [~VanCo@unaffiliated/vanco] has joined #bitcoin-core-dev
17:46 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection]
17:48 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #bitcoin-core-dev
18:05 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]
18:05 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl]
18:10 -!- Murch [~murch@c-73-223-113-121.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
18:11 < gmaxwell> theymos has a new announcement up https://www.reddit.com/r/Bitcoin/comments/9hkoo6/new_info_escalates_importance_upgrading_to_0163/
18:12 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
18:17 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 272 seconds]
18:20 < gmaxwell> should I PR the extended test case?
18:35 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
18:38 < luke-jr> gmaxwell: I'd wait
18:39 < gmaxwell> OK.
18:41 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds]
18:44 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #bitcoin-core-dev
18:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
18:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
18:50 -!- VanCo [~VanCo@unaffiliated/vanco] has quit [Ping timeout: 252 seconds]
18:56 < luke-jr> did anyone mail the announcement ML about 0.16.3? I don't think I saw one..
18:56 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 272 seconds]
18:56 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection]
18:58 < achow101> luke-jr: there was an announcement for it
19:00 < aj> is bitcoin-core-dev the announcement list? https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2018-September/000060.html
19:00 < luke-jr> no
19:00 < luke-jr> this one https://bitcoincore.org/en/list/announcements/join/
19:03 < nanotube> would it make sense to propose a 'contact' page on bitcoin.org  similar to the one on bitcoincore.org? it appears it is non-trivial to find where to privately report security issues unless one knows to go to bitcoincore.org, since earlz had to come asking on #bitcoin-dev and -core-dev for a way to report.
19:03 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has joined #bitcoin-core-dev
19:04 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds]
19:05 < gmaxwell> nanotube: :( I feel really uncomfortable with people going to bitcoin.org for that kind of information. 
19:05 < harding> nanotube: any page on Bitcoin.org, top menu, Participate, Development, "to report an issue, please see the Bug Reporting page", Responsible Disclosure.
19:05 < gmaxwell> but its there
19:05 < gmaxwell> yea
19:08 -!- Krellan [~Krellan@50-242-94-241-static.hfc.comcastbusiness.net] has quit [Ping timeout: 252 seconds]
19:11 < nanotube> yes not ideal, but people probably still go there unless they know to check bitcoincore.org... so, good that it has the bug reporting page in there somewhere. 
19:35 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-fchnfmtpsssilufp] has joined #bitcoin-core-dev
19:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
19:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
19:55 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
19:58 < echeveria> there used to be bitcoin-security, but that was handled sort of poorly. 
19:59 < echeveria> the contents of it ended up being published when someone stole the old satoshi email address. 
19:59 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 252 seconds]
20:11 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
20:13 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
20:15 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
20:18 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 252 seconds]
20:37 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
20:41 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 245 seconds]
20:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
20:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
20:45 -!- shinohai [btcinfo@gateway/shell/xshellz/x-uzgxflnncphzskwv] has quit [Ping timeout: 252 seconds]
21:00 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Read error: Connection reset by peer]
21:08 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Ping timeout: 252 seconds]
21:09 -!- jnewbery [~john@rrcs-67-251-193-154.nyc.biz.rr.com] has quit [Ping timeout: 260 seconds]
21:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
21:14 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-core-dev
21:17 < kanzure> hi. mailing list admin has hit a bug and is unusable at the moment.
21:18 < kanzure> We're sorry, we hit a bug!
21:18 < kanzure> Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs.
21:21 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds]
21:22 < sipa> great.
21:22 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-core-dev
21:32 -!- paracyst_ [paracyst@unaffiliated/paracyst] has joined #bitcoin-core-dev
21:32 -!- paracyst [paracyst@unaffiliated/paracyst] has quit [Ping timeout: 245 seconds]
21:33 < echeveria> I was looking at one of the public internet mapping tools for bitcoin core versions. there's a pretty disturbing number of hosts that have 8332 open. 
21:35 -!- baldur [~baldur@pool-72-69-77-244.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds]
21:36 < echeveria> is there some tool or setup guide that is telling people to open this port? I thought it was pretty difficult (not a single switch) to get Bitcoin Core to bind the RPC interface to 0.0.0.0. 
21:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
21:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
21:46 < echeveria> of 8000 IPv4 nodes, 1142 have a RPC port 8332 that respond to a SYN. 
21:47 -!- bsm117532 [~mcelrath@c-24-61-184-150.hsd1.ma.comcast.net] has joined #bitcoin-core-dev
21:48 -!- baldur [~baldur@pool-72-69-77-244.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
21:49 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
21:54 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 252 seconds]
21:54 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 272 seconds]
21:56 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #bitcoin-core-dev
21:59 -!- jarthur [~jarthur@2605:6000:1019:41ab:bcc0:73f9:3650:bafb] has quit [Quit: good night]
22:09 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
22:10 < gmaxwell> maybe honeypots?
22:10 < gmaxwell> as you note, you must take extra steps to bind..
22:13 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 246 seconds]
22:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
22:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
22:52 < echeveria> I don't think so. they're over a huge number of different hosts, old and new.
22:53 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
22:58 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 260 seconds]
23:03 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
23:08 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Ping timeout: 240 seconds]
23:14 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has joined #bitcoin-core-dev
23:17 -!- promag [~promag@bl22-247-244.dsl.telepac.pt] has quit [Remote host closed the connection]
23:20 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 272 seconds]
23:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #bitcoin-core-dev
23:25 -!- Urgo [~Urgo@cpe-107-15-142-254.nc.res.rr.com] has joined #bitcoin-core-dev
23:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has quit [Remote host closed the connection]
23:45 -!- tryphe [~tryphe@unaffiliated/tryphe] has joined #bitcoin-core-dev
23:52 -!- hebasto [~hebasto@195.60.70.234] has joined #bitcoin-core-dev
--- Log closed Fri Sep 21 00:00:15 2018