summaryrefslogtreecommitdiff
path: root/b1/bcf271ff460e6fce6213af267fc6293a781cb3
blob: 3022b6d7ea45515232d5d24cacf84e3e09eb88cd (plain)
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
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
Return-Path: <daniel@gap600.com>
Received: from smtp1.osuosl.org (smtp1.osuosl.org [IPv6:2605:bc80:3010::138])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 6572FC0032
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  2 Aug 2023 10:38:35 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp1.osuosl.org (Postfix) with ESMTP id 4077B80C44
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  2 Aug 2023 10:38:35 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 4077B80C44
Authentication-Results: smtp1.osuosl.org;
 dkim=pass (2048-bit key) header.d=gap600.com header.i=@gap600.com
 header.a=rsa-sha256 header.s=google header.b=jmzZppir
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 smtp1.osuosl.org ([127.0.0.1])
 by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id TDRDTnIPLMkf
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  2 Aug 2023 10:38:34 +0000 (UTC)
Received: from mail-vk1-xa2b.google.com (mail-vk1-xa2b.google.com
 [IPv6:2607:f8b0:4864:20::a2b])
 by smtp1.osuosl.org (Postfix) with ESMTPS id B1C8580C12
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed,  2 Aug 2023 10:38:33 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org B1C8580C12
Received: by mail-vk1-xa2b.google.com with SMTP id
 71dfb90a1353d-4864a9faf90so524864e0c.0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Wed, 02 Aug 2023 03:38:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gap600.com; s=google; t=1690972712; x=1691577512;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=0RoWyz95lvIgQQfhBi6MnEdAE0+fAs45XjF6tIe1/Nk=;
 b=jmzZppire9nVHfy2W39GcG6DKxiUSbzhlxq5DzOcizyswdFTYQi02IDCrjEf4IciVp
 vyfvI9C1DrW6UbnNBcCARDKY4TG+cgNAQjG7j/Md3HEnW/GTKVeid9z4my4tFe4lU0lt
 EC9PKIQyJwb5NeCeo8JDWLxX+sF9BjA1DBdfdTJCLWuV3pd4/jO33QG5OSglpt6EZKN5
 HY+0B16IKozkB7EaSWqXDwEcEvGLrVvT5Pmtt/UUGd51AXWc2Oiu/ZfVOdY+UGEl9YRn
 91yv65Je+i1XNoeSawq62ASoQyLuvegJi3mprkXae39tPSgnP2jF6p6A9UOCzsPeymN5
 sKVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1690972712; x=1691577512;
 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=0RoWyz95lvIgQQfhBi6MnEdAE0+fAs45XjF6tIe1/Nk=;
 b=TYqZ0CnNF6XWYtzQlRpLduv4G/jhpBlhWzr7qh8lfywH0RtRfOZB94BzXbxE7yHXoV
 VnRgNbpzBjoe6LRUiBzd0pT6WyW4RdT2w5xPvjUTUD/JZ2fz5+NQph8ayUtf4ZyKpPqN
 gJvsTO/4WSbs+gXd3HhlCYCn1EQ8JElXqQ0dBIZboQ0f3R6fccQr+law5/26VbGmFXdm
 LcOGx1+y6r0UgerCsVxOkjZImN3WK/QVys2bhDPakdnC+WPJfGyMl093EdBfPP6/ngyF
 7jYE7HS6BQsoAmfJGPwerRsldHss/J/umJqm/OJn8qvuCgFVqmjSdKPzYYiCNkjbAjIg
 WJmw==
X-Gm-Message-State: ABy/qLboblsxwD4p3OwCWVoRJ1kskVkceQmbhtNXIEtILU73sLxnXrhH
 eDnpOkaZCX8DAYj1AXqFfryalnW/Kt5qqee7l4LwMTBxSnpBlXayJcf/Jw==
X-Google-Smtp-Source: APBJJlEFPlQ/H/QD/YUkjX4Iq5NozCoIY2uOnxK+REeAI3VpKHUockx7/S9Wno+wzxyQE/JYBsb/cezwNLS5L5KIJXM=
X-Received: by 2002:a1f:ad44:0:b0:47d:57a0:b8ba with SMTP id
 w65-20020a1fad44000000b0047d57a0b8bamr2110688vke.6.1690972712377; Wed, 02 Aug
 2023 03:38:32 -0700 (PDT)
MIME-Version: 1.0
References: <mailman.126799.1690753843.956.bitcoin-dev@lists.linuxfoundation.org>
 <CACkWPs9JRYNd5bNGCZzihhywY1GDaXfSh858GhL7TrU=uzUB0A@mail.gmail.com>
 <ZMke8q+5iDUH8fm+@petertodd.org>
 <CACkWPs9GiGxn-F2DBy6tA+f+b1Kv6bmoivAqqz7CSfPsiMwcgQ@mail.gmail.com>
 <ZMmxJoL1ZH4//8Fg@petertodd.org>
In-Reply-To: <ZMmxJoL1ZH4//8Fg@petertodd.org>
From: Daniel Lipshitz <daniel@gap600.com>
Date: Wed, 2 Aug 2023 13:38:21 +0300
Message-ID: <CACkWPs-jW-bae2oywp-LswFhmWhNAFZEFg7M=rXLi6nMGLUgRw@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>
Content-Type: multipart/alternative; boundary="000000000000d8b60a0601ee4317"
X-Mailman-Approved-At: Wed, 02 Aug 2023 10:44:51 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Pull-req to enable Full-RBF by default
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: Wed, 02 Aug 2023 10:38:35 -0000

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

Your assessment of my dishonesty is based on your assumption of how I
should be running GAP600, your assumptions are baseless and lack commercial
experience and likewise your conclusions are false.

I have provided already back in December clear access to clarify opposite
our clients corroborated with easily verifiable trxs activity of a major
client of ours. This is more than enough to corroborate our statistics.

As far as validating real RBF adoption I have offered a clear option here
https://github.com/bitcoin/bitcoin/pull/28132#issuecomment-1661960440
something like this or similar would offer a clear assessment of adoption.
Since you are not able to provide documents or public emails of hashing
pools confirming there adoption of Full RBF.
________________________________

Daniel Lipshitz
GAP600| www.gap600.com
Phone: +44 113 4900 117
Skype: daniellipshitz123
Twitter: @daniellipshitz


On Wed, Aug 2, 2023 at 4:28=E2=80=AFAM Peter Todd <pete@petertodd.org> wrot=
e:

> On Wed, Aug 02, 2023 at 01:27:24AM +0300, Daniel Lipshitz wrote:
> > Your research is not thorough and reaches an incorrect conclusion.
> >
> > As stated many times - we service payment processors and some merchants
> > directly  - Coinspaid services multiple merchants and process a
> > significant amount of BTC they are a well known and active in the space=
 -
> > as I provided back in December 2022 a email from Max the CEO of Coinspa=
id
> > confirming their use of 0-conf as well as providing there cluster
> addresses
> > to validate there deposit flows see here again -
> >
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021=
239.html
> > - if this is not sufficient then please email support@coinspaid.com and
> ask
> > to be connected to Max or someone from the team who can confirm Conspai=
d
> is
> > clients of GAP600. Max also at the time was open to do a call, I can
> check
> > again now and see if this is still the case and connect you.
> >
> > That on its own is enough of a sample to validate our statistics.
>
> Why don't you just give me an example of some merchants using Coinspaid,
> and
> another example using Coinpayments, who rely on unconfirmed transactions?
> If
> those merchants actually exist it should be very easy to give me some
> names of
> them.
>
> Without actual concrete examples for everyone to see for themselves, why
> should
> we believe you?
>
> > I have also spoken to Changelly earlier today and they offered to email
> pro
> > @ changelly.com and they will be able to confirm GAP600 as a service
>
> Emailed; waiting on a reply.
>
> > provider. Also please send me the 1 trx hash you tested and I can see i=
f
> it
> > was queried to our system and if so offer some info as to why it wasnt
> > approved. Also if you can elaborate how you integrated with Changelly -=
 I
> > can check with them if that area is not integrated with GAP600.
>
> Why don't you just tell me exactly what service Changelly offers that
> relies on
> unconfirmed transactions, and what characteristics would meet GAP600's ri=
sk
> criteria? I and others on this mailing list could easily do test
> transactions
> if you told us what we can actually test. If your service actually works,
> then
> you can safely provide that information.
>
> I'm not going to give you any exact tx hashes of transactions I've alread=
y
> done, as I don't want to cause any problems for the owners of the account=
s
> I
> borrowed for testing. Given your lack of honesty so far I have every
> reason to
> believe they might be retalliated against in some way.
>
> > As the architect of such a major change to the status of 0-conf
> > transactions I would think you would welcome the opportunity to speak t=
o
> > business and users who actual activities will be impacted by full RBF
> > becoming dominant.
>
> Funny how you say this, without actually giving any concrete examples of
> businesses that will be affected. Who exactly are these businesses? Payme=
nt
> processors obviously don't count.
>
> > Are you able to provide the same i.e emails and contacts of people at
> > the mining pools who can confirm they have adopted FULL RBF ?
>
> I've already had multiple mining pools complain to me that they and their
> employees have been harassed over full-rbf, so obviously I'm not going to
> provide you with any private contact information I have. There's no need =
to
> expose them to further harassment.
>
> If you actually offered an unconfirmed transaction guarantee service, wit=
h
> real
> customers getting an actual benefit, you'd be doing test transactions
> frequently and would already have a very good idea of what pools do
> full-rbf.
> Why don't you already have this data?
>
> --
> https://petertodd.org 'peter'[:-1]@petertodd.org
>

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

<div dir=3D"ltr">Your=C2=A0assessment=C2=A0of my dishonesty is based on you=
r assumption of how I should be running GAP600, your assumptions are basele=
ss and lack commercial experience and likewise your conclusions are false.<=
div><br></div><div>I have provided already back in December clear access to=
 clarify opposite our clients corroborated with easily verifiable=C2=A0trxs=
 activity of a major client=C2=A0of ours. This is more than enough to corro=
borate=C2=A0our statistics.=C2=A0</div><div><br></div><div>As far as valida=
ting real RBF adoption I have offered a clear option here=C2=A0<a href=3D"h=
ttps://github.com/bitcoin/bitcoin/pull/28132#issuecomment-1661960440">https=
://github.com/bitcoin/bitcoin/pull/28132#issuecomment-1661960440</a> someth=
ing like this or similar would offer a clear assessment=C2=A0of adoption. S=
ince you are not able to provide documents=C2=A0or public emails of hashing=
 pools confirming there adoption of Full RBF.<br clear=3D"all"><div><div di=
r=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div=
 dir=3D"ltr"><div><div dir=3D"ltr"><div style=3D"font-size:12.8px">________=
________________________</div><div style=3D"font-size:12.8px"><br></div><di=
v style=3D"font-size:12.8px"><font face=3D"tahoma, sans-serif">Daniel Lipsh=
itz</font></div><div style=3D"font-size:12.8px;color:rgb(0,0,0)"><font face=
=3D"tahoma, sans-serif">GAP600|=C2=A0<a href=3D"http://www.gap600.com/" tar=
get=3D"_blank">www.gap600.com</a></font></div><div style=3D"font-size:12.8p=
x;color:rgb(0,0,0)"><font face=3D"tahoma, sans-serif">Phone:=C2=A0</font><s=
pan style=3D"font-family:tahoma,sans-serif;font-size:12.8px">+44 113 4900 1=
17</span></div><div style=3D"font-size:12.8px;color:rgb(0,0,0)"><font face=
=3D"tahoma, sans-serif">Skype: daniellipshitz123</font></div><div style=3D"=
font-size:12.8px;color:rgb(0,0,0)"><font face=3D"tahoma, sans-serif">Twitte=
r: @daniellipshitz</font></div></div></div></div></div></div><br></div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On W=
ed, Aug 2, 2023 at 4:28=E2=80=AFAM Peter Todd &lt;<a href=3D"mailto:pete@pe=
tertodd.org">pete@petertodd.org</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">On Wed, Aug 02, 2023 at 01:27:24AM +0300, =
Daniel Lipshitz wrote:<br>
&gt; Your research is not thorough and reaches an incorrect conclusion.<br>
&gt; <br>
&gt; As stated many times - we service payment processors and some merchant=
s<br>
&gt; directly=C2=A0 - Coinspaid services multiple merchants and process a<b=
r>
&gt; significant amount of BTC they are a well known and active in the spac=
e -<br>
&gt; as I provided back in December 2022 a email from Max the CEO of Coinsp=
aid<br>
&gt; confirming their use of 0-conf as well as providing there cluster addr=
esses<br>
&gt; to validate there deposit flows see here again -<br>
&gt; <a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/202=
2-December/021239.html" rel=3D"noreferrer" target=3D"_blank">https://lists.=
linuxfoundation.org/pipermail/bitcoin-dev/2022-December/021239.html</a><br>
&gt; - if this is not sufficient then please email <a href=3D"mailto:suppor=
t@coinspaid.com" target=3D"_blank">support@coinspaid.com</a> and ask<br>
&gt; to be connected to Max or someone from the team who can confirm Conspa=
id is<br>
&gt; clients of GAP600. Max also at the time was open to do a call, I can c=
heck<br>
&gt; again now and see if this is still the case and connect you.<br>
&gt; <br>
&gt; That on its own is enough of a sample to validate our statistics.<br>
<br>
Why don&#39;t you just give me an example of some merchants using Coinspaid=
, and<br>
another example using Coinpayments, who rely on unconfirmed transactions? I=
f<br>
those merchants actually exist it should be very easy to give me some names=
 of<br>
them.<br>
<br>
Without actual concrete examples for everyone to see for themselves, why sh=
ould<br>
we believe you?<br>
<br>
&gt; I have also spoken to Changelly earlier today and they offered to emai=
l pro<br>
&gt; @ <a href=3D"http://changelly.com" rel=3D"noreferrer" target=3D"_blank=
">changelly.com</a> and they will be able to confirm GAP600 as a service<br=
>
<br>
Emailed; waiting on a reply.<br>
<br>
&gt; provider. Also please send me the 1 trx hash you tested and I can see =
if it<br>
&gt; was queried to our system and if so offer some info as to why it wasnt=
<br>
&gt; approved. Also if you can elaborate how you integrated with Changelly =
- I<br>
&gt; can check with them if that area is not integrated with GAP600.<br>
<br>
Why don&#39;t you just tell me exactly what service Changelly offers that r=
elies on<br>
unconfirmed transactions, and what characteristics would meet GAP600&#39;s =
risk<br>
criteria? I and others on this mailing list could easily do test transactio=
ns<br>
if you told us what we can actually test. If your service actually works, t=
hen<br>
you can safely provide that information.<br>
<br>
I&#39;m not going to give you any exact tx hashes of transactions I&#39;ve =
already<br>
done, as I don&#39;t want to cause any problems for the owners of the accou=
nts I<br>
borrowed for testing. Given your lack of honesty so far I have every reason=
 to<br>
believe they might be retalliated against in some way.<br>
<br>
&gt; As the architect of such a major change to the status of 0-conf<br>
&gt; transactions I would think you would welcome the opportunity to speak =
to<br>
&gt; business and users who actual activities will be impacted by full RBF<=
br>
&gt; becoming dominant.<br>
<br>
Funny how you say this, without actually giving any concrete examples of<br=
>
businesses that will be affected. Who exactly are these businesses? Payment=
<br>
processors obviously don&#39;t count.<br>
<br>
&gt; Are you able to provide the same i.e emails and contacts of people at<=
br>
&gt; the mining pools who can confirm they have adopted FULL RBF ?<br>
<br>
I&#39;ve already had multiple mining pools complain to me that they and the=
ir<br>
employees have been harassed over full-rbf, so obviously I&#39;m not going =
to<br>
provide you with any private contact information I have. There&#39;s no nee=
d to<br>
expose them to further harassment.<br>
<br>
If you actually offered an unconfirmed transaction guarantee service, with =
real<br>
customers getting an actual benefit, you&#39;d be doing test transactions<b=
r>
frequently and would already have a very good idea of what pools do full-rb=
f.<br>
Why don&#39;t you already have this data?<br>
<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>

--000000000000d8b60a0601ee4317--