📅 Original date posted:2014-04-10 📝 Original message:anyway, any kind of ...

Ricardo Filipe [ARCHIVE] /

npub14fw…ksaj

2023-06-07 15:18:33

in reply to nevent1q…p7rc

📅 Original date posted:2014-04-10
📝 Original message:anyway, any kind of compression that comes to the blockchain is
orthogonal to pruning.

I agree that you will probably want some kind of replication on more
recent nodes than on older ones. However, nodes with older blocks
don't need to be "static", get the block distribution algorithm to
sort it out.

2014-04-10 17:28 GMT+01:00 Mike Hearn <mike at plan99.net>:
> Suggestions always welcome!
>
> The main problem with this is that the block chain is mostly random bytes
> (hashes, keys) so it doesn't compress that well. It compresses a bit, but
> not enough to change the fundamental physics.
>
> However, that does not mean the entire chain has to be stored on expensive
> rotating platters. I've suggested that in some star trek future where the
> chain really is gigantic, it could be stored on tape and spooled off at high
> speed. Literally a direct DMA from tape drive to NIC. But we're not there
> yet :)
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

Author Public Key

npub14fwd2yh320mh4ge46ute8ukdyx2kjxy2ak4a05prjwrtzlmh9rvq8hksaj

Show more details

Published at

2023-06-07 15:18:33

Kind type

1 Short Text Note

Event JSON

{ "id": "037675b07742f72d51a4eb1687042426e539469ea1e7091b7ec591d80a282e5d", "pubkey": "aa5cd512f153f77aa335d71793f2cd219569188aedabd7d0239386b17f7728d8", "created_at": 1686151113, "kind": 1, "tags": [ [ "e", "aae8a2dedee78eef571f285fef23331d89c84b104c87b098618414541001d13e", "", "root" ], [ "e", "ddfe70eaae7915b553f7762ad14cc92b9830aa2150ac08dbe3eccda91706f439", "", "reply" ], [ "p", "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73" ] ], "content": "📅 Original date posted:2014-04-10\n📝 Original message:anyway, any kind of compression that comes to the blockchain is\northogonal to pruning.\n\nI agree that you will probably want some kind of replication on more\nrecent nodes than on older ones. However, nodes with older blocks\ndon't need to be \"static\", get the block distribution algorithm to\nsort it out.\n\n2014-04-10 17:28 GMT+01:00 Mike Hearn \u003cmike at plan99.net\u003e:\n\u003e Suggestions always welcome!\n\u003e\n\u003e The main problem with this is that the block chain is mostly random bytes\n\u003e (hashes, keys) so it doesn't compress that well. It compresses a bit, but\n\u003e not enough to change the fundamental physics.\n\u003e\n\u003e However, that does not mean the entire chain has to be stored on expensive\n\u003e rotating platters. I've suggested that in some star trek future where the\n\u003e chain really is gigantic, it could be stored on tape and spooled off at high\n\u003e speed. Literally a direct DMA from tape drive to NIC. But we're not there\n\u003e yet :)\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Put Bad Developers to Shame\n\u003e Dominate Development with Jenkins Continuous Integration\n\u003e Continuously Automate Build, Test \u0026 Deployment\n\u003e Start a new project now. Try Jenkins in the cloud.\n\u003e http://p.sf.net/sfu/13600_Cloudbees\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e", "sig": "dc7b957e2a5cc4409b78fa25a93017b3ea51ccf31a9be5e8c91934ee0b339f5c68464dd0e988bf0c5035ca16c633ae708203e65ecf9411e87851796f8770b60f" }