📅 Original date posted:2016-10-16 📝 Original message:---- On Mon, 17 Oct 2016 ...

Johnson Lau [ARCHIVE] /

npub1fyh…2mv9

2023-06-07 17:54:03

in reply to nevent1q…plk9

📅 Original date posted:2016-10-16
📝 Original message:---- On Mon, 17 Oct 2016 02:54:04 +0800 Tom Zander via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote ----

> Honestly, if the reason for the too-short-for-safety timespan is that you
> want to use BIP9, then please take a step back and realize that SegWit is a
> contriversial soft-fork that needs to be deployed in a way that is extra
> safe because you can't roll the feature back a week after deployment.
> All transactions that were made in the mean time turn into everyone-can-
> spent transactions.

No one should use, nor anyone is advised to use, segwit transactions before it is fully activated. Having 2 months or 2 weeks of grace period makes totally no difference in this regard. If anyone tried to use segwit tx during your proposed 2 months grace period, all those txs were still everyone-can-spent.

All you are advocating is just stalling the process with no improvement in security.

>
> I stand by the minimum of 2 months. There is no reason to use BIP9 as it was
> coded in an older client. That is an excuse that I don't buy.
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

Author Public Key

npub1fyh6gqhg8zgyhhywkty047s64z2a7fjr307enrr3kqwtnk64plmsup2mv9

Show more details

Published at

2023-06-07 17:54:03

Kind type

1 Short Text Note

Event JSON

{ "id": "6d2224de9884e3a76659c5fc17297600f4538a4e3e0ad90b82c35afe91a9c4b6", "pubkey": "492fa402e838904bdc8eb2c8fafa1aa895df26438bfd998c71b01cb9db550ff7", "created_at": 1686160443, "kind": 1, "tags": [ [ "e", "013851964e0006d489daca620e14c7c6c63358b79bff34620f9703c31bcdc761", "", "root" ], [ "e", "8a6f547f3b1196efc1728b1061e63a69b086ebe6836b8327ca13b8556507b3fc", "", "reply" ], [ "p", "dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7" ] ], "content": "📅 Original date posted:2016-10-16\n📝 Original message:---- On Mon, 17 Oct 2016 02:54:04 +0800 Tom Zander via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote ---- \n\n \u003e Honestly, if the reason for the too-short-for-safety timespan is that you \n \u003e want to use BIP9, then please take a step back and realize that SegWit is a \n \u003e contriversial soft-fork that needs to be deployed in a way that is extra \n \u003e safe because you can't roll the feature back a week after deployment. \n \u003e All transactions that were made in the mean time turn into everyone-can- \n \u003e spent transactions. \n\nNo one should use, nor anyone is advised to use, segwit transactions before it is fully activated. Having 2 months or 2 weeks of grace period makes totally no difference in this regard. If anyone tried to use segwit tx during your proposed 2 months grace period, all those txs were still everyone-can-spent.\n\nAll you are advocating is just stalling the process with no improvement in security.\n\n \u003e \n \u003e I stand by the minimum of 2 months. There is no reason to use BIP9 as it was \n \u003e coded in an older client. That is an excuse that I don't buy. \n \u003e -- \n \u003e Tom Zander \n \u003e Blog: https://zander.github.io \n \u003e Vlog: https://vimeo.com/channels/tomscryptochannel \n \u003e _______________________________________________ \n \u003e bitcoin-dev mailing list \n \u003e bitcoin-dev at lists.linuxfoundation.org \n \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev \n \u003e", "sig": "37ce05bbcfe59cc837df9bfe6bbde88aab658ec944301561c419437a31f98ec5200edd5915568cdd17588cdf8b2289a3d238291ab050a0e6e69e190e0c20621f" }