From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4C415C0037 for ; Fri, 19 Jan 2024 21:10:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2139C83A80 for ; Fri, 19 Jan 2024 21:10:13 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2139C83A80 Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com header.a=rsa-sha256 header.s=protonmail3 header.b=X0dMW8Nd X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.549 X-Spam-Level: X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KP6HO-VPY9VB for ; Fri, 19 Jan 2024 21:10:12 +0000 (UTC) Received: from mail-0301.mail-europe.com (mail-0301.mail-europe.com [188.165.51.139]) by smtp1.osuosl.org (Postfix) with ESMTPS id EBA8583E3A for ; Fri, 19 Jan 2024 21:10:11 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org EBA8583E3A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1705698604; x=1705957804; bh=QYxuHf9/FCGm2vDdzCj6STZsUkwEEuUOotQ8neMbfrw=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=X0dMW8NddP8EfEADRabHQamm45lb6xTDU92wTXE3ILLAOJIGf3fzGkJ0uZvVUjw98 rzB9ueYcg06+Q939eRYWSHLafxfR09U9wM0vYWVza8abBZyKKAtr54umPfpNa5ka1m 9Yb62tEoEAK2Bv+VRRF6VeSB4AmeqycBahJJsRuHB6c7wISMsZUGuVaXCf5JVwmKVe cfO7q7b51KfHjZPV6YP3KSiqhPlN++Turif5VHbQIJ+jm1vcUgixhmWIMF2sGSoW8+ GR5ePl5yEEnNpwqSyzvQGxb5IEan1CFdXEAogMxId62w95qq4iJbMf6hrIaqq21bcD F0IxsBYkg61EA== Date: Fri, 19 Jan 2024 21:09:35 +0000 To: Jonas Schnelli From: Tom Briar Message-ID: In-Reply-To: References: Feedback-ID: 43655394:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 23 Jan 2024 13:46:37 +0000 Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Compressed Bitcoin Transactions X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2024 21:10:13 -0000 Hi Jonas, As it turns out, most of our size savings come from eliminating unneeded ha= shes and public keys, which get recovered on decompression. gzip actually e= xpands transactions due to the way it attempts to compress pseudorandom dat= a, my numbers show a legacy transaction of 222 bytes being expanded to 267 = bytes. gzip can possibly shrink the 4-byte integers which have only a couple typic= al values, and can eliminate some of the "boilerplate" in the tx format, bu= t that's pretty much it at the expense of expanding the signatures, public = keys, and hashes. And your absolutely right this would have to be done at the application lay= er in a V2-P2P encrypted traffic system. Thanks- Tom.