Return-Path: Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 43B5AC002D for ; Mon, 27 Jun 2022 20:35:49 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id 1E15F4063E for ; Mon, 27 Jun 2022 20:35:49 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 1E15F4063E Authentication-Results: smtp2.osuosl.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=RqAXJMIY X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEd0E0bBhOq7 for ; Mon, 27 Jun 2022 20:35:48 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 20C6E40289 Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by smtp2.osuosl.org (Postfix) with ESMTPS id 20C6E40289 for ; Mon, 27 Jun 2022 20:35:47 +0000 (UTC) Received: by mail-ot1-x32b.google.com with SMTP id 7-20020a9d0107000000b00616935dd045so8227758otu.6 for ; Mon, 27 Jun 2022 13:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/HPAPglwnGLdpa5W7FxELrUBCWK9WcTERNjfp+f+hW8=; b=RqAXJMIYvqDoku09OpFGqrfX+QBUkFZeB1JGMLbWVVWYsUAFb8m4/hGdghfuXGIfGx GCsfa+XWbioQEcDwC66tYjziuwxDIqELWqAXUdQOZ0UzMuobNnMPk+DG9MGbXPC9Mria h2sCvfBYA1KSJcisRQioDtNl726kpDqJp9+iyWoMdZAgbycYHUVUphEKq7Qs7IOmn/BX OZpEKoIlPmUhXNi5Qepn+BkqeE56LWf32Juhs328/PemSILjir73+IERhJ5u9hulHJg2 wzmZ5MJ0SXEfuasBqT1mqnZkg6q91BQxzaP+nR3N7qW4QvnXqCKlB9IPwRtexuJTVMXS 2f3A== 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=/HPAPglwnGLdpa5W7FxELrUBCWK9WcTERNjfp+f+hW8=; b=Do9AAmzVkto71Gx0MeNlD18QvrfrCWmvODJZ8/ASeeNcChKawh9kJTef7r/KMtaNmO jMUNcp0zoqfZ7EgO2TX5wlncl4rxSf6ZFeTMrtR0qNMrZi/PienjpMYKtvC37RgqPZlo X/zSyPU4AUjagB90T/MNcXTtx5EhiHOGm93vDr2J0qjvkevaocubDCi3HdOUkdzP58dh 2t5+IwLmNiDWhIine17Dr5yVcYpMwhpwPzM+mdj5dBIKVzqrEPSHXDMmHf4SXMDumsVG ZBVZIrv9ABcNQ9uY6thQX0S+pBZo753AYjwUYUY9vgioE+b9lTGX79L5cTBKnnPwnKK/ plIg== X-Gm-Message-State: AJIora9n8VYGwMigmPlyEc/AeDLx6+av95rF98wAEiR5k913Mw+pPxao q7e3omHcutDqwAq0+y5nY3OOB5Da6Y1vyZTDfrk= X-Google-Smtp-Source: AGRyM1sOM85q6TnMnKvR6VL5C2pIBTkQaUVgok2YiMtZlKQkJ5hOopxOs1SV0EHIylWAqwhOg+uiVR7ACU6Rn65sve0= X-Received: by 2002:a05:6830:2783:b0:60c:1052:b67d with SMTP id x3-20020a056830278300b0060c1052b67dmr6893996otu.313.1656362147219; Mon, 27 Jun 2022 13:35:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ruben Somsen Date: Mon, 27 Jun 2022 22:35:34 +0200 Message-ID: To: Bryan Bishop , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000678f6a05e273ddc4" X-Mailman-Approved-At: Mon, 27 Jun 2022 20:36:23 +0000 Subject: Re: [bitcoin-dev] [BIP proposal] Private Payments 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: Mon, 27 Jun 2022 20:35:49 -0000 --000000000000678f6a05e273ddc4 Content-Type: text/plain; charset="UTF-8" Hi Bryan, >just publishing on a tor hidden service that other wallets check The problem is that this data is critical to access the funds. By putting it on-chain you're guaranteeing that it's always available when you restore your funds from backup. Cheers, Ruben On Mon, Jun 27, 2022 at 10:21 PM Bryan Bishop via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > Hi, > > On Mon, Jun 27, 2022 at 2:14 PM Alfred Hodler via bitcoin-dev < > bitcoin-dev@lists.linuxfoundation.org> wrote: > >> 2. Notification transactions still exist but no longer leave a privacy >> footprint on the blockchain. Instead, a notification transaction is simply >> a single OP_RETURN containing a value that only Alice and Bob can >> calculate. If Alice's notification transaction uses UTXOs not associated >> with her identity, there is never a footprint showing that either her or >> Bob are using private payments. If Alice uses tainted coins, only she is >> exposed as a user of Private Payments but Bob still isn't. >> > > That's a neat trick. What about not using OP_RETURN at all, and just > publishing on a tor hidden service that other wallets check? Alice > wouldn't have to expose on-chain that she is a sender of a private payment. > > - Bryan > https://twitter.com/kanzure > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000678f6a05e273ddc4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Bryan,

>just publishing on a tor = hidden service that=C2=A0other wallets check

The p= roblem is that this data is critical=C2=A0to access the funds. By putting i= t on-chain you're guaranteeing that it's always available when you = restore your funds from backup.

Cheers,
= Ruben

--000000000000678f6a05e273ddc4--