Topic: FaucetBOX.com Discussion - page 142. (Read 237001 times)

Hello,
I have suggestion for you.

How about banning from hostname? not IP address or IP range.

Example
This is hostname VPS list:
XXXXX.XXXXXX.compute.amazonaws.com
XXXXXX[Suspicious link removed]ltr.com
XXXXXXX.static.cloud-ips.com
XXXXXXX.members.linode.com
XXXXXXX.softlayer.com
etc

I don't care they are bots or real. Because advertiser not counting visitors from VPS IP.

https://2captcha.com/ Check This Out it`s like https://rucaptcha.com/

Minteye has shutdown I believe, according to a person in my faucet guide either way. Besides, I have heard reports from faucet owners that Minteye was very easy to bot, so I doubt it would have helped much.

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)...

Perhaps using a random timer (1-5 seconds), and only displaying the captcha and form once the timer has been completed could help. Granted, it could probably be bypassed by changing the Javascript or HTML DOM but it could possibly put things in their tracks for a short while. I would try to see how the API works and if there is a way around it, but I do not know Russian and all translation services fail to translate it.

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.

I can provide you with the full list of sites affected...

We're getting reports about iMacro scripts for abusing faucets (all kinds, not just Faucet in a Box, but also Microwallet's Microfaucet and Elbandi's Minifaucet). Does anyone have any details about that?

it seems that everything is good now, thanks

Can you check it now? If you still don't see it, please send me transaction id.

i think its a problem with deposits,because just I deposited some satoshi but do not appear transaction and in blockchain have more than 4 confirmations

it seems ok now...
thanks for your prompt work.

Other faucets seem to work correctly. Can you upload this to your server and send me a link to it: http://pastebin.com/raw.php?i=JzMjX3AX ? It will tell something more I hope.

we have "unknow problem" message after faucet claim.

I've worked around the problem so it should work for now, but it can stop working again for a couple minutes later today.

Looks like routing problems at our datacenter. Too early to say for sure.


No idea.

is it going to be a long maintenance or short one? thanks

why is down?

Working on it already.