A proposal to make co-signer policies compatible
In a post to Delving Bitcoin, Luke Carriere proposed standardizing the spending policies enforced by co-signers in designs that emulate covenants. Bitcoin Optech Newsletter #430, published Nov. 6, 2026, reported on the proposal. It is a draft, not an adopted standard.
Why a common policy format could matter
Bitcoin Optech says several recent designs—including Johan Halseth’s blinded co-signers and chain code delegation—define their own policies. As a result, a wallet built for one design cannot use a co-signer or oracle built for another. A shared policy structure could address that mismatch by giving wallets and co-signers a common way to describe what spending is permitted.
The five parts of a policy
Bitcoin Optech describes the draft policy as having five components, each specifying a different part of the spending arrangement:
Output: the taproot descriptor that holds the funds.
Co-signer group: which co-signers participate and how many must sign.
Templates: the transactions co-signers may sign, including their exact outputs.
Conditions: what must be true before each template can be signed.
Profiles: the verification mode, evidence formats and any accountability scheme.
Important design choices remain open
Bitcoin Optech reports that the draft leaves several questions unresolved: whether to serialize policies as JSON or TLV; whether to specify blinded verification now or wait for more implementation experience; whether statement attestation formats belong in the proposal or in the DLC specifications; and whether the fallback path must be timelocked.
The newsletter also reports that Carriere agreed with two points raised in the discussion and said he would add a finality flag and pin down the verifier rules. Those were planned changes, not a report that they had already been implemented.