Return-Path: Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0C1A2C002D for ; Wed, 25 May 2022 13:13:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp3.osuosl.org (Postfix) with ESMTP id E0C4261307 for ; Wed, 25 May 2022 13:13:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.402 X-Spam-Level: X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Authentication-Results: smtp3.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=q32-com.20210112.gappssmtp.com Received: from smtp3.osuosl.org ([127.0.0.1]) by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYysXB4I77Vy for ; Wed, 25 May 2022 13:13:20 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) by smtp3.osuosl.org (Postfix) with ESMTPS id DFF9360B67 for ; Wed, 25 May 2022 13:13:19 +0000 (UTC) Received: by mail-lj1-x231.google.com with SMTP id a23so24415780ljd.9 for ; Wed, 25 May 2022 06:13:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=q32-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wicsP8XqSLbAkic9PnZCI5+00h27nBN//h52PP3CafQ=; b=4ImMksQTmUIQ6KOOXep3ZtfaZQPXQxn9cZ77f8x4gui5RbN70ivoDdO7R6FCaxwn0n /yQG+/ZCeH+ZgqM3NNIxat0XUJkj2aNRLwazxy8cfINx6IMII//StAM+Ccs8YTooNtF0 1b5Rz1SaQtGcEjyNKOiNGaMAtqkfsewIjvx04AKK4vtW2vEc/tvrXxPdDrUUt3S3r3WX BzXN3+G8VgXhrcxwMeffc54b1L9jR+nkveJwy+9aIguMAKgfQpKpaJBcnDxTdolPQ++p CRwj/EEZzp2nM4ykIkbKH65/1akKablrnjhj5jG6WwdQbiwcogWHKvwfnCMh2e7Bzasu 5pdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wicsP8XqSLbAkic9PnZCI5+00h27nBN//h52PP3CafQ=; b=vJa8wIllQp6Fu8i+9XjW5IcC84oV7OlemdoIPQq0j+VyPP739qGVfXxgLJYQP8FwW+ akEPRVQqFilV1F0Y/yK182+YQJIWvPKH3YBTQKwW+SRQ4FQzfmg7uzJPq5MmbdeM+4qq YRp953iYQaSPaGR3oAuWvxaf8jcWrz9UKyr8AXJCsyzb8rEgcqSnkokwuiHdO1jxRSHE LFj3PflFJkEInNtvrCrD+xF+yvPaHGIi0WKa0vUbuuI3S5lVPibgvovavCIXLbi8VAWJ 4B++DFOVDdbQ85zoIziJdUs7a2KbQFnfO3aD/qVFx6Jh0odqdobJIqSpwb3+nIR0Gy4g 6nIA== X-Gm-Message-State: AOAM533CGx2SZ0PaJr+upk6Yku/Wq29xNCQVHy50N6w6COWq6Vzzp3Bx Hi8karWuwz9kqiQi/w4RHLq9desdcBuoqkK5aym+wid35FwA7fo= X-Google-Smtp-Source: ABdhPJzdsiwVMk8iayrpUJDd5+R43+EQk69uoCboSiuqGKWJxhGVUtOYjP0zBzW5WcDVAsJBdSLuEUbaELYaUJv99ZU= X-Received: by 2002:a05:651c:1544:b0:253:f389:51e5 with SMTP id y4-20020a05651c154400b00253f38951e5mr6160265ljp.252.1653484397581; Wed, 25 May 2022 06:13:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Erik Aronesty Date: Wed, 25 May 2022 09:13:05 -0400 Message-ID: To: alicexbt , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000028dbf205dfd5d6f2" X-Mailman-Approved-At: Wed, 25 May 2022 13:14:57 +0000 Subject: Re: [bitcoin-dev] =?utf-8?q?Silent_Payments_=E2=80=93_Non-interactive?= =?utf-8?q?_private_payments_with_no_on-chain_overhead?= X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 May 2022 13:13:23 -0000 --00000000000028dbf205dfd5d6f2 Content-Type: text/plain; charset="UTF-8" i like the 00 || X_spend || X_scan + mandate address reuse prevention. might as well start with something strict easy to loosen it later - if needed - harder to tighten it later because of back-compatibility with addresses in-use On Tue, May 24, 2022 at 11:02 AM alicexbt via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > 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 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. > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --00000000000028dbf205dfd5d6f2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
i like the=C2=A0 00 || X_spend || X_scan=C2=A0+ mandate address reuse= prevention.=C2=A0

might as well start with something strict
easy to loosen it later - if needed - harder to tighten it later because o= f back-compatibility with addresses in-use


<= div class=3D"gmail_quote">
On Tue, May= 24, 2022 at 11:02 AM alicexbt via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org&= gt; wrote:
Hi woltx,

Thanks for implementing silent payments in Bitcoin Core. I tried the st= eps shared in tutorial and everything works as expected.=C2=A0

I have upda= ted the silent payment address (signet) as TXT record for domain alice.silentbitco.in

=
<= span>$ dig -t txt alice.silentbitco.in=C2=A0+short
"tb1px3kma8e8y8= z9l7e640v0x2chzrzww9cu06mqvwyrz805ffletu3s067sgh"
I have also added basic information about silent payments propo= sal, 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 fla= g but a new address/descriptor format should be a better approach.=C2=A0I could not review the code in detail or test edge cases however these = suggestions by Pavol Rusnak make sense:=C2=A0https://gist.github.com/RubenSomsen/c43b79517e7cb701ebf77eec6d= bb46b8?permalink_comment_id=3D4177027#gistcomment-4177027=
<= span style=3D"background-color:rgb(255,255,255);display:inline">
=
<= span style=3D"background-color:rgb(255,255,255);display:inline">
=
<= span style=3D"background-color:rgb(255,255,255);display:inline">/dev/fd0

Sent with ProtonMail secure email.

------- Original Message -------
On Tuesday, May 24th, 2022 at 7:01 AM, woltx via bitcoin-dev <bi= tcoin-dev@lists.linuxfoundation.org> wrote:

I created a short and simple tutorial o= n how to make silent payments on signet.

In thi= s tutorial, the user will generate an address, publish it, receive and spen= d coins from it and still no transactions are shown from this address in a = blockchain explorer.

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--00000000000028dbf205dfd5d6f2--