From: Karl Johan Alm <karljohan-alm@garage•co.jp>
To: Erik Aronesty <erik@q32•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Rate Limiting with server specified Proof of Work challenges
Date: Tue, 9 May 2017 10:15:25 +0900 [thread overview]
Message-ID: <CALJw2w6TBpWXMGQXYcGLevLdYzfFQA_YMAr4Rn3qkQt=DNvDEA@mail.gmail.com> (raw)
In-Reply-To: <CAJowKgJPZ=sQFXW631Czr7zYTX-ghg5ousjjkedJo-fXsefHvQ@mail.gmail.com>
Erik,
On Tue, May 9, 2017 at 3:58 AM, Erik Aronesty <erik@q32•com> wrote:
> - 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".
I'm not entirely sure what you mean, but right now you can make an
arbitrary chain of challenges, and the BIP includes methods for
determining an approximate time to solve (nodes will, at the very
least, discard any challenge which will on average take longer time to
solve than the expiration of the challenge itself, for example, i.e.
the "nope too hard" part).
> - 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.
Others mentioned this approach. I haven't given it much thought.
Admittedly it would be an effective way to prevent DoS but it also has
some unwanted side effects that need to be cleared up (e.g. in a
no-gains scenario like the BIP proposes, the node requesting PoW done
doesn't *gain* anything from lying to the node performing the work).
next prev parent reply other threads:[~2017-05-09 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 2:48 Karl Johan Alm
2017-05-08 18:58 ` Erik Aronesty
2017-05-09 1:15 ` Karl Johan Alm [this message]
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='CALJw2w6TBpWXMGQXYcGLevLdYzfFQA_YMAr4Rn3qkQt=DNvDEA@mail.gmail.com' \
--to=karljohan-alm@garage$(echo .)co.jp \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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