📅 Original date posted:2016-10-16 📝 Original message:The fallow period sounds ...

Tom Zander [ARCHIVE] /

npub1mju…xnq7

2023-06-07 17:54:00

in reply to nevent1q…uh63

📅 Original date posted:2016-10-16
📝 Original message:The fallow period sounds waaaay to short. I suggest 2 months at minimum
since anyone that wants to be safe needs to upgrade.

Also, please comment on why you won't use the much more safe and much
smaller Flexible Transactions.

On Sunday, 16 October 2016 16:31:55 CEST Pieter Wuille via bitcoin-dev
wrote:
> Hello all,
>
> We're getting ready for Bitcoin Core's 0.13.1 release - the first one
> to include segregated witness (BIP 141, 143, 144, 145) for Bitcoin
> mainnet, after being extensively tested on testnet and in other
> software. Following the BIP9 recommendation [1] to set the versionbits
> start time a month in the future and discussion in the last IRC
> meeting [2], I propose we set BIP 141's start time to November 15,
> 2016, 0:00 UTC (unix time 1479168000).
>
> Note that this is just a lower bound on the time when the versionbits
> signalling can begin. Activation on the network requires:
> (1) This date to pass
> (2) A full retarget window of 2016 blocks with 95% signalling the
> version bit (bit 1 for BIP141)
> (3) A fallow period consisting of another 2016 blocks.
>
> [1] https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki
> [2]
> http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.
> 2016-10-13-19.04.log.html
>
> Cheers,

--
Tom Zander
Blog: https://zander.github.io
Vlog: https://vimeo.com/channels/tomscryptochannel

Author Public Key

npub1mju50kqcm07heu967fkq6h4kq666xgekc4yrldf7q52xx9vr8jnsrdxnq7

Seen on

wss://relay.nostr.band

Show more details

Published at

2023-06-07 17:54:00

Kind type

1 Short Text Note

Event JSON

{ "id": "e3b04b2e63ba915c27690461e3ddf8614352ebc3b5dee61e955db474ba38d288", "pubkey": "dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7", "created_at": 1686160440, "kind": 1, "tags": [ [ "e", "013851964e0006d489daca620e14c7c6c63358b79bff34620f9703c31bcdc761", "", "root" ], [ "e", "76d000a5aa07db7c7360605f14cde2e67eca63e493b76b5cdd16688d09b3241b", "", "reply" ], [ "p", "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6" ] ], "content": "📅 Original date posted:2016-10-16\n📝 Original message:The fallow period sounds waaaay to short. I suggest 2 months at minimum \nsince anyone that wants to be safe needs to upgrade.\n\nAlso, please comment on why you won't use the much more safe and much \nsmaller Flexible Transactions.\n\nOn Sunday, 16 October 2016 16:31:55 CEST Pieter Wuille via bitcoin-dev \nwrote:\n\u003e Hello all,\n\u003e \n\u003e We're getting ready for Bitcoin Core's 0.13.1 release - the first one\n\u003e to include segregated witness (BIP 141, 143, 144, 145) for Bitcoin\n\u003e mainnet, after being extensively tested on testnet and in other\n\u003e software. Following the BIP9 recommendation [1] to set the versionbits\n\u003e start time a month in the future and discussion in the last IRC\n\u003e meeting [2], I propose we set BIP 141's start time to November 15,\n\u003e 2016, 0:00 UTC (unix time 1479168000).\n\u003e \n\u003e Note that this is just a lower bound on the time when the versionbits\n\u003e signalling can begin. Activation on the network requires:\n\u003e (1) This date to pass\n\u003e (2) A full retarget window of 2016 blocks with 95% signalling the\n\u003e version bit (bit 1 for BIP141)\n\u003e (3) A fallow period consisting of another 2016 blocks.\n\u003e \n\u003e [1] https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki\n\u003e [2]\n\u003e http://www.erisian.com.au/meetbot/bitcoin-core-dev/2016/bitcoin-core-dev.\n\u003e 2016-10-13-19.04.log.html\n\u003e \n\u003e Cheers,\n\n\n-- \nTom Zander\nBlog: https://zander.github.io\nVlog: https://vimeo.com/channels/tomscryptochannel", "sig": "5d128fdf09a57b5c3f0d8bb2545965a651714a87442f32ff04bc968bf6035d5009447a0cfa73b662de63cdefe132e16984d037140afeb73ae871f440289e67c5" }