📅 Original date posted:2022-08-22
📝 Original message:Besides, all silent payments are mined at the end of the day, so they are still transactions that are included in publicly auditable blocks.
The only thing that changes from the user's point of view is that these addresses cannot be heirarchically derived with BIP44 (or any other path for that matter). Nobody else can find out the HD paths of an address anyway.
- Ali
On Sun, 21 Aug 2022 22:01:34 +0000, woltx at protonmail.com wrote:
> The current Silent Payment implementation uses the standard Taproot script (Segwit V1).
>
> This does not in any way affect the consensus or auditability rules.
>
>
>
>
> Sent with Proton Mail secure email.
>
> ------- Original Message -------
> On Wednesday, August 17th, 2022 at 11:21 PM, <damian at willtech.com.au> wrote:
>
>
> > Let's be clear, if Bitcoin allows secret payments that cannot be
> > publicly audited then they have exceeded the original consensus that
> > gave Bitcoin fungibility and I will be publicly disavowing Bitcoin and
> > advocating for a full sell down. Why don't you resurrect Monero. -DA.
> >
> > On 2022-08-17 10:08, woltx via bitcoin-dev wrote:
> >
> > > 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
Ali Sherief [ARCHIVE] /
npub1xq…q2u5f
2023-06-07 23:12:51
in reply to nevent1q…ym2f
Author Public Key
npub1xq96jnxfzrdq4zgre20yqjrjsd29vcw8ymypl4v59cg6q6p66cts8q2u5fPublished at
2023-06-07 23:12:51Event JSON
{
"id": "55e6c738556685c95d8dd8b295a161700008efbfbb4359811068c6e1a4faf182",
"pubkey": "300ba94cc910da0a8903ca9e40487283545661c726c81fd5942e11a0683ad617",
"created_at": 1686179571,
"kind": 1,
"tags": [
[
"e",
"d5641420a4571dd01457439a06079449d8736471e211c54129d5e0b80ee12407",
"",
"root"
],
[
"e",
"a3a8289f1975f708367dd0fb81d378a6b728770f55c3e575dc800938cb7154a6",
"",
"reply"
],
[
"p",
"acd89cd353b3a1ceb91673b875a43f68d41d9d33bcf60fc037c3519a8e7f9354"
]
],
"content": "📅 Original date posted:2022-08-22\n📝 Original message:Besides, all silent payments are mined at the end of the day, so they are still transactions that are included in publicly auditable blocks.\n\nThe only thing that changes from the user's point of view is that these addresses cannot be heirarchically derived with BIP44 (or any other path for that matter). Nobody else can find out the HD paths of an address anyway.\n\n- Ali\n\nOn Sun, 21 Aug 2022 22:01:34 +0000, woltx at protonmail.com wrote:\n\u003e The current Silent Payment implementation uses the standard Taproot script (Segwit V1).\n\u003e\n\u003e This does not in any way affect the consensus or auditability rules.\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e Sent with Proton Mail secure email.\n\u003e\n\u003e ------- Original Message -------\n\u003e On Wednesday, August 17th, 2022 at 11:21 PM, \u003cdamian at willtech.com.au\u003e wrote:\n\u003e\n\u003e\n\u003e \u003e Let's be clear, if Bitcoin allows secret payments that cannot be\n\u003e \u003e publicly audited then they have exceeded the original consensus that\n\u003e \u003e gave Bitcoin fungibility and I will be publicly disavowing Bitcoin and\n\u003e \u003e advocating for a full sell down. Why don't you resurrect Monero. -DA.\n\u003e \u003e\n\u003e \u003e On 2022-08-17 10:08, woltx via bitcoin-dev wrote:\n\u003e \u003e\n\u003e \u003e \u003e PR #24897 (https://github.com/bitcoin/bitcoin/pull/24897) has been\n\u003e \u003e \u003e updated with a new silent payment version, which eliminates some\n\u003e \u003e \u003e manual steps from the previous version (such as the need to set the\n\u003e \u003e \u003e `keypool` to avoid costly multi-key scan).\n\u003e \u003e \u003e\n\u003e \u003e \u003e This is achieved by using a new descriptor type (\"sp()\") that has no\n\u003e \u003e \u003e range and contains exactly one key.\n\u003e \u003e \u003e\n\u003e \u003e \u003e Example: \"sp(cQq73sG9....JD51uaRD)#9llg6xjm\"\n\u003e \u003e \u003e\n\u003e \u003e \u003e This descriptor introduces a new type of output: \"silent-payment\".\n\u003e \u003e \u003e This output type returns a standard Taproot script (Segwit V1), but\n\u003e \u003e \u003e with HRP changed from \"bc\" to \"sp\" on the mainnet (or \"tsp\" on\n\u003e \u003e \u003e testnet and signet).\n\u003e \u003e \u003e\n\u003e \u003e \u003e This output type will always generate the same address (unless another\n\u003e \u003e \u003e \"sp\" descriptor is enabled on the same wallet).\n\u003e \u003e \u003e\n\u003e \u003e \u003e $ ./src/bitcoin-cli -signet getnewaddress '' 'silent-payment'\n\u003e \u003e \u003e tsp1pfmjyl7ecpmx8yf8cu6g3ez36jy7s9mzuh5pdnal3k0n588uzgmfs4s4fws\n\u003e \u003e \u003e\n\u003e \u003e \u003e To create a silent transaction, simply use the silent payment address\n\u003e \u003e \u003e as one of the outputs.\n\u003e \u003e \u003e\n\u003e \u003e \u003e The \"send\" RPC will automatically identify and tweak it.\n\u003e \u003e \u003e\n\u003e \u003e \u003e The transaction can contain multiple outputs, combining silent and\n\u003e \u003e \u003e standard addresses.\n\u003e \u003e \u003e\n\u003e \u003e \u003e I have written a step by step signet tutorial so reviewers can test\n\u003e \u003e \u003e this new version easily.\n\u003e \u003e \u003e\n\u003e \u003e \u003e https://gist.github.com/w0xlt/a7b498ac1ff14b8c292a22be789bd93f",
"sig": "a9e255061b08f9e29379f2bc0c667d3666a3eedb01fc1512acebee0a57c207238e7a6cfbfc04aedf4e838eaf3630dfd9162a4d8ad91d7fb488554440e140132b"
}