
Beatoz Faucet
A testnet faucet delivered as a contract, API, and web interface. reCAPTCHA, Redis cooldowns, and queued transaction processing limit abuse and expose claim status.
A testnet faucet delivered as a contract, API, and web interface. reCAPTCHA, Redis cooldowns, and queued transaction processing limit abuse and expose claim status.
What made this system difficult?
Needed to throttle abuse and confirm on-chain transactions reliably under concurrent requests, while keeping claim status observable in the UI.
How did the design respond?
Implemented contract-side cooldown/blacklist rules, reCAPTCHA + Redis rate limit/cooldown, and Bull queue processors for claim execution with confirmation polling/retry. Shipped a claim UI with address validation and transaction status checks.
NestJSReactViteRadix UIBullRedisTailwind CSS
Overview
- Solo-built faucet service (contract + API + UI) for developer token distribution.
Key Components
- Contract-side abuse controls (cooldown/blacklist patterns)
- Backend async processing via Bull/Redis for broadcast + confirmation tracking
- reCAPTCHA + Redis rate limiting for request throttling
