From: Luke Carriere <luke@lukecarriere.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] Re: BIP draft: Co-signer Spending Policies (v2.1)
Date: Sun, 8 Nov 2026 13:28:50 -0800 [thread overview]
Message-ID: <CAFYm+PeOHzp7A8_pcCFQ0tG95Rt_Zd7v4t3c50DAMkzxa91Czw@mail.gmail.com> (raw)
In-Reply-To: <CAFYm+Pe8_a568_=GtHhHMVZUF8j8JSS_eYJEaTSbJnOn-dkCHw@mail.gmail.com>
Hi all,
The Delving discussion for this draft is here:
https://delvingbitcoin.org/t/bip-draft-co-signer-spending-policies/2955
Draft v2.1 is now published:
https://github.com/lukecarriere/bip-cosigner-spending-policies/commit/c21ed45c1eb78a562962d17a5fdaa86c9d7befb3
- Thanks @tehiyadu: fail-closed policy validation, explicit fields and
version-first CSP/policy/v0 commitments.
- Thanks @PREDGE: signed statement finality and finality-aware
evidence and escrow; exact-byte vectors remain TBD.
- Also corrected the k-of-n safety condition, citations and headers.
JSON versus TLV, the complete wire schema and a reference
implementation remain open. This is still a draft seeking criticism;
please reply here or on Delving.
Luke
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAFYm%2BPeOHzp7A8_pcCFQ0tG95Rt_Zd7v4t3c50DAMkzxa91Czw%40mail.gmail.com.
prev parent reply other threads:[~2026-11-08 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 1:16 [bitcoindev] Luke Carriere
2026-11-08 21:28 ` Luke Carriere [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFYm+PeOHzp7A8_pcCFQ0tG95Rt_Zd7v4t3c50DAMkzxa91Czw@mail.gmail.com \
--to=luke@lukecarriere.com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox