📅 Original date posted:2020-12-05 📝 Original message:On Friday, November 6, ...

Pieter Wuille [ARCHIVE] /

npub1tje…tl6r

2023-06-07 18:27:41

in reply to nevent1q…yd3c

📅 Original date posted:2020-12-05
📝 Original message:On Friday, November 6, 2020 11:49 AM, Mike Schmidt via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:

> Well I sure picked a bad couple weeks to volunteer to send a bunch of Bitcoin test transactions...
>
> While I tested less than I would have liked, there are some notable results:

I think these results really show there is no reason to try to maintain the old-software-can-send-to-future-segwit-versions property, given that more than one not just didn't support it, but actually sent coins into a black hole.

Thus, I agree with Rusty that we should change the checksum for v1+ unconditionally. That also means that old senders are protected from the insertion issue (by failing, as we can guarantee that new-checksum addresses, even after a few errors, are invalid to old software).

I've sent another mail in this thread with details, but the TL;DR is that we should use the constant M=0x2bc830a3 rather than 0x3fffffff as previous suggested. More information on https://gist.github.com/sipa/14c248c288c3880a3b191f978a34508e.

Absent objections, I'll write up a BIP soon.

Cheers,

--
Pieter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20201205/32d286a4/attachment.html>;

Author Public Key

npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 18:27:41

Kind type

1 Short Text Note

Event JSON

{ "id": "3b5b0eeaf11d6bb6e61c8b9ad7f6a5ce6bfa78d56e4d6cf3724a8a9db2932995", "pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6", "created_at": 1686162461, "kind": 1, "tags": [ [ "e", "a33b31314cc146fbf560014adb2469570c5de8ee11aa7f1e7f70e8cf3a07a02d", "", "root" ], [ "e", "e668de79b261c35924bb40a7e1ccf68a93be2204ca6890190cebbc93ae09500c", "", "reply" ], [ "p", "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6" ] ], "content": "📅 Original date posted:2020-12-05\n📝 Original message:On Friday, November 6, 2020 11:49 AM, Mike Schmidt via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Well I sure picked a bad couple weeks to volunteer to send a bunch of Bitcoin test transactions...\n\u003e\n\u003e While I tested less than I would have liked, there are some notable results:\n\nI think these results really show there is no reason to try to maintain the old-software-can-send-to-future-segwit-versions property, given that more than one not just didn't support it, but actually sent coins into a black hole.\n\nThus, I agree with Rusty that we should change the checksum for v1+ unconditionally. That also means that old senders are protected from the insertion issue (by failing, as we can guarantee that new-checksum addresses, even after a few errors, are invalid to old software).\n\nI've sent another mail in this thread with details, but the TL;DR is that we should use the constant M=0x2bc830a3 rather than 0x3fffffff as previous suggested. More information on https://gist.github.com/sipa/14c248c288c3880a3b191f978a34508e.\n\nAbsent objections, I'll write up a BIP soon.\n\nCheers,\n\n--\nPieter\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20201205/32d286a4/attachment.html\u003e", "sig": "487ebbefcccf20ed871f9b977c4bce37c813fc5451c98f9cd33fffa1a2d42066b03e4c22da9246140b554bacae298bbc8d5488ea2819c931905e484ac393b45f" }