Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 47694B9E for ; Fri, 19 May 2017 04:09:57 +0000 (UTC) X-Greylist: from auto-whitelisted 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 68C361F6 for ; Fri, 19 May 2017 04:09:55 +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 1823614C0AD for ; Fri, 19 May 2017 13:09:53 +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; 19 May 2017 13:09:53 +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 0C3E84C084 for ; Fri, 19 May 2017 13:09:53 +0900 (JST) (envelope-from karljohan-alm@garage.co.jp) Received: from gw31.oz.hdemail.jp (ip-10-173-133-236.ap-northeast-1.compute.internal [10.173.133.236]) by mo.garage.hdemail.jp (hde-mf-postfix) with ESMTP id 0A0FF14C0AD for ; Fri, 19 May 2017 13:09:53 +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 gw31.oz.hdemail.jp (gw31.oz.hdemail.jp [127.0.0.1]) by gw31.oz.hdemail.jp (gw31.oz.hdemail.jp [127.0.0.1]); Fri, 19 May 2017 13:09:52 +0900 X-Received: from mail-qk0-f199.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 gw31.oz.hdemail.jp (Postfix) with ESMTP id 501C8148C11B for ; Fri, 19 May 2017 13:09:52 +0900 (JST) X-Received: by mail-qk0-f199.google.com with SMTP id u75so22840368qka.13 for ; Thu, 18 May 2017 21:09:52 -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:in-reply-to:references:from:date :message-id:subject:to; bh=bx9porWP8oOj0lbi/gMgSeb0G0e6+KlzSBZe/xTxxAI=; b=idnOWQFuiKOcSxrb6Rka7lxYkwjsp4aiz76+3t8F7fB9p7VffUf+VCabEhC+pfatzn LZH+3McpL45hV36187Y3qPsMrU/Q/8Mf+FYZRxQwrbbJqAVNuXWJnm+Ry2IEPnrRudhm 5yNpUVcoMlhA55Z7JG16/Avuxi3ILnbdwzPEd37c7VYtWTzhS/qQ5N0t+qnSweAkKIOq kJQkerrYSUQj5EZznw5vvyP7Nc29M4+MdT1UINXnpVWfEgC19A/YpimRkq/Kjy4hacpT E3gigDPjKPDaSuX16NaaXoQLDrsoeZ8oJyM1CQcAVRMFOvXRKbpPC6LXgTZ6euspgKAZ QwuQ== X-Gm-Message-State: AODbwcCo5rGecGgDyzi8p6/h3uV5KnVnB20yuZ/m3a0H289zOiDb6uSo h7cxg/UGdGY7TW/tVcqLrXiNKH++z1OBm+cZC1sG6c8OFqoIblGVP/HjcmNNv/u8O18iWlxfgmx z2WMOAlu9ACX/2bjYtjqXcOdcb3YC7rKSpglk9VXc3p79cw== X-Received: by 10.200.43.99 with SMTP id 32mr7298499qtv.6.1495166990301; Thu, 18 May 2017 21:09:50 -0700 (PDT) X-Received: by 10.200.43.99 with SMTP id 32mr7298488qtv.6.1495166990146; Thu, 18 May 2017 21:09:50 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.12.137.38 with HTTP; Thu, 18 May 2017 21:09:29 -0700 (PDT) In-Reply-To: References: From: Karl Johan Alm Date: Fri, 19 May 2017 13:09:29 +0900 Message-ID: To: Bitcoin Protocol Discussion 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: Fri, 19 May 2017 12:01:09 +0000 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 May 2017 04:09:57 -0000 Hello, Some time has passed since this was initially posted, and I have not received any negative feedback. If no objections are raised, I would like to have a BIP number assigned. On Mon, May 8, 2017 at 11:48 AM, Karl Johan Alm 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.