From: woltx <woltx@protonmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] New Silent Payment version
Date: Wed, 17 Aug 2022 00:08:11 +0000 [thread overview]
Message-ID: <p3J90rsvbXPQnI7AtPXq1dLllvkiKmzccP-hbGd_NL7XTYM8O6ckjT3ocsixjebylnFDNKPP9XT9w0YFzY0OiW2Gvw_69SybOSOhhgio1wY=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
PR #24897 (https://github.com/bitcoin/bitcoin/pull/24897) has been updated with a new silent payment version, which eliminates some manual steps from the previous version (such as the need to set the `keypool` to avoid costly multi-key scan).
This is achieved by using a new descriptor type ("sp()") that has no range and contains exactly one key.
Example: "sp(cQq73sG9....JD51uaRD)#9llg6xjm"
This descriptor introduces a new type of output: "silent-payment". This output type returns a standard Taproot script (Segwit V1), but with HRP changed from "bc" to "sp" on the mainnet (or "tsp" on testnet and signet).
This output type will always generate the same address (unless another "sp" descriptor is enabled on the same wallet).
$ ./src/bitcoin-cli -signet getnewaddress '' 'silent-payment'
tsp1pfmjyl7ecpmx8yf8cu6g3ez36jy7s9mzuh5pdnal3k0n588uzgmfs4s4fws
To create a silent transaction, simply use the silent payment address as one of the outputs.
The "send" RPC will automatically identify and tweak it.
The transaction can contain multiple outputs, combining silent and standard addresses.
I have written a step by step signet tutorial so reviewers can test this new version easily.
https://gist.github.com/w0xlt/a7b498ac1ff14b8c292a22be789bd93f
[-- Attachment #2: Type: text/html, Size: 2055 bytes --]
next reply other threads:[~2022-08-17 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 0:08 woltx [this message]
[not found] ` <22205257d1c57f97303cda85c814ef64@willtech.com.au>
2022-08-21 22:01 ` woltx
[not found] <mailman.11.1661169603.9362.bitcoin-dev@lists.linuxfoundation.org>
2022-08-22 12:55 ` Ali Sherief
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='p3J90rsvbXPQnI7AtPXq1dLllvkiKmzccP-hbGd_NL7XTYM8O6ckjT3ocsixjebylnFDNKPP9XT9w0YFzY0OiW2Gvw_69SybOSOhhgio1wY=@protonmail.com' \
--to=woltx@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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