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
|
Return-Path: <earonesty@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 161323EE
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 18:58:56 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f175.google.com (mail-qt0-f175.google.com
[209.85.216.175])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 51768224
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 18:58:55 +0000 (UTC)
Received: by mail-qt0-f175.google.com with SMTP id n4so57903563qte.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 08 May 2017 11:58:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to:cc;
bh=wwP4WcO36MvutXw/CDqEcDgjUlWT+R8lw91+9yCzlhU=;
b=bE+aWYcXLKyI31EI8MmNYP1LPpfRcX1IlKmLlXxVGRkUMytQlIxzKu27PCjndAxEz0
WT/Lt7mvUf4/N0/04fp0NQJqFVT6P1tVBl2JBERr+pzCzD+HqR6nnzdL2zT49iQ4QmSr
18MjXKAGIQKZnV5nNDjB72C/VAUTAVOh6nRqNxUk8I2SpFpIOR7i4C6ITPUm/txYfZ09
Kl/yDyOLQ5s1Tt8bTx9vQWP9fFFQegyQQTLPTOLZFMUxUAJFzjNOAi5PTkBjC6QzloP7
6rl4AVJS//eLw7baO299Xy/wO/AfBqkAIfJVwpg7HPD8tmLFoHiIGoLlN5Se3hyp3iyt
R5Cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:to:cc;
bh=wwP4WcO36MvutXw/CDqEcDgjUlWT+R8lw91+9yCzlhU=;
b=Er27htYE++BPKgmcZLDnL5kZwcnDBuiwkhAStjMuxI7Eqg8G89iSHO++vS9VYVlKxU
dz0pkmyZSjMs2DKt4AUkzC4oa5rUXS6cR4thkNkl9SHba/dZ6wihZX47KdzYWqnibLLy
dixh/MadUjPAZqHSjvoS+2LF5iZ5mmJAnfKgx6tiF6u/xSo95QSx0H8bS/P5VEFEr7nv
DTZcNf2nVgGd6rG6QY8Vcbin50hcI1ROH4/jxvFRdOIOouQnyynhaRjeSngW4ICWi9wp
lzSNRIINBY0RTkYebVNxJG4nrxgFj9AeavVjyM7X7JuNdB1FqJjvSYSz9I3/oSzFQbVD
eDqg==
X-Gm-Message-State: AN3rC/4RwD/IvlcIyY709hYBARZZgKP671bcPmav7x+evFMTINckZbtG
NfFOpJlYcq0vJL8Ztv67jCUAh6HYBdEp
X-Received: by 10.237.34.22 with SMTP id n22mr54692692qtc.164.1494269934542;
Mon, 08 May 2017 11:58:54 -0700 (PDT)
MIME-Version: 1.0
Sender: earonesty@gmail.com
Received: by 10.200.39.43 with HTTP; Mon, 8 May 2017 11:58:54 -0700 (PDT)
In-Reply-To: <CALJw2w7CBFU-xFnar6p4k+84Umh5rsuaQ6UA1-8E2_N3_AOSpQ@mail.gmail.com>
References: <CALJw2w7CBFU-xFnar6p4k+84Umh5rsuaQ6UA1-8E2_N3_AOSpQ@mail.gmail.com>
From: Erik Aronesty <erik@q32.com>
Date: Mon, 8 May 2017 14:58:54 -0400
X-Google-Sender-Auth: krqzAiMG7Kw_gjjCpSUwXEb2NH0
Message-ID: <CAJowKgJPZ=sQFXW631Czr7zYTX-ghg5ousjjkedJo-fXsefHvQ@mail.gmail.com>
To: Karl Johan Alm <karljohan-alm@garage.co.jp>
Content-Type: multipart/alternative; boundary=001a113e49b8a5a3e3054f07d4a1
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 08 May 2017 19:00:19 +0000
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Rate Limiting with server specified
Proof of Work challenges
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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, 08 May 2017 18:58:56 -0000
--001a113e49b8a5a3e3054f07d4a1
Content-Type: text/plain; charset=UTF-8
- It would be cool if any rate-limiting POW was specified as bytecode ...
so nodes can plug in as many "machine-captcha" things as they please, and
solvers can choose to solve... or just say "nope too hard".
- Alternately, it would be a lot nicer if you just required people to pay a
nanobit .... that could prevent DDOS even better, and generate a revenue
stream for nodes.
On Sun, May 7, 2017 at 10:48 PM, Karl Johan Alm via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> I am proposing a new feature for rate limiting purposes where nodes
> can make and solve arbitrary PoW challenges in return for connection
> slots (to be expanded to cover e.g. bloom filters or other DoS risky
> services).
>
> The BIP currently includes two proofs of work (sha256 and
> cuckoo-cycle) which can be combined (e.g. sha256(cuckoo-cycle) or
> sha256(sha256(sha256)), etc).
>
> Link: https://github.com/kallewoof/bips/blob/pow-connection-
> slots/bip-rate-limiting-via-pow.mediawiki
>
> Feedback welcome.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a113e49b8a5a3e3054f07d4a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>- It would be cool if any rate-limiting POW was speci=
fied as bytecode ... so nodes can plug in as many "machine-captcha&quo=
t; things as they please, and solvers can choose to solve... or just say &q=
uot;nope too hard".<br><br></div>- Alternately, it would be a lot nice=
r if you just required people to pay a nanobit .... that could prevent DDOS=
even better, and generate a revenue stream for nodes.<br><div><br></div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, May 7=
, 2017 at 10:48 PM, Karl Johan Alm via bitcoin-dev <span dir=3D"ltr"><<a=
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bi=
tcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Hello,<br>
<br>
I am proposing a new feature for rate limiting purposes where nodes<br>
can make and solve arbitrary PoW challenges in return for connection<br>
slots (to be expanded to cover e.g. bloom filters or other DoS risky<br>
services).<br>
<br>
The BIP currently includes two proofs of work (sha256 and<br>
cuckoo-cycle) which can be combined (e.g. sha256(cuckoo-cycle) or<br>
sha256(sha256(sha256)), etc).<br>
<br>
Link: <a href=3D"https://github.com/kallewoof/bips/blob/pow-connection-slot=
s/bip-rate-limiting-via-pow.mediawiki" rel=3D"noreferrer" target=3D"_blank"=
>https://github.com/kallewoof/<wbr>bips/blob/pow-connection-<wbr>slots/bip-=
rate-limiting-via-<wbr>pow.mediawiki</a><br>
<br>
Feedback welcome.<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</blockquote></div><br></div>
--001a113e49b8a5a3e3054f07d4a1--
|
