Show Posts
A blockchain store for embedded devices would be a plus, I'm having space problems on a 50GB VPS.
For static data compression is usually a good thing, actually a compressed representation for block and transaction data should be a milestone for the P2P network. Compress once, read many is "always" a win for space/time/energy/ect. If I'm not mistaken the LevelDB supports compression, it may already be compressed and in that case further compression makes the storage requirements larger.
For static data compression is usually a good thing, actually a compressed representation for block and transaction data should be a milestone for the P2P network. Compress once, read many is "always" a win for space/time/energy/ect. If I'm not mistaken the LevelDB supports compression, it may already be compressed and in that case further compression makes the storage requirements larger.
Do you have any good idea for small memory embedded devices optimisation.
Bitcoind used at least 256MB mermory, but many devices only have 128MB physical memory. Swap space is need but slowdown the whole system.
