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
|
Return-Path: <karljohan-alm@garage.co.jp>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id E69BB2C
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 02:59:08 +0000 (UTC)
X-Greylist: delayed 00:09:47 by SQLgrey-1.7.6
Received: from mo.garage.hdemail.jp (mo.garage.hdemail.jp [46.51.242.127])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1A534192
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 02:59:08 +0000 (UTC)
Received: from ip-10-217-1-36.ap-northeast-1.compute.internal
(localhost.localdomain [127.0.0.1])
by mo.garage.hdemail.jp (hde-mf-postfix) with SMTP id 5B45714C0BD
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 11:49:19 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
X-Received: from unknown (HELO mo.garage.hdemail.jp) (127.0.0.1)
by 0 with SMTP; 8 May 2017 11:49:19 +0900
X-Received: from mo.garage.hdemail.jp (localhost.localdomain [127.0.0.1])
by mo.garage.hdemail.jp (hde-ma-postfix) with ESMTP id 4FDB14C082
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 11:49:19 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
Received: from gw30.oz.hdemail.jp
(ip-10-188-135-23.ap-northeast-1.compute.internal [10.188.135.23])
by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id 48CEA14C0BD
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 11:49:19 +0900 (JST)
(envelope-from karljohan-alm@garage.co.jp)
X-Durian-MailFrom: karljohan-alm@garage.co.jp
X-Durian-RcptTo: bitcoin-dev@lists.linuxfoundation.org
Received: from gw30.oz.hdemail.jp (gw30.oz.hdemail.jp [127.0.0.1])
by gw30.oz.hdemail.jp (gw30.oz.hdemail.jp [127.0.0.1]);
Mon, 8 May 2017 11:49:17 +0900
X-Received: from mail-qt0-f200.google.com (lb1.oz.lo.hdemail.jp
[54.248.222.53])
(using TLSv1 with cipher AES128-SHA (128/128 bits))
(No client certificate requested)
by gw30.oz.hdemail.jp (Postfix) with ESMTP id 36DDF148C0F5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 8 May 2017 11:49:17 +0900 (JST)
X-Received: by mail-qt0-f200.google.com with SMTP id g55so7766108qtc.8
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 07 May 2017 19:49:17 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=J6xzRv+gmyi8yI7Thw5D/YQlEsvwfrbhC1gBupOxxw0=;
b=an5I3JA1Brsm4GVQ3p+eDShUfJHs8sgviCALVR0o0UtPjCmUqzqOo85cBt2AT+fkmK
PPJyc5ifwppyFJsO2Xfw2+xSRdDdYg9sH/fTR2t60MoiRSWdLFNgDWi0j5H3yAGoODck
BUbd7ucc0BfQxwH6tesdQfsjkTmgMw9dcfgHni6lmnlyRKcTfQDhxqz9k76/1IDNvYTp
FHe69Iggxs9NF+gX15gcr2Z4m3bPLuKO3GN3mE5pAtfieEwwyAau39Ot3r2KExwZnqK0
6GM44l/JyToUlQ36EYAw4AtFgg0OqU7m58Jf3aSY9d2QP/ImRlBlMkDZvJ3vh3aSxOQt
e2iw==
X-Gm-Message-State: AODbwcBBhYgbq3ZLGs881/YCo/meeHaY9azkrcsD76rIpCI8xrlQ5UxQ
UqhWe5IzG0XgNhOOJJ6A2O0QnG6Qx5LYu+WS+W0fJcoOGMGXC7u/wCjNmtf4+ZmS9rQ59ogfBXb
6rLWLB1G+LDpY8VJH8B9AHzsLExbth8zokilsF2NxR+apdg==
X-Received: by 10.55.169.193 with SMTP id s184mr22417064qke.118.1494211755226;
Sun, 07 May 2017 19:49:15 -0700 (PDT)
X-Received: by 10.55.169.193 with SMTP id s184mr22417060qke.118.1494211755091;
Sun, 07 May 2017 19:49:15 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.12.137.38 with HTTP; Sun, 7 May 2017 19:48:54 -0700 (PDT)
From: Karl Johan Alm <karljohan-alm@garage.co.jp>
Date: Mon, 8 May 2017 11:48:54 +0900
Message-ID: <CALJw2w7CBFU-xFnar6p4k+84Umh5rsuaQ6UA1-8E2_N3_AOSpQ@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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 03:06:41 +0000
Subject: [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 02:59:09 -0000
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.
|
