From: Karl Johan Alm <karljohan-alm@garage.co.jp>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BIP Proposal: Rate Limiting with server specified Proof of Work challenges
Date: Mon, 8 May 2017 11:48:54 +0900 [thread overview]
Message-ID: <CALJw2w7CBFU-xFnar6p4k+84Umh5rsuaQ6UA1-8E2_N3_AOSpQ@mail.gmail.com> (raw)
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.
next reply other threads:[~2017-05-08 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 2:48 Karl Johan Alm [this message]
2017-05-08 18:58 ` [bitcoin-dev] BIP Proposal: Rate Limiting with server specified Proof of Work challenges Erik Aronesty
2017-05-09 1:15 ` Karl Johan Alm
2017-05-19 4:09 ` Karl Johan Alm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALJw2w7CBFU-xFnar6p4k+84Umh5rsuaQ6UA1-8E2_N3_AOSpQ@mail.gmail.com \
--to=karljohan-alm@garage.co.jp \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox