<p>Every soft-fork must have an activation block. This is also important for the consensus rules, because through that block it is defined from which point the new rules must be respected for the nodes that will be synchronized in the future and will have the latest consensus rules (take a <a href="https://bitcoin.stackexchange.com/a/100388/145749">look</a>).</p>
<p>I'm interested in how is a soft-fork activation block determined?</p>

CC BY-SA 4.0
2023-12-24T19:46:16.330Z
Does this answer your question? https://bitcoin.stackexchange.com/a/97047/208
Pieter Wuille
CC BY-SA 4.0
2023-12-24T20:04:37.940Z
@PieterWuille It does. Just have one question. For BIP16/30 timestamp is used, for BIP34/BIP65/BIP66 block number is used, but what is used for locktime, segWit and Taproot soft-forks? I can't find it in third part of your linked answer ("*Versionbits-based signalling: BIP68/112/113, BIP141/143/144, BIP91, BIP341/342*").
LeaBit
CC BY-SA 4.0
2023-12-24T20:15:13.543Z
@PieterWuille I am not referring to the way of signaling (BIP 9), but the way of checking in the consensus from which the given rules are applied.
LeaBit
CC BY-SA 4.0
2023-12-24T20:15:47.037Z
That is quite literally described in BIP9.
Pieter Wuille
CC BY-SA 4.0
2023-12-24T20:19:31.057Z
@PieterWuille I assumed that, but I do not have a time now to read entire BIP. Never mind, thanks anyway
LeaBit
<soft-fork>
How is a soft-fork activation block defined?
LeaBit
# How is a soft-fork activation block defined?

(Asked by: username_0 on 2023-12-24)

Every soft-fork must have an activation block. This is also important for the consensus rules, because through that block it is defined from which point the new rules must be respected for the nodes that will be synchronized in the future and will have the latest consensus rules (take a [look](https://bitcoin.stackexchange.com/a/100388/145749)).

I'm interested in how is a soft-fork activation block determined?

**Tags:** soft-fork

> **Comments:**
> **username_1**: Does this answer your question? https://bitcoin.stackexchange.com/a/97047/208  
> **username_0**: @username_1 It does. Just have one question. For BIP16/30 timestamp is used, for BIP34/BIP65/BIP66 block number is used, but what is used for locktime, segWit and Taproot soft-forks? I can't find it in third part of your linked answer ("*Versionbits-based signalling: BIP68/112/113, BIP141/143/144, BIP91, BIP341/342*").  
> **username_0**: @username_1 I am not referring to the way of signaling (BIP 9), but the way of checking in the consensus from which the given rules are applied.  
> **username_1**: That is quite literally described in BIP9.  
> **username_0**: @username_1 I assumed that, but I do not have a time now to read entire BIP. Never mind, thanks anyway  

---

## 0 answers

