Re: Bitcoin Faucet changes

So I’ve been watching the IP addresses of people getting 5 free bitcoins from the Bitcoin Faucet ( ).

And I see some… uh, interesting patterns. Like these successful requests for coins: - - [21/Jun/2010:12:17:02 -0700] "POST / HTTP/1.1" 200 1234 - - [21/Jun/2010:12:16:24 -0700] "POST / HTTP/1.1" 200 1234 - - [21/Jun/2010:12:10:23 -0700] "POST / HTTP/1.1" 200 1234 - - [21/Jun/2010:12:08:50 -0700] "POST / HTTP/1.1" 200 1234 - - [21/Jun/2010:12:08:07 -0700] "POST / HTTP/1.1" 200 1234

My apologies if there actually are a bunch of new bitcoin users using IP addresses in the 79.117 range… but I’m guessing somebody there is getting more than their fair share of free bitcoins.

There are several suspicious requests from the 192.38.95.* address block, too.

So I’ve made some changes to the Faucet. You won’t notice them unless you try to cheat; if you do try to cheat, you’ll have to solve a CAPTCHA to get coins.

If that doesn’t discourage cheating, I’ll modify the code so that if it think you’re trying to cheat it requires a CAPTCHA and only gives out a bitcoin nickel (0.05 bitcoins)…

Many big ISPs give you a new IP every time you connect, usually in the same class B (a.b.?.?).  Maybe you should have a minimum time between payments per class-B.

If you can’t solve the problem, you can always keep lowering the amount of bitcoins given until it’s manageable, and always require captcha.

25,227 total views, 5 views today