--- Day changed Wed Feb 03 2016
00:09 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
00:54 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
01:02 -!- adam3us [~Adium@195.138.228.8] has quit [Read error: Connection reset by peer]
01:03 -!- adam3us [~Adium@195.138.228.28] has joined #bitcoin-core-dev
01:12 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
01:13 -!- p15_ [~p15@88.91.145.64.client.static.strong-tk2.bringover.net] has quit [Ping timeout: 252 seconds]
01:19 -!- p15 [~p15@24.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-core-dev
01:23 -!- adnn_ [adnn@gateway/vpn/mullvad/x-ysbusgrapvrekwgh] has joined #bitcoin-core-dev
01:25 -!- adnn [~adnn@cpe-158-222-198-108.nyc.res.rr.com] has quit [Ping timeout: 250 seconds]
01:29 < GitHub129> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/fd13fe7ca01b...5fd95b4490a9
01:29 < GitHub129> bitcoin/master 77b55a0 Luke Dashjr: Rename permitrbf to replacebyfee...
01:29 < GitHub129> bitcoin/master d65dee9 Luke Dashjr: Accept replacebyfee=opt-in for turning on opt-in RBF...
01:29 < GitHub129> bitcoin/master 3b66e54 Luke Dashjr: Simplify check for replacebyfee=opt-in
01:29 < GitHub93> [bitcoin] laanwj closed pull request #7431: Rename permitrbf to mempoolreplacement and provide minimal string-list forward compatibility (needs 0.12 backport) (master...permitrbf_rename) https://github.com/bitcoin/bitcoin/pull/7431
01:30 < GitHub133> [bitcoin] laanwj pushed 7 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/86755bc85a86...c76bfff11e38
01:30 < GitHub133> bitcoin/0.12 1205f87 Luke Dashjr: Rename permitrbf to replacebyfee...
01:30 < GitHub133> bitcoin/0.12 e8d19ab Luke Dashjr: Accept replacebyfee=opt-in for turning on opt-in RBF...
01:30 < GitHub133> bitcoin/0.12 5f456a6 Luke Dashjr: Simplify check for replacebyfee=opt-in
01:30 < GitHub94> [bitcoin] laanwj closed pull request #7440: [0.12] Rename permitrbf to mempoolreplacement and provide minimal string-list forward compatibility (0.12...permitrbf_rename-0.12.x) https://github.com/bitcoin/bitcoin/pull/7440
01:32 < GitHub21> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/294f4320a246e453a0509c82b4112b2a5203dd81
01:32 < GitHub21> bitcoin/0.12 294f432 MarcoFalke: [qt] Peertable: Increase SUBVERSION_COLUMN_WIDTH...
01:34 < GitHub38> [bitcoin] laanwj closed pull request #7405: [0.12] Backports (0.12...Mf1601-012Backports) https://github.com/bitcoin/bitcoin/pull/7405
01:36 -!- Guest87962 [~ChillazZ@194.97.152.20] has quit [Ping timeout: 240 seconds]
01:37 -!- ChillazZ [~ChillazZ@194.97.152.20] has joined #bitcoin-core-dev
01:38 -!- ChillazZ is now known as Guest37749
01:54 -!- cjc [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has joined #bitcoin-core-dev
01:54 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
01:54 -!- cjc is now known as Guest41062
01:59 < GitHub133> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/294f4320a246...b1f031d43520
01:59 < GitHub133> bitcoin/0.12 a7939f8 Wladimir J. van der Laan: doc: update release notes for rc3
01:59 < GitHub133> bitcoin/0.12 b1f031d Wladimir J. van der Laan: qt: translations update pre-rc3
02:00 < wumpus> going to tag rc3...
02:03 < wumpus>  * [new tag]         v0.12.0rc3 -> v0.12.0rc3
02:46 -!- adam3us [~Adium@195.138.228.28] has quit [Changing host]
02:46 -!- adam3us [~Adium@unaffiliated/adam3us] has joined #bitcoin-core-dev
02:50 < btcdrak> \o/
03:05 -!- BananaLotus [~BananaLot@54.186.186.141] has quit [Remote host closed the connection]
03:05 -!- guruvan [~guruvan@unaffiliated/guruvan] has quit [Remote host closed the connection]
03:05 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Remote host closed the connection]
03:05 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
03:07 -!- guruvan [~guruvan@unaffiliated/guruvan] has joined #bitcoin-core-dev
03:08 -!- adnn_ [adnn@gateway/vpn/mullvad/x-ysbusgrapvrekwgh] has quit [Remote host closed the connection]
03:09 -!- BananaLotus [~BananaLot@54.186.186.141] has joined #bitcoin-core-dev
03:30 < GitHub138> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/5fd95b4490a9...4cdbd4255b94
03:30 < GitHub138> bitcoin/master 2f19905 Peter Todd: Improve block validity/ConnectBlock() comments...
03:30 < GitHub138> bitcoin/master 4cdbd42 Wladimir J. van der Laan: Merge #7444: Improve block validity/ConnectBlock() comments...
03:30 < GitHub133> [bitcoin] laanwj closed pull request #7444: Improve block validity/ConnectBlock() comments (master...2016-01-improve-block-validity-comments) https://github.com/bitcoin/bitcoin/pull/7444
03:36 -!- gavink [~g@184.75.223.211] has quit [Ping timeout: 256 seconds]
03:40 -!- zander is now known as TZander
03:51 -!- gavink [~g@71.19.249.196] has joined #bitcoin-core-dev
04:02 < jtimon> phantomcircuit: thanks!
04:04 < jtimon> is it planned that we also always have 3 release candidates or is just coincidence?
04:05 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Remote host closed the connection]
04:24 < GitHub116> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/4cdbd4255b94...eb331794a22b
04:24 < GitHub116> bitcoin/master dbb89dc Suhas Daftuar: Eliminate unnecessary call to CheckBlock...
04:24 < GitHub116> bitcoin/master eb33179 Wladimir J. van der Laan: Merge #7225: Eliminate unnecessary call to CheckBlock...
04:24 < GitHub183> [bitcoin] laanwj closed pull request #7225: Eliminate unnecessary call to CheckBlock (master...eliminate-extra-checkblock) https://github.com/bitcoin/bitcoin/pull/7225
04:25 < GitHub99> [bitcoin] laanwj closed pull request #7291: Add CNetAddr and CService tests demonstrating constructor differences (master...cservice) https://github.com/bitcoin/bitcoin/pull/7291
04:26 < GitHub65> [bitcoin] laanwj closed pull request #6819: WIP: force zeromq to work with static linking+mingw (master...zeromq-mingw) https://github.com/bitcoin/bitcoin/pull/6819
04:28 -!- BashCo_ [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
04:31 < GitHub105> [bitcoin] laanwj closed pull request #7339: Support building without libevent (master...opt_libevent) https://github.com/bitcoin/bitcoin/pull/7339
04:31 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
04:34 -!- BashCo [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 240 seconds]
04:34 -!- BananaLotus [~BananaLot@54.186.186.141] has quit [Ping timeout: 240 seconds]
04:36 -!- BananaLotus [~BananaLot@54.186.186.141] has joined #bitcoin-core-dev
04:38 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
04:49 -!- Eliel [~jojkaart@91-159-8-128.elisa-laajakaista.fi] has joined #bitcoin-core-dev
04:57 < GitHub18> [bitcoin] zander opened pull request #7460: Make internal (core) errors show up in the Qt client. (0.12...propagateAlert12) https://github.com/bitcoin/bitcoin/pull/7460
04:57 < GitHub50> [bitcoin] zander opened pull request #7461: Make internal (core) errors show up in the Qt client. (master...propagateAlert) https://github.com/bitcoin/bitcoin/pull/7461
04:58 -!- TZander is now known as zander
05:02 < zander> I just opened those two; not sure what "Wladimir J. van der Laan"'s nick is. Nothing stands out.. But if you have questions about those MRs, ping me :)
05:04 < wumpus> <-
05:09 < zander> hi
05:14 < wumpus> zander: re: #7461, as the 0 .12 and master change is pretty much the same, there is not really a need to open two pulls, just filing it to master and stating that it needs backport to 0.12 is enough; this makes sure that there is only one place per 'issue' to review/comment instead of multiple (which has led to confusion)
05:16 < zander> wumpus: Ok, my logic was that I had to test it before sumitting a backport MR. But fine, either way.
05:17 < wumpus> zander: yes that's reasonable, it's just that the github way of working doesn't really work very well with multiple branches
05:18 < zander> fair enough
05:18 < wumpus> PRs are pretty much discussion topics, so having two with the same topic will confuse people (like me, thinking it is a duplicate)
05:18 < wumpus> or what you could also do is post a link to a 0.12 branch,and say you've already backported it
05:19 < wumpus> anyhow I'll now just rename one [0.12] but it will get out of hand if we have two pulls for every single thing :)
05:23 < zander> whatever works for you :)
05:23 < zander> I just want to make it as smooth as possible for you.
05:24 < zander> It would be really nice to get this into the next release since any forking stuff going on needs to be shown to the user.
05:25 < wumpus> yes, makes sense
05:33 -!- guruvan [~guruvan@unaffiliated/guruvan] has quit [Remote host closed the connection]
05:33 -!- BananaLotus [~BananaLot@54.186.186.141] has quit [Remote host closed the connection]
05:35 -!- BananaLotus [~BananaLot@54.186.186.141] has joined #bitcoin-core-dev
05:36 -!- guruvan [~guruvan@unaffiliated/guruvan] has joined #bitcoin-core-dev
05:48 -!- Chris_Stewart_5 [~Chris_Ste@104.156.228.195] has joined #bitcoin-core-dev
05:57 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
06:04 -!- zander [~quassel@kde/zander] has quit [Quit: No Ping reply in 180 seconds.]
06:14 -!- TZander [~quassel@kde/zander] has joined #bitcoin-core-dev
06:37 -!- Prattler [~ttttt@78-60-12-33.static.zebra.lt] has quit [Ping timeout: 252 seconds]
06:40 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Read error: Connection reset by peer]
06:41 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
06:41 -!- Prattler [~ttttt@78-60-12-33.static.zebra.lt] has joined #bitcoin-core-dev
06:53 < GitHub168> [bitcoin] zander closed pull request #7460: [0.12] Make internal (core) errors show up in the Qt client. (0.12...propagateAlert12) https://github.com/bitcoin/bitcoin/pull/7460
07:12 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer]
07:15 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
07:17 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
07:22 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 276 seconds]
07:45 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
07:49 -!- zooko [~user@2601:281:8001:26aa:1800:8e00:8f4c:c385] has joined #bitcoin-core-dev
07:50 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #bitcoin-core-dev
07:53 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
07:55 < OxADADA> TIL wumpus is Waldimir.
07:56 < OxADADA> my nick would be 0xADADA if IRC supported nicks starting with 0 :(
07:59 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Read error: Connection reset by peer]
08:01 < gijensen> I've been wondering this whole time
08:01 < gijensen> (about your nick I mean)
08:02 < OxADADA> gijensen: everyone does ;)
08:11 -!- p15 [~p15@24.91.145.64.client.static.strong-tk2.bringover.net] has quit [Ping timeout: 240 seconds]
08:14 < cfields> wumpus: wrt win signing for rc3/final, creating the new cert will revoke the previous one. Previous releases are timestamped, so I don't believe they should be affected.
08:15 < cfields> wumpus: would you prefer to use a new key for rc3 and risk problems with older releases, or stick with the old key and risk issues with win7+ ?
08:27 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Remote host closed the connection]
08:43 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 276 seconds]
08:43 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
08:45 -!- adnn_ [adnn@gateway/vpn/mullvad/x-bihlvwrycevjkruo] has joined #bitcoin-core-dev
08:46 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 276 seconds]
08:47 -!- fkhan [weechat@gateway/vpn/mullvad/x-bmjciwqtadjbitvg] has quit [Ping timeout: 276 seconds]
08:49 -!- grubles [~grubles@185.92.221.103] has joined #bitcoin-core-dev
08:49 -!- grubles is now known as Guest18098
08:51 < wumpus> OxADADA: hah, yes, last time I tried to type your nick I tried 0<tab>, and wondered why nothing would come upr
08:51 -!- fkhan [weechat@gateway/vpn/mullvad/x-jugobwzifekozhhk] has joined #bitcoin-core-dev
08:51 < wumpus> cfields: ouch. does that mean all previous releases will stop working on windows?
08:52 < wumpus> cfields: or does it just mean that nothing new can be signed with those keys?
08:52 < cfields> wumpus: since they're timestamped, they're _supposed to_ remain valid as long as the timestamp falls before the revocation time
08:52 < cfields> but i can't attest to that working as described, could only hope
08:53 < wumpus> cfields: ok, let's use the new key for rc3. If this screws up it doesn't really matter if it happens now or for final it'd be a disaster in both cases
08:53 < wumpus> and unavoidable too, unfortunately. I guess we could re-sign old releases but bleh
08:54 < wumpus> I hoep you're right
08:55 < cfields> heh
08:55 < cfields> well, I've for sure always timestamped previous releases
08:56 < cfields> (as long as i've been doing them, anyway)
08:57 < cfields> wumpus: we also have the option of changing the name/org for the key while we're at it. Would you prefer to try to change to Bitcoin Core, or keep all else the same?
08:57 < wumpus> can you just choose that name? sure, yes I'd like it to be Bitcoin Core
08:59 < cfields> yea. Not sure what verification mechanisms it triggers. I'm nervous to go any further because I want to ensure that the old one isn't revoked yet
09:10 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:20 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Remote host closed the connection]
09:28 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
09:29 -!- adnn_ [adnn@gateway/vpn/mullvad/x-bihlvwrycevjkruo] has quit [Remote host closed the connection]
09:33 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 264 seconds]
09:42 -!- Guest18098 is now known as grubles_
09:42 -!- grubles_ [~grubles@185.92.221.103] has quit [Changing host]
09:42 -!- grubles_ [~grubles@unaffiliated/grubles] has joined #bitcoin-core-dev
09:51 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
09:57 < Tasoshi> congrats gmaxwell on raising 55 million dollars
09:57 < Tasoshi> how do you plan on spending them?
10:28 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
10:29 -!- grubles_ is now known as grubles
10:29 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
10:29 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Quit: Leaving.]
10:31 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Ping timeout: 250 seconds]
10:33 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 252 seconds]
10:36 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev
10:45 -!- wallet42 [~wallet42@rrcs-198-179-71-70.nyc.biz.rr.com] has joined #bitcoin-core-dev
10:55 -!- wallet42 [~wallet42@rrcs-198-179-71-70.nyc.biz.rr.com] has quit [Quit: Leaving.]
11:09 -!- arubi_ is now known as arubi
11:25 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
11:29 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
11:30 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
11:34 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 240 seconds]
11:45 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Quit: Leaving.]
11:45 -!- gevs is now known as Guest31056
11:46 -!- Guest31056 [~greg@unaffiliated/gevs] has quit [Quit: Leaving]
11:48 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
11:50 -!- gevs [~greg@unaffiliated/gevs] has quit [Client Quit]
11:50 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
12:08 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
12:09 -!- gevs [~greg@unaffiliated/gevs] has quit [Remote host closed the connection]
12:10 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Client Quit]
12:12 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has joined #bitcoin-core-dev
12:14 -!- gevs [~greg@unaffiliated/gevs] has joined #bitcoin-core-dev
12:30 < OxADADA> Tasoshi: If they're smart, they'll prove their value as a modern startup company and buy a Foosball or Table Tennis. If they're "oldschool" they'll prove it by buying Aeron chairs.
12:31 -!- MarcoFalke [8af60249@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.73] has joined #bitcoin-core-dev
12:31 < OxADADA> all the kewl startups must do this, by law.
12:31  * OxADADA scoffs at Taek (WHERE IS YOUR FOOSBALL TABL!?)
12:47 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
12:53 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
12:55 -!- wallet42 [~wallet42@rrcs-50-74-70-195.nyc.biz.rr.com] has joined #bitcoin-core-dev
12:57 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
13:12 -!- Rebroad [~RE@cpc76150-clif11-2-0-cust623.12-4.cable.virginm.net] has quit [Ping timeout: 260 seconds]
13:13 -!- Rebroad [~RE@cpc76150-clif11-2-0-cust623.12-4.cable.virginm.net] has joined #bitcoin-core-dev
13:13 -!- JackH [~Jack@host-2-103-125-6.as13285.net] has joined #bitcoin-core-dev
13:16 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
13:21 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 252 seconds]
13:50 < zooko> Hey folks, we're setting up continuous integration for the Zcash project, including running tests in response to PRs.
13:52 -!- zooko` [~user@2601:281:8001:26aa:1800:8e00:8f4c:c385] has joined #bitcoin-core-dev
13:53 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Read error: Connection reset by peer]
13:54 -!- zooko [~user@2601:281:8001:26aa:1800:8e00:8f4c:c385] has quit [Ping timeout: 250 seconds]
13:55 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
13:56 -!- zooko` is now known as zooko
14:01 -!- treehug88 [~textual@static-108-30-103-59.nycmny.fios.verizon.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
14:02 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev
14:06 -!- arubi [~ese168@unaffiliated/arubi] has quit [Ping timeout: 240 seconds]
14:06 < Luke-Jr> zooko: cool. Core has done that for a long time ;)
14:06 < GitHub47> [bitcoin] wangchun opened pull request #7464: Opt-in RBF must be strictly enabled or disabled before GBT can be called (master...master) https://github.com/bitcoin/bitcoin/pull/7464
14:10 < zooko> Luke-Jr: with travis-ci, right? Yeah.
14:10 < zooko> Luke-Jr: one thing that I hope to add soonish is an ARMv8 buildslave. "Soonish" meaning a matter of weeks.
14:11 < zooko> Luke-Jr: anyway, let me know if you have some desired for testing/measurement/CI that might overlap with mine.
14:17 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
14:22 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
14:23 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 250 seconds]
14:34 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
14:34 -!- AtashiCon [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
15:03 < GitHub135> [bitcoin] MarcoFalke opened pull request #7465: [doc] Update release-process.md (master...Mf1601-releaseProc) https://github.com/bitcoin/bitcoin/pull/7465
15:19 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
15:21 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Remote host closed the connection]
15:24 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 250 seconds]
15:32 -!- MarcoFalke [8af60249@gateway/web/cgi-irc/kiwiirc.com/ip.138.246.2.73] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
15:35 < kanzure> release-process.md says https://bitcoincore.org/cfields/osslsigncode-Backports-to-1.7.1.patch but bitcoincore.org now redirects this to dev.bitcoincore.org perhaps the release-process.md document should be updated? does anyone care about this detail?
15:40 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Ping timeout: 250 seconds]
16:20 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
16:23 -!- adam3us [~Adium@unaffiliated/adam3us] has quit [Read error: Connection reset by peer]
16:24 -!- adam3us [~Adium@unaffiliated/adam3us] has joined #bitcoin-core-dev
16:25 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 276 seconds]
16:44 -!- arubi_ [~ese168@unaffiliated/arubi] has quit [Ping timeout: 245 seconds]
16:51 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt]
16:57 -!- bityogi [~textual@208-104-143-200.brvd.dsl.dyn.comporium.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
17:00 < Luke-Jr> kanzure: it's  intentional I think
17:07 -!- arubi_ [~ese168@unaffiliated/arubi] has joined #bitcoin-core-dev
17:21 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
17:25 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 245 seconds]
17:48 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-ntvjuvipyyezlzcr] has quit [Quit: Connection closed for inactivity]
17:48 -!- bityogi [~textual@208-104-143-200.brvd.dsl.dyn.comporium.net] has joined #bitcoin-core-dev
17:48 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
17:50 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
17:54 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
17:57 < PRab> Any idea why "./bin/gbuild -i --commit signature=v${VERSION} ../bitcoin/contrib/gitian-descriptors/gitian-win-signer.yml" is giving "fatal: ambiguous argument 'v0.12.0rc3':"?
17:58 < PRab> All of the other gitian stuff worked.
18:08 -!- bityogi [~textual@208-104-143-200.brvd.dsl.dyn.comporium.net] has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
18:10 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
18:10 < Luke-Jr> what is VERSION?
18:12 < PRab> echo ${VERSION}
18:12 < PRab> 0.12.0rc3
18:16 -!- wallet42 [~wallet42@rrcs-50-74-70-195.nyc.biz.rr.com] has quit [Quit: Leaving.]
18:19 < cfields> PRab: sigs aren't posted yet
18:20 < cfields> waiting to see if the new cert comes through
18:21 < PRab> cfields: I thought I was generating my own sigs. What sig needs to be posted?
18:21 < cfields> PRab: win-signer attaches the detached codesign payload to the binaries
18:21 < cfields> same as osx-signer
18:22 < PRab> Oh, gotcha. I didn't realize that what it was doing.
18:22 < Luke-Jr> jtimon: "A soft-fork BIP strictly requires a clear miner majority expressed by blockchain voting (eg, using BIP 9). In addition, if the economy seems willing to make a "no confidence" hard-fork (such as a change in proof-of-work algorithm), the soft-fork does not become Final for as long as such a hard-fork has potentially-majority support, or at most three months. Soft-fork BIPs may also set additional requirements for their adoption. 
18:22 < Luke-Jr> Because of the possibility of changes to miner dynamics, especially in light of delegated voting (mining pools), it is highly recommended that a supermajority vote around 95% be required by the BIP itself, unless rationale is given for a lower threshold."
18:22 < Luke-Jr> jtimon: is this clearer?
18:23 < PRab> I thought it was just signing the binary so that it could be checked before somebody preformed the windows signature. This is even cooler.
18:23 < PRab> Out of curiosity, where does the detached codesign payload live?
18:24 < PRab> In a git repo?
18:25 < cfields> PRab: https://github.com/bitcoin/bitcoin-detached-sigs/tree/0.12
18:26 < PRab> cfields: Ah, I had looked in there, but I looked at master.
18:27 < PRab> So until that is posted, it sounds like I can't do that part of the gitian build.
18:27 < PRab> No big deal. I can do it later.
18:27 -!- p15 [~p15@15.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-core-dev
18:28 < cfields> PRab: i sign, detach the sigs, and push them up, without posting the binaries anywhere. That way it's nearly guaranteed that the signer hasn't tampered with anything
18:28 < cfields> PRab: yep, this one's going to be delayed a bit. fingers crossed it should be taken care of soon.
18:28 < PRab> Yep, makes sense now. Thanks for all the hard work.
18:29 < cfields> np, sorry for the inconvenience
18:30 < Luke-Jr> cfields: btw, would you be interested in making sigs for Bitcoin LJR as well?
18:31 < cfields> Luke-Jr: sure, though tbh i'd rather put the effort into porting an osx signer
18:31 < cfields> fyi, win is already signed in linux. osx is the only hold-out
18:31 < Luke-Jr> cfields: well, I didn't see any trivial way to get keys to sign with :/
18:32 < cfields> Luke-Jr: oh, no, i wouldn't be comfortable signing with the same keys :)
18:34 < Luke-Jr> do you have an easy way to get another set? XD
18:35 < cfields> Luke-Jr: i'm honestly not sure what the requirements are. we'll be going down that path after 0.12 though, need to get new keys for Core. i can let you know how it goes
18:36 < Luke-Jr> cfields: ok. maybe if you get a convenient opportunity for two key-pairs, get one for LJR? ;)
18:36 < cfields> heh, sure
18:46 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Remote host closed the connection]
18:55 < jtimon> Luke-Jr: that's definitely clearer, but...
18:56 < jtimon> let's think for a moment about the sequence of events
18:57 -!- adam3us1 [~Adium@195.138.228.7] has joined #bitcoin-core-dev
18:57 -!- adam3us [~Adium@unaffiliated/adam3us] has quit [Read error: Connection reset by peer]
18:57 < jtimon> 1) controversial softfork gets activated
18:57 < jtimon> 2) some time
18:57 < jtimon> 3.a) asic-reset hardfork to revert 1
18:57 < jtimon> 3.b) there's not "economic consensus" to revert 1
18:58 < jtimon> ho much time is 2?
18:58 < jtimon> s/ho/how
18:58 < Luke-Jr> that's the "at most three months"
18:59 < Luke-Jr> perhaps I should also clarify that the Final soft-fork can still be moved to a Replaced status should it later gain consensus?
19:00 < jtimon> so if 3.a happens 6 months after 1, the softfork BIP proposing 1 will get to final?
19:00 < Luke-Jr> (maybe not; I guess that's implied in a hardfork anyway)
19:00 < jtimon> oh, I guess that would solve my time concern
19:00 < Luke-Jr> jtimon: Final and then Replaced
19:01 < jtimon> yep, if a softfork that gets to the final state can then be reverted to replaced if it's found to be controversial, then I guess my concern goes away
19:02 < Luke-Jr> What happens if the economy decides to hard-fork away from a controversial soft-fork, more than three months later?
19:02 < Luke-Jr> * The controversial soft-fork, in this circumstance, changes from Final to Replaced status to reflect the nature of the hard-fork replacing the previous (final) soft-fork.
19:02 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
19:02 < Luke-Jr> ^ sound good?
19:04 < jtimon> I would still really like to make uncontroversial soft/hard forks as similar as possible, since I believe philosohpically there's much more difference between controversial/uncontroversial than between soft/hard fork (the latter being just a time/technical/convenience advantage in softforks, but nothing fundamentally different for non-deployment concerns)
19:04 < Luke-Jr> we can't change the nature of the differences. :P
19:05 < jtimon> of course not, we can just change our terms and definitions
19:07 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
19:09 < jtimon> mhmm...so I was, I guess, previously asking that only uncontroversial changes could get to the final state (neither controversial soft nor hard should ever get to final), but you propose that instead controversial softforks can get to final and then reverted to replaced by a hardfork
19:10 < Luke-Jr> even controversial hardforks can get to Final, provided they have de facto destroyed the dissent
19:10 < Luke-Jr> (not to say they *should*..)
19:10 < jtimon> mmhmm, can a controversial hardfork be "replaced" by another controversial hardfork? how does this all look when there's 8 controversial hardforks living in parallel?
19:11 < Luke-Jr> everyone needs to be using the hardforked rules to get to Final
19:11 < Luke-Jr> a controversial hardfork gets there, by forcing everyone else to use its rules
19:12 < jtimon> ok, so if at one point two controversial hardforks coexist (that is, the controversial hardfork and the no-hardfork ruleset) there will never be a final hardfork again?
19:13 < jtimon> no hardfork (controversial or not) can force any user to validate a particular ruleset
19:14 < Luke-Jr> I would think users of a non-Final hard-fork do not count toward subsequent hard-fork proposals
19:15 < Luke-Jr> since they're no longer using Bitcoin
19:17 < jtimon> you said a hardfork is only final if the dissenting branch died, if two branches coexist forever, both of them are non-final forever and this no subsequent hardfork proposal count for any of the two branches!
19:18 < Luke-Jr> hmm
19:18 < jtimon> let's bring my canonical example: let's say some users suddenly decide bitcoin should have 5% annual demurrage
19:18 < Luke-Jr> I don't see a solution for that hypothetical :P
19:19 < jtimon> and we have 2 branches that live forever (let's call them bitcoin and freifork respectively)
19:20 < Luke-Jr> no
19:20 < Luke-Jr> the original is not a branch
19:21 < jtimon> the recommendation in bip99 should be that if freiforkers know beforehand the two branches will never merge, they should consider starting an altcoin instead of a controversial hardfork
19:21 < Luke-Jr> no difference
19:22 < jtimon> but there's theoretically cases for a legitimate controversial hardfork (asic-reset for starters)
19:23 < jtimon> yes, there's a difference: an altcoin gives you far more parameter choosing flexibility (say, you deeply believe that 100 is a more round number than 21 or whatever)
19:23 < Luke-Jr> asic-reset isn't controversial, and still needs consensus
19:24 < Luke-Jr> a non-consensus hardfork that never becomes Final, is literally an altcoin
19:25 < jtimon> Luke-Jr: I already admited we disagree on whether an asic-reset hardfork is intrinsically controversial (as bip99 indicates) or not (as you believe), let's please agree to disagree on that
19:26 < Luke-Jr> well, then don't try to use it as a premise :p
19:26 < jtimon> well the premise in bip99 is that uncontroversial things require bip9 regardless of them being softforks or hardforks
19:27 < Luke-Jr> ewww
19:27 < Luke-Jr> hardforks should never use miner voting :<
19:27 < Luke-Jr> unless maybe it's super clear that miners are only indicating economic consensus
19:27 < jtimon> because "uncontroversial" always means "uncontroversial" (by any defintion), no matter how long you have to wait to deploy it for practical purposes
19:28 < Luke-Jr> ie, they'd manually set the vote and not merely run software supporting it
19:29 < jtimon> Luke-Jr: "hardforks should never use miner voting" as you hopefully know already, bip99 (and I believe petertodd) directly contradicts this, modulo s/miner voting/miner upgrade coordination/
19:30 < Luke-Jr> I have no read BIP 99 yet. Remind me to oppose it I guess >_<
19:31 < Luke-Jr> unless the modulo there changes it
19:31 < jtimon> would you agree that "mining voting" is a confusing term that leads people to talk about "hashing power democracy" and other confusing concepts?
19:31 < Luke-Jr> shrug
19:32 < Luke-Jr> the problem is trying to use a consensus-establishing system for something it cannot establish consensus on
19:32 < Luke-Jr> not the terminology
19:32 < jtimon> Luke-Jr: "I have no read BIP 99 yet. Remind me to oppose it I guess" shrug maybe you should have read it before writting your own
19:32 < Luke-Jr> mine has different goals than BIP 99
19:32 < Luke-Jr> BIP 99 is, as I understand it, aimed at successful deployment of softforks and hardforks
19:32 < jtimon> Luke-Jr: how do you know if you haven't read bip99 yet?
19:33 < Luke-Jr> I did skim it :P
19:33 < Luke-Jr> am I wrong?
19:35 < jtimon> not on the goals, I would complete it with "and deploy an uncontroversial hardfork" and classify not-recommended/unsuccesful soft/hard-forks as well"
19:35 < Luke-Jr> I do think you should split the HF proposal out to another BIP, FWIW
19:36 < jtimon> but really, I was assuming that you had read it all along, that could have probably saved us a lot of terminology discussion...
19:36 < Luke-Jr> I probably should go read it.
19:38 < Luke-Jr> (I had mostly forgotten it even existed when I started this one)
19:39 < jtimon> Luke-Jr: thanks, that's useful feedback I realized conflating "let's clasify uncontroversial hardforks with all the rest of theorethically potential hardforks" and "and let's deploy one of those uncontroversial hardforks, what was the point of putting them in context otherwise" is potentially confusing: I will reaplace the code entire code section with a link to another bip draft
19:40 < jtimon> to reiterate, having a bip in draft state for an undefined amount of time is right, right?
19:41 < Luke-Jr> ?
19:41 < jtimon> unless someone complains that it should move to replaced or something, obviously
19:42 < jtimon> last question: is it fine if bip99 stays as a darft while I wait to rebase the informational part on top of yours and move the code/hardfork-proposal part to a different bip to be linked from this one?
19:43 < jtimon> (without knowing when any of those two things may happen)
19:43 < Luke-Jr> jtimon: I don't see why not
19:43 < Luke-Jr> Rejected status has a timeout of 3 years
19:45 < jtimon> oh, I missed that, "not touched in 3 years" -> rejected, I think I have time or it will be replaced by some other first hardfork by that time, great
19:47 -!- adnn_ [adnn@gateway/vpn/mullvad/x-bqhhjgktyythjmcn] has joined #bitcoin-core-dev
19:47 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
19:47 < jtimon> Luke-Jr: thanks for answering many questions, this was really helpful (but could have been even more productive if you had read bip99)
19:48 < Luke-Jr> jtimon: np, hopefully I'll get them added to the BIP's Rationale so others get the answers too ☺
19:48 < Luke-Jr> I'll try to read BIP 99 soon, unless you'd rather I wait for you to split it?
19:51 < jtimon> no, the part to be splitted is just the code section (and its respective references)
19:51 < Luke-Jr> k
19:52 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has quit [Ping timeout: 250 seconds]
19:52 < jtimon> please read it, I think you will understand some of my points better
19:52 < Luke-Jr> I will
19:56 < jtimon> in fact the next main change I had plannned was just to add "use a negative block version number after activation" to both of the hardfork recommendations (as explained in the talk), plus incorporate some of the feedback (like incorporate the "let's keep 50 btc subsidy forever" as an example of a failed controversial hardfork)
19:56 < Luke-Jr> eh, negative? just don't interpret it as signed and ignore the first bit :P
19:57 < Luke-Jr> or better yet, set the first bit on the first block, and make a consensus rule that it be clear from that point forward..
19:57 < Luke-Jr> so it can be reused
19:57 < Luke-Jr> frankly, it's pretty dumb that versionbits considers it as a number at all at this point
19:57 < jtimon> yeah, "negative" or "first bit active" mean the seam here: non-upgraded nodes will preceive it as invalid [unless they have a more advanced warning system backported]
19:58 < Luke-Jr> I should assign a number for biprevised so I don't need to keep saying "my BIP" for it..
19:59 < jtimon> in any case we both know what bit we're talking about: the one that would old nodes think a given block is invalid
19:59 < jtimon> Luke-Jr: ack on number, or at least just open a PR to the bips repo
19:59 < Luke-Jr> jtimon: can't open a PR until GitHub fixes their crap :/
19:59 < Luke-Jr> my repo is somehow de-linked so it can't PR to the main on
19:59 < Luke-Jr> one*
20:00 < jtimon> github crap?
20:00 < Luke-Jr> jtimon: try opening a PR from my repo to the main repo, and you'll find it's impossible :<
20:00 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer]
20:01 < jtimon> mhmm, I believe destroying your repo, forking bitcoin/bips again, etc would solve it
20:01 < Luke-Jr> yes, but I don't want to do that :p
20:01 < Luke-Jr> https://github.com/bitcoin/bips/pull/314 and https://github.com/bitcoin/bips/pull/315 could use more reviews btw
20:02 -!- justanotheruser [~Justan@24.219.72.137] has joined #bitcoin-core-dev
20:03 -!- Chris_Stewart_5 [~Chris_Ste@104.156.228.195] has quit [Ping timeout: 250 seconds]
20:03 < jtimon> fair enough, but other people need to open a PR before getting a bip number, someone will accuse you of abusing your power :p
20:03 -!- justanotheruser [~Justan@24.219.72.137] has quit [Changing host]
20:03 -!- justanotheruser [~Justan@unaffiliated/justanotheruser] has joined #bitcoin-core-dev
20:03 < Luke-Jr> jtimon: that's not true, people have been assigned numbers without a PR many times
20:04 < Luke-Jr> and I just assigned BIP 74 pre-PR a week or so ago, so that's certainly not changed since I became editor either :p
20:04 < jtimon> oh, I thought the new modus operandis was PR before number
20:05 < jtimon> I was just teasing anyway, assign yourself a number, but at some point you will need to open a PR as well
20:06 < Luke-Jr> anyway, since it's dealing specifically with the BIP process, I was thinking BIP 2
20:06 < Luke-Jr> yes, I am nagging GitHub support to fix the PR stuff
20:06 < jtimon> Luke-Jr: I think bip 2 would be most appropriate
20:07 < jtimon> Luke-Jr: just curious, has the github bug anything to do with the fact that bips is not a "base project" but a fork of ptodd's?
20:08 < jtimon> that way we will be able to say "read bip 1 and 2..."
20:09 < Luke-Jr> jtimon: a few weeks ago it seems they delinked genjix/bips from the rest
20:11 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has quit [Read error: Connection reset by peer]
20:11 -!- lightningbot` [supybot@2400:8900::f03c:91ff:fedf:3a06] has joined #bitcoin-core-dev
20:11 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
20:12 -!- lightningbot [supybot@2400:8900::f03c:91ff:fedf:3a06] has quit [Ping timeout: 260 seconds]
20:12 -!- zmanian_ [sid113594@gateway/web/irccloud.com/x-pfgahnjwyncrhxcs] has quit [Ping timeout: 260 seconds]
20:12 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-ywzjlfvonxlhtivl] has quit [Ping timeout: 260 seconds]
20:12 -!- windsok_ [~windsok@45.63.59.8] has quit [Quit: No Ping reply in 180 seconds.]
20:14 -!- jl2012 [uid133844@gateway/web/irccloud.com/x-uyvqnkugqlorfpkb] has joined #bitcoin-core-dev
20:14 -!- windsok [~windsok@45.63.59.8] has joined #bitcoin-core-dev
20:14 -!- morcos [~morcos@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 260 seconds]
20:14 -!- morcos [~morcos@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
20:16 -!- mr_burdell_ [~mr_burdel@bounce.cryptolabs.net] has joined #bitcoin-core-dev
20:17 -!- zmanian_ [sid113594@gateway/web/irccloud.com/x-ynzqmhdrqasdrfoj] has joined #bitcoin-core-dev
20:19 -!- mr_burdell [~mr_burdel@unaffiliated/mr-burdell/x-7609603] has quit [Ping timeout: 260 seconds]
20:19 -!- Guest50070 [~s1w@128.199.100.16] has quit [Ping timeout: 260 seconds]
20:19 -!- roasbeef [~root@104.131.26.124] has quit [Ping timeout: 260 seconds]
20:19 -!- mr_burdell_ is now known as mr_burdell
20:19 -!- petertodd [~pete@ec2-52-5-185-120.compute-1.amazonaws.com] has quit [Ping timeout: 263 seconds]
20:19 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has quit [Ping timeout: 263 seconds]
20:19 -!- Lightsword [~Lightswor@107.170.253.193] has quit [Ping timeout: 263 seconds]
20:19 < jtimon> Luke-Jr: what do you mean? the parent of petertodd/bips was genjix/bips in github?
20:19 < Luke-Jr> indeed
20:19 -!- Lightsword [~Lightswor@2604:a880:1:20::1d3:9001] has joined #bitcoin-core-dev
20:19 -!- mr_burdell is now known as Guest97100
20:19 -!- devrandom [~devrandom@unaffiliated/niftyzero1] has joined #bitcoin-core-dev
20:20 -!- s1w [~s1w@2400:6180:0:d0::4e1:5001] has joined #bitcoin-core-dev
20:20 -!- roasbeef [~root@104.131.26.124] has joined #bitcoin-core-dev
20:20 -!- petertodd [~pete@ec2-52-5-185-120.compute-1.amazonaws.com] has joined #bitcoin-core-dev
20:20 -!- s1w is now known as Guest51729
20:20 -!- petertodd is now known as Guest60961
20:20 < jtimon> I see
20:22 -!- frankenmint [~frankenmi@174-25-38-39.ptld.qwest.net] has joined #bitcoin-core-dev
20:23 < jtimon> can't someone create the PR while giving you the rights to force push in it?
20:25 < jtimon> I believe btcdrak somehow took over maaku's bip68/bip112 opened bips with no problem, maybe someone else can create it and somehow transfer control to you or something (random thoughts, who knows how github works inside for this)
20:32 < Luke-Jr> sure, but no big deal
20:32 < Luke-Jr> I expect resolution in a few days
20:40 -!- adam3us1 [~Adium@195.138.228.7] has quit [Ping timeout: 250 seconds]
21:07 -!- adnn__ [~adnn@cpe-158-222-198-108.nyc.res.rr.com] has joined #bitcoin-core-dev
21:08 -!- adnn_ [adnn@gateway/vpn/mullvad/x-bqhhjgktyythjmcn] has quit [Ping timeout: 240 seconds]
21:22 -!- adam3us [~Adium@unaffiliated/adam3us] has joined #bitcoin-core-dev
21:35 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
21:35 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has quit [Ping timeout: 256 seconds]
21:36 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
21:58 -!- Amnez777 [~Amnez777@37.157.216.184] has joined #bitcoin-core-dev
21:58 -!- Amnez777 [~Amnez777@37.157.216.184] has quit [Max SendQ exceeded]
21:58 -!- Amnez777 [~Amnez777@37.157.216.184] has joined #bitcoin-core-dev
21:58 -!- Amnez777 [~Amnez777@37.157.216.184] has quit [Max SendQ exceeded]
21:59 -!- Amnez777 [~Amnez777@37.157.216.184] has joined #bitcoin-core-dev
21:59 -!- Amnez777 [~Amnez777@37.157.216.184] has quit [Changing host]
21:59 -!- Amnez777 [~Amnez777@unaffiliated/amnez777] has joined #bitcoin-core-dev
22:07 -!- go1111111 [~go1111111@104.232.116.217] has quit [Ping timeout: 240 seconds]
22:21 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-hmyxqipsaasogtbv] has joined #bitcoin-core-dev
22:21 -!- go1111111 [~go1111111@104.200.154.96] has joined #bitcoin-core-dev
23:00 -!- zibbo [~zibbo@static.173.197.47.78.clients.your-server.de] has quit [Quit: Lost terminal]
23:48 -!- dcousens [~anon@c110-22-219-15.sunsh4.vic.optusnet.com.au] has joined #bitcoin-core-dev
23:55 < GitHub71> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/eb331794a22b...898fedf42fdc
23:55 < GitHub71> bitcoin/master c77c662 kirkalx: peers.dat, banlist.dat recreated when missing
23:55 < GitHub71> bitcoin/master 898fedf Wladimir J. van der Laan: Merge #7458: [Net] peers.dat, banlist.dat recreated when missing...
23:55 < GitHub150> [bitcoin] laanwj closed pull request #7458: [Net] peers.dat, banlist.dat recreated when missing (master...master) https://github.com/bitcoin/bitcoin/pull/7458