From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 02CD9C0032 for ; Fri, 1 Sep 2023 00:49:40 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id DE9CC41C0A for ; Fri, 1 Sep 2023 00:49:39 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org DE9CC41C0A Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=mail.wpsoftware.net header.i=@mail.wpsoftware.net header.a=rsa-sha256 header.s=default header.b=tOm30Fyn X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.107 X-Spam-Level: X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JdjQKePi6-2 for ; Fri, 1 Sep 2023 00:49:38 +0000 (UTC) Received: from mail.wpsoftware.net (unknown [66.183.0.205]) by smtp4.osuosl.org (Postfix) with ESMTP id 97A7E41BEA for ; Fri, 1 Sep 2023 00:49:38 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 97A7E41BEA Received: from camus (camus-andrew.lan [192.168.0.190]) by mail.wpsoftware.net (Postfix) with ESMTPSA id BB3C0400FC; Fri, 1 Sep 2023 00:49:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail.wpsoftware.net; s=default; t=1693529377; bh=Cxv1noiCSd7NpAzli3hOVGXm2jekbJSSFEtR5EI8t6w=; h=Date:From:To:Subject:References:In-Reply-To; b=tOm30FynLLF0KVPcrt4CcftqmdOqMjnmLeOzQdEI0Gq6e6skQJNI0C2OeH9syDXB4 v1UMnDMEcgux6fs/7qM5AeodAjK30dJOhMEiP8+ekMKQuTBJBrtIKfbwYTcyRtUwWv jqYWddgSqKnxNZemP0k32ubKD6Pbdrfg6UgWHgDjg/WtvV5WhOM4d1PzwHdaXIPDhz 2GvO/H/zZK9hut8MCqnSkAzFPGompILxCIXvx3YGxQckhCTf3qNpY9b4vCMj/yUKIT o4SWDRRNvi/qqbc+L+FFx4Fs+idH2bOZw5i8OJs3682ors3AC4xPZ+erwnQsDaTKuB K5TacWVRchANw== Date: Fri, 1 Sep 2023 00:49:36 +0000 From: Andrew Poelstra To: Tom Briar , Bitcoin Protocol Discussion Message-ID: References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="16KvIL3Ed5eSzw0Z" Content-Disposition: inline In-Reply-To: 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, 01 Sep 2023 00:49:40 -0000 --16KvIL3Ed5eSzw0Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 31, 2023 at 09:30:16PM +0000, Tom Briar via bitcoin-dev wrote: > Hey everyone, >=20 > I've been working on a way to compress bitcoin transactions for transmiss= ion throughsteganography, satellite broadcasting, > and other low bandwidth channels with high CPU availability on decompress= ion. >=20 > [compressed_transactions.md](https://github.com/TomBriar/bitcoin/blob/202= 3-05--tx-compression/doc/compressed_transactions.md) >=20 > In the document I describe a compression schema that's tailored for the m= ost common transactions single parties are likely to make. > In every case it falls back such that no transaction will become malforme= d or corrupted. > Here's a PR for implementing this schema. >=20 > [2023 05 tx compression](https://github.com/TomBriar/bitcoin/pull/3) Hey Tom, Thank you for posting this. Could you put together a chart with some size numbers so we can get a picture of how strong this compression is? I understand that because this is targeted at stego/satellite applications where the user is expected to "shape" their transaction, that you won't get great numbers if you just look at the historical chain or try to analyze "average" transactions. But it would be great to post a chart with uncompressed/compressed sizes for "optimum" transactions. At the very least, a 2-in-2-out wpkh transaction, and a 2-in-2-out Taproot transaction. Since the scheme includes explicit support for p2sh-wpkh and p2pkh it would also be great to see numbers for those, though they're less common and less interesting. Cheers Andrew --=20 Andrew Poelstra Director of Research, Blockstream Email: apoelstra at wpsoftware.net Web: https://www.wpsoftware.net/andrew The sun is always shining in space -Justin Lewis-Webster --16KvIL3Ed5eSzw0Z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEkPnKPD7Je+ki35VexYjWPOQbl8EFAmTxNR8ACgkQxYjWPOQb l8Fh3gf9EvAOACmJbtW9TdnfKliIm6cCVNAKfIzwPNj3qoR0ZkmSQly4xc8J6M53 fLujrsR/3Rka3ZTEbOPzwGm5JQ5l+hjDE389pP2J+leYR/WpTKQwbiFsxjsG6xU9 VMGnaNCAHJupkAwJDAAJ0yEhRZ2PHU/TPITOUHmaO0OerK55wMSGUqAYz2ex0jba LSvHTNqbAZwUnRuLihTnLYG0DfyiDXt3dZ9dJa8RGdH7KBkZMeVDyt1pPpaDflZx 2E453Qz6cPFm6WQ/bgE8XhbPcThVPFILY3Ghv8QO+HbS483M/6u3QVls9fz+rFnB k1PmIGj9G2MY7QuQlxjBq2AUqf9GQA== =ePrk -----END PGP SIGNATURE----- --16KvIL3Ed5eSzw0Z--