1 2014-01-25 13:08:53 <rodders> Dudes Whats new in bitcoin software developments? What projects do you guys have?
 2 2014-01-25 13:09:20 <CCSLNS> I want to script with python to access the data we get from the wallet through the console commands. Best resources?
 3 2014-01-25 13:10:16 <Jouke> https://en.bitcoin.it/wiki/API_reference_%28JSON-RPC%29
 4 2014-01-25 13:14:02 <waxwing> probably a stupid question, but is there any way to derive an ssh key from a bitcoin private key? is there enough entropy? i'd like to use the bitcoin key to avoid having another key for users
 5 2014-01-25 13:14:26 <sipa> no
 6 2014-01-25 13:14:38 <sipa> ssh does not use the same elliptic curve
 7 2014-01-25 13:15:39 <sipa> you can of course use a bitcoin key as seed for generating an ssh key, but it will nit allow verification using the bitcoin public key or address
 8 2014-01-25 13:15:48 <sipa> also, you should not reuse bitcoin keys
 9 2014-01-25 13:16:01 <waxwing> heh just one reason was enough :)
10 2014-01-25 13:16:12 <waxwing> but yeah i think i get it
11 2014-01-25 13:16:15 <waxwing> thanks
12 2014-01-25 13:18:55 <waxwing> i could imagine it working for ephemeral identities all the same, i mean, you can just generate the new pubkey (the ssh one)
13 2014-01-25 13:43:47 <shamoon> how do you calculate the hash160 from a bitcoin address?
14 2014-01-25 13:52:23 <sipa> shamoon: base58 decode it, strip the version byte in front, and strip the 4 last bytes (checksum)
15 2014-01-25 13:52:30 <shamoon> thanks
16 2014-01-25 13:52:34 <shamoon> what exactly is a hash160?
17 2014-01-25 13:52:49 <sipa> it's a 160-bit hash of the public key
18 2014-01-25 13:53:04 <sipa> ripemd160(sha256(pulickey))
19 2014-01-25 13:53:17 <shamoon> what is the use?
20 2014-01-25 13:53:46 <sipa> what is the use of addrewsses?
21 2014-01-25 13:53:52 <sipa> *addresses
22 2014-01-25 13:53:59 <shamoon> publicly identify a recipient
23 2014-01-25 13:54:00 <shamoon> of a tx
24 2014-01-25 13:55:13 <sipa> yeah
25 2014-01-25 13:55:54 <sipa> well, the reason for not using full public keys, but addresses instead, is because satoshi believed public keys were 65 bytes long (this is not true, 33 suffices)
26 2014-01-25 13:56:12 <sipa> which would result in very long strings to identify destinations
27 2014-01-25 13:56:39 <sipa> so instead, we use the 160-bit hash of that public jey, which is over 3 times shorter
28 2014-01-25 13:57:48 <sipa> and use transactions that say "give me a public key and signature, such that that signature is valid for that public key, and the hash of that public key is X"
29 2014-01-25 13:58:03 <sipa> instead of "give a signature valid for public key Y"
30 2014-01-25 14:30:44 <sipa> wumpus: regarding BIP30 integration
31 2014-01-25 14:31:22 <sipa> wumpus: i'm wondering about abolishing the keypool, and simply considering a key used when it is seen in a receiving transaction
32 2014-01-25 14:31:39 <sipa> which wouldn't require any state in the wallet
33 2014-01-25 14:31:50 <sipa> apart from the transactions which are already there
34 2014-01-25 14:32:10 <sipa> wait, that can't work
35 2014-01-25 14:32:43 <sipa> if you ask for a new address a second time, it needs to be a different one
36 2014-01-25 14:33:53 <sipa> wumpus: do you think we should retain non-deterministic behaviour?
37 2014-01-25 14:42:48 <fanquake> Dipolo Ended up installing Qt 5.2 this arvo. Haven't actually compiled yet, need to fix some includes somewhere.
38 2014-01-25 14:43:18 <sipa> "arvo" ?
39 2014-01-25 14:43:44 <fanquake> sipa: It's aussie slang for afternoon.
40 2014-01-25 14:43:59 <sipa> heh, ok
41 2014-01-25 14:44:03 <sipa> never heard it before
42 2014-01-25 14:48:05 <fanquake> sipa: heh, not too surprising. We have plenty of weird words over here.
43 2014-01-25 16:44:20 <mr_burdell> is this where the people that write sx hang out?  it's not creating deterministic addresses
44 2014-01-25 17:35:30 <andytoshi> mr_burdell: sx is entirely genjix i think, i dunno where he idles
45 2014-01-25 19:53:39 <andytoshi> i just announced my coinjoin client on bct https://bitcointalk.org/index.php?topic=432121
46 2014-01-25 19:53:58 <andytoshi> my bct account has 23 posts, if anybody here is well-known there and would like to vouch for its legitimacy, that'd be great
47 2014-01-25 21:14:34 <jerseykx> hi. would someone like to take a look at my two transactions which i can't get to work? one is paid to P2SH 2-of-2 multisig, another attempts to redeem the first one, but bitcoind rejects it with "VerifySignature failed" in debug.log. i've tried signing it manually using signrawtransaction but then i get "ERROR: Non-canonical signature: too short" and the resulting tx has only zeros in place of signatures... i can provide private
48 2014-01-25 21:18:04 <shesek> jerseykx, have you `addmultisigaddress` to your bitcoind?
49 2014-01-25 21:18:21 <shesek> and is your client aware of the transaction paying to the multisig?
50 2014-01-25 21:19:00 <jerseykx> shesek: no, i haven't tried addmultisigaddress, but my client is aware - it puts the redeemScript into the new scriptSig
51 2014-01-25 21:19:37 <shesek> you need to addmultisigaddress, and make sure the public keys are in the correct order
52 2014-01-25 21:19:56 <jerseykx> ok, let me try this. thanks!
53 2014-01-25 21:24:03 <jerseykx> shesek: hmm. ok, i've added the multisig address i'm trying to redeem, but `signrawtransaction` attempt still gives 'Non-canonical signature: too short', no matter what order i pass the keys in
54 2014-01-25 21:38:12 <jerseykx> anyway, if someone is interested in checking what might be wrong, i've put the data at http://pastebin.com/k6m71nBM - i suspect some of my two signatures are wrong, but i'm not sure how to check them separately. the transaction is from local regtest network, so it's not available anywhere else. i've got to go now, will be back in some 30mins, but will stay logged in here
55 2014-01-25 22:10:17 <netg_> can an bitcoind node be made avaible on TOR and clearnet?
56 2014-01-25 22:10:26 <netg_> like if he listens on both networks
57 2014-01-25 22:10:56 <sipa> yes
58 2014-01-25 22:11:18 <sipa> see doc/tor.md
59 2014-01-25 22:21:21 <netg_> tnx sipa
60 2014-01-25 23:00:28 <sipa> TD[away]: just to prevent you from doing duplicate work, i'm rewriting BIP32 significantly
61 2014-01-25 23:01:40 <sipa> TD[away]: calling the m/3' keys "hardened", explaining all combinations of deriving a key from a parent, and introduce explicit functions for converting between numbers, keys, byte sequences, and going from private to public keys
62 2014-01-25 23:04:58 <midnightmagic> sipa: Thank you