From: "'pyth' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] [BIP Draft] Signing message encoding
Date: Thu, 12 Nov 2026 09:50:06 +0100 [thread overview]
Message-ID: <52cfe0e671891ce094d49c85b284a1e990e23f1f.camel@pythcoiner.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Hi all,
A few months ago I started a thread on delvingbitcoin about the
payloads a wallet and an air-gapped signing device exchange over QR
codes in a miniscript context: getting xpubs, registering descriptors,
verifying addresses and signing PSBTs.
Since then the spec has grown into a draft BIP. Nothing in its messages
is specific to QR codes, so it now targets any external signer,
whatever carries the bytes (QR, USB, NFC, a file, etc.). It covers
descriptors and miniscript, BIP-388 wallet policies, MuSig2 (BIP-373)
and silent payment sends (BIP-375).
I would like to share the draft in order to collect feedback, and
reviews.
Draft BIP: https://github.com/bitcoin/bips/pull/2353
Delving post:
https://delvingbitcoin.org/t/qr-based-signing-flow-payloads-in-miniscript-context/2464
Any thoughts or suggestions are welcome.
Thanks,
Pyth
--
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/52cfe0e671891ce094d49c85b284a1e990e23f1f.camel%40pythcoiner.dev.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 525 bytes --]
reply other threads:[~2026-11-12 10:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52cfe0e671891ce094d49c85b284a1e990e23f1f.camel@pythcoiner.dev \
--to=bitcoindev@googlegroups.com \
--cc=pyth@pythcoiner.dev \
/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