Re: [Bitcoin-development] Fwd: Service bits for pruned nodes

2013-05-01 Thread Andy Parkins
On Wednesday 01 May 2013 15:26:57 Jeff Garzik wrote: > A generalized HTTP REST query protocol would be a nice addition... it > is just off-topic for this thread. On IRC yesterday, we discussed an > HTTP query interface like you suggested. It was agreed that it was a > nice interface, and might b

Re: [Bitcoin-development] Fwd: Service bits for pruned nodes

2013-05-01 Thread Jeff Garzik
On Wed, May 1, 2013 at 10:05 AM, Andy Parkins wrote: > On Tuesday 30 April 2013 21:11:47 Jeff Garzik wrote: > >> Hardly. The storage format is bitcoin protocol wire format, plus a >> tiny header. It is supported in multiple applications already, and is >> the most efficient storage format for bi

Re: [Bitcoin-development] Fwd: Service bits for pruned nodes

2013-05-01 Thread Andy Parkins
On Tuesday 30 April 2013 21:11:47 Jeff Garzik wrote: > Hardly. The storage format is bitcoin protocol wire format, plus a > tiny header. It is supported in multiple applications already, and is > the most efficient storage format for bitcoin protocol blocks. "Most efficient" for what purpose?

Re: [Bitcoin-development] Service bits for pruned nodes

2013-05-01 Thread Jeff Garzik
On Sun, Apr 28, 2013 at 11:51 AM, Pieter Wuille wrote: > Hello all, > > I think it is time to move forward with pruning nodes, i.e. nodes that fully > validate and relay blocks and transactions, but which do not keep (all) > historic blocks around, and thus cannot be queried for these. > > The big