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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <adrian@coinbase.com>) id 1Z5y7q-0000lx-HM
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 15:22:38 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of coinbase.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=adrian@coinbase.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5y7m-0006qk-JS
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 15:22:38 +0000
Received: by wibdq8 with SMTP id dq8so21836164wib.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 08:22:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=QIycPV5J6yze5CqMhVTI0+5QGWE/Mlrm/gm5VAD46O4=;
b=daLNGQObarWv1sV/qgiNx/mVXazNObfIDL/j1vLpxnajwXvchiPt+lJ1IGLkyYQQaN
Ga4rJuL/JrtulBmqKXTWOxAYQfiU2cR+6R5ySdEVFjV5weckk5XsRKITl37Lb78MGbPy
ZGE22QeShuAorTUuizLV/KUHM9gCkhUfe9asxLN3Ibc9ee1X5QczkoKvMLuhE51RLXfe
sjq873JYi6Imr28yCnbMbFQocNGFogDTT+pcZmH/8h+pcWs1j1LfDUwzxye1rrQCTc5f
qsv7CxoRM5S+eI0ANU/57nJ2hzkmxnDzWYtqRcf1FCyGdDWPm/X60xl476eLo8Ea198C
fp4w==
X-Gm-Message-State: ALoCoQkNEiNCWehfoHrIkCKv888vHVBTWzvf6gI0Zd8fexF49XBboqfp0bfwL7NWrkuqM9l70IQ7
MIME-Version: 1.0
X-Received: by 10.181.11.193 with SMTP id ek1mr7668789wid.15.1434727348609;
Fri, 19 Jun 2015 08:22:28 -0700 (PDT)
Received: by 10.27.177.99 with HTTP; Fri, 19 Jun 2015 08:22:28 -0700 (PDT)
In-Reply-To: <CAFzgq-wS6-grST9NL63zKQSpjw9GgJydZGAELV_=ToLS54k5Ug@mail.gmail.com>
References: <20150619103959.GA32315@savin.petertodd.org>
<CABsx9T1pnT=Tty3+tg+EUphLwQrWXf9EEwUOGuyNcdu=4wAqTg@mail.gmail.com>
<20150619135245.GB28875@savin.petertodd.org>
<CAMK47c_kCgb6hEUf_JePAC_tBK8aCF1W4f1guiAah-Gj_cFfSw@mail.gmail.com>
<CAFzgq-wS6-grST9NL63zKQSpjw9GgJydZGAELV_=ToLS54k5Ug@mail.gmail.com>
Date: Fri, 19 Jun 2015 08:22:28 -0700
Message-ID: <CAMK47c-R2TM=Fg-5doL=paZKTydgut91=e0w1LBXModQWQQ2jw@mail.gmail.com>
From: Adrian Macneil <adrian@coinbase.com>
To: Chun Wang <1240902@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043bdedaf6a7a30518e07d06
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z5y7m-0006qk-JS
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 19 Jun 2015 15:22:38 -0000
--f46d043bdedaf6a7a30518e07d06
Content-Type: text/plain; charset=UTF-8
Great. Thank you for this!
Adrian
On Fri, Jun 19, 2015 at 7:40 AM, Chun Wang <1240902@gmail.com> wrote:
> On Fri, Jun 19, 2015 at 10:00 PM, Adrian Macneil <adrian@coinbase.com>
> wrote:
> > However, we do rely pretty heavily on zeroconf transactions for merchant
> > processing, so if any significant portion of the mining pools started
> > running your unsafe RBF patch, then we would probably need to look into
> this
> > as a way to prevent fraud.
>
> This might be useful to you: https://www.f2pool.com/api/mempool
>
>
--f46d043bdedaf6a7a30518e07d06
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Great. Thank you for this!<div><br></div><div>Adrian</div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jun=
19, 2015 at 7:40 AM, Chun Wang <span dir=3D"ltr"><<a href=3D"mailto:124=
0902@gmail.com" target=3D"_blank">1240902@gmail.com</a>></span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><span class=3D"">On Fri, Jun 19, 2015 at 1=
0:00 PM, Adrian Macneil <<a href=3D"mailto:adrian@coinbase.com">adrian@c=
oinbase.com</a>> wrote:<br>
> However, we do rely pretty heavily on zeroconf transactions for mercha=
nt<br>
> processing, so if any significant portion of the mining pools started<=
br>
> running your unsafe RBF patch, then we would probably need to look int=
o this<br>
> as a way to prevent fraud.<br>
<br>
</span>This might be useful to you: <a href=3D"https://www.f2pool.com/api/m=
empool" rel=3D"noreferrer" target=3D"_blank">https://www.f2pool.com/api/mem=
pool</a><br>
<br>
</blockquote></div><br></div>
--f46d043bdedaf6a7a30518e07d06--
|
