1 2016-02-07 11:34:47 <priidu> just a reminder, wrote about this the other day -- the estimated hashrate in "getmininginfo" and "getnetworkhashps" RPCs (and maybe elsewhere) will wrap if the hashrate rises by another order of magnitude
 2 2016-02-07 11:35:24 <priidu> maybe someone more comfortable with the codebase could create a PR or should I create an issue myself?
 3 2016-02-07 11:36:24 <priidu> Luke advised me to create a PR myself but I find myself ill-equipped (don't know the codebase well enough and am not a professional C++ dev), so dont want to mess something up
 4 2016-02-07 11:40:20 <priidu> IIRC, the hashrate is cast into int64_t
 5 2016-02-07 11:40:59 <priidu> so where about 13% the way there currently, to it wrapping
 6 2016-02-07 11:42:01 <priidu> it's probably used in more places then mining.cpp though, so might need a more thorough rewrite then just chaning the cast?
 7 2016-02-07 11:42:14 <priidu> or maybe not? :P
 8 2016-02-07 11:42:21 <aj> priidu: create an issue at least? https://github.com/bitcoin/bitcoin/issues
 9 2016-02-07 11:44:06 <priidu> Yeah, I suppose I will do just that then
10 2016-02-07 11:44:07 <priidu> thanks
11 2016-02-07 11:53:18 <phantomcircuit> priidu, that's actually really neat
12 2016-02-07 12:49:57 <priidu> created an issue here: https://github.com/bitcoin/bitcoin/issues/7476 at least it's documented now :P
13 2016-02-07 19:18:04 <arubi> I never did appreciate the word 'magic' until I tried understanding how core signs arbitrary messages.
14 2016-02-07 19:18:18 <Diablo-D3> I didn't appreciate the word magic
15 2016-02-07 19:18:25 <Diablo-D3> until I saw how L4 messaging works
16 2016-02-07 19:18:54 <arubi> I don't even know what's L4, and searching for it will be very hard
17 2016-02-07 19:19:31 <arubi> anyway, The "Bitcoin Signed Message:\n" is easy enough to find, but then somewhere down the line a 0x18 byte is prepended (thank you nanotube for that), then after 0x0a there's a length byte.  now, it seems I can't properly hash some lengths of a message.
18 2016-02-07 19:20:03 <Diablo-D3> arubi: its a kernel/OS based around message passing
19 2016-02-07 19:20:44 <Diablo-D3> arubi: in x86 builds that are optimized well, it does a message pass between two userland apps in something like 40 actual assembly instructions
20 2016-02-07 19:21:10 <Diablo-D3> anything that can jump into kernel space and do that, and jump back out in that short of a runway is fucking magic
21 2016-02-07 19:22:06 <arubi> that does sound magical.  I'll have to read more
22 2016-02-07 19:22:36 <Diablo-D3> https://en.wikipedia.org/wiki/L4_microkernel_family
23 2016-02-07 19:22:55 <arubi> right, I'm in the page already
24 2016-02-07 19:23:05 <Diablo-D3> k
25 2016-02-07 19:23:34 <arubi> also, just so I won't leave an open question  lying around, I hash256 this data: '0x18''Signed Bitcoin Message:''0x0a''0x<len>''message'.  It comes out fine if len(message)={0x01..0xFC} (1..252), but not {0xFD..FF}.
26 2016-02-07 19:24:16 <arubi> I know it's wrong because I'm feeding ( z=(hash256(m) mod n), r, s) to a 'recover' function and it only recovers the correct public key in those 1..252 times.  I'm always using the same "address" to sign the message in core.
27 2016-02-07 19:25:02 <arubi> and I can't even begin to wonder how a 256 byte message length would look like.  I tried.. I couldn't get it :(
28 2016-02-07 19:26:57 <arubi> I'd try signing myself and validate against core's signature, but I didn't implement generation of k yet.  I grab k's from valid signatures currently and see that I get correct results, and I can't get k if I can't get z
29 2016-02-07 19:51:40 <arubi> crap.  also, I'm effectively on a 70% uptime 128kb/s dsl line at the moment.  if I appear to be ignoring your answers as to how the length byte is appended, please use gribble to tell me.  thanks.
30 2016-02-07 19:53:58 <arubi> er,  "Bitcoin Signed Message:"  ^, my bad.
31 2016-02-07 20:27:48 <fakesatoshi> hi just ran core with prune !! wish me good luck !!
32 2016-02-07 20:28:54 <fakesatoshi> i use special setup .dat files are symlinks because no room on /home .. hope it works
33 2016-02-07 20:33:43 <fakesatoshi> holy shit it's up. and wallet works with pruning? just send myself few satoshi
34 2016-02-07 20:34:41 <fakesatoshi> WTF I love it.
35 2016-02-07 20:34:47 <fakesatoshi> THAAAANKS!!!
36 2016-02-07 20:35:45 <belcher> congratulations, you are using bitcoin in the most secure and trustless way possible
37 2016-02-07 20:59:26 <magichex> hi there
38 2016-02-07 20:59:36 <magichex> im trying to do gitian build for fun
39 2016-02-07 20:59:43 <magichex> and getting this err
40 2016-02-07 20:59:46 <magichex> /lib/x86_64-linux-gnu/libdl.so.2: error adding symbols: DSO missing from command line
41 2016-02-07 20:59:50 <magichex> any ideas?