pull down to refresh
Im actually the real creator of the faucet ill soon drop it on github in the upcomming weeks
but i appreciate someone posting about it on here while i work hard on the actual project lol
My faucet have built in safeguards that make draining it tedious and not worth it for example a dynamic payout system and is also protected by cloudflare
- You just paste your lightning adress in the field and press pour and it immediately gives you a chance at the jackpot. The sats arrive immediately
2.there is no lottery. You have 2% chance of hitting the jackpot every day when you click pour and reiceve your free sats
3.That is so that the community can refill the fountain at anytime when the keeper is not available. Plus the more donations the bigger payouts and bigger jackpots but the chance stay the same. There is zero requirement to pay anything
Everyone have heard about the famous btc faucet from 2012 well its back but more modern thanks to lightning integration. Its still really early but i would love everyone's feedback both good and bad. In the future I hope it could be self sustainable. I dont care about profits. I just wanted a faucet that didnt steal my email or needed passwords, and a clean ui without ads. Apparently that didnt exist so I made my own. I will be posting the source code on github aswell soon enough
Just enter your lightning adress and immediately receive btc. Zero ads Zero Tracking Zero Bullshit
Update:V1.1 is now live.
-payouts scale with the pot, bigger pot bigger payouts
-A donation button to people who want the fountain to remain flowing, grants no boosted jackpot odds and no more daily pours than usual 1.
-added a terms of service,FAQ and policy tab at the bottom .
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.