1 2017-04-05 03:00:22	0|chatter29|hey guys
  2 2017-04-05 03:00:24	0|chatter29|allah is doing
  3 2017-04-05 03:00:30	0|chatter29|sun is not doing allah is doing
  4 2017-04-05 03:00:32	0|chatter29|to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger
  5 2017-04-05 05:59:23	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/080d7c700fc3...fadf078c9cd7
  6 2017-04-05 05:59:24	0|bitcoin-git|13bitcoin/06master 14bd41d98 15Andrew Chow: Datadir option in linearize scripts...
  7 2017-04-05 05:59:24	0|bitcoin-git|13bitcoin/06master 14fadf078 15Wladimir J. van der Laan: Merge #10104: linearize script: Option to use RPC cookie...
  8 2017-04-05 05:59:46	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10104: linearize script: Option to use RPC cookie (06master...06linearize-use-cookie) 02https://github.com/bitcoin/bitcoin/pull/10104
  9 2017-04-05 06:11:03	0|bitcoin-git|[13bitcoin] 15laanwj pushed 4 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/fadf078c9cd7...5fc6a77aa626
 10 2017-04-05 06:11:04	0|bitcoin-git|13bitcoin/06master 145b95a19 15Alex Morcos: Make pcoinsTip memory calculations consistent...
 11 2017-04-05 06:11:04	0|bitcoin-git|13bitcoin/06master 14f33afd3 15Alex Morcos: Lower default memory footprint slightly
 12 2017-04-05 06:11:05	0|bitcoin-git|13bitcoin/06master 141b55e07 15Alex Morcos: Make threshold for flushing more conservative....
 13 2017-04-05 06:11:23	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10133: Clean up calculations of pcoinsTip memory usage (06master...06cachememory) 02https://github.com/bitcoin/bitcoin/pull/10133
 14 2017-04-05 06:23:38	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 060.14: 02https://github.com/bitcoin/bitcoin/compare/a44a6a15f94a...0e5133cb2ef8
 15 2017-04-05 06:23:39	0|bitcoin-git|13bitcoin/060.14 14ab864d3 15Alex Morcos: Make pcoinsTip memory calculations consistent...
 16 2017-04-05 06:23:39	0|bitcoin-git|13bitcoin/060.14 14d686768 15Alex Morcos: Lower default memory footprint slightly...
 17 2017-04-05 06:23:40	0|bitcoin-git|13bitcoin/060.14 140e5133c 15Alex Morcos: Make threshold for flushing more conservative....
 18 2017-04-05 06:37:13	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/5fc6a77aa626...f93f9b92969b
 19 2017-04-05 06:37:14	0|bitcoin-git|13bitcoin/06master 14ba7dd8b 15Suhas Daftuar: Test prioritisetransaction and ancestor fee state...
 20 2017-04-05 06:37:15	0|bitcoin-git|13bitcoin/06master 149bef02e 15Suhas Daftuar: Bugfix: ancestor modifed fees were incorrect for descendants...
 21 2017-04-05 06:37:15	0|bitcoin-git|13bitcoin/06master 14f93f9b9 15Wladimir J. van der Laan: Merge #10144: Prioritisetransaction wasn't always updating ancestor fee...
 22 2017-04-05 06:37:33	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10144: Prioritisetransaction wasn't always updating ancestor fee (06master...062017-04-fix-mempool-modified-ancestor-fees) 02https://github.com/bitcoin/bitcoin/pull/10144
 23 2017-04-05 06:52:17	0|wumpus|I think we're ready to tag 0.14.1rc1 again
 24 2017-04-05 06:55:53	0|jonasschnelli|ack
 25 2017-04-05 06:56:51	0|sipa|awesöme
 26 2017-04-05 07:05:00	0|gmaxwell|awesöme
 27 2017-04-05 07:10:41	0|fanquake|I didn't realise we'd already done it once
 28 2017-04-05 07:13:09	0|bitcoin-git|[13bitcoin] 15laanwj pushed 3 new commits to 060.14: 02https://github.com/bitcoin/bitcoin/compare/0e5133cb2ef8...47d24c85b71b
 29 2017-04-05 07:13:10	0|bitcoin-git|13bitcoin/060.14 14d947afc 15Suhas Daftuar: Test prioritisetransaction and ancestor fee state...
 30 2017-04-05 07:13:11	0|bitcoin-git|13bitcoin/060.14 1447d24c8 15Wladimir J. van der Laan: Bump version to 0.14.1
 31 2017-04-05 07:13:11	0|bitcoin-git|13bitcoin/060.14 14ea060c7 15Suhas Daftuar: Bugfix: ancestor modifed fees were incorrect for descendants...
 32 2017-04-05 07:13:29	0|wumpus|no I didn't actually do it last friday, but was about to
 33 2017-04-05 07:14:32	0|gmaxwell|technically we're supposted to update the assumevalid, and work.. doesn't really matter much if we don't. But stating it for the future.
 34 2017-04-05 07:16:00	0|wumpus|that would need another review cycle
 35 2017-04-05 07:16:16	0|wumpus|it's not 'obvious' like the version bump
 36 2017-04-05 07:18:04	0|gmaxwell|yea, thats why I'm not saying "hold up hold up"
 37 2017-04-05 07:20:00	0|wumpus|but yes it's close enough after 0.14.0 that it shouldn't really matter
 38 2017-04-05 07:20:19	0|gmaxwell|yea, it's fine.
 39 2017-04-05 07:21:38	0|wumpus|v0.14.1rc1 pushed
 40 2017-04-05 07:24:21	0|bitcoin-git|13bitcoin/06master 14faab624 15MarcoFalke: logging: Fix off-by-one for shrinkdebugfile
 41 2017-04-05 07:24:21	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/f93f9b92969b...fade78854cf4
 42 2017-04-05 07:24:22	0|bitcoin-git|13bitcoin/06master 14fade788 15Wladimir J. van der Laan: Merge #10153: logging: Fix off-by-one for shrinkdebugfile default...
 43 2017-04-05 07:24:41	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10153: logging: Fix off-by-one for shrinkdebugfile default (06master...06Mf1704-offbyoneDebug) 02https://github.com/bitcoin/bitcoin/pull/10153
 44 2017-04-05 07:26:52	0|wumpus|MarcoFalke: off-by-one errors on booleans are an interesting concept :)
 45 2017-04-05 07:27:08	0|wumpus|off-by-one and off-by-everything at the same time
 46 2017-04-05 07:49:30	0|bitcoin-git|[13bitcoin] 15laanwj opened pull request #10155: build: Deduplicate version numbers (06master...062017_03_version_bump) 02https://github.com/bitcoin/bitcoin/pull/10155
 47 2017-04-05 07:52:06	0|bitcoin-git|[13bitcoin] 15AllanDoensen opened pull request #10156: Fix for issues with startup and mutiple monitors on windows. (06master...06masterMultiMonFix) 02https://github.com/bitcoin/bitcoin/pull/10156
 48 2017-04-05 09:28:35	0|bitcoin-git|13bitcoin/06master 14faafa80 15MarcoFalke: init: Remove redundant logging code
 49 2017-04-05 09:28:35	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/fade78854cf4...3c95bd43d8ff
 50 2017-04-05 09:28:36	0|bitcoin-git|13bitcoin/06master 143c95bd4 15Wladimir J. van der Laan: Merge #10154: init: Remove redundant logging code...
 51 2017-04-05 09:28:55	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10154: init: Remove redundant logging code (06master...06Mf1704-lognodebug) 02https://github.com/bitcoin/bitcoin/pull/10154
 52 2017-04-05 09:30:28	0|bitcoin-git|13bitcoin/06master 14cd7f394 15John Newbery: initialize flag variable to 0 (and continue if GetLogCategory() fails)
 53 2017-04-05 09:30:28	0|bitcoin-git|[13bitcoin] 15laanwj pushed 2 new commits to 06master: 02https://github.com/bitcoin/bitcoin/compare/3c95bd43d8ff...c7e73eafa139
 54 2017-04-05 09:30:29	0|bitcoin-git|13bitcoin/06master 14c7e73ea 15Wladimir J. van der Laan: Merge #10151: [logging] initialize flag variable to 0 (and continue if GetLogCategory() fails)...
 55 2017-04-05 09:30:52	0|bitcoin-git|[13bitcoin] 15laanwj closed pull request #10151: [logging] initialize flag variable to 0 (and continue if GetLogCategory() fails) (06master...06logging_initialization) 02https://github.com/bitcoin/bitcoin/pull/10151
 56 2017-04-05 09:53:04	0|bitcoin-git|13bitcoin/060.14 14920acbc 15Wladimir J. van der Laan: doc: Update release notes for 0.14.1
 57 2017-04-05 09:53:04	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 060.14: 02https://github.com/bitcoin/bitcoin/commit/920acbcca8240cb11a74055a81d5129c8a4c85af
 58 2017-04-05 09:53:22	0|wumpus|anoyone care to write something about notable changes in 0.14.1? https://github.com/bitcoin/bitcoin/blob/0.14/doc/release-notes.md#notable-changes
 59 2017-04-05 09:55:57	0|wumpus|(or if you contributed to 0.14.1 and somehow your name is missing in the credits, let me know)
 60 2017-04-05 10:03:30	0|sipa|only behavior changes are the already listed arg rename, memory usage changes, and default segwit enable?
 61 2017-04-05 10:04:20	0|wumpus|yes, I think so
 62 2017-04-05 10:04:44	0|wumpus|lol "#10094 37bf0d5 0.14: Clear release notes (MarcoFalke)" I left a meta-PR in
 63 2017-04-05 10:04:45	0|gribble|https://github.com/bitcoin/bitcoin/issues/10094 | 0.14: Clear release notes by MarcoFalke · Pull Request #10094 · bitcoin/bitcoin · GitHub
 64 2017-04-05 10:38:32	0|fanquake|Looks alright
 65 2017-04-05 10:39:14	0|fanquake|wumpus will you try push detached sigs tonight? I'll upload my unsigned sigs in a minute.
 66 2017-04-05 10:41:22	0|wumpus|fanquake: that's up to cfields, I think he waits for a few unsigned sigs first
 67 2017-04-05 11:03:02	0|bitcoin-git|[13bitcoin] 15laanwj pushed 1 new commit to 060.14: 02https://github.com/bitcoin/bitcoin/commit/df82ea914f6f569e244ab59ca24e4eea898eb1a9
 68 2017-04-05 11:03:03	0|bitcoin-git|13bitcoin/060.14 14df82ea9 15Wladimir J. van der Laan: doc: Remove release note about release notes
 69 2017-04-05 11:08:25	0|Victorsueca|lol, release-note-inception
 70 2017-04-05 11:09:02	0|wumpus|yeah :-)
 71 2017-04-05 12:22:46	0|sdaftuar|wumpus: i think the backport of the test in #10144 to the 0.14 branch is broken, due to the api change in prioritisetransaction
 72 2017-04-05 12:22:47	0|gribble|https://github.com/bitcoin/bitcoin/issues/10144 | An error has occurred and has been logged. Please contact this bot's administrator for more information.
 73 2017-04-05 12:23:35	0|wumpus|okay
 74 2017-04-05 12:24:25	0|sdaftuar|i'll try to pr a fix shortly
 75 2017-04-05 12:25:21	0|wumpus|yes I only looked whether the test wouldn't start failing after backport
 76 2017-04-05 12:25:35	0|BlockchainKid|hi
 77 2017-04-05 12:25:35	0|wumpus|it could be passing wrongly
 78 2017-04-05 12:27:11	0|sdaftuar|wumpus: odd, the test is failing for me locally due to the api change, maybe its an extended test?
 79 2017-04-05 12:27:45	0|sdaftuar|ah, yes its an extended test
 80 2017-04-05 12:33:18	0|wumpus|oh indeed didn't check the extended ones
 81 2017-04-05 12:34:35	0|bitcoin-git|[13bitcoin] 15sdaftuar opened pull request #10157: [0.14] Fix the mempool_packages.py test (060.14...06test-0.14.1rc1) 02https://github.com/bitcoin/bitcoin/pull/10157
 82 2017-04-05 13:32:29	0|achow101|weren't there some memory usage improvements in 0.14.1?
 83 2017-04-05 13:35:50	0|BlueMatt|achow101: for default configs, yes, and slightly reduced in general from 0.14.0, yes?
 84 2017-04-05 13:43:09	0|achow101|Ok. Well I think they should be documented in the release notes
 85 2017-04-05 16:22:53	0|cfields|I'm working on building/signing rc1. I'm out of town and using my laptop, so it's a bit painful and slower than usual.
 86 2017-04-05 17:17:53	0|bincap|when writting functional tests in python, we can use .generate to add blocks to test blockchain; and can I add a block with manually set flags, like segwit signalling on/off?
 87 2017-04-05 17:20:30	0|bincap|also, how to set given date of the block generation? I want to test bip148 that rejects blocks that do not signal for segwit activation
 88 2017-04-05 17:27:22	0|bitcoin-git|[13bitcoin] 15gmaxwell opened pull request #10158: Add some more release notes for 0.14.1. (060.14...06relnote141) 02https://github.com/bitcoin/bitcoin/pull/10158
 89 2017-04-05 19:57:40	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10159: [tests] color test results and sort alphabetically (06master...06sort_test_results) 02https://github.com/bitcoin/bitcoin/pull/10159
 90 2017-04-05 21:40:40	0|gmaxwell|https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/013996.html
 91 2017-04-05 21:49:05	0|bitcoin-git|[13bitcoin] 15jnewbery opened pull request #10160: [WIP] updatepeer RPC (06master...06updatepeer) 02https://github.com/bitcoin/bitcoin/pull/10160
 92 2017-04-05 22:22:48	0|jeremyrubin|gmaxwell: I think your asicboost description is backwards?
 93 2017-04-05 22:23:04	0|jeremyrubin|or am I misunderstanding
 94 2017-04-05 22:23:38	0|jeremyrubin|distinct first 64-byte chunks but identical 16-byte
 95 2017-04-05 22:25:50	0|jeremyrubin|Oh maybe I'm misunderstanding how asicboost works?
 96 2017-04-05 22:26:33	0|gmaxwell|I think you were misunderstanding, or my explination is unclear.
 97 2017-04-05 22:27:30	0|gmaxwell|for asic boost you need multiple different first-compression runs for each second compression run.  This allows you to reuse the computation for the message expansion in the second compression run.
 98 2017-04-05 22:27:55	0|jeremyrubin|yeah I'm misunderstanding merkle damgard
 99 2017-04-05 22:28:05	0|gmaxwell|I think part of the reason people haven't taken it seriously as a threat is because it's tricky to understand.
100 2017-04-05 22:29:27	0|gmaxwell|while talking about it privately for the last month I ran into many experts that kept lapsing into thinking that the collision required 2^32 work, and other misunderstandings.
101 2017-04-05 22:31:28	0|jeremyrubin|gmaxwell: I think it gets a bit scarier if you don't include any transactions?
102 2017-04-05 22:32:10	0|jeremyrubin|gmaxwell: Maybe this is related to why ------- is mining empty blocks?
103 2017-04-05 22:32:32	0|jeremyrubin|gmaxwell: or if you only include stale transactions you control and guarantee won't be spent in a prior block
104 2017-04-05 22:33:33	0|jeremyrubin|gmaxwell: this would suggest your solution of including header hash is worth it
105 2017-04-05 22:36:52	0|gmaxwell|My goal here is only to block the form which is incompatible with protocol improvements like segwit that add additional per transaction data.  I leave blocking asicboost more generally an open question.  A miner could mine empty blocks too, but they'll at least be disadvantaged by the loss of fee income-- so, personally, I feel that is largely self correcting.
106 2017-04-05 22:37:45	0|jeremyrubin|I see; I think that's reasonable.
107 2017-04-05 22:38:33	0|jeremyrubin|You don't nescessarily lose that much fee though this way, I'd point out. You can just mine things closer to the bottom which are unlikely to get mined.
108 2017-04-05 22:39:10	0|jeremyrubin|You can also mask it by mining a full block with only your transactions in it.
109 2017-04-05 22:40:53	0|Taek|even masked, you are still disadvantaged
110 2017-04-05 22:42:09	0|jeremyrubin|Taek: yeah, but you get a huge benefit, because your set of valid RHS commitments goes up over time and only decreases (by 1) when you mine
111 2017-04-05 23:02:56	0|gmaxwell|jeremyrubin: if you can't do the left/right split trick you have to do a log(txn) hashes for each try.
112 2017-04-05 23:03:39	0|gmaxwell|In any case: the goal, again, isn't to stop asicboost but to stop forms that are incompatible with protocol extensions. I believe anything that works after this bip works just as well with segwit and friends.
113 2017-04-05 23:04:15	0|gmaxwell|I expect other people to make proposals to block asicboost more completely (in fact, I kind of cut off private discussion along these lines with this proposal-- because I think it's critical to seperate the concerns)
114 2017-04-05 23:32:50	0|btcdrak|There's a writeup of the process https://www.irccloud.com/pastebin/JjfwEylh/