--- Day changed Sat Jan 09 2016
00:03 -!- jtimon [~quassel@103.red-80-26-235.adsl.dynamic.ccgg.telefonica.net] has quit [Ping timeout: 272 seconds]
00:34 < arubi> anyone at all using segnet?  I can't find any nodes to connect to.  would appreciate an ipv4\tor host I can connect to.  thanks.
00:52 < btcdrak> arubi: sorted in PM
00:52 < arubi> oh, right ^
01:32 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
01:33 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
01:42 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
01:53 -!- trippysalmon [rob@2001:984:6466:0:51d:b5ab:ab61:bed8] has joined #bitcoin-core-dev
01:54 -!- tripleslash_k [~triplesla@unaffiliated/imsaguy] has quit [Ping timeout: 246 seconds]
02:02 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
02:03 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
02:06 -!- jtimon [~quassel@103.red-80-26-235.adsl.dynamic.ccgg.telefonica.net] has joined #bitcoin-core-dev
03:34 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Quit: Leaving.]
03:40 -!- Alopex [~bitcoin@cyber.dealing.ninja] has quit [Remote host closed the connection]
03:41 -!- Alopex [~bitcoin@cyber.dealing.ninja] has joined #bitcoin-core-dev
03:58 -!- jtimon [~quassel@103.red-80-26-235.adsl.dynamic.ccgg.telefonica.net] has quit [Ping timeout: 256 seconds]
04:25 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
04:26 -!- btccharm [~02@107.150.94.8] has joined #bitcoin-core-dev
04:50 -!- murch [~murch@p4FDB776C.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
04:52 -!- btccharm [~02@107.150.94.8] has quit [Ping timeout: 264 seconds]
05:04 -!- murch [~murch@p4FDB776C.dip0.t-ipconnect.de] has quit [Quit: Leaving.]
05:13 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has joined #bitcoin-core-dev
06:28 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has quit [Quit: This computer has gone to sleep]
06:28 -!- Chris_Stewart_5 [~Chris_Ste@173-26-115-141.client.mchsi.com] has joined #bitcoin-core-dev
06:31 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
06:42 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-core-dev
06:49 -!- arowser [~quassel@106.120.101.38] has quit [Ping timeout: 265 seconds]
06:50 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
06:50 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
06:50 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Client Quit]
06:58 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
06:58 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
07:17 -!- arowser [~quassel@106.120.101.38] has quit [Read error: Connection reset by peer]
07:17 -!- arowser [~quassel@106.120.101.38] has joined #bitcoin-core-dev
07:27 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Ping timeout: 265 seconds]
07:30 < GitHub197> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/9de541a9c95a...93ca5a35b045
07:30 < GitHub197> bitcoin/master 82a0ce0 Suhas Daftuar: Add race-condition debugging tool to mininode
07:30 < GitHub197> bitcoin/master 168915e Suhas Daftuar: Eliminate race condition in sendheaders.py test...
07:30 < GitHub197> bitcoin/master 93ca5a3 Wladimir J. van der Laan: Merge pull request #7308...
07:30 < GitHub163> [bitcoin] laanwj closed pull request #7308: [Tests] Eliminate intermittent failures in sendheaders.py (master...fix-sendheaders) https://github.com/bitcoin/bitcoin/pull/7308
07:32 < GitHub56> [bitcoin] laanwj pushed 1 new commit to 0.12: https://github.com/bitcoin/bitcoin/commit/d513405cb71425dd615e88aca4f6222e08d150a5
07:32 < GitHub56> bitcoin/0.12 d513405 Suhas Daftuar: [Tests] Eliminate intermittent failures in sendheaders.py...
07:34 < GitHub3> [bitcoin] laanwj pushed 3 new commits to 0.11: https://github.com/bitcoin/bitcoin/compare/5f09cda0bf4c...00aefccb126f
07:34 < GitHub91> [bitcoin] laanwj closed pull request #7259: [0.11] dbwrapper: Detect obfuscation (0.11...MarcoFalke-2015-dbWrapperObfuscation-0.11) https://github.com/bitcoin/bitcoin/pull/7259
07:34 < GitHub3> bitcoin/0.11 fa24941 MarcoFalke: [dbwrapper] Detect obfuscation
07:34 < GitHub3> bitcoin/0.11 fa3cb49 MarcoFalke: [init] Fix typo
07:34 < GitHub3> bitcoin/0.11 00aefcc Wladimir J. van der Laan: Merge pull request #7259...
07:43 -!- MarcoFalke [05c7b6cb@gateway/web/cgi-irc/kiwiirc.com/ip.5.199.182.203] has joined #bitcoin-core-dev
07:45 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
07:46 < MarcoFalke> Luke-Jr, even though a merge commit (or rebase) may appear trivial, I don't think we should put the burden on laanwj to go through that. (Not to mention it is hard to verify if any conflicts were solved during the final merge into bitcoin/bitcoin)
07:47 < wumpus> right - I don't do non-trivial merge commits
07:47 < wumpus> (except in some rare cases, but in general you should keep your own work up to date)
07:50 < MarcoFalke> wumpus, 
07:50 < MarcoFalke> keypoolrefill is quite expensive, so I think a sleep(1) is enough. Let's make it 1.1 to get another 10 % overhead?
07:54 < wumpus> sure
07:56 < wumpus> I just don't want to introduce false positives. I've had some bad experiences at a previous employer where a bit of extra load on the test bench caused the test results to light up like a christmas tree, because of tightly timed tests, sending people to chase after nothing every time
07:58 < wumpus> using mock time would be ideal, but libevent will ignore that anyway it's a non-starter :)
07:59 < Luke-Jr> MarcoFalke: that's not what I said. :p  *when* someone is ready to merge, they just need to ping me and I will do the merge
08:11 < wumpus> Luke-Jr: can you do your thing for #7081 then?
08:12 < Luke-Jr> yep, sec
08:18  * Luke-Jr peers at github
08:19 < Luke-Jr> wumpus: ok done
08:22 < Luke-Jr> wumpus: shall I resubmit for 0.12 also?
08:24 -!- aj_ is now known as aj
08:28 -!- Chris_Stewart_5 [~Chris_Ste@173-26-115-141.client.mchsi.com] has quit [Ping timeout: 260 seconds]
08:42 -!- Chris_Stewart_5 [~Chris_Ste@104.156.228.192] has joined #bitcoin-core-dev
08:44 -!- jtimon [~quassel@103.red-80-26-235.adsl.dynamic.ccgg.telefonica.net] has joined #bitcoin-core-dev
08:45 < MarcoFalke> Luke-Jr, why twice?
08:45 < MarcoFalke> Couldn't you just merge 901b01d674031f9aca717deeb372bafa160a24af?
08:45 < MarcoFalke> It should slide into master and 0.12, regardless
08:45 < Luke-Jr> MarcoFalke: O.o?
08:47 < Luke-Jr> wrong commithash?
08:47 < MarcoFalke> did you copy the `?`
08:49 < Luke-Jr> no
08:53 < Luke-Jr> MarcoFalke: got it thx
09:00 < wumpus> Luke-Jr: I think so - with a merge commiit in it it's harder to rebase/cherry-pick
09:01 < GitHub123> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/93ca5a35b045...dd1304ec216c
09:01 < GitHub123> bitcoin/master 45b8e27 Luke Dashjr: -bytespersigop option to additionally limit sigops in transactions we relay and mine
09:01 < GitHub123> bitcoin/master fdc202f Luke Dashjr: Merge branch bytespersigop
09:01 < GitHub123> bitcoin/master dd1304e Wladimir J. van der Laan: Merge pull request #7081...
09:01 < GitHub185> [bitcoin] laanwj closed pull request #7081: -bytespersigop option to additionally limit sigops in transactions we relay and mine (master...bytespersigop) https://github.com/bitcoin/bitcoin/pull/7081
09:03 < Luke-Jr> wumpus: k, https://github.com/bitcoin/bitcoin/pull/7323
09:03 < GitHub115> [bitcoin] luke-jr opened pull request #7323: 0.12: Backport -bytespersigop option (0.12...bytespersigop-0.12.x) https://github.com/bitcoin/bitcoin/pull/7323
09:04 < wumpus> I tried to merge fdc202f into 0.12 but that gets a merge conflict in main.cpp
09:05 < wumpus> ok
09:05 < Luke-Jr> yeah, looks like 0.12 picked up the conflicting change as a cherry-pick or something
09:05 < Luke-Jr> btw, ACK/NACK on importing 0.11's test_framework to 0.10 so we can run newer tests against it?
09:05 < btcdrak> luke-jr, wumpus: another difficulty with merging topic branches back into master. Topic branches are just better rebased: it's less hassle all round
09:06 < wumpus> Luke-Jr: I don't care about 0.10 anymore
09:06 < Luke-Jr> btcdrak: disagree; see the links :p
09:06 < wumpus> Luke-Jr: but fine with me, if you want to put the effort in
09:06 < Luke-Jr> wumpus: ok, so I'll just maintain it myself going forward?
09:07 < Luke-Jr> should I move the branch to another repo like I used to, continue to go through PRs, or would it make sense to give me push access just for that branch (not sure if GitHub can enforce)?
09:07 < sipa> wumpus: i think that should be announced then
09:07 < Luke-Jr> sipa: well, I'll continue to be maintaining it for now either way
09:07 < wumpus> sipa: well if Luke-Jr wants to pick it up that's great
09:08 < sipa> wumpus: i do think we need some clearly visible policy about which versions the bitcoin core project maintains and will issue bug fix releases for
09:08 < wumpus> I just don't have the time to maintain lots of back versions
09:08 < sipa> whether that's decided on an ad-hoc basis 
09:08 < wumpus> but if someone else wants to do that that's great
09:09 < wumpus> well in the case of a critical problem I'm sure we can roll a 0.10 release
09:09 < Luke-Jr> sipa: can go on a website somewhere maybe? a table with supported/unsupported versions?
09:09 < sipa> wumpus: don't get me wrong, i completely agree with not backporting in perpetuity, but i think it is not obvious to the world
09:10 < wumpus> but the focus has always been last release + the previous major release, so right now that'ts 0.12 and 0.11
09:10 < wumpus> (well, almost)
09:11 < wumpus> except in the case of critical security issues
09:11 < sipa> ok, what about "After 0.X's branching, 0.X-1 will receive all bug fixes, and 0.X-2 only critical bug fixes"
09:11 < wumpus> makes sense to me
09:11 < wumpus> except if someone wants to put more work into it like Luke-Jr
09:11 < wumpus> but that's all I'm willing to do, yes
09:12 < Luke-Jr> makes sense to phrase what sipa said as a "commitment"
09:12 < Luke-Jr> anything beyond that is not guaranteed
09:12 < sipa> well it's not just about you, but about we as a team commit to doing :)
09:12 < cfields> wumpus: just heard back from Travis. They'll be enabling caching for their new infrastructure later this month. That gets us Trusty, docker, and caching.
09:12 < sipa> cfields: nice
09:12 < wumpus> sipa: I know, but I can only speak for myself
09:12 < Luke-Jr> cfields: that requires us to switch to the container-based stuff though, right?
09:13 < wumpus> cfields: nice!
09:13 < cfields> Luke-Jr: nope, sudo enabled too. So our current config should just work (tm)
09:13 < Luke-Jr> sipa: one thing missing in that is with regard to softforks/hardforks
09:13 < Luke-Jr> cfields: oh, nice
09:13 < cfields> so, I think it makes sense to hold out for that, rather than hacking around too much for now
09:13 < sipa> Luke-Jr: well there is a statement around that now on the website
09:13 < wumpus> cfields: sure
09:14 < sipa> Luke-Jr: but it's not clearly tied to releases
09:14 < wumpus> cfields: good to hear it's 'later this month' 
09:14 < wumpus> cfields: makes no sense to hurry more than that
09:14 < Luke-Jr> sipa: once 0.12 is released, even 0.11.x won't likely get sufficient testing, so maybe it's better not to tie it to releases
09:15 < Luke-Jr> vague commitment + current status of each branch, seems perhaps ideal?
09:16 < MarcoFalke> You mean as a table on the website?
09:16 < Luke-Jr> right
09:16 < MarcoFalke> makes sense
09:16 < wumpus> yes makes sense
09:17 < GitHub143> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/d513405cb714...a344880e6ae3
09:17 < GitHub143> bitcoin/0.12 5b144b7 Luke Dashjr: Merge branch bytespersigop
09:17 < GitHub143> bitcoin/0.12 a344880 Wladimir J. van der Laan: Merge pull request #7323...
09:17 < GitHub48> [bitcoin] laanwj closed pull request #7323: 0.12: Backport -bytespersigop option (0.12...bytespersigop-0.12.x) https://github.com/bitcoin/bitcoin/pull/7323
09:17 < btcdrak> sipa: wumpus: we should have a maintenance cycle listed somewhere then people know when EOL comes.
09:21 < MarcoFalke> And hardcode the EOL into the software?
09:21 < MarcoFalke> So a notification could pop up
09:25 < Luke-Jr> MarcoFalke: well, EOLing a specific release vs branch is another thing
09:26 < Luke-Jr> an automatic internal alert might not be a bad idea, but we need to be careful not to *force* upgrades too
09:26 < Luke-Jr> and ideally, it'd be best if people didn't all upgrade at the same time
09:27 < Luke-Jr> specific releases tend to be EOL'd unpredictably anyway
09:27 < Luke-Jr> ie, "when there is a notable thing to fix"
09:28 < wumpus> hardcoding it into the software that goes too far IMO
09:28 < wumpus> people are free to upgrade or not upgrade
09:28 < MarcoFalke> They may not be aware their sofware is outdated?
09:28 < wumpus> but having EOL status on the website is a great idea
09:29 < Luke-Jr> MarcoFalke: then they can check..
09:29 < Luke-Jr> MarcoFalke: their software won't know it's outdated either
09:30 < Luke-Jr> still, it might be good to put a time limit for "hardfork required by now" stuff .. like 2036 :p
09:37 < Luke-Jr> someone with push access want to: git tag branch-0.12 3cd836c1d855b92e7c73ab31979f471c4f8dad68 # ? :P
09:41 < GitHub10> [bitcoin] luke-jr opened pull request #7324: doc/bips: Document BIP 125 support (master...bips_rbf) https://github.com/bitcoin/bitcoin/pull/7324
09:59 -!- PRab_ [~chatzilla@68.34.102.231] has quit [Quit: ChatZilla 0.9.92 [Firefox 43.0.3/20151223140742]]
10:22 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
10:24 < afk11> Anyone running segnet that I can connect up to? and a pool/faucet? 
10:29 < sipa> afk11: we're going to reset the chain soon (1-2 days, i expect), and then invite more people to connect
10:34 -!- MarcoFalke [05c7b6cb@gateway/web/cgi-irc/kiwiirc.com/ip.5.199.182.203] has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
10:36 -!- Thireus [~Thireus@vps-92.197.170.217.stwvps.net] has quit [Quit: Leaving.]
10:39 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Quit: .]
10:41 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
10:43 < moli> sipa: hi, can segwit be tested in windows?
10:48 < sipa> moli: i guess we can do test builds for windows
10:49 < moli> sipa: that would be great, thank you
10:55 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
11:06 -!- JackH [~Jack@host-80-43-143-228.as13285.net] has joined #bitcoin-core-dev
11:22 -!- afk11 [~afk11@unaffiliated/afk11] has quit [Quit: Leaving.]
11:24 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
11:32 -!- afk11 [~afk11@unaffiliated/afk11] has joined #bitcoin-core-dev
11:36 -!- SmiteMeSmith [~SmiteMeSm@WLLDON1606W-LP140-01-2925330739.dsl.bell.ca] has joined #bitcoin-core-dev
12:06 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
12:06 -!- AtashiCon [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
12:23 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
12:41 < afk11> sipa:  had to step out, but thanks for that. 
12:47 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Quit: laurentmt]
12:56 -!- orbiting [~orbiting@71-19-183-102.dedicated.allstream.net] has joined #bitcoin-core-dev
13:21 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev
13:22 -!- shiinko [~shiinko@151.80.78.204] has left #bitcoin-core-dev ["AndroIRC - Android IRC Client ( http://www.androirc.com )"]
13:31 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
13:32 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
13:39 -!- trippysalmon [rob@2001:984:6466:0:51d:b5ab:ab61:bed8] has quit [Ping timeout: 250 seconds]
13:42 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
14:18 -!- brg444 [18257df2@gateway/web/freenode/ip.24.37.125.242] has quit [Quit: Page closed]
14:22 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:46 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has joined #bitcoin-core-dev
14:48 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
14:48 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
14:51 -!- jtimon [~quassel@103.red-80-26-235.adsl.dynamic.ccgg.telefonica.net] has quit [Ping timeout: 246 seconds]
14:52 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has quit [Ping timeout: 264 seconds]
15:00 -!- randy-waterhouse [~kiwigb@opentransactions/dev/randy-waterhouse] has joined #bitcoin-core-dev
15:03 -!- neilf_ [~neilf@40.121.88.219] has joined #bitcoin-core-dev
15:06 -!- neilf [~neilf@40.121.88.219] has quit [Ping timeout: 265 seconds]
15:28 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
15:46 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:47 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
15:47 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
15:52 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
15:53 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
15:53 -!- orbiting [~orbiting@71-19-183-102.dedicated.allstream.net] has quit [Quit: Leaving]
16:03 -!- Guyver2 [~Guyver2@guyver2.xs4all.nl] has quit [Quit: :)]
16:07 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
16:25 -!- dgenr8 [~dgenr8@unaffiliated/dgenr8] has joined #bitcoin-core-dev
16:29 -!- CoffeeCup [~IceChat9@108-254-160-61.lightspeed.livnmi.sbcglobal.net] has joined #bitcoin-core-dev
16:41 -!- CoffeeCup [~IceChat9@108-254-160-61.lightspeed.livnmi.sbcglobal.net] has quit [Quit: For Sale: Parachute. Only used once, never opened, small stain.]
16:42 -!- d_t [~textual@c-24-4-96-213.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
16:50 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has joined #bitcoin-core-dev
16:51 -!- laurentmt [~Thunderbi@128-79-141-196.hfc.dyn.abo.bbox.fr] has quit [Client Quit]
17:00 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
17:00 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
17:24 -!- d_t [~textual@c-24-4-96-213.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:33 -!- Chris_Stewart_5 [~Chris_Ste@104.156.228.192] has quit [Ping timeout: 256 seconds]
17:34 < afk11> What would be the plan for the OP_CSV softfork? I notice the block v5 and the script verification flag is shared with segwit. They could be soft-forked serially in v5, but perhaps different script flags? 
17:39 < btcdrak> afk11: that'll get resolved at merge. 
17:41 < afk11> btcdrak: do we know if there'll be two soft forks? TBD?
17:41 < btcdrak> afk11: TDB. I personally see no reason not to combine them as one.
17:49 -!- d_t [~textual@c-24-4-96-213.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
18:19 -!- AtashiCon [arnavion@unaffiliated/arnavion] has quit [Disconnected by services]
18:19 -!- Arnavion3 [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
18:19 -!- Arnavion3 is now known as AtashiCon
18:20 -!- d_t [~textual@c-24-4-96-213.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:26 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
18:37 -!- btccharm [~02@107.150.94.10] has joined #bitcoin-core-dev
18:50 -!- JackH [~Jack@host-80-43-143-228.as13285.net] has quit [Ping timeout: 264 seconds]
18:50 -!- tripleslash [~triplesla@unaffiliated/imsaguy] has joined #bitcoin-core-dev
18:54 -!- jcorgan|away is now known as jcorgan
18:56 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
18:58 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
19:01 < Luke-Jr> sipa: #7217.. "@sipa and I went back and traced the blame for that line…it looks like when the corruption possible flag was set for this case, it was, indeed needed as it was checked before the merkle tree was checked. As the order has now changed we do, indeed, no longer need this check."
19:01 < Luke-Jr> sipa: so you can confirm the order in 0.10 is safe for that?
19:04 < sipa> Luke-Jr: i need to look, thanks for reminding me of that
19:08 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-hbmxghgcknsejwnt] has quit [Quit: Connection closed for inactivity]
19:23 -!- belcher [~user@unaffiliated/belcher] has quit [Ping timeout: 240 seconds]
20:00 -!- adam3us [~Adium@195.138.228.8] has quit [Quit: Leaving.]
20:06 -!- xiangfu [~xiangfu@123.125.212.71] has joined #bitcoin-core-dev
20:09 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has joined #bitcoin-core-dev
20:14 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:22 -!- Cory [~C@unaffiliated/cory] has quit [Ping timeout: 256 seconds]
20:24 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
20:25 -!- Cory [~C@unaffiliated/cory] has joined #bitcoin-core-dev
20:41 -!- zookolaptop [~user@2601:281:8001:26aa:3497:5ba3:9f3c:cb4e] has joined #bitcoin-core-dev
20:46 -!- NicolasDorier [uid129442@gateway/web/irccloud.com/x-jtytiycxyqddiyiv] has joined #bitcoin-core-dev
21:00 -!- adam3us [~Adium@37.75.38.22] has joined #bitcoin-core-dev
21:07 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
21:07 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
21:14 -!- adam3us [~Adium@37.75.38.22] has quit [Quit: Leaving.]
21:27 -!- brg444 [415ce066@gateway/web/freenode/ip.65.92.224.102] has quit [Ping timeout: 252 seconds]
21:30 -!- xiangfu [~xiangfu@123.125.212.71] has quit [Remote host closed the connection]
22:36 -!- p15 [~p15@112.91.145.64.client.static.strong-tk2.bringover.net] has joined #bitcoin-core-dev
22:59 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Remote host closed the connection]
23:00 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
23:25 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:32 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
23:40 -!- zookolaptop [~user@2601:281:8001:26aa:3497:5ba3:9f3c:cb4e] has quit [Ping timeout: 240 seconds]
23:48 -!- cjcj [2e3b026a@gateway/web/freenode/ip.46.59.2.106] has joined #bitcoin-core-dev
23:58 -!- d_t [~textual@c-98-234-64-218.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]