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 84355904 for ; Thu, 3 Dec 2015 19:14:58 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7DBCC125 for ; Thu, 3 Dec 2015 19:14:57 +0000 (UTC) Received: by lbbkw15 with SMTP id kw15so7664770lbb.0 for ; Thu, 03 Dec 2015 11:14:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qsOMn9PT9CD6iIc2Fw9B8bisySx1h74j7gC9slrk7gM=; b=cTDK+7JIIE2g3ebdGIxbd52sKGnkIDH1oB70Qmo+vbNnl8RTNaddfmDZgORETYwmJP Ho5Fslvp1ipPa5in6yZewVY0oaS1Tlvn1itnobxHrBDfg0iLor3ri23biAzcAI0n1Gii +ac2xMa0TBtQ7OJVwxr+pT8W8755WjYdpsy1A86EN/YZVoZZqmVkDGsSayhziNGshXTZ D6fY700Oeew7q7Gf7sBwXNamT18dFqLEZKdmO3Sb7cuhrygEj29EgjoVHaulHYXK4RFI P2WiAFbuVLHub3aFunsxGUq2M7sBdL3QknSa07z/82DmDbSBUvFlq0Zw3UfISFoX2hBg xwCA== MIME-Version: 1.0 X-Received: by 10.112.180.35 with SMTP id dl3mr6365464lbc.27.1449170095688; Thu, 03 Dec 2015 11:14:55 -0800 (PST) Received: by 10.25.22.95 with HTTP; Thu, 3 Dec 2015 11:14:55 -0800 (PST) In-Reply-To: References: <565CD7D8.3070102@gmail.com> <90EF4E6C-9A71-4A35-A938-EAFC1A24DD24@mattcorallo.com> Date: Thu, 3 Dec 2015 14:14:55 -0500 Message-ID: From: Gavin Andresen To: =?UTF-8?Q?Emin_G=C3=BCn_Sirer?= Content-Type: multipart/alternative; boundary=089e01182b3ac5d4b505260334bb X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev 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: Thu, 03 Dec 2015 19:14:58 -0000 --089e01182b3ac5d4b505260334bb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Dec 2, 2015 at 1:57 PM, Emin G=C3=BCn Sirer < bitcoin-dev@lists.linuxfoundation.org> wrote: > How to Do It > > If we want to compress Bitcoin, a programming challenge/contest would be > one of the best ways to find the best possible, Bitcoin-specific > compressor. This is the kind of self-contained exercise that bright young > hackers love to tackle. It'd bring in new programmers into the ecosystem, > and many of us would love to discover the limits of compressibility for > Bitcoin bits on a wire. And the results would be interesting even if the > final compression engine is not enabled by default, or not even merged. > I love this idea. Lets build a standardized data set to test against using real data from the network (has anybody done this yet?). Something like: Starting network topology: list of: nodeid, nodeid, network latency between the two peers Changes to network topology: list of: nodeid, add/remove nodeid, time of change Transaction broadcasts: list of : transaction, node id that first broadcast, time first broadcast Block broadcasts: list of : block, node id that first broadcast, time first broadcast Proposed transaction/block optimizations could then be measured against this standard data set. --=20 -- Gavin Andresen --089e01182b3ac5d4b505260334bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On W= ed, Dec 2, 2015 at 1:57 PM, Emin G=C3=BCn Sirer <bitco= in-dev@lists.linuxfoundation.org> wrote:
=
How to Do It

If we want to compress Bitcoin, a=C2=A0programming challenge/contest would be one of the best ways to fi= nd the best possible, Bitcoin-specific compressor. This is the kind of self= -contained exercise that bright you= ng hackers love to tackle. It'd bring in new programmers into the ecosy= stem, and many of us would love to discover the limits of compressibility f= or Bitcoin bits on a wire. And the results would be interesting even if the= final compression engine is not enabled by default, or not even merged.

I love this idea. Lets build a = standardized data set to test against using real data from the network (has= anybody done this yet?).

Something like:

Starting network topology:
list of: =C2=A0nodeid, nodeid, network latency between the tw= o peers

Changes to network topology:
list of: =C2= =A0nodeid, add/remove nodeid, time of change

Transaction broadcasts:
list of : =C2=A0transaction, node id that first broadca= st, time first broadcast

Block broadcasts:
list o= f : =C2=A0block, node id that first broadcast, time first broadcast

Proposed tran= saction/block optimizations could then be measured against this standard da= ta set.


--
--
Gavin Andresen
--089e01182b3ac5d4b505260334bb--