📅 Original date posted:2023-09-01
🗒️ Summary of this message: Tom thanks Fabian for his effort in the research and implementation. Fabian suggests using an index from a sorted UTXO set for potential space saving and compatibility with pruning.
📝 Original message:
Hi Tom,
without having gone into the details yet, thanks for the great effort you have put into this research and implementation already!
> The bulk of our size savings come from replacing the prevout of each input by a block height and index.
Have you also considered using just an index from a sorted UTXO set instead? The potential additional space saving might be minor but this would make the scheme compatible with pruning. I had this on my list as a future research topic but didn't get around to it yet.
Thanks,
Fabian
------- Original Message -------
On Thursday, August 31st, 2023 at 11:30 PM, Tom Briar via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> Hey everyone,
>
> I've been working on a way to compress bitcoin transactions for transmission throughsteganography, satellite broadcasting,
> and other low bandwidth channels with high CPU availability on decompression.
>
> [compressed_transactions.md](https://github.com/TomBriar/bitcoin/blob/2023-05--tx-compression/doc/compressed_transactions.md)
>
> In the document I describe a compression schema that's tailored for the most common transactions single parties are likely to make.
> In every case it falls back such that no transaction will become malformed or corrupted.
> Here's a PR for implementing this schema.
>
> [2023 05 tx compression](https://github.com/TomBriar/bitcoin/pull/3)
> Thanks-
> Tom.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230901/5c5c8657/attachment-0001.html>;
Fabian [ARCHIVE] /
npub1wc…ehvcp
2023-09-07 13:52:34
in reply to nevent1q…6hyg
Author Public Key
npub1wcar64n6956qjf28fxpepytx89up2ty4gex0zqzntpxnt7djydvsyehvcpPublished at
2023-09-07 13:52:34Event JSON
{
"id": "c2417943cafb8c8ee976472d466ed87dd61dc6172bfd8970be72f0ccaa22e4ee",
"pubkey": "763a3d567a2d3409254749839091663978152c95464cf10053584d35f9b22359",
"created_at": 1694087554,
"kind": 1,
"tags": [
[
"e",
"78fe78a45d9bfe314bbcb6fae22953a0d8cd7b75e1607bd1dafdcafde1e45cfb",
"",
"root"
],
[
"e",
"f6fdf14db2a437052ce0eb12c1f196a688edefc9025b3dd84753ac35c1361556",
"",
"reply"
],
[
"p",
"ee55eb03423bd4db01d5c92ad434d52c602d9da1de37ed37cc5bf7d2a13a4cab"
]
],
"content": "📅 Original date posted:2023-09-01\n🗒️ Summary of this message: Tom thanks Fabian for his effort in the research and implementation. Fabian suggests using an index from a sorted UTXO set for potential space saving and compatibility with pruning.\n📝 Original message:\nHi Tom,\n\nwithout having gone into the details yet, thanks for the great effort you have put into this research and implementation already!\n\n\u003e The bulk of our size savings come from replacing the prevout of each input by a block height and index.\n\nHave you also considered using just an index from a sorted UTXO set instead? The potential additional space saving might be minor but this would make the scheme compatible with pruning. I had this on my list as a future research topic but didn't get around to it yet.\n\nThanks,\nFabian\n------- Original Message -------\nOn Thursday, August 31st, 2023 at 11:30 PM, Tom Briar via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hey everyone,\n\u003e\n\u003e I've been working on a way to compress bitcoin transactions for transmission throughsteganography, satellite broadcasting,\n\u003e and other low bandwidth channels with high CPU availability on decompression.\n\u003e\n\u003e [compressed_transactions.md](https://github.com/TomBriar/bitcoin/blob/2023-05--tx-compression/doc/compressed_transactions.md)\n\u003e\n\u003e In the document I describe a compression schema that's tailored for the most common transactions single parties are likely to make.\n\u003e In every case it falls back such that no transaction will become malformed or corrupted.\n\u003e Here's a PR for implementing this schema.\n\u003e\n\u003e [2023 05 tx compression](https://github.com/TomBriar/bitcoin/pull/3)\n\u003e Thanks-\n\u003e Tom.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230901/5c5c8657/attachment-0001.html\u003e",
"sig": "b73f171564c9127321cb37c80e3cfeaa4629f9c850f38c2fc3c898eb5c3d74038f1e7a3447f53f0797697bb41b534e508b6bf0fb37d81970e223892d3ca39f56"
}