📅 Original date posted:2016-10-16
📝 Original message:If somebody is not "running their own validation code" then they aren't actually using Bitcoin, so their ease in transition is irrelevant. For all they know they are accepting random numbers.
e
> On Oct 16, 2016, at 9:35 AM, Gavin Andresen via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
>> On Sun, Oct 16, 2016 at 10:58 AM, Tom Zander via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> The fallow period sounds waaaay to short. I suggest 2 months at minimum
>> since anyone that wants to be safe needs to upgrade.
>
> 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.
>
> --
> --
> Gavin Andresen
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/57ac3ff7/attachment-0001.html>;
Eric Voskuil [ARCHIVE] /
npub1sg…ppx3c
2023-06-07 17:54:01
in reply to nevent1q…7v24
Author Public Key
npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3cSeen on
wss://relay.noswhere.comPublished at
2023-06-07 17:54:01Event JSON
{
"id": "eed3e6fc06f54f481a7183ed2f6085af7f76debd7c1677cc714e93dddfe82d49",
"pubkey": "82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e",
"created_at": 1686160441,
"kind": 1,
"tags": [
[
"e",
"013851964e0006d489daca620e14c7c6c63358b79bff34620f9703c31bcdc761",
"",
"root"
],
[
"e",
"f3a8023f3ca33104740fbfc8e9fb7864ceee72b70801f72aaff167913e69a50a",
"",
"reply"
],
[
"p",
"492fa402e838904bdc8eb2c8fafa1aa895df26438bfd998c71b01cb9db550ff7"
]
],
"content": "📅 Original date posted:2016-10-16\n📝 Original message:If somebody is not \"running their own validation code\" then they aren't actually using Bitcoin, so their ease in transition is irrelevant. For all they know they are accepting random numbers.\n\ne\n\n\u003e On Oct 16, 2016, at 9:35 AM, Gavin Andresen via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e\u003e On Sun, Oct 16, 2016 at 10:58 AM, Tom Zander via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e The fallow period sounds waaaay to short. I suggest 2 months at minimum\n\u003e\u003e since anyone that wants to be safe needs to upgrade.\n\u003e \n\u003e 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.\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 assume they're sophisticated enough to figure out how to mitigate any risks associated with segwit activation on their own.\n\u003e \n\u003e -- \n\u003e --\n\u003e Gavin Andresen\n\u003e \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-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20161016/57ac3ff7/attachment-0001.html\u003e",
"sig": "2fc2bed44c5d283e3b3848a33d864c1d2ddcbda1cd1ba00396e950bbb9ef61e0565355e52e4f867f62bb3171995b347547e9d71c6be00c5b554ed0481a236ba8"
}