Bitcoin covenants remain unactivated ahead of MATT signet testing

By Tom Whitfield

Bitcoin’s BIP 443 covenant proposal remained unactivated on mainnet as of late 2026, while MATT was assigned BIN-2026-0002 for signet testing, according to Cointelegraph Research.

The research says BIP 443, which defines OP_CCV, gained BIP status in May 2025. MATT traces to November 2022, when Salvatore Ingala first introduced the idea on the bitcoin-dev mailing list and later presented it at BTCAzores.

How does MATT carry state through Bitcoin transactions?

MATT embeds contract-state data directly inside Taproot output keys through cryptographic tweaks. The state travels inside the key itself, allowing a contract’s memory to accompany the coins under an output.

OP_CCV acts as the referee when a participant spends one of those outputs. The proposed opcode lets the script read state data supplied on the witness stack, and the script can then perform computations on that data.

Enforcement follows the computation. OP_CCV can require the resulting updated state to be committed again in a designated output. If the new output does not carry the required state, the spend fails, so coins can move forward only along contract-permitted paths.

That mechanism differs from standard Bitcoin Script, which evaluates each transaction in a stateless way. MATT would let Bitcoin enforce state transitions on-chain while keeping each transition tied to a prior output and its embedded memory.

What could developers build with MATT?

Cointelegraph Research lists vaults, payment pools, transferable discreet log contracts, or DLCs, and optimistic smart contracts among possible MATT applications. The framework would supply the state-carrying mechanism for those use cases through Taproot output keys.

MATT is designed to make fraud proofs more efficient, particularly when paired with OP_CAT, a separate proposed opcode for Merkle proof verification. In an optimistic setup, a computation is assumed correct unless someone proves otherwise.

Combined with OP_CAT, MATT facilitates on-chain Merkle proofs and fraud proofs that could support arbitrary computations. The research presents these broader capabilities through that pairing, and neither proposal has reached Bitcoin mainnet.

The research also identifies a design goal for node operators: provide limited state and introspection without adding significant computational overhead to base-layer nodes. The stated target lets developers examine richer contracts while keeping base-layer work limited.

Why did OP_VAULT give way to MATT?

Around the May 2025 change in BIP 443’s status, OP_VAULT, specified in BIP 345, was withdrawn in favor of the MATT-based approach. That change placed the MATT design and OP_CCV in the position of the favored covenant proposal.

As of late 2026, no covenant proposal, including BIP 443, had activated on Bitcoin mainnet. The research summary also says the technical discussion carries no immediate implications for bitcoin prices.

Consensus among Bitcoin developers remains the crucial barrier. Cointelegraph Research puts it plainly: “The bigger obstacle is social, not technical.” For MATT, that means developers must agree on the proposal before implementation can follow.

OP_CAT remains a separate thread because several of MATT’s most ambitious use cases depend on it for Merkle proof verification. The research frames those combined use cases as dependent on that pairing.

Which milestones matter next?

The immediate milestone is signet testing under BIN-2026-0002. Signet gives developers a Bitcoin test environment for trying features without touching real money, providing a controlled test for MATT’s proposed state transitions.

Beyond signet testing, the research asks whether developer discussion converges or fragments and whether any covenant proposal makes a credible move toward activation. Until then, MATT and OP_CCV remain proposals, and the listed MATT applications remain unavailable through the framework on Bitcoin mainnet.

The next market-structure checkpoint is the BIN-2026-0002 signet trial, followed by evidence that developer consensus can carry a covenant proposal toward mainnet activation.