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
Erik,
On Tue, May 9, 2017 at 3:58 AM, Erik Aronesty 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 w
- 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 t
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) w