From: Tom Briar <tombriar11@protonmail•com>
To: Jonas Schnelli <dev@jonasschnelli•ch>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Compressed Bitcoin Transactions
Date: Fri, 19 Jan 2024 21:09:35 +0000 [thread overview]
Message-ID: <xmXvUSue_zG2b5fAInP4nlZ6YSCuPDhDBX_s9WwS7prB7KeIEw_gEj6f9_2ysP2oUBdXcXxNE9SCmt0WOrx-EOEHl1s7G9_Xc8WzLXZVWw0=@protonmail.com> (raw)
In-Reply-To: <A1A794D6-E465-4F45-BF67-EB24B2CB9773@jonasschnelli.ch>
Hi Jonas,
As it turns out, most of our size savings come from eliminating unneeded hashes and public keys, which get recovered on decompression. gzip actually expands transactions due to the way it attempts to compress pseudorandom data, 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 typical values, and can eliminate some of the "boilerplate" in the tx format, but 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 layer in a V2-P2P encrypted traffic system.
Thanks-
Tom.
next prev parent reply other threads:[~2024-01-19 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 21:30 Tom Briar
2023-09-01 0:49 ` Andrew Poelstra
2023-09-01 10:24 ` Fabian
2023-09-01 10:43 ` Fabian
2023-09-01 13:56 ` Andrew Poelstra
2023-09-01 14:12 ` Tom Briar
2023-09-05 18:00 ` Peter Todd
2023-09-05 18:30 ` Tom Briar
2024-01-05 15:06 ` Tom Briar
2024-01-05 15:19 ` Andrew Poelstra
2024-01-09 15:31 ` Tom Briar
2024-01-16 17:08 ` Tom Briar
2024-01-18 9:24 ` Jonas Schnelli
2024-01-19 21:09 ` Tom Briar [this message]
2023-09-01 16:56 ` Jonas Schnelli
2023-09-01 17:05 ` Tom Briar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='xmXvUSue_zG2b5fAInP4nlZ6YSCuPDhDBX_s9WwS7prB7KeIEw_gEj6f9_2ysP2oUBdXcXxNE9SCmt0WOrx-EOEHl1s7G9_Xc8WzLXZVWw0=@protonmail.com' \
--to=tombriar11@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dev@jonasschnelli$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox