Blockchain size - 8.09 GB
Question. How can it be, that everyone has another size for the block chain. I read here sometimes about 11Gig, now you have 8,09. I have 9,79? From which factors the size it dependend?
Topic: Once again, what about the scalability issue? - page 9. (Read 11259 times)
Question. How can it be, that everyone has another size for the block chain. I read here sometimes about 11Gig, now you have 8,09. I have 9,79? From which factors the size it dependend?
Blockchain size - 8.09 GB
What about Simplfied Payment Verification implementation?
A reasonable question.
The wiki says " In Satoshi's paper he describes "pruning", a way to delete unnecessary data about transactions that are fully spent... As of October 2012 (block 203258) there have been 7,979,231 transactions, however the size of the unspent output set is less than 100MiB, which is small enough to easily fit in RAM for even quite old computers."
I would like to read the Satoshi pruning description, and here it is:
7. Reclaiming Disk Space
Once the latest transaction in a coin is buried under enough blocks, the spent transactions before
it can be discarded to save disk space. To facilitate this without breaking the block's hash,
transactions are hashed in a Merkle Tree, with only the root included in the block's hash.
Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do
not need to be stored.
A block header with no transactions would be about 80 bytes. If we suppose blocks are
generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems
typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of
1.2GB per year, storage should not be a problem even if the block headers must be kept in
memory.
The wiki says " In Satoshi's paper he describes "pruning", a way to delete unnecessary data about transactions that are fully spent... As of October 2012 (block 203258) there have been 7,979,231 transactions, however the size of the unspent output set is less than 100MiB, which is small enough to easily fit in RAM for even quite old computers."
I would like to read the Satoshi pruning description, and here it is:
7. Reclaiming Disk Space
Once the latest transaction in a coin is buried under enough blocks, the spent transactions before
it can be discarded to save disk space. To facilitate this without breaking the block's hash,
transactions are hashed in a Merkle Tree, with only the root included in the block's hash.
Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do
not need to be stored.
A block header with no transactions would be about 80 bytes. If we suppose blocks are
generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems
typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of
1.2GB per year, storage should not be a problem even if the block headers must be kept in
memory.
It seems to me Bitcoin core devs prefer ostrich policy. The blockchain keeps growing, pruning is not implemented yet (is it possible btw?), Gavin spoke about everything except the scalability issue on Bitcoin 2013 conference...
Is there any progress? Or is the game over?
Is there any progress? Or is the game over?
Jump to: