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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1Y9ZWI-0002Fh-Ty
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Jan 2015 13:22:30 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.214.169 as permitted sender)
client-ip=209.85.214.169; envelope-from=jgarzik@bitpay.com;
helo=mail-ob0-f169.google.com;
Received: from mail-ob0-f169.google.com ([209.85.214.169])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Y9ZWE-0000oa-MB
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Jan 2015 13:22:28 +0000
Received: by mail-ob0-f169.google.com with SMTP id vb8so12995075obc.0
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Jan 2015 05:22:21 -0800 (PST)
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:from:date
:message-id:subject:to:cc:content-type;
bh=sJGA60+azraSEWWmov+OiFrtx+So5oub9g8g/2EP6G4=;
b=HolXAgxDp5BEsjXY3mSMGgjPk6IXoYpTf8SKRHKEt5HA2IqIoIILQTZ608SmrP7LfJ
UwUfoHoEFQLxPvffVmb6IUj4X4zaXwG8VAnrQrRJQO33C/Ozo2GPpeZIOjwPX8ux0lST
aSxRBCP7IebzHUVn/2gP6CLe4vw1vpb4Q5dQnzYP+euJN/5ags+9pawI/wGJ0h1lWlzp
53eu8Iyy/vdpEqUpaVq/cwnKja8zjA7MOASQ1o1scLMxYt8oWSXBz9xU3LA+tv5tmrFF
F9ThAUYCtqT7T1oQZFOn4meg6YsOXVFxNFxcwWnZEaL44b7Y8fmkTz6rp4uCcmhosblC
Te0A==
X-Gm-Message-State: ALoCoQmyyLDJJN9CtVyt6cH6FcoPOFEFauVU8x0Rk/x7B88MNqEjV/Tcbb/ntn9CT5o2L5pthhet
X-Received: by 10.202.173.198 with SMTP id w189mr8599340oie.27.1420809741228;
Fri, 09 Jan 2015 05:22:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.209.9 with HTTP; Fri, 9 Jan 2015 05:22:00 -0800 (PST)
In-Reply-To: <CANEZrP0ZabL2S=UhB2u7en2AfrckPk5CQe0YN-i4eDXQK-LF6A@mail.gmail.com>
References: <CAGNXQMSSCtgiyFEGHS2ufuc-RZcAtpEJyFpQMDmNKd1qEDq5qA@mail.gmail.com>
<CANEZrP0ZabL2S=UhB2u7en2AfrckPk5CQe0YN-i4eDXQK-LF6A@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 9 Jan 2015 08:22:00 -0500
Message-ID: <CAJHLa0NoDU+DOPfubhbVs8_Y92+uGG=mZ2+ruRCXkeULghWVVg@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a113eabb4eb7565050c380b16
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: 1Y9ZWE-0000oa-MB
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bi-directional micropayment channels with
CHECKLOCKTIMEVERIFY
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, 09 Jan 2015 13:22:31 -0000
--001a113eabb4eb7565050c380b16
Content-Type: text/plain; charset=UTF-8
Mike, Can you be more specific? You reference "original design" without
saying how it was different/better.
On Fri, Jan 9, 2015 at 8:20 AM, Mike Hearn <mike@plan99.net> wrote:
> A limitation on most existing micropayment channel ideas is that payments
>> can only flow in one direction.
>>
>
> It's worth noting that the original protocol as designed by Satoshi did
> not have this limitation. It has evolved this way because of ad-hoc DoS
> fixes over time (btw I'm not saying they were the wrong thing to do, as non
> "ad hoc" solutions are significantly more work). But it seems like
> eventually a different approach to handling DoS attacks based on resource
> prioritisation and scheduling will become needed / implemented, and at that
> point the original design could be safely brought back to life.
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is
> your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--001a113eabb4eb7565050c380b16
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Mike, Can you be more specific?=C2=A0 You reference "=
original design" without saying how it was different/better.<br><br><b=
r></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, J=
an 9, 2015 at 8:20 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"mailto:m=
ike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-colo=
r:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"lt=
r"><div>A limitation on most existing micropayment channel ideas is that pa=
yments can only flow in one direction.=C2=A0</div></div></blockquote><div><=
br></div></span><div>It's worth noting that the original protocol as de=
signed by Satoshi did not have this limitation. It has evolved this way bec=
ause of ad-hoc DoS fixes over time (btw I'm not saying they were the wr=
ong thing to do, as non "ad hoc" solutions are significantly more=
work). But it seems like eventually a different approach to handling DoS a=
ttacks based on resource prioritisation and scheduling will become needed /=
implemented, and at that point the original design could be safely brought=
back to life.</div><div><br></div></div></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
Dive into the World of Parallel Programming! The Go Parallel Website,<br>
sponsored by Intel and developed in partnership with Slashdot Media, is you=
r<br>
hub for all things parallel software development, from weekly thought<br>
leadership blogs to news, videos, case studies, tutorials and more. Take a<=
br>
look and join the conversation now. <a href=3D"http://goparallel.sourceforg=
e.net" target=3D"_blank">http://goparallel.sourceforge.net</a><br>_________=
______________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail=
_signature">Jeff Garzik<br>Bitcoin core developer and open source evangelis=
t<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" targe=
t=3D"_blank">https://bitpay.com/</a></div>
</div>
--001a113eabb4eb7565050c380b16--
|
