A provably fair draw anyone can verify
Commit to a server seed before the draw, publish it after, and let any user reproduce the result themselves. The scheme, and the mistake that makes it worthless.
Reference library · 94 entries · 10 free tools
Payouts, cooldowns, reward tables, captcha checks, ledger maths, popunders, postbacks. The pieces every faucet and crypto micro-economy site needs, written out properly instead of half-answered on a forum. No signup, no timer, no shortlink between you and the code.
Commit to a server seed before the draw, publish it after, and let any user reproduce the result themselves. The scheme, and the mistake that makes it worthless.
Earn while away, but only up to a ceiling — computed on read from a timestamp, so there is no cron and no per-user tick.
Debit on request, not on approval. The state machine that makes double payouts and phantom balances impossible.
The swap technique, plus the one line that stops the visitor's own click from cancelling it — the reason most popunder code silently loses the traffic it was supposed to send.
Reward the claim and start the next cooldown in one transaction, so a double-submitted form pays once instead of twice.
A minimal, correct call to FaucetPay's /api/v1/send endpoint, including the part almost everyone gets wrong: the amount is in the coin's smallest unit, not USD.
Convert between satoshi, whole coins and USD for any coin, with the unit counts faucet APIs actually expect.
Put in your traffic, claim rate and payout, and see whether the ad revenue covers what you are paying out.
Set the prize tiers and weights, see the odds, the expected cost per claim and what the jackpot really costs you.
Work backwards from a daily budget to a cooldown and reward that your faucet can actually sustain.
Check a wallet address before you pay it: base58check, bech32 and EIP-55 checksums for the coins faucets use.
Paste a crontab line and get it in plain English, with the next few times it will actually run.
Snapshot the standings, pay from the snapshot, mark the contest closed — all in one transaction, with the entry rules decided before it opens.
Rate limited, length capped, link stripped, moderatable, and cheap to poll. The five constraints that keep a chat box usable.
Generate the day's tasks once, track progress against a date key, and pay the completion bonus exactly once — no midnight cron required.
A table of conditions, a checker that runs after activity, and a unique key so an achievement can only be awarded once.
Commit to a server seed before the draw, publish it after, and let any user reproduce the result themselves. The scheme, and the mistake that makes it worthless.
GeoIP at the edge or in PHP, applied to earning and signup rather than to content, with a message that says what happened.
Export as JSON, delete as anonymise-and-keep-the-ledger — because financial records have to survive a deletion request.
No third-party consent script. A dismissible banner, a stored choice, and ad code that only loads once consent exists.