> If we wanted to go the route of shipping pruned chains I'd prefer to > have a deterministic process to produce archival chains
Yeah, that sounds reasonable. I mean, I can't see why pruning would not be deterministic. So if you download a binary that contains a pre-indexed and pruned chain up to block 180,000 or whatever, you should be able to blow away the data files and run with "-syncto=180000 -prune", then check the hashes of the newly created files vs what you downloaded. Unless BDB has some weird behaviour in it, that shouldn't require any additional effort, and anyone could set up a cron job to verify the downloads match what is expected. Even if a more complex scheme is used whereby commitments are in the block chain, somebody still has to verify the binaries match the source. If that isn't true, the software could do anything and you'd never know. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
