1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138])
by lists.linuxfoundation.org (Postfix) with ESMTP id C4B62C002D
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 3 Dec 2022 12:12:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp1.osuosl.org (Postfix) with ESMTP id 67CC181CEF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 3 Dec 2022 12:12:10 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 67CC181CEF
Authentication-Results: smtp1.osuosl.org; dkim=pass (2048-bit key,
unprotected) header.d=messagingengine.com header.i=@messagingengine.com
header.a=rsa-sha256 header.s=fm1 header.b=cp3iQGKr
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level:
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Received: from smtp1.osuosl.org ([127.0.0.1])
by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id NSwXB7H2YGvy
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 3 Dec 2022 12:12:09 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org D0DD181CE7
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com
[66.111.4.29])
by smtp1.osuosl.org (Postfix) with ESMTPS id D0DD181CE7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 3 Dec 2022 12:12:08 +0000 (UTC)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.47])
by mailout.nyi.internal (Postfix) with ESMTP id BFBCC5C0058;
Sat, 3 Dec 2022 07:12:06 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163])
by compute6.internal (MEProxy); Sat, 03 Dec 2022 07:12:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=cc:cc:content-type:date:date:feedback-id
:feedback-id:from:from:in-reply-to:in-reply-to:message-id
:mime-version:references:reply-to:sender:subject:subject:to:to
:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=
fm1; t=1670069526; x=1670155926; bh=41MEjh6jI+JzZDF6ir1WcuURSAnY
xSvgE3wvuevS2+U=; b=cp3iQGKrBu3mcQd+1dv6xh/XbIvz+8HY3MlOVxbn5cAz
zE+cj3pyPw8FSU2aKuVK3erhfipMnw4iEbfHlhVWqLl34RYAfTiFuwD6odRhccAu
hrv7dX8DnmBkfPA8lu36w6vCjt3ZA5xR0m4q5xdDxqTWDMUmeThdB4HRbQ1LLgS2
d55jmI55cRM1v7AouMMhwiwCKKIaT/+eg+1VneFijcbv54Zyy/GJeYT/GtHOwyXr
fvZ0gbnyMdiv+5GxZQcpa88f+RLDd8uUJ8kmiDcxKGdwQ5bb7u/wKMVwLW5bAlAR
rENjeY980duQifMCaXxoOu0Lrx8baLd3CNIoiyWUrg==
X-ME-Sender: <xms:Fj2LY3AsXzhIWL63RENGg1MULUeC05IOQP9MQLFaGht8jr0of7J4DA>
<xme:Fj2LY9inqOH_a0z_-1hvHjjHk_qbkSuCLTCo8pNXY-tlrjlteYogzRjF9yb7bmkSQ
7at-hleJV6HO2e0TJI>
X-ME-Received: <xmr:Fj2LYynfG55iomMSiXAjrLNRquQqriSNJkDKm2m0I16BV4OoluUzwIbXlEWY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedruddtgdefkecutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
fjughrpeffhffvvefukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefrvghtvghr
ucfvohguugcuoehpvghtvgesphgvthgvrhhtohguugdrohhrgheqnecuggftrfgrthhtvg
hrnhepuedufeeugfetffefveelvefhheejvdehkeeuudeuudegvddukeffuedvgfekgeel
necuffhomhgrihhnpehgrghpiedttddrtghomhdptghoihhnughirhgvtghtrdgtohhmpd
gtohhinhhifhihrdgtohhmpdhpvghtvghrthhouggurdhorhhgnecuvehluhhsthgvrhfu
ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphgvthgvsehpvghtvghrthhoug
gurdhorhhg
X-ME-Proxy: <xmx:Fj2LY5xGDOnEXh9eLoL7BnTtCohXWlR_t_eLcsVX-jz8BkFFASU_rQ>
<xmx:Fj2LY8T8vd28kNuXdW-SoTRBzzf-t7gV-XEPV6kM5NmDcIKJzbMgHw>
<xmx:Fj2LY8ZTk5iJF9IB9Rc6RijA2J1RHVIhSprv1g0gB-QA7rNeqtFuzw>
<xmx:Fj2LYycsTCfWt6l9h6ny24o5B4Kj8VlAuNWosttYSuma990ZvYwT9Q>
Feedback-ID: i525146e8:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat,
3 Dec 2022 07:12:06 -0500 (EST)
Received: by localhost (Postfix, from userid 1000)
id 521B75F84B; Sat, 3 Dec 2022 07:12:02 -0500 (EST)
Date: Sat, 3 Dec 2022 07:12:02 -0500
From: Peter Todd <pete@petertodd.org>
To: Daniel Lipshitz <daniel@gap600.com>
Message-ID: <Y4s9EqMfk+yXCzIO@petertodd.org>
References: <CACkWPs8-rZpGSJSEyLsg9gVAuPpHztXWSZvfGscGJCn05th0DQ@mail.gmail.com>
<Y4l/ZHl9EvhaCpix@petertodd.org>
<CACkWPs_v=MYFrn=LzPSK4+=Enw2R5+REap+MFLRhwtxcwGvEHA@mail.gmail.com>
<Y4sNxWkBp7+ogcJb@petertodd.org>
<CACkWPs9p0K-1RbVMipiAwjhexaNgmMgjENYvd9S1DpA+JVcE=w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
protocol="application/pgp-signature"; boundary="VL0KHd0h3JlJne/c"
Content-Disposition: inline
In-Reply-To: <CACkWPs9p0K-1RbVMipiAwjhexaNgmMgjENYvd9S1DpA+JVcE=w@mail.gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate
danger
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: Sat, 03 Dec 2022 12:12:10 -0000
--VL0KHd0h3JlJne/c
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Dec 03, 2022 at 01:01:16PM +0200, Daniel Lipshitz wrote:
> Shapeshift used to be clients in fact one of our first when we started in
> 2016.
>=20
> They no longer use our service but from time to time use us for fee
> recommendations. So we actually should remove their logo as a current
> client.
Yes you should. When did ShapeShift stop using your service? Did they expla=
in
why?
> If you wish to test it out try find a merchant using Coinpayments or
> Coinspaid.
>=20
> Also some of our non custodial liquidity providers offer service no
> custodial wallets. I am not sure which.
I see that you also advertise that Gap600 is "Trusted by" Coindirect and
Coinify, both AML/KYC crypto exchanges. Obviously, with full AML/KYC
double-spends are not much of a concern. And it's not even clear that
either accepts zeroconf anyway, as I'll explain later.
On this list you claimed that:
> 1. As of end of Nov 2022 - GAP600 has processed i.e responded to circa
> 15M transactions
> 2. These transactions have a cumulative value of 2.3B USD value.
> 3. We currently are seeing circa 1.5M transactions queired per month.
What's the value and number of transactions that *actually* rely on your
unconfirmed transaction tools? The only category that would apply for is go=
ods
provided immediately and irrovocably, without AML/KYC. Because it sounds li=
ke
these figures may be significantly overstated.
Re: CoinsPaid, what you say here makes it also sound like it relies on AML/=
KYC:
> CoinsPaid applies a special software tool across its solutions to conduct
> stringent KYC procedures and a risk-based approach to CDD that verify user
> identities to mitigate fraud, money laundering and other activities linke=
d to
> criminality and terrorism.
https://www.gap600.com/uncategorized/coinspaid/
Re: Coindirect, the documentation I can find appears to say that confirmati=
ons
are required before you can use coins deposited into Coindirect:
> Digital currency transactions must be confirmed on the relevant network b=
lock
> before they are considered valid. Only once confirmed, will you be able to
> use the coins deposited in your Coindirect wallet.
https://help.coindirect.com/hc/en-us/articles/115002441974-How-quickly-can-=
I-use-coins-deposited-into-my-Coindirect-wallet-
This is repeated here as well: https://help.coindirect.com/hc/en-us/article=
s/4409120006546--Deposits-
Re: Coinify, the API docs don't give any indication of risk scoring or any
other Gap600 integration:
https://merchant.coinify.com/docs/api/#payment-object
--=20
https://petertodd.org 'peter'[:-1]@petertodd.org
--VL0KHd0h3JlJne/c
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmOLPQsACgkQLly11TVR
LzcPThAAsS6iPOvSQTizMCduMdB/+/mkhlveHI4Uds/ricBc1TVbRo9Fec1QkMfP
LUzff9tOS8NDM2iwjgtNbdgJqvVB6APSLHPhOzRw0ifeMCV86KLBmOlJU3j4o9+p
c+7tic9YThKx146ibrGYmvFFys5DPg2fre2p8s97vJFw4wNvAyEg4Km+f/BN4MPq
ZIJbEnic014+5kDUBEqW79OkZK5tvbM47ei80uncy5Bndsoaij0sqNFnZIB3gUWN
8LN7atCKtm6PK5ZiOIMFKAdzyUbZNtGPU7HpS60L1pcQxzS/PUCUzsxnmDLgMzot
ZdCrfEL3J5CG6cq0d9WBkzxYWIrlYJ6xjRIzJmCmCD1cPZth7M/+JV7xaOTL834Q
g29zMAcz9udy+Xntzip1j1iMv6j1oMMsHUAmMfRp0qUoP13L4npc2Q0dIKQiLepf
g/JcRvUQzEQ+/Oj8tfmayvFix8eW9QWQ62qzU8JT0pEyylAfFw+cSGLvq4lPWqpq
pUgry15j9pLq3K4Sh08ifIxEjrZwx7s0k8hmhKaYhMgAAsT3ZHZxFffjIazQjrl/
I3ilf4HKEY+oQT4wrsuU+rcICZ4dr41KWLrjvH6rtjR/fx2UPEWdcqq7sjIu1wJp
BfCqMbGB6aDyJ/UjFgO60ipRIbHRv1r/hOl3p/wRAnE4tgtkb5s=
=wKho
-----END PGP SIGNATURE-----
--VL0KHd0h3JlJne/c--
|
