Cointelegraph Research released the fifth part of its Bitcoin covenants series, focusing on the MATT framework and the proposed opcode OP_CHECKCONTRACTVERIFY (OP_CCV) defined in BIP 443.
How MATT and OP_CCV work
The MATT framework embeds contract state data inside Taproot output keys using cryptographic tweaks. When an output is spent, OP_CCV reads the supplied state data from the witness stack, allows script computations on that data, and can require the updated state to be correctly committed in a designated output. If the new output does not contain the expected state, the spend fails, enforcing contract‑defined state transitions on-chain.
Potential applications
Proposed uses for the MATT framework include vaults, payment pools, transferable discreet log contracts (DLCs) and optimistic smart contracts. The design also aims to improve fraud‑proof efficiency, especially when combined with the separate OP_CAT opcode for Merkle proof verification.
Development history
The concept was first introduced by Salvatore Ingala in November 2022 on the bitcoin‑dev mailing list and presented at BTCAzores. BIP 443, which defines OP_CCV, received BIP status in May 2025, and the related OP_VAULT proposal (BIP 345) was withdrawn in favor of the MATT approach. The proposal is identified as BIN-2026-0002 for testing on Bitcoin’s signet test network.
Current status
As of late 2026, no covenant proposal, including BIP 443, has been activated on the Bitcoin mainnet. The research notes that the discussion has no immediate price implications and that consensus among developers remains the primary hurdle for implementation. Ongoing milestones include signet testing under BIN-2026-0002 and monitoring developer consensus.
