Re: [Bitcoin-development] HTTP REST API for bitcoind

2013-07-22 Thread Michael Hendricks
+1 and thank you. I've prototyped a couple different Bitcoin projects that would benefit from this. I'm traveling with poor 'net so I haven't read the patches yet. I echo pull request comments about using Accept and Accept-Encoding headers. Same for an API version number in the URL. It'd be helpf

Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed with optional encryption

2013-07-22 Thread Jean-Paul Kogelman
I added a 2 byte 'weeks since 2013-01-01' field and updated the prefixes, ranges and test vectors.The updated proposal lives here:https://bitcointalk.org/index.php?topic=258678Cheers,jpOn Jul 22, 2013, at 06:14 AM, Mike Hearn wrote:This isn't usable for SPV wallets unless it has a birthday in it.

[Bitcoin-development] HTTP REST API for bitcoind

2013-07-22 Thread Jeff Garzik
URL: https://github.com/bitcoin/bitcoin/pull/2844 Adding an HTTP REST API for bitcoind has been occasionally tossed about as a useful thing. Such an API would essentially provide a decentralized block explorer capability, enabling easy external access to transaction/address/block indices that we

[Bitcoin-development] [RFC] Standard for private keys with birth timestamp

2013-07-22 Thread Pieter Wuille
Hello, I should have brought up this suggestion before, as there seems to be relevant other work. I'd like to propose encoding keys data (whatever type) with a birth timestamp as: * @ The reason for not incorporating this inside the key serialization (for example BIP32), is because birth tim

Re: [Bitcoin-development] [RFC] Standard for private keys with birth timestamp

2013-07-22 Thread Melvin Carvalho
On 22 July 2013 16:44, Pieter Wuille wrote: > Hello, > > I should have brought up this suggestion before, as there seems to be > relevant other work. > > I'd like to propose encoding keys data (whatever type) with a birth > timestamp as: > * @ > > The reason for not incorporating this inside the

Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed with optional encryption

2013-07-22 Thread Jean-Paul Kogelman
Hi Mike, I had a similar request on the forums. I suggested adding either a 2 byte 'weeks since genesis' or 'months since genesis', but starting from spec birth works too. Would either of those work for you? jp On Jul 22, 2013, at 6:14 AM, Mike Hearn wrote: > This isn't usable for SPV walle

Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet master seed with optional encryption

2013-07-22 Thread Mike Hearn
This isn't usable for SPV wallets unless it has a birthday in it. Otherwise you either need to scan the entire chain (slow) or find a fully indexed copy of the block chain (expensive, more centralised). Just add a UNIX time as an extra 4 bytes, or if you want to save a few characters then use a uin

Re: [Bitcoin-development] Introducing BitcoinKit.framework

2013-07-22 Thread Mike Hearn
As an FYI, I've sent Wendell and co some example code for how to use CPPJVM to use bitcoinj from native code. A rather rough Hello World app looks like this: https://github.com/mikehearn/cppjvm/blob/master/mytest/bcj-hello-world.cpp So, fairly C++ like. Further discussion of this should take pla