Some updates on OP_CHECKCONTRACTVERIFY:
- BIP draft: 
- bitcoin-core concept implementation: 
- Delving post: 
In the new post on delving, I delve into the amount logic of CCV, something that has somewhat evolved since the initial posts.
I argue that while scriptPubKey checks are just equality checks this transaction-wide logic is preferable, and it's difficult to replicate it otherwise.
However, while the amount logic is not difficult, transaction-wide checks present some implementation challenges, because of multi-threaded Script validation in core.
Solving this seems to be necessary for several possible soft forks (CCV, VAULT, TXHASH, CISA), but even just to implement batch validation for Schnorr signatures, which is an optimization available today.
More details in the PR.
As usual, you'll find all the links at .
I look forward to your comment and ideas.
GitHub
BIP 443: OP_CHECKCONTRACTVERIFY by bigspider · Pull Request #1793 · bitcoin/bips
Hi all,
This is a draft for the formal specifications of the OP_CHECKCONTRACTVERIFY (CCV) opcode.
CCV enables to build Script-based state machines ...
GitHub
OP_CHECKCONTRACTVERIFY by bigspider · Pull Request #32080 · bitcoin/bitcoin
This is a first draft implementation of the OP_CHECKCONTRACTVERIFY (CCV) opcode.
CCV enables to build Script-based state machines that span across ...
Delving Bitcoin
OP_CHECKCONTRACTVERIFY and its amount semantic
I have done some work on formalizing the semantic of OP_CHECKCONTRACTVERIFY. I also wrote the first draft BIP and an implementation in bitcoin-cor...
matt
MATT (Merkleize All The Things)
The revolution will be merkleized