📅 Original date posted:2016-10-16
📝 Original message:On 2016/10/16 09:35, Gavin Andresen via bitcoin-dev wrote:
> I asked a lot of businesses and individuals how long it would take them
> to upgrade to a new release over the last year or two.
>
> Nobody said it would take them more than two weeks.
>
> If somebody is running their own validation code... then we should
> assume they're sophisticated enough to figure out how to mitigate any
> risks associated with segwit activation on their own.
In addition, there has been a page up for several months
(https://bitcoincore.org/en/segwit_adoption/) that gauges whether or not
wallets are ready for SegWit. Unfortunately, it appears that the page
hasn't been updated since May. I do know that several wallets have
finished or are close to finishing their support, though.
Would I want anyone to lose money due to faulty wallets? Of course not.
By the same token, devs have had almost a year to tinker with SegWit and
make sure the wallet isn't so poorly written that it'll flame out when
SegWit comes along. It's not like this is some untested, mostly unknown
feature that's being slipped out at the last minute, unlike other
features I could name but won't. :)
--
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark at vt.edu
PGP key ID: 26623924
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/f31664df/attachment.sig>;
Douglas Roark [ARCHIVE] /
npub12v…dqa4q
2023-06-07 17:54:02
in reply to nevent1q…y500
Author Public Key
npub12vlytlltjj7g3s227u9jtx2g8qtsu7gscynnn99k808ydr4vygcqvdqa4qPublished at
2023-06-07 17:54:02Event JSON
{
"id": "9d64275daf3dcef291fbcdb8fa6b1036e5e563758c64b8e94112fd2a6d3ce14e",
"pubkey": "533e45ffeb94bc88c14af70b25994838170e7910c1273994b63bce468eac2230",
"created_at": 1686160442,
"kind": 1,
"tags": [
[
"e",
"013851964e0006d489daca620e14c7c6c63358b79bff34620f9703c31bcdc761",
"",
"root"
],
[
"e",
"eed3e6fc06f54f481a7183ed2f6085af7f76debd7c1677cc714e93dddfe82d49",
"",
"reply"
],
[
"p",
"82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e"
]
],
"content": "📅 Original date posted:2016-10-16\n📝 Original message:On 2016/10/16 09:35, Gavin Andresen via bitcoin-dev wrote:\n\u003e I asked a lot of businesses and individuals how long it would take them\n\u003e to upgrade to a new release over the last year or two.\n\u003e \n\u003e Nobody said it would take them more than two weeks.\n\u003e \n\u003e If somebody is running their own validation code... then we should\n\u003e assume they're sophisticated enough to figure out how to mitigate any\n\u003e risks associated with segwit activation on their own.\n\nIn addition, there has been a page up for several months\n(https://bitcoincore.org/en/segwit_adoption/) that gauges whether or not\nwallets are ready for SegWit. Unfortunately, it appears that the page\nhasn't been updated since May. I do know that several wallets have\nfinished or are close to finishing their support, though.\n\nWould I want anyone to lose money due to faulty wallets? Of course not.\nBy the same token, devs have had almost a year to tinker with SegWit and\nmake sure the wallet isn't so poorly written that it'll flame out when\nSegWit comes along. It's not like this is some untested, mostly unknown\nfeature that's being slipped out at the last minute, unlike other\nfeatures I could name but won't. :)\n\n-- \n---\nDouglas Roark\nCryptocurrency, network security, travel, and art.\nhttps://onename.com/droark\njoroark at vt.edu\nPGP key ID: 26623924\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 842 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/f31664df/attachment.sig\u003e",
"sig": "c30cc5bdbaf1671a44ac5d4e6086ee80116eeb0919753eab2cc3472c5122d6a5c6a8fb4ab336ee67e1e25d40d19d71b23eafbb8935d14b6b17b7722f2e4d8ae4"
}