12016-06-21T00:04:07 *** Chris_Stewart_5 has quit IRC
22016-06-21T00:05:16 *** alpalp has joined #bitcoin-core-dev
32016-06-21T00:17:25 *** Chris_Stewart_5 has joined #bitcoin-core-dev
42016-06-21T00:17:34 *** alpalp has quit IRC
52016-06-21T00:26:00 *** alpalp has joined #bitcoin-core-dev
62016-06-21T00:26:00 *** alpalp has joined #bitcoin-core-dev
72016-06-21T00:41:47 *** Guest77060 has joined #bitcoin-core-dev
82016-06-21T00:43:05 *** Guest77060 is now known as roidster
92016-06-21T00:43:59 <_anthony_> the CSV fix is in :)
102016-06-21T00:48:09 *** jannes has quit IRC
112016-06-21T00:49:07 *** Chris_Stewart_5 has quit IRC
122016-06-21T00:58:35 *** afk11 has quit IRC
132016-06-21T01:01:19 *** Ylbam has quit IRC
142016-06-21T01:02:25 *** afk11 has joined #bitcoin-core-dev
152016-06-21T01:02:25 *** afk11 has quit IRC
162016-06-21T01:02:25 *** afk11 has joined #bitcoin-core-dev
172016-06-21T01:05:36 *** Chris_Stewart_5 has joined #bitcoin-core-dev
182016-06-21T01:13:45 *** molly has joined #bitcoin-core-dev
192016-06-21T01:17:03 *** molz has quit IRC
202016-06-21T01:29:19 *** belcher has quit IRC
212016-06-21T01:41:35 *** fengling has joined #bitcoin-core-dev
222016-06-21T01:59:51 *** sanada has joined #bitcoin-core-dev
232016-06-21T02:14:09 *** ghtdak has quit IRC
242016-06-21T02:28:26 *** alpalp has quit IRC
252016-06-21T02:39:09 *** pedrobranco has joined #bitcoin-core-dev
262016-06-21T02:41:53 *** Chris_Stewart_5 has quit IRC
272016-06-21T02:43:04 *** pedrobranco has quit IRC
282016-06-21T02:58:47 *** adamg has joined #bitcoin-core-dev
292016-06-21T03:04:53 *** fengling has quit IRC
302016-06-21T03:04:58 <luke-jr> cfields_: https://docs.travis-ci.com/user/ip-addresses/
312016-06-21T03:05:29 *** zooko has joined #bitcoin-core-dev
322016-06-21T03:11:46 *** fengling has joined #bitcoin-core-dev
332016-06-21T03:21:26 *** netsinn has joined #bitcoin-core-dev
342016-06-21T03:21:37 *** ghtdak has joined #bitcoin-core-dev
352016-06-21T03:47:11 *** _anthony_ has quit IRC
362016-06-21T03:52:54 *** Sosumi has joined #bitcoin-core-dev
372016-06-21T04:00:15 *** netsinn has quit IRC
382016-06-21T04:27:05 *** frankenmint has joined #bitcoin-core-dev
392016-06-21T04:39:06 <jl2012> just want to confirm: during bip9 locked_in, blocks with any nVersion >=4 are valid?
402016-06-21T04:45:01 <btcdrak> jl2012: what do you mean? once lockin is reached signalling is no longer required but recommended.
412016-06-21T04:45:35 <jl2012> btcdrak: you have answered my question: no longer required
422016-06-21T04:46:01 <jl2012> i think certains pools are setting their version manually
432016-06-21T04:46:41 <jl2012> they have to turn it back to 0x20000000 at or before 419328
442016-06-21T04:47:02 <jl2012> or that may trigger the unknown softfork warning
452016-06-21T04:55:59 <jl2012> should we ask miners (who are manually setting the version) to change the version to 0x20000000 *at* or *before* 419328?
462016-06-21T04:57:43 <jl2012> I think it'd be better if they change it before 419328. Otherwise, if they keep signalling 0x20000001 after 419328, Bitcoin Core clients will think there is an unknown softfork
472016-06-21T05:00:49 *** netsinn has joined #bitcoin-core-dev
482016-06-21T05:01:35 *** netsinn has quit IRC
492016-06-21T05:01:51 *** netsinn has joined #bitcoin-core-dev
502016-06-21T05:17:47 <jl2012> "csv": {
512016-06-21T05:17:47 <jl2012> "status": "locked_in",
522016-06-21T05:17:47 <jl2012> "startTime": 1462060800,
532016-06-21T05:17:47 <jl2012> "timeout": 1493596800
542016-06-21T05:17:47 <jl2012> },
552016-06-21T05:18:55 <btcdrak> how many 0x20000001 blocks?
562016-06-21T05:18:59 <jl2012> In the last difficulty round, CSV had 1946/2016 (96.53%)
572016-06-21T05:19:17 <jl2012> 0x20000001 is 1916/2016 (95.04%)
582016-06-21T05:20:12 <jl2012> so we could have a locked_in just with only standard Bitcoin Core 0.12.1 blocks
592016-06-21T05:23:23 <gmaxwell> if the signaling goes away now we will panic
602016-06-21T05:23:36 <gmaxwell> because it will suggest the network state will diverge if a CSV violation is mined.
612016-06-21T05:25:32 <btcdrak> the spec says should but not must continue to signal during locked in state.
622016-06-21T05:26:08 <gmaxwell> the purpose of the continued signaling is to let us humans see that the consensus state hasn't changed. it's not enforced by anything, thus not must.
632016-06-21T05:26:43 <jl2012> after activation of CSV, how many blocks are needed to trigger the unknown softfork warning?
642016-06-21T05:27:39 <gmaxwell> 50 out of 100. is the lower threshold.
652016-06-21T05:28:03 *** roidster has quit IRC
662016-06-21T05:28:21 <jl2012> so they have to react in less than one day if we ask them to change it after it is active
672016-06-21T05:28:58 <gmaxwell> Since we're now aware of miners manually setting version bits we should start work on a new deployment mechenism and depricate BIP9. :(
682016-06-21T05:29:34 <gmaxwell> I think BIP9 is too unsafe to use with parties manually setting the bits. The issue is if they have old nodes that don't enforce the consensus rules and they're failing over to them and getting work from them it can split the network, and it would be completely silent.
692016-06-21T05:29:53 <btcdrak> well it is just f2pool and antpool afaik
702016-06-21T05:30:51 <gmaxwell> if it's most of the hashpower it means that BIP9 is a currently failed design. The initial switch to signal CSV was _Exactly_ at the starting time, so I felt confident that the version numbers weren't being faked.
712016-06-21T05:30:52 <jl2012> gmaxwell: the same problem applies to ISM
722016-06-21T05:31:03 <gmaxwell> I'm really crestfallen to find that it's being faked now.
732016-06-21T05:31:27 <gmaxwell> jl2012: yes, and we had a failure with ISM, we hoped that the new mechenism which did not orphan non-conforming blocks would not be faked.
742016-06-21T05:32:14 <gmaxwell> the fact that that failure involved empty blocks is the only thing that prevented there from being large doublespending losses.
752016-06-21T05:33:04 <gmaxwell> jl2012: in any case, if we know now that they're turning the bit off, we can not freak out when it happens.
762016-06-21T05:33:32 <gmaxwell> but we should urge them to check very carefully that _all_ of their infrastructure is upgraded and that there are no old nodes that might come back up, e.g. after a power cycle.
772016-06-21T05:33:51 <btcdrak> i am sure we can solve the problem by talking with them. i think we should advice them to stop signalling before activation
782016-06-21T05:34:43 <gmaxwell> the problem is likely that version is something exposed to front end mining equipment, and if they are doing 'fake' block generation then they need to have the block version succession logic in their own software, or configure it manually.
792016-06-21T05:34:46 <btcdrak> the general public just need education
802016-06-21T05:35:23 <gmaxwell> btcdrak: we can educate around risk people impose on themselves, for risk they impose on others we should strive towards designs that are hard to misconfigure.
812016-06-21T05:35:51 <gmaxwell> I thought BIP9 got us there, but apparently I was mistaken. An intended feature of the design isn't working.
822016-06-21T05:36:40 <btcdrak> the website faq advises miners to stop signalling before activation for those manually setting the bit
832016-06-21T05:37:17 <gmaxwell> ...
842016-06-21T05:38:04 <btcdrak> gmaxwell: i dont see how the issue is any different than ISM. it is better under VB since there is a two week period before enforcement.
852016-06-21T05:38:19 <gmaxwell> This is seriously fucked up, miners signaling versions inconsistent with the consensus rules they were running already forked the network once and narrowly avoided an incident. BIP9's design was partially motivated in avoiding that. (with no "set version or get orphaned" the beliefe was there would be no reason to fake it.
862016-06-21T05:38:30 <btcdrak> miners have been manually setting bloxk version long ago
872016-06-21T05:38:49 <gmaxwell> yes, and it already caused one ~6 block deep chain fork!
882016-06-21T05:40:38 <btcdrak> right. VB is better because of grace period. but maybe I am not explainimg well. when I talked to ant and fish they said they upgraded first and then changed the version number.
892016-06-21T05:41:26 <btcdrak> so they are not putting anyone at risk by doing it in that order.
902016-06-21T05:42:12 <gmaxwell> btcdrak: the grace period doesn't help this issue. The issue is that we don't get any strong, hard to screw up, indication that their upgrades were effective. This depends on their internal monitoring being effective, which it is not historically for many mining operations, and we shouldn't expect it to be because the risk is predominantly not held by them.
912016-06-21T05:42:19 <gmaxwell> btcdrak: only if they made no errors.
922016-06-21T05:42:48 <gmaxwell> and it's hard to tell, because the manual setting covers up the indicator.
932016-06-21T05:43:47 <btcdrak> it is true. they do forget nodes... i dont see how you can get around this problem. miners need to change their habits.
942016-06-21T05:44:08 <jl2012> Let's assume a miner is not setting manually, and some how fall back to 0.12.0 after activation. What will happen?
952016-06-21T05:45:02 <gmaxwell> jl2012: won't be detected anymore, the tradeoff for getting the bit back is that you only learn about the status during the month of signaling and grace period.
962016-06-21T05:45:17 <gmaxwell> But even that is meaningless if manually overridden.
972016-06-21T05:45:21 <btcdrak> jl2012: they could mine an invalid block.. except their relay policy is unlikely to accept an invalid tx.
982016-06-21T05:45:48 <gmaxwell> btcdrak: they'll extend an invalid chain when someone else mines an invalid block.
992016-06-21T05:46:02 <btcdrak> truee
1002016-06-21T05:46:50 <btcdrak> well i dont see a solution other than education. it is why we wrote the FAQ
1012016-06-21T05:47:55 <btcdrak> https://bitcoincore.org/en/2016/06/08/version-bits-miners-faq/
1022016-06-21T05:51:31 <gmaxwell> jl2012: in theory the mandatory version increase protected against downgrades, but in practice we found it did the opposite, since miners manually set the version to avoid being orphaned... so not only did it not protect against downgrades, it concealed a lack of true enforcement.
1032016-06-21T05:52:22 <gmaxwell> So the expectation with bip9 was that since it was no longer forced there would be no incentive to lie, and at least the measure of upgrade status would be faithful.
1042016-06-21T06:00:53 <jl2012> This could be corrected only with education
1052016-06-21T06:01:31 <btcdrak> jl2012: i agree
1062016-06-21T06:01:38 <gmaxwell> We could introduce signaling elsewhere in the block in locations that miners have not already built infrastructure around faking the values.
1072016-06-21T06:01:45 <jl2012> Some miners didn't really understand bip9
1082016-06-21T06:01:47 <gmaxwell> This would be systematically safe.
1092016-06-21T06:02:16 <jl2012> nlocktime, maybe
1102016-06-21T06:02:20 <gmaxwell> Expecting education to work is a losing fight... because we can educate but the parties will continue to rotate out.
1112016-06-21T06:02:36 <gmaxwell> nlocktime in coinbase txn perhaps, yes.
1122016-06-21T06:02:44 <gmaxwell> (which is where height should have gone, but oh well. :) )
1132016-06-21T06:03:01 <gmaxwell> Not that I don't think that we should educate, of course. But its risky to count on that for safty.
1142016-06-21T06:04:18 <jl2012> But nlocktime is determined by stratum
1152016-06-21T06:04:28 <btcdrak> gmaxwell: in any case for csv miner have upgraded to 0.12.1.
1162016-06-21T06:04:31 <gmaxwell> Then can't use that either.
1172016-06-21T06:04:34 <jl2012> So they will fake it again
1182016-06-21T06:05:45 <gmaxwell> In any case there are many potential places to put it, not something that needs to be figured out now. Any solution would need to be carefully evaluated.
1192016-06-21T06:06:29 <gmaxwell> avoiding interaction with any customized infratructure is one reason why mark advocated the dummy transactions for additional commitments.
1202016-06-21T06:07:14 <btcdrak> yes was about to say use first tx.
1212016-06-21T06:08:05 <gmaxwell> Really the major loss with stratum is that we lost the clean domain of authority layering in the system. Now there isn't a nice boundary where complex consensus details are hidden behind, and where people who don't care about them don't have to worry about them.
1222016-06-21T06:08:34 *** arubi has quit IRC
1232016-06-21T06:08:38 <gmaxwell> With getwork nothing that was up for adjustment really mattered much except changes that would just make your block invalid even to SPV nodes.
1242016-06-21T06:10:38 <jl2012> btw, we also need to warn the miners who are using coinbase nSequence as mining nonce
1252016-06-21T06:11:04 <jl2012> they must keep the coinbase nVersion as 1 or the block might be orphaned
1262016-06-21T06:17:12 <sipa> or above 2^31
1272016-06-21T06:17:46 <jl2012> sipa, i.e. negative?
1282016-06-21T06:18:28 *** arubi has joined #bitcoin-core-dev
1292016-06-21T06:19:10 <sipa> right
1302016-06-21T06:27:23 <jl2012> we may need a email to miners to tell them what to double check in the coming 2 weeks
1312016-06-21T06:28:07 <jl2012> 1. make sure every nodes are upgraded to 0.12.1, and won't somehow fall back to an older version
1322016-06-21T06:28:52 <jl2012> 2. make sure they will stop signalling CSV at or before block 419328
1332016-06-21T06:29:19 <jl2012> (if they are doing that manually)
1342016-06-21T06:29:41 <jl2012> 3. make sure the coinbase tx compiles with BIP68
1352016-06-21T06:30:24 <jl2012> 4. make sure the coinbase tx compiles with BIP113 (in case someone use nLockTime for mining --> unlikely)
1362016-06-21T06:30:39 <jl2012> anymore?
1372016-06-21T06:31:28 <jl2012> s/compiles/complies/
1382016-06-21T06:34:26 *** fengling has quit IRC
1392016-06-21T06:35:02 <sipa> i don't think 68 applies to coinbase inputs
1402016-06-21T06:35:47 <jl2012> really? let me check the code
1412016-06-21T06:36:05 <sipa> oh, i mean 113
1422016-06-21T06:36:37 <jl2012> nlocktime of coinbase is not checked?
1432016-06-21T06:37:02 *** netsinn has quit IRC
1442016-06-21T06:37:14 <sipa> it's not an input
1452016-06-21T06:37:25 <sipa> and not validated as one
1462016-06-21T06:37:30 <sipa> (i think)
1472016-06-21T06:37:52 *** netsinn has joined #bitcoin-core-dev
1482016-06-21T06:38:47 <jl2012> 113 is the median-time-past, not OP_CSV
1492016-06-21T06:39:56 <sipa> yes, so 113 does not apply to coinbases
1502016-06-21T06:40:28 <jl2012> so i can put whatever value in the nLockTime of coinbase and it is still valid?
1512016-06-21T06:41:27 <sipa> i am only half awake and should shut up
1522016-06-21T06:41:37 <sipa> i may be confusing things
1532016-06-21T06:42:11 <jl2012> that's fine :)
1542016-06-21T06:57:06 *** bustd_soket has quit IRC
1552016-06-21T07:01:06 *** laurentmt has joined #bitcoin-core-dev
1562016-06-21T07:01:18 *** laurentmt has quit IRC
1572016-06-21T07:02:17 *** fengling has joined #bitcoin-core-dev
1582016-06-21T07:07:34 *** Ylbam has joined #bitcoin-core-dev
1592016-06-21T07:12:03 *** netsinn has quit IRC
1602016-06-21T07:12:24 *** Ylbam has quit IRC
1612016-06-21T07:12:30 *** jl2012 has quit IRC
1622016-06-21T07:13:18 *** bustd_soket has joined #bitcoin-core-dev
1632016-06-21T07:22:05 *** paveljanik has quit IRC
1642016-06-21T07:24:58 *** assder has quit IRC
1652016-06-21T07:29:05 *** Guyver2 has joined #bitcoin-core-dev
1662016-06-21T07:30:28 *** jl2012 has joined #bitcoin-core-dev
1672016-06-21T07:31:03 <jl2012> i think all transactions including coinbase are subject to nLockTime and BIP113 rules
1682016-06-21T07:40:45 *** frankenmint has quit IRC
1692016-06-21T07:45:13 *** assder has joined #bitcoin-core-dev
1702016-06-21T07:52:42 *** jl2012 has quit IRC
1712016-06-21T08:01:01 *** frankenmint has joined #bitcoin-core-dev
1722016-06-21T08:10:34 <GitHub3> [bitcoin] laanwj pushed 2 new commits to 0.12: https://github.com/bitcoin/bitcoin/compare/44fdacc19f9f...f3eebcf5158f
1732016-06-21T08:10:34 <GitHub3> bitcoin/0.12 ba61949 TheLazieR Yip: Fix LogPrint to LogPrintf...
1742016-06-21T08:10:34 <GitHub149> [bitcoin] laanwj closed pull request #8230: Fix LogPrint to LogPrintf (0.12...patch-1) https://github.com/bitcoin/bitcoin/pull/8230
1752016-06-21T08:10:35 <GitHub3> bitcoin/0.12 f3eebcf Wladimir J. van der Laan: Merge #8230: Fix LogPrint to LogPrintf...
1762016-06-21T08:19:29 *** bustd_soket has quit IRC
1772016-06-21T08:22:04 <GitHub142> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/bf9c70b1008e1eada462955a6420e79a7d2a8352
1782016-06-21T08:22:04 <GitHub142> bitcoin/master bf9c70b TheLazieR Yip: Fix LogPrint to LogPrintf...
1792016-06-21T08:23:37 *** xiangfu has quit IRC
1802016-06-21T08:24:39 <GitHub112> [bitcoin] laanwj pushed 5 new commits to master: https://github.com/bitcoin/bitcoin/compare/bf9c70b1008e...0d41d705c83d
1812016-06-21T08:24:40 <GitHub112> bitcoin/master fa8ce3b MarcoFalke: [qa] assert 'changePosition out of bounds'
1822016-06-21T08:24:40 <GitHub112> bitcoin/master fa32465 MarcoFalke: [qa] fundrawtransaction: Create get_unspent()
1832016-06-21T08:24:41 <GitHub112> bitcoin/master fa3b379 MarcoFalke: [qa] pull-tester: Fix assertion and check for run_parallel
1842016-06-21T08:24:44 <GitHub198> [bitcoin] laanwj closed pull request #8216: [qa] assert 'changePosition out of bounds' (master...Mf1606-qaFundrawtransaction) https://github.com/bitcoin/bitcoin/pull/8216
1852016-06-21T08:34:52 *** MarcoFalke has joined #bitcoin-core-dev
1862016-06-21T08:35:16 *** bustd_soket has joined #bitcoin-core-dev
1872016-06-21T08:35:53 *** Ylbam has joined #bitcoin-core-dev
1882016-06-21T08:38:34 *** Giszmo has quit IRC
1892016-06-21T08:49:57 *** jl2012 has joined #bitcoin-core-dev
1902016-06-21T08:57:42 <GitHub95> [bitcoin] jonasschnelli opened pull request #8231: [Qt] fix a bug where the SplashScreen will not be hidden during startup (master...2016/06/qt_min_fix) https://github.com/bitcoin/bitcoin/pull/8231
1912016-06-21T09:06:37 *** frankenmint has quit IRC
1922016-06-21T09:08:00 *** pedrobranco has joined #bitcoin-core-dev
1932016-06-21T09:13:04 <MarcoFalke> ./boost/config/posix_features.hpp:18:15: fatal error: 'unistd.h' file not found
1942016-06-21T09:13:10 <MarcoFalke> https://travis-ci.org/bitcoin/bitcoin/jobs/138877841
1952016-06-21T09:14:16 <wumpus> ... huh. I didn't change anything there since last time, just re-triggered travis
1962016-06-21T09:14:59 <wumpus> looks like they performed a magic trick to make a basic system header disappear
1972016-06-21T09:15:37 <jonasschnelli> hmm... could that be related to the OSX SDK 10.11 update?
1982016-06-21T09:15:58 <jonasschnelli> I had similar issues when /home/travis/build/bitcoin/bitcoin/depends/SDKs/MacOSX10.11.sdk was not present
1992016-06-21T09:16:05 <wumpus> possibly, though it must be an intermittent problem
2002016-06-21T09:16:40 <wumpus> there's no error in the log about the sdk
2012016-06-21T09:17:06 <jonasschnelli> Wait!
2022016-06-21T09:17:28 <wumpus> also: protobuf compiles fine, you'd say it wouldn't get past that without basic C headers
2032016-06-21T09:17:28 <jonasschnelli> It tries to access "/home/travis/build/bitcoin/bitcoin/depends/SDKs/MacOSX10.11.sdk" but export OSX_SDK=10.9?!
2042016-06-21T09:17:49 <wumpus> gah
2052016-06-21T09:17:59 <jonasschnelli> Why export OSX_SDK10.9?
2062016-06-21T09:18:03 <jonasschnelli> Maybe rebase the PR?!
2072016-06-21T09:18:19 <wumpus> I don't know, I haven't touched *anything* macosx related
2082016-06-21T09:18:29 <wumpus> I don't even change the dependencies, it's a silly test change
2092016-06-21T09:18:37 <jonasschnelli> The current master travis file (https://github.com/bitcoin/bitcoin/blob/master/.travis.yml) points clearly to 10.11
2102016-06-21T09:20:09 <MarcoFalke> There are issues with travis when .travis.yml changes in master but not in the pull
2112016-06-21T09:20:15 <jonasschnelli> wumpus MarcoFalke: I guess it's a temporary issue
2122016-06-21T09:20:35 <jonasschnelli> A commit from https://github.com/bitcoin/bitcoin/pull/8227 has a .travis file poining to 10.9 where depends expectes 10.11
2132016-06-21T09:20:51 <jonasschnelli> https://github.com/bitcoin/bitcoin/blob/bee60e3bc200be33146699380cbd8f9d9e72c372/.travis.yml
2142016-06-21T09:21:09 <jonasschnelli> Rebase should to the thing.
2152016-06-21T09:21:51 <MarcoFalke> I guess travis will use the .travis.yml from the pull to set up the vm but uses the cache from master to build
2162016-06-21T09:22:01 <GitHub69> [bitcoin] mcccs opened pull request #8232: Add IRC link to README.md (master...patch-1) https://github.com/bitcoin/bitcoin/pull/8232
2172016-06-21T09:22:42 <MarcoFalke> or just merge into master :) if we are confident that the pull is what we want
2182016-06-21T09:22:51 <MarcoFalke> it is still running for 30 min
2192016-06-21T09:23:00 <MarcoFalke> prob communication overhead with wine?
2202016-06-21T09:23:24 *** MCCCS has joined #bitcoin-core-dev
2212016-06-21T09:23:38 <MarcoFalke> but when we get rid of java-blocktester, we need to turn on rpc test for windows in any case
2222016-06-21T09:23:43 <wumpus> I'm confident it is what we want, but I'm afraid of making travis more flakey that's why I'm testing on the pull insted of in master
2232016-06-21T09:24:19 <wumpus> the last thing we want is a flakey travis in the stabilization phase of a release
2242016-06-21T09:24:21 *** Guyver2 has quit IRC
2252016-06-21T09:24:23 <wumpus> so I'd prefer to merge it later
2262016-06-21T09:24:51 <wumpus> also with cfields_ not here to solve our build system/travis howlers :-)
2272016-06-21T09:25:25 <wumpus> yes, wine clearly has some overhead, it's not clear where and why
2282016-06-21T09:25:39 <wumpus> maybe it's just the bitcoind startup overhead, maybe it's some other delay introduced somewhere
2292016-06-21T09:25:59 <wumpus> (e.g. a polling loop in the test that either connects immediately, otherwise waits a few seconds before trying again)
2302016-06-21T09:26:33 <wumpus> java-blocktester is a worry after the 0.13 release
2312016-06-21T09:27:36 *** MCCCS has quit IRC
2322016-06-21T09:31:07 <wumpus> re-based the pull to master
2332016-06-21T10:26:51 *** afk11 has quit IRC
2342016-06-21T10:31:26 *** afk11 has joined #bitcoin-core-dev
2352016-06-21T10:31:26 *** afk11 has quit IRC
2362016-06-21T10:31:26 *** afk11 has joined #bitcoin-core-dev
2372016-06-21T10:37:40 *** go1111111 has quit IRC
2382016-06-21T11:23:46 *** fengling has quit IRC
2392016-06-21T11:55:31 *** rubensayshi has quit IRC
2402016-06-21T12:21:04 *** fengling has joined #bitcoin-core-dev
2412016-06-21T12:22:17 *** rubensayshi has joined #bitcoin-core-dev
2422016-06-21T12:22:39 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2432016-06-21T12:25:46 *** fengling has quit IRC
2442016-06-21T12:32:34 *** cryptapus_afk is now known as cryptapus
2452016-06-21T12:35:11 <GitHub137> [bitcoin] laanwj opened pull request #8233: Mention Linux ARM executables in release process and notes (master...2016_06_release_process_arm) https://github.com/bitcoin/bitcoin/pull/8233
2462016-06-21T12:38:14 <sipa> wumpus: there is the abcore project, which uses the arch or debian built arm binaries for bitcoin core on android
2472016-06-21T12:38:42 <sipa> wumpus: they cheat, by copying the libstc++ and a few more files from those distributions as well
2482016-06-21T12:39:07 <sipa> but still, it seems common arm binaries seem to work with such hacks on android
2492016-06-21T12:39:53 <wumpus> ok, well we'll have to see, I just want to warn people to not get their hopes up that it will work out of the box with android
2502016-06-21T12:40:22 <sipa> yes, warning that it's expiremental is obviously needed
2512016-06-21T12:40:26 <wumpus> probably if you 'disguise' your android as a debian box by providing the preerquisite libraries and /etc/ files you can get it to work
2522016-06-21T12:40:33 *** rubensayshi has quit IRC
2532016-06-21T12:41:47 <sipa> right, i'm not suggesting you change the text
2542016-06-21T12:42:08 <wumpus> I'm fine with changing the text, just wouldn't know how to incorporate this without making it too technical
2552016-06-21T12:42:33 <sipa> but maybe you were unaware of the approach they used
2562016-06-21T12:42:39 <sipa> agree
2572016-06-21T12:42:43 <sipa> just giving some background
2582016-06-21T12:43:02 <wumpus> yes, thanks for the background, I didn't know they emulalated
2592016-06-21T12:44:13 <wumpus> "expected to work on Android." -> maybe add as-is in there?
2602016-06-21T12:44:23 <wumpus> or "out of the box"
2612016-06-21T12:44:42 <sipa> sounds good
2622016-06-21T12:57:34 *** rubensayshi has joined #bitcoin-core-dev
2632016-06-21T13:02:36 <btcdrak> abcore https://github.com/greenaddress/abcore
2642016-06-21T13:03:43 <wumpus> thanks btcdrak
2652016-06-21T13:04:15 *** laurentmt has joined #bitcoin-core-dev
2662016-06-21T13:04:25 *** laurentmt has quit IRC
2672016-06-21T13:12:56 *** assder has quit IRC
2682016-06-21T13:12:56 *** cjcj has quit IRC
2692016-06-21T13:14:42 <wumpus> what is the locale en_US? it is one of the languages being added on transifex, but it lokos like Spanish, that can't be correct
2702016-06-21T13:15:05 <instagibbs> US english?
2712016-06-21T13:15:06 <pigeons> "american" english.
2722016-06-21T13:15:35 <wumpus> https://www.transifex.com/bitcoin/bitcoin/viewstrings/#en_US/qt-translation-013x/86275741
2732016-06-21T13:16:23 <wumpus> well it's not English so I'm going to delete it
2742016-06-21T13:18:40 *** Chris_Stewart_5 has quit IRC
2752016-06-21T13:19:41 <wumpus> wish we had someone with language knowledge actually watching these things
2762016-06-21T13:19:51 *** owowo has quit IRC
2772016-06-21T13:22:33 *** fengling has joined #bitcoin-core-dev
2782016-06-21T13:27:26 *** fengling has quit IRC
2792016-06-21T13:28:09 *** owowo has joined #bitcoin-core-dev
2802016-06-21T13:31:30 <GitHub33> [bitcoin] laanwj opened pull request #8234: Periodic transifex update (master...2016_06_transifex_update) https://github.com/bitcoin/bitcoin/pull/8234
2812016-06-21T13:34:29 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2822016-06-21T13:36:13 *** pedrobranco has quit IRC
2832016-06-21T13:36:26 *** pedrobranco has joined #bitcoin-core-dev
2842016-06-21T13:37:02 *** whphhg has quit IRC
2852016-06-21T13:44:24 <wumpus> per-function address space randomization, this looks interesting https://github.com/immunant/selfrando
2862016-06-21T13:45:05 *** Chris_Stewart_5 has quit IRC
2872016-06-21T13:45:55 *** MCCCS has joined #bitcoin-core-dev
2882016-06-21T13:46:45 *** MCCCS has quit IRC
2892016-06-21T13:54:37 *** bustd_soket has quit IRC
2902016-06-21T13:55:31 *** whphhg has joined #bitcoin-core-dev
2912016-06-21T14:00:48 *** Chris_Stewart_5 has joined #bitcoin-core-dev
2922016-06-21T14:10:09 *** bustd_soket has joined #bitcoin-core-dev
2932016-06-21T14:23:59 *** fengling has joined #bitcoin-core-dev
2942016-06-21T14:25:37 *** zooko has quit IRC
2952016-06-21T14:27:32 <wumpus> pretty clever, it just uses compiler's -ffunction-sections to generate the necessary ELF data, then slices the program up at load time based onthat
2962016-06-21T14:28:46 *** fengling has quit IRC
2972016-06-21T14:31:19 *** Giszmo has joined #bitcoin-core-dev
2982016-06-21T14:32:42 <GitHub30> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/0d41d705c83d...8ccdac1f5f77
2992016-06-21T14:32:43 <GitHub30> bitcoin/master e5a680d fanquake: [Doc] Update OS X build notes for 10.11 SDK
3002016-06-21T14:32:43 <GitHub30> bitcoin/master 8ccdac1 Wladimir J. van der Laan: Merge #8229: [Doc] Update OS X build notes for 10.11 SDK...
3012016-06-21T14:32:52 <GitHub127> [bitcoin] laanwj closed pull request #8229: [Doc] Update OS X build notes for 10.11 SDK (master...osx-build-notes-new) https://github.com/bitcoin/bitcoin/pull/8229
3022016-06-21T14:41:58 *** cryptapus_ has joined #bitcoin-core-dev
3032016-06-21T14:54:20 *** cryptapus_ has quit IRC
3042016-06-21T15:01:59 *** PaulCapestany has quit IRC
3052016-06-21T15:03:10 *** PaulCapestany has joined #bitcoin-core-dev
3062016-06-21T15:04:51 *** Chris_Stewart_5 has quit IRC
3072016-06-21T15:09:32 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3082016-06-21T15:14:07 *** laurentmt has joined #bitcoin-core-dev
3092016-06-21T15:14:43 *** laurentmt has quit IRC
3102016-06-21T15:25:34 *** fengling has joined #bitcoin-core-dev
3112016-06-21T15:31:43 *** Chris_Stewart_5 has quit IRC
3122016-06-21T15:32:46 *** fengling has quit IRC
3132016-06-21T15:43:43 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3142016-06-21T16:01:38 *** murch has joined #bitcoin-core-dev
3152016-06-21T16:20:57 *** Chris_Stewart_5 has quit IRC
3162016-06-21T16:29:32 *** fengling has joined #bitcoin-core-dev
3172016-06-21T16:34:26 *** fengling has quit IRC
3182016-06-21T16:38:08 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3192016-06-21T16:44:30 *** anchow101 has joined #bitcoin-core-dev
3202016-06-21T16:45:18 *** anchow101 has joined #bitcoin-core-dev
3212016-06-21T16:59:52 *** Chris_Stewart_5 has quit IRC
3222016-06-21T17:13:12 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3232016-06-21T17:21:10 *** ratoder has joined #bitcoin-core-dev
3242016-06-21T17:21:11 *** ratoder has quit IRC
3252016-06-21T17:24:25 *** ratoder has joined #bitcoin-core-dev
3262016-06-21T17:24:28 *** ratoder has quit IRC
3272016-06-21T17:29:29 *** ratoder has joined #bitcoin-core-dev
3282016-06-21T17:31:09 *** fengling has joined #bitcoin-core-dev
3292016-06-21T17:31:55 *** ratoder has quit IRC
3302016-06-21T17:36:06 *** fengling has quit IRC
3312016-06-21T17:40:56 *** paveljanik has joined #bitcoin-core-dev
3322016-06-21T17:40:56 *** paveljanik has joined #bitcoin-core-dev
3332016-06-21T17:43:39 *** ratoder has joined #bitcoin-core-dev
3342016-06-21T18:07:48 <JackH> !seen maaku
3352016-06-21T18:07:48 <gribble> maaku was last seen in #bitcoin-core-dev 6 weeks, 4 days, 1 hour, 19 minutes, and 54 seconds ago: <maaku> yeah but still, we should try not to add to the noise
3362016-06-21T18:09:47 *** cjcj has joined #bitcoin-core-dev
3372016-06-21T18:17:25 *** molly has quit IRC
3382016-06-21T18:29:07 *** moli has joined #bitcoin-core-dev
3392016-06-21T18:32:49 *** fengling has joined #bitcoin-core-dev
3402016-06-21T18:35:20 *** pedrobranco has quit IRC
3412016-06-21T18:37:26 *** fengling has quit IRC
3422016-06-21T18:53:47 *** pedrobranco has joined #bitcoin-core-dev
3432016-06-21T18:55:20 *** robs has quit IRC
3442016-06-21T18:55:53 *** Sosumi has quit IRC
3452016-06-21T18:59:03 *** pedrobranco has quit IRC
3462016-06-21T19:10:05 *** MarcoFalke has left #bitcoin-core-dev
3472016-06-21T19:13:39 *** go1111111 has joined #bitcoin-core-dev
3482016-06-21T19:17:18 *** zooko has joined #bitcoin-core-dev
3492016-06-21T19:17:39 *** Chris_Stewart_5 has quit IRC
3502016-06-21T19:27:15 *** RoyceX has joined #bitcoin-core-dev
3512016-06-21T19:27:15 *** RoyceX has joined #bitcoin-core-dev
3522016-06-21T19:28:40 *** Cory has quit IRC
3532016-06-21T19:29:53 *** Inaltoasinistra has quit IRC
3542016-06-21T19:30:28 *** bustd_soket has quit IRC
3552016-06-21T19:30:29 *** Cheeseo has quit IRC
3562016-06-21T19:30:29 *** face has quit IRC
3572016-06-21T19:30:30 *** BonyM has quit IRC
3582016-06-21T19:30:31 *** ybit_ has quit IRC
3592016-06-21T19:30:47 *** bustd_soket has joined #bitcoin-core-dev
3602016-06-21T19:31:58 *** ybit has joined #bitcoin-core-dev
3612016-06-21T19:32:40 *** Cory has joined #bitcoin-core-dev
3622016-06-21T19:33:43 *** Inaltoasinistra has joined #bitcoin-core-dev
3632016-06-21T19:34:05 *** fengling has joined #bitcoin-core-dev
3642016-06-21T19:38:46 *** fengling has quit IRC
3652016-06-21T19:42:26 *** Chris_Stewart_5 has joined #bitcoin-core-dev
3662016-06-21T19:43:30 *** face has joined #bitcoin-core-dev
3672016-06-21T19:45:35 *** BonyM has joined #bitcoin-core-dev
3682016-06-21T19:49:05 *** pedrobranco has joined #bitcoin-core-dev
3692016-06-21T19:53:45 *** pedrobranco has quit IRC
3702016-06-21T19:55:50 *** TomMc has joined #bitcoin-core-dev
3712016-06-21T19:56:47 *** Guyver2 has joined #bitcoin-core-dev
3722016-06-21T20:00:03 *** zooko has quit IRC
3732016-06-21T20:11:47 *** ratoder has quit IRC
3742016-06-21T20:17:08 *** ratoder has joined #bitcoin-core-dev
3752016-06-21T20:22:34 *** anchow101 has quit IRC
3762016-06-21T20:23:55 *** robs has joined #bitcoin-core-dev
3772016-06-21T20:26:50 <GitHub4> [bitcoin] TheBlueMatt opened pull request #8235: Compact Block Tweaks (master...cmpctblock) https://github.com/bitcoin/bitcoin/pull/8235
3782016-06-21T20:35:36 *** fengling has joined #bitcoin-core-dev
3792016-06-21T20:40:06 *** fengling has quit IRC
3802016-06-21T20:59:25 *** zooko has joined #bitcoin-core-dev
3812016-06-21T21:01:34 *** Chris_Stewart_5 has quit IRC
3822016-06-21T21:04:22 *** belcher has joined #bitcoin-core-dev
3832016-06-21T21:14:29 *** JackH has quit IRC
3842016-06-21T21:36:37 *** fengling has joined #bitcoin-core-dev
3852016-06-21T21:39:01 *** anchow101 has joined #bitcoin-core-dev
3862016-06-21T21:41:26 *** fengling has quit IRC
3872016-06-21T21:59:04 *** jl2012 has quit IRC
3882016-06-21T22:04:55 *** face has quit IRC
3892016-06-21T22:05:16 *** Guyver2 has quit IRC
3902016-06-21T22:12:26 *** cryptapus is now known as cryptapus_afk
3912016-06-21T22:13:31 *** murch has quit IRC
3922016-06-21T22:15:33 *** laurentmt has joined #bitcoin-core-dev
3932016-06-21T22:15:53 *** laurentmt has quit IRC
3942016-06-21T22:35:20 *** robs has quit IRC
3952016-06-21T22:38:07 *** fengling has joined #bitcoin-core-dev
3962016-06-21T22:43:06 *** fengling has quit IRC
3972016-06-21T23:06:04 *** anchow101 has quit IRC
3982016-06-21T23:11:28 *** jouke_ has quit IRC
3992016-06-21T23:12:05 *** zooko has quit IRC
4002016-06-21T23:17:58 *** jouke has joined #bitcoin-core-dev
4012016-06-21T23:18:41 *** anchow101 has joined #bitcoin-core-dev
4022016-06-21T23:34:43 *** cryptapus_ has joined #bitcoin-core-dev
4032016-06-21T23:34:43 *** cryptapus_ has joined #bitcoin-core-dev
4042016-06-21T23:35:18 *** cryptapus_ has joined #bitcoin-core-dev
4052016-06-21T23:35:18 *** cryptapus_ has joined #bitcoin-core-dev
4062016-06-21T23:35:24 *** cryptapus_ has quit IRC
4072016-06-21T23:36:13 *** cryptapus has joined #bitcoin-core-dev
4082016-06-21T23:37:23 *** shesek has quit IRC
4092016-06-21T23:39:48 *** fengling has joined #bitcoin-core-dev
4102016-06-21T23:44:06 *** fengling has quit IRC