From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id E6DC28FE for ; Tue, 1 Dec 2015 20:06:56 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from janik.cz (h.janik.cz [79.98.78.37]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1A4AD145 for ; Tue, 1 Dec 2015 20:06:55 +0000 (UTC) Received: from [10.0.0.100] (unknown [10.0.0.100]) by janik.cz (Server) with ESMTP id 73B8734E2F5; Tue, 1 Dec 2015 21:07:32 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) From: =?utf-8?Q?Pavel_Jan=C3=ADk?= In-Reply-To: <90EF4E6C-9A71-4A35-A938-EAFC1A24DD24@mattcorallo.com> Date: Tue, 1 Dec 2015 21:06:53 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <04188281-6A0C-4178-B2CA-BDE799C4FE9F@Janik.cz> References: <565CD7D8.3070102@gmail.com> <90EF4E6C-9A71-4A35-A938-EAFC1A24DD24@mattcorallo.com> To: Bitcoin Dev X-Mailer: Apple Mail (2.2104) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Tue, 01 Dec 2015 22:40:22 +0000 Subject: Re: [bitcoin-dev] [BIP Draft] Datastream compression of Blocks and Transactions X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Dec 2015 20:06:57 -0000 > On 01 Dec 2015, at 06:28, Matt Corallo via bitcoin-dev = wrote: >=20 > 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. -- =20 Pavel Jan=C3=ADk