📅 Original date posted:2023-09-01
🗒️ Summary of this message: Tom is updating the code to match the document and estimates that 100 blocks are safe from reorg. He will add it to the document.
📝 Original message:
Hi Jonas,
I’m working to get numbers based on both historical data and from fuzz tests but I’m in the middle of updating the code to match the doc, I should have it finished before the end of the week.
We estimate that 100 blocks is safe from reorg, that is the same policyfor spending coin base transactions, in the PR I add a compressrawtransaction RPC endpoint that has that limit built in and will warn the user that the TxIdis uncompresssed due to it not being old enough. That said I’ll add it into the doc in case anyone adds onto it.
Thanks for the feedback!-
Tom.
On Fri, Sep 1, 2023 at 10:56 AM, Jonas Schnelli <[dev at jonasschnelli.ch](mailto:On Fri, Sep 1, 2023 at 10:56 AM, Jonas Schnelli <<a href=)> wrote:
> Hi Tom
>
>> I've been working on a way to compress bitcoin transactions for transmission through steganography, satellite broadcasting,
>
> Interesting. Some size numbers (vs plain, vs gzip) would be nice.
>
> Maybe add a definition to your BIP that makes clear when NOT to use height/index due to risk of reorgs (similar to BIP136).
>
> /j
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230901/66a683b8/attachment-0001.html>;
Tom Briar [ARCHIVE] /
npub1yg…7ya2e
2023-09-07 11:52:35
in reply to nevent1q…60gm
Author Public Key
npub1ygnsxcgt3n6ltxmk6vh7fj2k9wfnte9085wl09vs3cr480um88asy7ya2eSeen on
wss://relay.nostr.bandPublished at
2023-09-07 11:52:35Event JSON
{
"id": "3f224f11c2e705b489d056cfbc4808112c89ac2f56b1890424d314e83978479e",
"pubkey": "222703610b8cf5f59b76d32fe4c9562b9335e4af3d1df795908e0753bf9b39fb",
"created_at": 1694087555,
"kind": 1,
"tags": [
[
"e",
"78fe78a45d9bfe314bbcb6fae22953a0d8cd7b75e1607bd1dafdcafde1e45cfb",
"",
"root"
],
[
"e",
"27f2982af0a79c97ffcb4b00c7a522f9ade2a5f80ca70bdc7b5f41e6b00555bc",
"",
"reply"
],
[
"p",
"9a463e0fab8963b013698c15a0f2449d19c97f3b88458e5874095b5006df9a0c"
]
],
"content": "📅 Original date posted:2023-09-01\n🗒️ Summary of this message: Tom is updating the code to match the document and estimates that 100 blocks are safe from reorg. He will add it to the document.\n📝 Original message:\nHi Jonas,\n\nI’m working to get numbers based on both historical data and from fuzz tests but I’m in the middle of updating the code to match the doc, I should have it finished before the end of the week.\n\nWe estimate that 100 blocks is safe from reorg, that is the same policyfor spending coin base transactions, in the PR I add a compressrawtransaction RPC endpoint that has that limit built in and will warn the user that the TxIdis uncompresssed due to it not being old enough. That said I’ll add it into the doc in case anyone adds onto it.\n\nThanks for the feedback!-\n\nTom.\n\nOn Fri, Sep 1, 2023 at 10:56 AM, Jonas Schnelli \u003c[dev at jonasschnelli.ch](mailto:On Fri, Sep 1, 2023 at 10:56 AM, Jonas Schnelli \u003c\u003ca href=)\u003e wrote:\n\n\u003e Hi Tom\n\u003e\n\u003e\u003e I've been working on a way to compress bitcoin transactions for transmission through steganography, satellite broadcasting,\n\u003e\n\u003e Interesting. Some size numbers (vs plain, vs gzip) would be nice.\n\u003e\n\u003e Maybe add a definition to your BIP that makes clear when NOT to use height/index due to risk of reorgs (similar to BIP136).\n\u003e\n\u003e /j\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20230901/66a683b8/attachment-0001.html\u003e",
"sig": "715bd35cb1f511f895991d802edf5f15db2e0179bf977ef5b1967894fd7883ae98abef1c9c906c977124fac0f50b0f5158a6cf7312a40f6e4c8cc31241c24ed7"
}