// Deployment of CTV (BIP-119)
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].bit = 5;
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].nStartTime = 1774809000; // 30 March 2026
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].nTimeout = 1806345000; // 30 March 2027
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].min_activation_height = 1001952; // May 2027
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].threshold = 1815; // 90%
consensus.vDeployments[Consensus::DEPLOYMENT_CTV].period = 2016;

Meeting logs

18 December 2025: https://ctv-activation.github.io/meeting/18dec2025.html

Source code and binaries for the activation client

https://github.com/ctv-activation/activation-client

FAQ

Q. Why is CHECKSIGFROMSTACK not included in this activation client?
A. CHECKSIGFROMSTACK is an interesting opcode with enough support from the developers. It could be added in an activation client built on top of this and use a different version bit for signaling.
Q. Can I test CHECKTEMPLATEVERIFY and build some proof of concept apps?
A. Yes, you can use createvault and createpool RPC in the inquisition fork. Also check other use cases on wiki.
Q. What is the difference between TEMPLATEHASH and CHECKTEMPLATEVERIFY?
A. TEMPLATEHASH is a taproot-only approach and commits to different transaction fields.
nVersion 4 bytes
nLockTime 4 bytes
ScriptSigs Hash 32 bytes (if any)
Input Count 4 bytes
Sequences Hash 32 bytes
Output Count 4 bytes
Outputs Hash 32 bytes
Input Index 4 bytes
nVersion 4 bytes
nLockTime 4 bytes
ScriptSigs Hash
Input Count
Sequences Hash 32 bytes
Output Count
Outputs Hash 32 bytes
Annex 32 bytes (if any)