bitcoin protocol needs an archival system so the blockchain doesn't become
too big to download
--
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous M
This is the sort of thing the payment protocol is for. The recipient would
vend a PaymentRequest containing identity details. The sender would submit
a Payment containing his/hers. The wallet then understands what to do.
On Fri, Sep 6, 2013 at 5:07 PM, Wendell wrote:
> Hi all,
>
> We're thinkin
> bitcoin protocol needs an archival system so the blockchain doesn't
> become too big to download
Some people may want it all ...
Balance at Point-In-Time summaries (say up to the penultimate
difficulty adjustment) would be one simple way.
And make new-adopters get up and running in minutes not
On Saturday, September 07, 2013 11:21:31 PM rob.gold...@astutium.com wrote:
> > bitcoin protocol needs an archival system so the blockchain doesn't
> > become too big to download
>
> Some people may want it all ...
>
> Balance at Point-In-Time summaries (say up to the penultimate
> difficulty adj
> (there's no way to be completely trust-free without this).
Not quite true, as I said balance-at-point-in-time would solve that
(and make the storage requirements much lower)
>> If going that route, then solutions to the 'consolidate
>> addresses/wallets'
>> question and formal 'discard' of ad
This is all FAQ territory, and has been covered on the forums for years.
Balance-at-point-in-time is not completely trust-free, as it is a
dataset that must be bootstrapped into trust by... an earlier dataset.
Continue this logic and you have a... chain.
There is plenty of on-going discussion on
6 matches
Mail list logo
