Which version of the script and what captcha are you using?

If a real user knows which captcha is being used then a bot can know that too.


There were no recent payouts from your faucet in our system. Make sure that your faucet is working and is actually paying out before submitting it to the list. Also make sure you're using correct API key.

It's the same story: just a couple lines of code are needed to autodetect that in bot.

Only with dumb bots that look for this field specifically. It can by bypassed with just a few lines of code. So technically it'll help, but don't expect wonders.

To everyone with captcha issues on Faucetinabox r54: make sure that you updated the <input> tag from something like this:
to this:

In other words: make sure that the name of the field is and not simply .

Okay, I'll try to reproduce that. Thanks for report.

Well... as they say, there are 2 types of people. Those who do backups and those who will do backups.
That said I've just tested it. I could type "12." just fine, nothing was reset. And to be honest there's no way it could do that...
Did you save your form by clicking the "Save changes" button with your mouse or did you just click the Enter key on keyboard?

I don't see how could that happen. Did you save it before at least once? Maybe saving doesn't work at all? There are some problems with saving on some hostings that we still haven't debugged.

You can see the changelog in your current faucet's admin panel. We've added FunCaptcha in r54. It should be immune to bots that use Rucaptcha.com and similar services, you should try it .

Remember to make a backup of your current faucet before updating.

Next versions of Faucet in a BOX script will probably include support for new captcha and some antibot measures. I've added these suggestions to our bug tracker. I think that there's a good chance we'll implement the timer and adblock detector in version after new captchas, I'm not so sure about the popup, but I have to talk with other guys about that

To everyone affected by bot issues: can you test this version of Faucet in a Box script: https://static.faucetinabox.com/download/faucetinabox-antibot-alpha.zip ? Disclaimer: it's not really tested in the field by us yet. It may break your faucet, stop paying out to anybody, pay only to some or eat your cookies. You've been warned.

That said I'll really appreciate a feedback on whether it helps at all with the bot issues. I'm also a little bit worried about the performance, so if you see significant slowdowns please share it with me too.




Make sure that you've set the Rewards on your faucet correctly. Fractions aren't allowed (except for DOGE).


Just as it was said. You can see all our Bitcoin transactions here: https://faucetbox.com/stats/withdrawals/BTC . We do pay fees, but we also send ~500 outputs in single transaction (that's also why we don't payout immediately, but after up to 48 hours), so the cost per address is significantly lower. Even then we don't pay it from our pocket. We take 2.5% fee from faucet owners when they deposit coins to their faucets and use that to pay fees.


I've sent you a follow-up on email.

Unfortunately I believe that wouldn't help either. The bot uses iMacros, which means that it doesn't inject any Javascript into the page. It injects a driver into the browser itself (just like Selenium if you're familiar with it). It's undetectable by any valuable means.

We can, but that won't help. Captcha solving services work like that:

1. bot opens the page and makes a screenshot of the captcha
2. screenshot is sent to people that sits all day solving captchas
3. they read the captcha and sends the answer (so it doesn't matter what's there as long as they can just read it and provide the answer)
4. bot enters the aswer

So the bot could just send the math problem and get a response, just like with other captchas.


Microfaucet ( http://www.freebitcoinfaucet.org/ ) works just fine after migration ( https://faucetbox.com/microwallet-migration ).

Still working on it. We must make sure it won't decrease performance too much and that it won't hit legitimate users.

I'm not responsible for support and approving faucets anymore, I'll ask my coworker about that.

However I see that you have the "claim" button overlayed over AdSense ad. While I'd accept such faucet to our list, you'll get banned by Google AdSense sooner or later, as it's against their Terms of Service.

It was already explained in this or previous thread. Transaction with more than 200 outputs is completely fine (all faucetbox.com transactions were so big since the beginning), it's just Blockchain.info that doesn't display them until they're confirmed. Now the problem is that they're not getting confirmed, but here the problem is that Bitcoin network is often under attack lately and there's huge backlog of unconfirmed, spammy transactions.
Such delays already happened once (27 June I believe) and transactions from that day got confirmed after ~3 days.
You can see current backlog here: https://tradeblock.com/blockchain . On the right under "Mempool" graph there's "Transactions: 33,935". ~34000 unconfirmed transactions is a huge number and it's causing problems.
We do use the estimatefee feature that automatically increases the fee (and it actually did that), but it reacts too slow sometimes.

So I'm really sorry for inconvenience. I assure you that it will get through eventually.

EDIT: I think that actually all FaucetBOX.com transactions are confirmed now. Can you confirm that?

Reverse DNS queries can be slow (I remember having problems with timeouts on faucets because of that), but we'll investigate that, thanks

Does any of the affected faucets use Are you a Human captcha? Looks like Rucaptcha doesn't support it.

EDIT: we'll also try experimenting with minteye.com captcha, but for now I can't even register on it (it timeouts)...

We've released a new release of Faucet in a BOX script: http://faucetinabox.com/static/download/v1/faucetinabox-r52.zip . It makes name of the address field random, which will break simple bots. It's just a minor change, changing a bot to detect that won't take more than 10 minutes, but it's something

Thanks for the PDF you've sent us through email with FAQ of the bot. So the problem is that https://rucaptcha.com/ became cheap enough to use to abuse faucets. With about $0.50 per 1000 solves it means that it's profitable for the abusers if a single normal payout + referral payout is more than ~170 satoshi (if I done the math right).

We're brainstorming about solutions right now, but it'll be tough to solve, especially if we don't want to hit legitimate users. The reasons are:

1. we can't block IP addresses, because they're using on-demand VPS services, which means that they can get a new IP address in 30 seconds. It also means that simply blocking by country won't work. What's more, FaucetBOX.com API doesn't know users' IP addresses (by design), so that would have to be done on faucet end.
2. we can't block bitcoin addresses, as creating a new one would take one second.
3. we can't try to identify whether a real browser is used or not, because this bot is using a real browser.
4. we don't want to require a registration and verification from users (which would make banning them possible). It was and is our main feature that faucet users don't have to visit FaucetBOX.com or even know about it to receive their coins. It's what allowed FaucetBOX.com and faucets based on it to grow.
5. there's nothing else we can use to identify users.

So things I can recommend to you right now if you're concerned about this issue is:

1. make your faucet as unique as possible (not just graphically, but for example by making a minigames). It's easy to abuse faucets if every one of them works almost the same way. No one will bother to write a bot just for your unique faucet.
2. lower your rewards, so that a single average reward + referral percent is lower than ~150 satoshi. You can offset that by lowering your timer too. That way abusers will pay more for solving the captcha then they're getting from you.
3. use unpopular captchas. I think that Rucaptcha works for reCaptcha and Solve Media, but I'm yet to confirm that.