Keep rewards worth the same in dollars as the coin moves
Store the reward in USD, convert at claim time, and clamp the movement so a price spike cannot empty the faucet in an afternoon.
13 entries
Store the reward in USD, convert at claim time, and clamp the movement so a price spike cannot empty the faucet in an afternoon.
Earn in integer credits, convert to coin only at withdrawal, and keep the rate in settings. Repricing the whole site becomes one field.
Production runs only while fuel lasts, and fuel comes from doing the thing you actually want done. Turns idle earning into a loop.
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.
Auto-pay when the API answers, hold when it does not, and never refund on a timeout. The three-state queue that keeps a faucet solvent.
An auto-submitting form POST with your own reference in the custom field — the field that makes the deposit traceable when it comes back.
One call that stops the worst failure mode on a faucet: telling a user they were paid when the wallet was already empty.
Pick a prize by weight, and compute the expected cost per claim before you launch instead of discovering it from your wallet balance.
Faucet software already knows how to talk to shortlink providers. Match the contract they expect and operators can point their existing config at you without writing anything.
Reward the claim and start the next cooldown in one transaction, so a double-submitted form pays once instead of twice.
If your ledger is in dollars and your payout API is in satoshi, this is the conversion, with the guard that stops a stale price from emptying your wallet.
The callback from FaucetPay's merchant checkout is not proof of payment. Here is the server-side verify call, including the endpoint shape that quietly 404s if you get it wrong.
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.