1 2017-02-04 03:39:12 <BW^-> Does BitcoinD have some DEFINE for individual target OS:es e.g. for OPENBSD, LINUX, FREEBSD, etc.?
 2 2017-02-04 03:47:07 <Diablo-D3> when you grepped the source, did you find it?
 3 2017-02-04 03:51:56 <BW^-> Diablo-D3: for LevelDB there's an "OS_OPENBSD" define..
 4 2017-02-04 03:53:31 <BW^-> em.. BitcoinD seems to rely on the "TARGET_OS" define.. and currently there's "linux", "darwin" and "windows".
 5 2017-02-04 04:16:25 <BW^-> diablo-d3,*: some more attention here pls https://github.com/bitcoin/bitcoin/pull/9677
 6 2017-02-04 04:20:39 <Diablo-D3> why me?
 7 2017-02-04 06:18:12 <BW^-> diablo-d3: the next thing here is to figure what DEFINE tells the BitcoinD code that it's an OpenBSD build target.
 8 2017-02-04 06:19:15 <BW^-> also, there should be some feedback about whether arc4random use should be OpenBSD-specific, or specific to any platfor with arc4random support. I guess the further is the more sensible approach, as other platforms with arc4random support (that is FreeBSD and Mac OS X) have unsecure arc4random implementations, at least they had until very recently.
 9 2017-02-04 18:18:40 <sturles> This "hardfork code" the Chineese miners are waiting for, will that contain provisions for switching mining algorithm as well?  I hope so..
10 2017-02-04 18:19:43 <TZander> Are the chinese waiting for any hardfork code?
11 2017-02-04 18:20:05 <sturles> I think it was part of a deal sometime ago.
12 2017-02-04 18:20:50 <TZander> oh, well, everyone gave up on that code months ago
13 2017-02-04 18:21:25 <TZander> many core devs said they had no say in the agreement and had no interest in shipping such a hard fork
14 2017-02-04 18:22:17 <sturles> https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d475a61ff#.6z8z3je7y
15 2017-02-04 18:24:34 <sturles> https://github.com/luke-jr/bips/blob/bip-mmhf/bip-mmhf.mediawiki