📅 Original date posted:2015-10-30
📝 Original message:On Fri, Oct 30, 2015 at 3:04 AM, Simon Liu via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> Given that UTXO storage is considered critical, it seems reasonable to
This sounds like a misunderstanding of what consensus criticial means.
It does not mean that it must be right (though obviously that is
preferable) but that it must be _consistent_, between all nodes.
> full node and keep up with the network, why not let those users with the
> resources to operate big iron databases do so? It would be a good
> feature to have.
Because it provides no value, the data is opaque and propritarily
encoded with a compression function which we may change from version
to version, and because many of these alternatives are enormously
slow; enough that they present problems with falling behind the
network even on high performance hardware.
Moreover, additional functional which will not be sufficiently used
will not adequately maintained and result in increased maintains costs
and more bugs.
Gregory Maxwell [ARCHIVE] /
npub1f2…crwet
2023-06-07 17:43:55
in reply to nevent1q…t9gg
Author Public Key
npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwetPublished at
2023-06-07 17:43:55Event JSON
{
"id": "a390785462c8a3cd16ff8f72744548aeb59a78344c61f8ca890c39d50e6e679b",
"pubkey": "4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73",
"created_at": 1686159835,
"kind": 1,
"tags": [
[
"e",
"09f07bc0e1ba48805727ba44deb034dc283bfadbc39b90714e52ddd0cad07414",
"",
"root"
],
[
"e",
"bc57e2c3e74a5d2fcb29e14533540ce549e530be48f46b2a35c8e3976f8712e2",
"",
"reply"
],
[
"p",
"ec441dce91fdd87933cc9222deff2be2b3ac971939fd1f23aa1f9b61f898f361"
]
],
"content": "📅 Original date posted:2015-10-30\n📝 Original message:On Fri, Oct 30, 2015 at 3:04 AM, Simon Liu via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e Given that UTXO storage is considered critical, it seems reasonable to\n\nThis sounds like a misunderstanding of what consensus criticial means.\nIt does not mean that it must be right (though obviously that is\npreferable) but that it must be _consistent_, between all nodes.\n\n\u003e full node and keep up with the network, why not let those users with the\n\u003e resources to operate big iron databases do so? It would be a good\n\u003e feature to have.\n\nBecause it provides no value, the data is opaque and propritarily\nencoded with a compression function which we may change from version\nto version, and because many of these alternatives are enormously\nslow; enough that they present problems with falling behind the\nnetwork even on high performance hardware.\n\nMoreover, additional functional which will not be sufficiently used\nwill not adequately maintained and result in increased maintains costs\nand more bugs.",
"sig": "d3f3b24b0fe63d91af9e7b2f50e0bd23ee26b18c55fce717d46923b4b6cdd753d362a50b853f39cdc4ef537d13d9fba716bf30400d84a62f0a03f2e52c73919e"
}