1 2016-04-06 00:24:34 <Lightsword> I’m thinking about adding block version to cgminer’s API, what’s the best format to display that?
 2 2016-04-06 01:14:39 <PRab> I don't know who maintains https://bitcoin.org/en/download, but it still quotes the blockchain at over 20GB. That should probably be updated to over 60GB at this point.
 3 2016-04-06 01:42:35 <moli> PRab, agreed, also it would be great if they put in a note when someone click on Core wallet, tell them something like "Depending on your hardware and bandwidth, this will wallet will take some time to sync before you can see your coins if you want to use it now. So, if you need to do a transaction immediately please choose another wallet like electrum."
 4 2016-04-06 02:45:01 <rusty> Anyone working on a new addr format for direct segwit programs?  Perhaps http://philzimmermann.com/docs/human-oriented-base-32-encoding.txt + Damm encoding with quasigroups optimized for that encoding + a few digits of extra csum?
 5 2016-04-06 03:22:59 <kanzure> "Note that signed commits only validate the commit file contents up to the SHA1 of the top level tree, it's not a GPG signature of the entire tree state. This means that a SHA1 collision on the tree object, or any blob object, still results in a valid GPG signature. So git GPG doesn't provide any additional security over SHA1; it only provides proof that a certain person signed a SHA1 and the commit message."
 6 2016-04-06 03:23:12 <kanzure> rusty: there was some discussion in #segwit-dev regarding encoding schemes like that, see backlog..
 7 2016-04-06 03:23:43 <rusty> kanzure: that channel isn't logged, right?
 8 2016-04-06 03:24:01 <kanzure> ugh
 9 2016-04-06 04:33:47 <DatBeeDoe> rning felaz
10 2016-04-06 12:34:57 <Lucifer333> hello
11 2016-04-06 12:35:37 <Lucifer333> I want to become a bitcoin dev, I have read the source code (jgarzik) forks , the  #bitcoin jobs is dead in the water though
12 2016-04-06 17:17:07 <xenog> Is anybody doing work on storing block data in a DHT?
13 2016-04-06 21:31:08 <williamcotton> does anyone know how the new Random-cookie RPC authentication works?
14 2016-04-06 21:32:10 <williamcotton> what's the name of the cookie file? and where is it located? I don't see it in the same dir as bitcoind.pid
15 2016-04-06 21:33:25 <williamcotton> https://bitcoin.org/en/release/v0.12.0#rpc-random-cookie-rpc-authentication
16 2016-04-06 21:44:48 <phantomcircuit> wumpus, ^
17 2016-04-06 21:57:45 <achow101> williamcotton: the file is .cookie in the data directory. make sure that you have -server set and no rpcpassword set