📅 Original date posted:2017-05-08
📝 Original message:Erik,
On Tue, May 9, 2017 at 3:58 AM, Erik Aronesty <erik at 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).
Karl Johan Alm [ARCHIVE] /
npub1e7…fg307
2023-06-07 18:00:54
in reply to nevent1q…tr33
Author Public Key
npub1e7vdq905zr4xjr5nxuz58l9jcvffxq728ysl6m2xxgr024mjy5vq4fg307Published at
2023-06-07 18:00:54Event JSON
{
"id": "f4e2395e412784d04f521b3f1a7beb6ee7efc26cbe19483a155d301d336a3d0d",
"pubkey": "cf98d015f410ea690e93370543fcb2c3129303ca3921fd6d463206f557722518",
"created_at": 1686160854,
"kind": 1,
"tags": [
[
"e",
"aa883b7af434afcd83d2ca86106a7476588c33a122eaeb098e1d3ae22ea02c7c",
"",
"root"
],
[
"e",
"a71a11fec654213dd5147959c2367196bf84f48fce3fdcb7c325caca80dee6f6",
"",
"reply"
],
[
"p",
"22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa"
]
],
"content": "📅 Original date posted:2017-05-08\n📝 Original message:Erik,\n\nOn Tue, May 9, 2017 at 3:58 AM, Erik Aronesty \u003cerik at q32.com\u003e wrote:\n\u003e - It would be cool if any rate-limiting POW was specified as bytecode ... so\n\u003e nodes can plug in as many \"machine-captcha\" things as they please, and\n\u003e solvers can choose to solve... or just say \"nope too hard\".\n\nI'm not entirely sure what you mean, but right now you can make an\narbitrary chain of challenges, and the BIP includes methods for\ndetermining an approximate time to solve (nodes will, at the very\nleast, discard any challenge which will on average take longer time to\nsolve than the expiration of the challenge itself, for example, i.e.\nthe \"nope too hard\" part).\n\n\u003e - Alternately, it would be a lot nicer if you just required people to pay a\n\u003e nanobit .... that could prevent DDOS even better, and generate a revenue\n\u003e stream for nodes.\n\nOthers mentioned this approach. I haven't given it much thought.\nAdmittedly it would be an effective way to prevent DoS but it also has\nsome unwanted side effects that need to be cleared up (e.g. in a\nno-gains scenario like the BIP proposes, the node requesting PoW done\ndoesn't *gain* anything from lying to the node performing the work).",
"sig": "0b02246f373b6bab180e6810c9271bdb64478224b69ff5c5d8d50edf56472d3634377cd2f7a9ceecbd2b0d8f31d7d14801ad2c154ae0d5294004463bf91309b7"
}