From: pyth <pyth@pythcoiner.dev>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] QR-based signing flow payloads in Miniscript context
Date: Wed, 29 Apr 2026 18:06:58 +0200 [thread overview]
Message-ID: <3205f013583131de7d8b59b48640641459ec5f66.camel@pythcoiner.dev> (raw)
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
Hi all,
I just published a post on Delving Bitcoin proposing a concrete set of
payloads for QR-based signing flowsin miniscript context::
https://delvingbitcoin.org/t/qr-based-signing-flow-payloads-in-miniscript-context/2464
The post defines the *content* of payloads and is intentionally
agnostic about the wire format, framing, and chunking.
Feedback very welcome, especially from people working on signing
devices or wallets/coordinators that already support, or are planning
to support, Miniscript.
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/3205f013583131de7d8b59b48640641459ec5f66.camel%40pythcoiner.dev.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-04-29 16: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=3205f013583131de7d8b59b48640641459ec5f66.camel@pythcoiner.dev \
--to=pyth@pythcoiner.dev \
--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