1 2016-02-06 00:20:36 <denisx> is it intentionally that all the files in the rc archives have the date of january first of 2016?
 2 2016-02-06 00:26:12 <Luke-Jr> denisx: probably, but I think it would be a good improvement to use their last-modified-date
 3 2016-02-06 00:26:14 <moa> exactly 46 years unix time
 4 2016-02-06 00:29:23 <gmaxwell> denisx: presumably a faketime artifact.
 5 2016-02-06 00:55:14 <gijensen> kaalia, the first release of my tool is (hopefully) ready: https://github.com/GIJensen/sbtc
 6 2016-02-06 01:50:41 <btc3535> Get free bitcoins at www.1freebitcoin.com
 7 2016-02-06 04:41:18 <maaku_> denisx: yes it is a result of the gitian build process
 8 2016-02-06 04:41:50 <maaku_> well, not intentional, but a known side effect
 9 2016-02-06 10:44:00 <sea`> Why must the blockchain store every transaction? Wouldn't it be better to keep a single state block 'at the beginning' recording the balances on each address with the rule: "Upon a block becoming older than n months, merge it into the 'state block', then delete it.", and with the 'current' state block's hash stored in each block, so bootstrapping nodes can spot fakes?
10 2016-02-06 10:53:28 <Luke-Jr> sea`: that's calling "flipping the chain", not implemented, and relies on trusting miners
11 2016-02-06 10:53:47 <Luke-Jr> sea`: also, addresses don't exist at the blockchain level; having balances would screw up privacy
12 2016-02-06 11:12:04 <sea`> Okay then, but why does it rely on trusting miners? Can't the non-mining nodes double-check the hash and reject new blocks that get it wrong?
13 2016-02-06 17:16:17 <JokerCatz> Hi , all , somebody can help me ? https://github.com/bitcoin/bitcoin/issues
14 2016-02-06 17:16:34 <JokerCatz> ...sorry... this : https://github.com/bitcoin/bitcoin/issues/7475
15 2016-02-06 17:17:08 <JokerCatz> & sorry me poor English
16 2016-02-06 17:23:10 <denisx> JokerCatz: youre running 0.11.2?
17 2016-02-06 17:24:13 <JokerCatz> yep~ 0.11.2
18 2016-02-06 17:24:42 <denisx> I had the same problems with 0.11.2. is it possible for you to try 0.12.0rc3?
19 2016-02-06 17:24:48 <denisx> because this version really rocks
20 2016-02-06 17:25:28 <JokerCatz> It danger? upgrade to 0.12.rc3?
21 2016-02-06 17:25:39 <JokerCatz> and where to download it?
22 2016-02-06 17:25:42 <denisx> JokerCatz: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-February/012356.html
23 2016-02-06 17:27:45 <denisx> JokerCatz: is a “bitcoin-cli getinfo” also slow for you?
24 2016-02-06 17:28:14 <denisx> JokerCatz: btw, you should not post the amount of your bitcoins on github
25 2016-02-06 17:28:31 <JokerCatz> yep , because sendfrom is very slow...
26 2016-02-06 17:29:06 <JokerCatz> okay thanx
27 2016-02-06 17:29:33 <denisx> JokerCatz: whatever you do, make backups!
28 2016-02-06 17:30:12 <JokerCatz> okay , I will try upgrade to 0.12.rc3 , first backup it
29 2016-02-06 17:30:32 <denisx> JokerCatz: and read the changelog before
30 2016-02-06 17:30:49 <denisx> if anything is not clear to you it is better to ask again
31 2016-02-06 17:31:23 <JokerCatz> okay : )
32 2016-02-06 17:53:07 <JokerCatz> denisx , same , very slow ... and we will try like split send and receive to different server...
33 2016-02-06 17:53:38 <denisx> JokerCatz: is your blockchain on a harddisk?
34 2016-02-06 17:53:58 <denisx> JokerCatz: also your wallet is very big, maybe you need to start a fresh wallet
35 2016-02-06 17:53:59 <JokerCatz> yep , full node
36 2016-02-06 17:54:14 <denisx> check your harddisk for io-errors
37 2016-02-06 17:54:36 <JokerCatz> okay and we will change to SSD too :x
38 2016-02-06 17:55:11 <JokerCatz> many thanx denisx : )
39 2016-02-06 17:55:41 <denisx> you can test with an empty wallet first
40 2016-02-06 17:56:04 <denisx> stop bitcoind, move your wallet to a safe place and start bitcoind
41 2016-02-06 17:56:21 <denisx> then you have an empty wallet. now check how fast it is with getinfo and so on
42 2016-02-06 17:56:40 <JokerCatz> ohh....okok
43 2016-02-06 17:56:54 <JokerCatz> so this call "empty wallet"?
44 2016-02-06 17:57:19 <denisx> if bitcoind sees no wallet it will create a new one
45 2016-02-06 17:58:42 <JokerCatz> hmm...no~ I need keep all wallet...it has relation from db :x
46 2016-02-06 17:59:46 <denisx> JokerCatz: ok, I understnd
47 2016-02-06 17:59:57 <JokerCatz> but I will check my server speed like IO / mem / CUP ...
48 2016-02-06 18:00:11 <denisx> my wallet is 25MB and switching to 0.12.0rc3 solved my problems
49 2016-02-06 18:00:38 <denisx> and I only had the problems with 0.11.2, not before
50 2016-02-06 22:42:25 <kanzure> "Is anyone trying to "fix" git's usage of SHA1?  I donno if that'd mean a migration path for git itself, complete with worries about downgrade attacks.. or another tool to run alongside git itself."
51 2016-02-06 22:42:29 <kanzure> "I forked git on github last week, thinking I'd do exactly that, but when I searched through the code, I found that SHA1 is hard-coded in a zillion places.  It can be done, obviously, but it will be a fair amount of work, and it will be impossible to keep it in sync with the master dev branch. Git should migrate.  The challenge is convincing Linus that it is worth doing, since he insists that git does not provide data integrity against ...
52 2016-02-06 22:42:36 <kanzure> ... malicious attacks, and that security must be built around git.  It would require either changing his mind, or getting momentum behind a hard fork."
53 2016-02-06 22:44:40 <kanzure> https://git.wiki.kernel.org/index.php/LinusTalk200705Transcript
54 2016-02-06 22:45:41 <anddevil> hello