📅 Original date posted:2015-12-01
📝 Original message:> On 01 Dec 2015, at 06:28, Matt Corallo via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> I'm really not a fan of this at all. To start with, adding a compression library that is directly accessible to the network on financial software is a really, really scary idea.
I have the same opinion.
On the other hand, I can imagine using compression on local blocks storage (be it compressed filesystem, or compression in the user space/in the application - compare with https://github.com/bitcoin/bitcoin/issues/2278). Now that we support pruning and obfuscating, this could be another option. Saving ~20% can be interesting in some usecases.
--
Pavel Janík
Pavel Janík [ARCHIVE] /
npub16t…jv5ke
2023-06-07 17:45:23
in reply to nevent1q…e3sv
Author Public Key
npub16t7f9mxe6a2slagy5m9vxssf54772e2crdczpyk4c97nvletewhq0jv5kePublished at
2023-06-07 17:45:23Event JSON
{
"id": "fc8c0bd0f8800e03a3fc86dc1c4b48b2559989fef1ca7429fa4f7ad23a05e91a",
"pubkey": "d2fc92ecd9d7550ff504a6cac34209a57de565581b702092d5c17d367f2bcbae",
"created_at": 1686159923,
"kind": 1,
"tags": [
[
"e",
"66e2fed0b01e52e71a1dd6b42fe6a9fda1f0a599c3d79a1ed608f15fbb8c1ad3",
"",
"root"
],
[
"e",
"c617a95ecd9a1074009dcc664dd4d20c11dad5fb3f5f37b7cefbf0d380ad8bfa",
"",
"reply"
],
[
"p",
"cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba"
]
],
"content": "📅 Original date posted:2015-12-01\n📝 Original message:\u003e On 01 Dec 2015, at 06:28, Matt Corallo via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e I'm really not a fan of this at all. To start with, adding a compression library that is directly accessible to the network on financial software is a really, really scary idea.\n\nI have the same opinion.\n\nOn the other hand, I can imagine using compression on local blocks storage (be it compressed filesystem, or compression in the user space/in the application - compare with https://github.com/bitcoin/bitcoin/issues/2278). Now that we support pruning and obfuscating, this could be another option. Saving ~20% can be interesting in some usecases.\n-- \nPavel Janík",
"sig": "70a0c8617a875def02f6a0d0e5ff49a4aa4a11dcd2e13fa701efbabc6a10eedda75571569bef4010054ab9758e53ad31494fa23f08ab6e7f8ff6857c7637b33a"
}