<p>The softfork defined by BIP 65 activated in december 2015. This means that the whole network enforces the new rules proposed by BIP 65, and it is safe to use CLTV opcodes in scripts since then.</p>

CC BY-SA 3.0
2017-01-10T03:01:30.140Z
hey @Pieter, BIP65 also includes a section called "Replace nLockTime entirely", has this been enforced as well? is nLockTime now deprecated?
knocte
CC BY-SA 3.0
2017-01-10T03:09:42.437Z
That section is under motivation, and explains one of the things that become possible to do (with more changes) due to the BIP65 rules. It does not describe BIP65 itself.
Pieter Wuille
CC BY-SA 3.0
2016-08-24T16:13:17.723Z
2016-08-24T16:13:17.723Z
Pieter Wuille
<p>I read in <a href="https://bitcoin.stackexchange.com/questions/18851/what-bips-are-supported-by-the-standard-client-bitcoin-core/34213">this great thread</a> that which BIP are standards is not always obvious.
<strong>What about BIP 65? To which extent is it standard?</strong> </p>

<p>Currently, all I know is that "Miners following the developers of the "Core" Bitcoin client have been adopting BIP-65, with approximately 25% of the last found blocks claiming to be ready for the soft fork on the version string in the block header. " ... not very precise.</p>

<p>Thanks</p>

CC BY-SA 3.0
2016-08-24T16:09:56.970Z
I updated the thread you linked to, since it only contained information up to 0.10.
Pieter Wuille
<bitcoin-core><bip><checklocktimeverify>
BIP 65 - how standard is it?
hartmut
# BIP 65 - how standard is it?

(Asked by: username_0 on 2016-08-24)

I read in [this great thread](https://bitcoin.stackexchange.com/questions/18851/what-bips-are-supported-by-the-standard-client-bitcoin-core/34213) that which BIP are standards is not always obvious.
**What about BIP 65? To which extent is it standard?**

Currently, all I know is that "Miners following the developers of the "Core" Bitcoin client have been adopting BIP-65, with approximately 25% of the last found blocks claiming to be ready for the soft fork on the version string in the block header. " ... not very precise.

Thanks

**Tags:** bitcoin-core, bip, checklocktimeverify

> **Comments:**
> **username_1**: I updated the thread you linked to, since it only contained information up to 0.10.  

---

## 1 answers

### Answer by username_1 on 2016-08-24. Score: 7 | Accepted answer

The softfork defined by BIP 65 activated in december 2015. This means that the whole network enforces the new rules proposed by BIP 65, and it is safe to use CLTV opcodes in scripts since then.

> **Comments:**
> **username_2**: hey @username_1, BIP65 also includes a section called "Replace nLockTime entirely", has this been enforced as well? is nLockTime now deprecated?  
> **username_1**: That section is under motivation, and explains one of the things that become possible to do (with more changes) due to the BIP65 rules. It does not describe BIP65 itself.  

---

