From: Tom Briar <tombriar11@protonmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Compressed Bitcoin Transactions
Date: Tue, 16 Jan 2024 17:08:54 +0000 [thread overview]
Message-ID: <jdBdzLD0bcOPikKGQd1VpWU6dIc3_X6I_Q1UFuEiYfiY_Z6xF86nlDqnU00PGsQS3XdBFwjlmYWN-7_aXbjVjkXmGEVf0cGKPHjzhYkVweY=@protonmail.com> (raw)
In-Reply-To: <IFgPQiCptuVM6I5AsCE6VFrPMsGzBMK3x78GHlupJj12-rBloASYdafdBzyjSKC0H0EWLG2NNBzu1wEyYyyl1VzMmjW3nO7M-9OJpMxoEMM=@protonmail.com>
Hi,
In addition to the use cases listed in the schema, such as steganography, satellite, and radio broadcast, an application can be made for Peer-to-peer communication between Bitcoin nodes. Except when compressing the Txid/Vout, which is optional, Transactions can gain up to 30% size savings while still being completely reversible. Furthermore, in a BIP-324 world, these savings are nontrivial.
BIP-324: https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki
Compressed Transaction Schema: compressed_transactions.md
Thanks-
Tom.
next prev parent reply other threads:[~2024-01-16 17:09 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 [this message]
2024-01-18 9:24 ` Jonas Schnelli
2024-01-19 21:09 ` Tom Briar
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='jdBdzLD0bcOPikKGQd1VpWU6dIc3_X6I_Q1UFuEiYfiY_Z6xF86nlDqnU00PGsQS3XdBFwjlmYWN-7_aXbjVjkXmGEVf0cGKPHjzhYkVweY=@protonmail.com' \
--to=tombriar11@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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