path: root/cb/25a01b073984f4e5c0554dd7d349f342d69975

Return-Path: <daniel@gap600.com>
Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 55E20C002B
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  6 Feb 2023 12:08:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp2.osuosl.org (Postfix) with ESMTP id 31826402EB
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  6 Feb 2023 12:08:54 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 31826402EB
Authentication-Results: smtp2.osuosl.org;
 dkim=pass (2048-bit key) header.d=gap600.com header.i=@gap600.com
 header.a=rsa-sha256 header.s=google header.b=wVrrjPwd
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, 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 0shOBo138BL1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  6 Feb 2023 12:08:53 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org CA7A6400BF
Received: from mail-vk1-xa33.google.com (mail-vk1-xa33.google.com
 [IPv6:2607:f8b0:4864:20::a33])
 by smtp2.osuosl.org (Postfix) with ESMTPS id CA7A6400BF
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  6 Feb 2023 12:08:52 +0000 (UTC)
Received: by mail-vk1-xa33.google.com with SMTP id b81so5995534vkf.1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 06 Feb 2023 04:08:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gap600.com; s=google;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=q3Vc55uIGX14WfAG/YMVLO6SC3EhCH4bTxuKaP740SY=;
 b=wVrrjPwdJPOnNyqwJIqmDvK6drTiYQWuj5+XTWGxGqFDIdlmfyK9WTMrDlkyQ+FDR7
 NUCtATRO4tcbJBj/rWlHPO95oIPWfLZ5urYIVURqoXFTQ07BYKFLutOPhwxYuybENGh4
 Jb6lCtfSOTE9UR2rcdtpFg3QkCrxhJKGkKa+lsO87cqnli0chryh81aQ8lTyDS4G/Oic
 eUvXApPT92b8MDds5q9TSrIghPF2OxYtIHFp0LXhKFfRswpT++lEw3NoIoiKN0uO7pmW
 h/shBWSDMNSr2enRJLTaojMGcvpACOYToSfHce5tdUJ7liQs0a/HSDor4me3ochmqWoT
 f+Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20210112;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id
 :reply-to;
 bh=q3Vc55uIGX14WfAG/YMVLO6SC3EhCH4bTxuKaP740SY=;
 b=GYjTC2IfDlfIseR5zJnRjDgLUwuztKEludrB5rXLPoGK0kWqLojgC1rgzCv/btnetu
 /TgYORS0rGlf9NtR3dsbSv8sfGlUtHUKAY8yejFpzJqjJ7MsWhwGpCOVtYCuOwWN9CqV
 /uEkXXP8GzQLf1wl8qWxaI/VdybdUl1nOPljR5QspRHfeh+pUKHVQL+uFPhlRAy7Lool
 cq7OrCuZrdhm9uu2BL7SZz5ChvJJEBWfnFxuh+v6TrUqZQ77SM2JMbvbYKmPu2NF7k1G
 xEIHrxAeNn+ylHGP4TBAH9p/CDzQ7FTuLbVEKGGJD8P5OVpPDf18eWoNJr5fjNyXMalX
 E0Hw==
X-Gm-Message-State: AO0yUKXD3xhamDAqgwmRd5WfFLKKiaX2CqxpEF3ZPhgtVPhR7gbWGnNy
 p22Ad3wqOgtW/4fvqETgbPTaIfIBC2voCjJ9B0jLJcxfk+WLeg==
X-Google-Smtp-Source: AK7set/fRIYeRz1yrKnVB9CdRRu++emN4brhiw+En7AbhQBNLRRuGX2SL6JX/2kq0CP5uFXyRpxtauiKGiwaTwP7ejY=
X-Received: by 2002:ac5:cc52:0:b0:3e9:55ba:2ad3 with SMTP id
 l18-20020ac5cc52000000b003e955ba2ad3mr2865769vkm.24.1675685331530; Mon, 06
 Feb 2023 04:08:51 -0800 (PST)
MIME-Version: 1.0
References: <CAAQdECAspoRJRz7j1ubAe=Cen==AVF5bm-Q2=0TiKc7NtbU65A@mail.gmail.com>
 <CACkWPs_4pjTo50=S86KPEznBs0PU7rd30rBGHq2Q5=6n6hYMgQ@mail.gmail.com>
 <CAHTn92wH17Z+p5cFOLpzsVUuTf4-nZc7tOjQr+_xjSU5groa0Q@mail.gmail.com>
 <CACkWPs9VawCYt7maiNqzafkFnHTiGJQkXMT4VXQQcG-rE2TTNw@mail.gmail.com>
 <Y5jxmItJIpIUVY+x@petertodd.org>
 <CACkWPs_jSLDg3seON0uu=ri6iR9cytXo2MEPJ5PVeap+iDreeQ@mail.gmail.com>
 <Y5zfuVGpRGaknwaU@petertodd.org>
 <CACkWPs_6z7UyXzejTqjy=i+SkSz-76VdzZ20K1DzcVJxan_HZg@mail.gmail.com>
 <Y8HvCbBd5+pm8Uj2@petertodd.org>
 <CACkWPs_Nqm1663c1q8xHX=A0Gpa7m1kV_QX6t0s8uPOEh3WQLA@mail.gmail.com>
 <Y96HgwjLkF6Bd2DV@petertodd.org>
In-Reply-To: <Y96HgwjLkF6Bd2DV@petertodd.org>
From: Daniel Lipshitz <daniel@gap600.com>
Date: Mon, 6 Feb 2023 14:08:40 +0200
Message-ID: <CACkWPs-78Ytv3dVRD_VsXUFpuqWgwapYuDP8Vy5sR4F12e9fdw@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary="000000000000f107c605f406e47a"
X-Mailman-Approved-At: Mon, 06 Feb 2023 13:07:02 +0000
Cc: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>,
 John Carvalho <john@synonym.to>
Subject: Re: [bitcoin-dev] A proposal for Full RBF to not exclude Zero Conf
 use case
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2023 12:08:54 -0000

--000000000000f107c605f406e47a
Content-Type: text/plain; charset="UTF-8"

On Sat, Feb 4, 2023 at 6:28 PM Peter Todd <pete@petertodd.org> wrote:

> On Sat, Jan 14, 2023 at 10:15:30PM +0200, Daniel Lipshitz wrote:
> > We have standard commercial information about the payment processors, non
> > custodial liquidity providers and merchants which become our clients - we
> > do not have any kyc/aml information or telephone number on who is sending
> > our clients the bitcoin for deposit.  For us these are just bitcoin Trx
> > which our clients choose to benefit from 0-conf deposit recognition. Our
> > service is provided via API with the only information our clients share
> > with us, regarding a specific bitcoin transaction, being public bitcoin
> > information like trx hash and output address.
>
> You know who your clients are, and thus every request for information on a
> transaction is reasonably likely to be a deposit associated with the
> client who
> requested it. Learning what addresses are associated with what entity is a
> significant benefit to Chainalysis operations, and there's every reason to
> expect that the data you learn will either be sold or leaked to Chainalysis
> companies.
>

I would estimate based on general discussions with clients and open
research more than 90% of our clients use different AML trx analysis
service providers for trx deposited on their platforms -
completely irrelevant to us or 0-conf. So if these clients were to stop
recognising 0-conf this would have no impact on these AML service providers
access to the data. We service payment processors and liquidity providers
and have little or no insight into which wallets or merchants our clients
service.

 Further to this many of the cluster addresses of our clients and just like
other service providers in the bitcoin space are publicly known - just as
Max had no issue sharing the cluster of his deposit address in his email
which I posted to the list.

>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>

--000000000000f107c605f406e47a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 4, 2023 at 6:28 PM Peter =
Todd &lt;<a href=3D"mailto:pete@petertodd.org">pete@petertodd.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Ja=
n 14, 2023 at 10:15:30PM +0200, Daniel Lipshitz wrote:<br>
&gt; We have standard commercial information about the payment processors, =
non<br>
&gt; custodial liquidity providers and merchants which become our clients -=
 we<br>
&gt; do not have any kyc/aml information or telephone number on who is send=
ing<br>
&gt; our clients the bitcoin for deposit.=C2=A0 For us these are just bitco=
in Trx<br>
&gt; which our clients choose to benefit from 0-conf deposit recognition. O=
ur<br>
&gt; service is provided via API with the only information our clients shar=
e<br>
&gt; with us, regarding a specific bitcoin transaction, being public bitcoi=
n<br>
&gt; information like trx hash and output address.<br>
<br>
You know who your clients are, and thus every request for information on a<=
br>
transaction is reasonably likely to be a deposit associated with the client=
 who<br>
requested it. Learning what addresses are associated with what entity is a<=
br>
significant benefit to Chainalysis operations, and there&#39;s every reason=
 to<br>
expect that the data you learn will either be sold or leaked to Chainalysis=
<br>
companies.<br></blockquote><div><br></div><div>I would estimate based on ge=
neral discussions with clients and open research more than 90% of our clien=
ts use different AML trx analysis service providers for trx deposited on th=
eir platforms - completely=C2=A0irrelevant to us or 0-conf. So if these cli=
ents were to stop recognising 0-conf this would have no impact on these AML=
 service providers access to the data. We service payment processors and li=
quidity providers and have little or no insight into which wallets or merch=
ants our clients service.</div><div><br></div><div>=C2=A0Further to this ma=
ny of the cluster addresses of our clients and just=C2=A0like other service=
 providers in the bitcoin space are publicly=C2=A0known - just as Max had n=
o issue sharing the cluster of his deposit address in his email which I pos=
ted to the list.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
-- <br>
<a href=3D"https://petertodd.org" rel=3D"noreferrer" target=3D"_blank">http=
s://petertodd.org</a> &#39;peter&#39;[:-1]@<a href=3D"http://petertodd.org"=
 rel=3D"noreferrer" target=3D"_blank">petertodd.org</a><br>
</blockquote></div></div>

--000000000000f107c605f406e47a--