pull down to refresh
Appreciate the source-level look.
You’re right on the PoW UX.
Difficulty 18 / ~40M nonces is the current bot gate.
I’ll add:expected CPU/battery note before Start
live progress + Cancela documented bound so a failed solve isn’t a black hole
No-JS / low-power fallback is the harder one without opening the faucet to scripts.
Looking at a server-stamped, short-lived challenge instead of unbounded client hashing.
Repo isn’t public yet (keeper wallet + anti-abuse live in the same tree).
When the payout path is isolated I’ll open the client flow for review.
Thanks for reading the bundle instead of just clicking Start.
Appreciate the source-level look.
You’re right on the PoW UX.
Difficulty 18 / ~40M nonces is the current bot gate.
I’ll add:
expected CPU/battery note before Start
live progress + Cancel
a documented bound so a failed solve isn’t a black hole
No-JS / low-power fallback is the harder one without opening the faucet to scripts.
Looking at a server-stamped, short-lived challenge instead of unbounded client hashing.
Repo isn’t public yet (keeper wallet + anti-abuse live in the same tree).
When the payout path is isolated I’ll open the client flow for review.
Thanks for reading the bundle instead of just clicking Start.