š
Original date posted:2017-05-08
š Original message:- 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 .... that could prevent DDOS even better, and generate a revenue
stream for nodes.
On Sun, May 7, 2017 at 10:48 PM, Karl Johan Alm via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> 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.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170508/81601374/attachment.html>;
Erik Aronesty [ARCHIVE] /
npub1y2ā¦5taj0
2023-06-07 18:00:54
in reply to nevent1qā¦m9wz
Author Public Key
npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0Seen on
wss://relay.noswhere.comPublished at
2023-06-07 18:00:54Event JSON
{
"id": "a71a11fec654213dd5147959c2367196bf84f48fce3fdcb7c325caca80dee6f6",
"pubkey": "22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa",
"created_at": 1686160854,
"kind": 1,
"tags": [
[
"e",
"aa883b7af434afcd83d2ca86106a7476588c33a122eaeb098e1d3ae22ea02c7c",
"",
"root"
],
[
"e",
"59431c8a9f90a201a09870fc82eba13a87c1d32a5e5ae17c062a9ac9b301480e",
"",
"reply"
],
[
"p",
"cf98d015f410ea690e93370543fcb2c3129303ca3921fd6d463206f557722518"
]
],
"content": "š
Original date posted:2017-05-08\nš Original message:- It would be cool if any rate-limiting POW was specified as bytecode ...\nso nodes can plug in as many \"machine-captcha\" things as they please, and\nsolvers can choose to solve... or just say \"nope too hard\".\n\n- Alternately, it would be a lot nicer if you just required people to pay a\nnanobit .... that could prevent DDOS even better, and generate a revenue\nstream for nodes.\n\n\nOn Sun, May 7, 2017 at 10:48 PM, Karl Johan Alm via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Hello,\n\u003e\n\u003e I am proposing a new feature for rate limiting purposes where nodes\n\u003e can make and solve arbitrary PoW challenges in return for connection\n\u003e slots (to be expanded to cover e.g. bloom filters or other DoS risky\n\u003e services).\n\u003e\n\u003e The BIP currently includes two proofs of work (sha256 and\n\u003e cuckoo-cycle) which can be combined (e.g. sha256(cuckoo-cycle) or\n\u003e sha256(sha256(sha256)), etc).\n\u003e\n\u003e Link: https://github.com/kallewoof/bips/blob/pow-connection-\n\u003e slots/bip-rate-limiting-via-pow.mediawiki\n\u003e\n\u003e Feedback welcome.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170508/81601374/attachment.html\u003e",
"sig": "c9781f66188f79bed3ed847cf5ea594c90c3beecf863da95620ea9678b15c9e5c07928a0d3c3495e2474e1e252b28dd6708c92dd71b364838b665abb1225468e"
}