From: "Pavel Janík" <Pavel@Janik.cz>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [BIP Draft] Datastream compression of Blocks and Transactions
Date: Tue, 1 Dec 2015 21:06:53 +0100 [thread overview]
Message-ID: <04188281-6A0C-4178-B2CA-BDE799C4FE9F@Janik.cz> (raw)
In-Reply-To: <90EF4E6C-9A71-4A35-A938-EAFC1A24DD24@mattcorallo.com>
> On 01 Dec 2015, at 06:28, Matt Corallo via bitcoin-dev <bitcoin-dev@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
next prev parent reply other threads:[~2015-12-01 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 23:12 [bitcoin-dev] [BIP Draft] Datastream compression of Blocks and Transactions Peter Tschipper
2015-12-01 5:28 ` Matt Corallo
2015-12-01 20:06 ` Pavel Janík [this message]
[not found] ` <565E30C6.1010002@bitcartel.com>
2015-12-02 6:47 ` Pavel Janík
2015-12-02 7:33 ` Simon Liu
2015-12-02 18:45 ` Patrick Strateman
2015-12-02 18:57 ` Emin Gün Sirer
2015-12-02 20:16 ` Peter Tschipper
2015-12-02 22:23 ` Matt Corallo
2015-12-02 23:02 ` Peter Tschipper
2015-12-04 13:30 ` Matt Corallo
2015-12-03 19:14 ` Gavin Andresen
2015-12-03 23:07 ` Rusty Russell
2015-12-02 23:05 ` Peter Tschipper
2015-12-03 5:52 ` Dave Scotese
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=04188281-6A0C-4178-B2CA-BDE799C4FE9F@Janik.cz \
--to=pavel@janik.cz \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox