From: Craig Raw <craigraw@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] [BIP Proposal] Add sp() output descriptor format for BIP352
Date: Thu, 4 Dec 2025 08:45:54 +0200 [thread overview]
Message-ID: <CAPR5oBNCd65XaipOF=eXW7PT+JRVC4m6ey+X42aQsKa1YzA-Xw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
Hi all,
There is a practical need for a silent payments output descriptor format in
order to enable wallet interoperability and backup/recovery. There has been
some prior discussion on this topic [1][2] which this BIP proposal builds
on:
https://github.com/bitcoin/bips/pull/2047
In summary a new top level script expression sp() is defined, which takes
as it's first argument one of two new key expressions:
- spscan1q... which encodes the scan private key and the spend public key
- spspend1q... which encodes the scan private key and the spend private
key
The outputs may then be generated by combining this key material with the
sender input public keys.
In order to reduce the scanning burden, a block height may be optionally
specified in the sp() expression as a second argument for a wallet
birthday. Finally, zero or more positive integers may be specified as
further arguments to scan for additional BIP352 labels. The change label (m
= 0) is implicitly included.
Examples:
sp(spscan1q...)
sp([deadbeef/352'/0'/0']spscan1q...,900000)
sp(spspend1q...,842579,1,2,3)
sp([deadbeef/352'/0'/0']spscan1q...,900000,1,5,10)
--Craig
[1]:
https://btctranscripts.com/bitcoin-core-dev-tech/2024-04/silent-payment-descriptors
[2]: https://delvingbitcoin.org/t/bip352-private-key-formats/2080
--
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/CAPR5oBNCd65XaipOF%3DeXW7PT%2BJRVC4m6ey%2BX42aQsKa1YzA-Xw%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2630 bytes --]
next reply other threads:[~2025-12-04 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 6:45 Craig Raw [this message]
2025-12-04 9:38 ` Oghenovo Usiwoma
2025-12-04 11:02 ` Craig Raw
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='CAPR5oBNCd65XaipOF=eXW7PT+JRVC4m6ey+X42aQsKa1YzA-Xw@mail.gmail.com' \
--to=craigraw@gmail.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