EN
EN Current RU
Telegram
Learn

Bitcoin Draft Seeks a Common Format for Co-Signer Spending Policies

Luke Carriere’s proposal would organize co-signer spending policies into five parts, aiming to improve compatibility between Bitcoin covenant-emulation designs. Key details remain open.

Share
Telegram X Bluesky Reddit WhatsApp
a bitcoin sitting on top of a pile of money
Photo by Aleksi Räisä on Unsplash

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:

  1. Output: the taproot descriptor that holds the funds.

  2. Co-signer group: which co-signers participate and how many must sign.

  3. Templates: the transactions co-signers may sign, including their exact outputs.

  4. Conditions: what must be true before each template can be signed.

  5. 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.

Sources

  1. Bitcoin Optech Newsletter #430

← All posts