Date: Fri, 1 Sep 2023 00:49:36 +0000
From: Andrew Poelstra <apoelstra@wpsoftware.net>
To: Tom Briar <tombriar11@protonmail.com>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZPE1IDggzquwP+WN@camus>
References: <WJoM7dyrk0o8ujOZOo462r66wS2Kl3L1ZZRodvaLK-HKEUc90yvwOqXbUUrGbV1lk6cOywTqLoCyHzk2Tm3TtBFyUL0NZ6D7v9NmTXypJPA=@protonmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature"; boundary="16KvIL3Ed5eSzw0Z"
Content-Disposition: inline
In-Reply-To: <WJoM7dyrk0o8ujOZOo462r66wS2Kl3L1ZZRodvaLK-HKEUc90yvwOqXbUUrGbV1lk6cOywTqLoCyHzk2Tm3TtBFyUL0NZ6D7v9NmTXypJPA=@protonmail.com>
Subject: Re: [bitcoin-dev] Compressed Bitcoin Transactions
Precedence: list


--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--