1 2016-04-16 02:58:45 0|GitHub107|[13bitcoin] 15kazcw opened pull request #7888: prevector: fix 2 bugs in currently unreached code paths (06master...06pvfix) 02https://github.com/bitcoin/bitcoin/pull/7888
2 2016-04-16 10:51:15 0|GitHub65|[13bitcoin] 15sipa opened pull request #7891: Always require OS randomness when generating secret keys (06master...06betterrng) 02https://github.com/bitcoin/bitcoin/pull/7891
3 2016-04-16 11:53:05 0|nsh|scary PR is scary...
4 2016-04-16 11:54:21 0|sipa|nsh: mine?
5 2016-04-16 11:54:43 0|nsh|aye, but doesn't look so bad on inspection
6 2016-04-16 11:55:07 0|nsh|had a brief but-for-the-grace-of-god moment
7 2016-04-16 11:56:38 0|nsh|heh, seems nothing else is using RandAddSeedPerfmon anymore
8 2016-04-16 11:57:26 0|sipa|there are calls at first startup, inside processmessages, and before signing in the wallet
9 2016-04-16 11:59:35 0|gmaxwell|I earlier made the observation to sipa that getting away from openssl's RNG has three parts: A combiner to take OS randomness at the point of key usage; an internal CSPRNG; and a seeding process. The internal CSPRNG has implementation annoyances around things like thread safty. But we can do the other two parts with openssl still there, taking the places of the eventual internal CSPRNG.
10 2016-04-16 11:59:46 0|gmaxwell|And so that would be a good way to make progress on this.
11 2016-04-16 12:00:39 0|nsh|makes sense
12 2016-04-16 12:05:13 0|nsh|what might be thread-unsafe about an internal CSPRNG?
13 2016-04-16 12:05:40 0|sipa|well you need locking on your entropy pool
14 2016-04-16 12:05:48 0|sipa|at the very least
15 2016-04-16 12:06:23 0|sipa|or perhaps per-thread entropy pools (using thread local storage), which only under certain conditions request entropy from the global process-wide one
16 2016-04-16 12:07:53 0|sipa|and these are things you can't easily do in a portable C library (which is something that was requested before in #5885 and #7162)
17 2016-04-16 13:51:10 0|GitHub86|[13bitcoin] 15laanwj opened pull request #7892: Add full UTF-8 support to RPC (06master...062016_04_i18n_unicode_rpc) 02https://github.com/bitcoin/bitcoin/pull/7892
18 2016-04-16 13:55:37 0|Chris_Stewart_5|With these version bits we could make radical departures to Script as we see it now right? For instance trying to type Script?
19 2016-04-16 13:56:01 0|sipa|yes
20 2016-04-16 13:56:16 0|Chris_Stewart_5|oooh so much potential :-)
21 2016-04-16 14:04:50 0|Luke-Jr|well, that's segwit's witness script versioning more than versionbits..
22 2016-04-16 14:06:26 0|sipa|Luke-Jr: oh, absolutely
23 2016-04-16 14:06:38 0|sipa|though the combination makes it even easier
24 2016-04-16 14:10:22 0|Chris_Stewart_5|I'll have to read up on the difference
25 2016-04-16 14:10:45 0|sipa|versionbits is about being to roll out multiple softforks in parallel
26 2016-04-16 14:11:02 0|sipa|segwit script versioning means every script change can be turned into a softfork
27 2016-04-16 14:11:46 0|Chris_Stewart_5|intuitively I thought the script verisioning just allows for versions similar to other PLs - for instance python 2.7.x is that more or less correct?
28 2016-04-16 14:12:29 0|sipa|right now, we can't for example change checksig to use a different signature type
29 2016-04-16 14:13:08 0|sipa|(that would be a hardfork)
30 2016-04-16 14:13:11 0|Chris_Stewart_5|sure
31 2016-04-16 14:13:28 0|sipa|with script versioning, we can just change checksig's definition
32 2016-04-16 14:13:52 0|sipa|wumpus or any other gitian building, are there any known problems with certain gitian virtualizations? (virtualbox, KVM, LXC, ...) ?
33 2016-04-16 14:14:22 0|sipa|or are they all known to work?
34 2016-04-16 14:14:56 0|sipa|nvm
35 2016-04-16 14:14:56 0|sipa|oh, that's the outer layer virtualization
36 2016-04-16 14:15:12 0|Chris_Stewart_5|What about size requirements? That is vague question but perhaps we decide not to use SHA256 anymore and switch to another hash algorithm that produces a different size of digest compared to SHA256
37 2016-04-16 14:15:32 0|sipa|yes, maybe
38 2016-04-16 14:15:35 0|Chris_Stewart_5|Could this 'bleed' out of the script versioning system into other parts of consensus code?
39 2016-04-16 14:15:40 0|Chris_Stewart_5|if that makes any sense
40 2016-04-16 14:15:50 0|sipa|it can be made not to
41 2016-04-16 14:16:02 0|Chris_Stewart_5|interesting
42 2016-04-16 16:09:47 0|MarcoFalke|re: cpp11
43 2016-04-16 16:09:48 0|MarcoFalke|> wumpus: hopefully we can start supporting it this week then
44 2016-04-16 16:09:57 0|MarcoFalke|Does this mean we have trusty in travis this week?
45 2016-04-16 16:10:24 0|wumpus|yes
46 2016-04-16 16:11:01 0|MarcoFalke|good, so the py3.2 issue is not a blocker for the py3 switch
47 2016-04-16 16:51:22 0|sipa|hmm, doc/release-process.md mentions that detached signatures are posted to https://github.com/bitcoin/bitcoin-detached-sigs
48 2016-04-16 16:51:31 0|sipa|but that seems to have only beed the case for 0.10 and 0.11
49 2016-04-16 16:53:12 0|MarcoFalke|0.12 has a fresh branch
50 2016-04-16 16:53:37 0|sipa|oh
51 2016-04-16 18:25:36 0|GitHub141|[13bitcoin] 15domob1812 opened pull request #7894: [Qt] Use CURRENCY_UNIT for BitcoinUnits. (06master...06currency-unit) 02https://github.com/bitcoin/bitcoin/pull/7894
52 2016-04-16 20:36:12 0|GitHub140|[13bitcoin] 15dooglus opened pull request #7896: fix typo in help text (06master...06patch-1) 02https://github.com/bitcoin/bitcoin/pull/7896
53 2016-04-16 20:43:15 0|GitHub127|[13bitcoin] 15dooglus opened pull request #7897: add missing newline (06master...06patch-2) 02https://github.com/bitcoin/bitcoin/pull/7897
54 2016-04-16 21:28:33 0|GitHub122|[13bitcoin] 15dooglus opened pull request #7898: optionally provide privkey to signmessage RPC (06master...06signmessage-using-privkey) 02https://github.com/bitcoin/bitcoin/pull/7898
55 2016-04-16 21:32:18 0|GitHub14|[13bitcoin] 15dooglus closed pull request #7898: optionally provide privkey to signmessage RPC (06master...06signmessage-using-privkey) 02https://github.com/bitcoin/bitcoin/pull/7898
56 2016-04-16 21:36:59 0|GitHub177|[13bitcoin] 15dooglus opened pull request #7899: optionally provide privkey to signmessage RPC (06master...06signmessage-using-privkey) 02https://github.com/bitcoin/bitcoin/pull/7899