From: alicexbt <alicexbt@protonmail•com>
To: woltx <woltx@protonmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
Date: Tue, 24 May 2022 13:49:34 +0000 [thread overview]
Message-ID: <p5vlwEtPHiiul4GbOK8j3x32FKrnNC9aba_5Q_MJnNVA9I6vvc3BrfQlbvUmBKJELMvORUk6JK68_rQMwsDpat4wHCkZZst79RJPIvyDPzI=@protonmail.com> (raw)
In-Reply-To: <yAzuw9BsMPNXQIeZG98n6d0-6C1ymv9ZCfKIV9ZZYc97wuVbsjkKF1pqS9Uc4ZTuGyh2nKNeRiDYPuklq64Y4UYQ4ITfnvvQo7vsSChvUMs=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Hi woltx,
Thanks for implementing silent payments in Bitcoin Core. I tried the steps shared in tutorial and everything works as expected.
I have updated the silent payment address (signet) as TXT record for domain alice.silentbitco.in
$ dig -t txt alice.silentbitco.in +short
"tb1px3kma8e8y8z9l7e640v0x2chzrzww9cu06mqvwyrz805ffletu3s067sgh"
I have also added basic information about silent payments proposal, implementation and tutorial on https://silentbitco.in
I had no issues with performance of the UTXO Set and the blocks scan. I don't mind using flag but a new address/descriptor format should be a better approach. I could not review the code in detail or test edge cases however these suggestions by Pavol Rusnak make sense: https://gist.github.com/RubenSomsen/c43b79517e7cb701ebf77eec6dbb46b8?permalink_comment_id=4177027#gistcomment-4177027
/dev/fd0
Sent with [ProtonMail](https://protonmail.com/) secure email.
------- Original Message -------
On Tuesday, May 24th, 2022 at 7:01 AM, woltx via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> I created a short and simple tutorial on how to make silent payments on signet.
> https://gist.github.com/w0xlt/72390ded95dd797594f80baba5d2e6ee
> In this tutorial, the user will generate an address, publish it, receive and spend coins from it and still no transactions are shown from this address in a blockchain explorer.
[-- Attachment #2: Type: text/html, Size: 4220 bytes --]
next prev parent reply other threads:[~2022-05-24 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 1:31 woltx
2022-05-24 13:49 ` alicexbt [this message]
2022-05-25 13:13 ` Erik Aronesty
-- strict thread matches above, loose matches on Subject: below --
2022-03-28 15:27 Ruben Somsen
2022-03-29 14:57 ` Billy
2022-03-29 15:36 ` Ruben Somsen
2022-03-30 5:58 ` Billy
2022-03-30 16:09 ` Billy
2022-03-31 10:48 ` Ruben Somsen
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='p5vlwEtPHiiul4GbOK8j3x32FKrnNC9aba_5Q_MJnNVA9I6vvc3BrfQlbvUmBKJELMvORUk6JK68_rQMwsDpat4wHCkZZst79RJPIvyDPzI=@protonmail.com' \
--to=alicexbt@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=woltx@protonmail$(echo .)com \
/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