Topic: FaucetBOX.com Discussion - page 100. (Read 237020 times)

Kazuldur... I have a doubt.

When the NastyHosts check function indentifies a bad IP, the script calls the banned() function?

I'm not finding the code that calls NastyHosts and handle with the blacklisted IPs...

Your PHP version isn't up to date. You should consider upgrading before running any scripts on your server. If you're using hosting, you should be able to select the PHP version in your cPanel. If not, just contact your host and they will sort it out.

i got a problem with the script.im trying to open a faucet site but the script is always a problem to me.can anyone help me , what to do for this

I dunno exactly what hapened but our faucet got emptied quite fast yesterday.

P.S would be REALLY helpful if you could add an export function to the payouts page..:  easier to scan for suspicious activity in a xls file

friends,

I am experiencing some issues with USA visitors.

I'm needing help to test and solve a problem in my faucet.

If you are from USA and want to help me, please send me a PM.

No, that means that that's the only IP that can send coins or call the API. So that should be the IP of your faucet.


I don't believe that any of Terms of Services of other services allow this. It would be pretty much like stealing.


I'm open for suggestions. Problem is that GetIPIntel has really small limits (1k requests daily, while there are faucets with 20k users...) and minFraud is expensive. I don't know others. If there's a service you'd like to see in Faucet in a BOX script, just tell us which one.


Has someone tried that already? I think it would help, but at the same time I think real users would stop using it too... If someone is doing it successfully then I think we can implement that.


Bots that inject into browser can just call something like document.getElementsByTagName('form')[0].submit() and bots that don't use browsers don't click any buttons at all, they just scrap the captcha and then make HTTP requests on their own.

That's just like the "anti-bot links". It doesn't stop bots, it just annoys real users. Things like that works good when they're deployed manually by faucet owners. Call it an arms race. But when we implement that in stock script, then bots are really quick to workaround it. And whatever a real user can do, bot can do too, it's just a matter of implementing it.

Just a suggestion... The same way you are using NastyHosts to check the claimer IPs, there are other services like this doing the same work.

You could install some codes to check those services like Nastyhosts.

Would be great if instead to select just one service We could select 2 or three to work a the same time.

Other good feature would be the possibility to install two simaultaneous captchas.

Maybe turning the simple submit claim button in a slice/slider button would avoid some bots. Its simple to implement.

I do not understand very well the functioning of ACL, does it mean that only the IP in the list can receive satoshi from the faucet?

Hello, Login history page remains blank.

Guys, please check your faucets and make sure you keep your passwords safe and you have MFA, ACL and Login notifications enabled. Also check your antibot measures.

Many people reported being hacked recently

EDIT: We're working on some basic anti-fraud measures that should prevent at least most obvious hacks, like withdrawing all balance in one send. I hope we'll be able to deliver them soon.

FaucetBOX.com will be down for about 30 minutes at 20:00 UTC today (that's about 50 minutes from now).

EDIT: we're back up.

That's what I meant, thanks. I knew you calculated the payouts on a slight 'delay' - couldn't phrase my points properly, sorry.

Your English is fine Kaz

Yes very clear! Thanks for that and glad the migration went well!

I have no idea what cutoff are you talking about. We don't 'approve' anything and nothing changed in the way payouts are calculated.

However we've got a new server, which can calculate payouts much faster. I know that it was source of some confusion, as calculating the payouts could take even 12 hours and when the calculation has finished it already had obsolete data, so at the moment the transaction was actually sent not all coins were actually sent.

I think I've already explained that a few times in this and previous thread, but my English isn't very good, so in case previous paragraph isn't clear, here's what happens step by step:

1. you accumulate some coins, let's say 20k satoshi
2. FaucetBOX.com starts calculating payouts
3. you accumulate some more, let's say another 30k for a total of 50k satoshi
4. your /check page now shows 50k satoshi accumulated, 0 satoshi paid
5. FaucetBOX.com finished calculating payouts and it has data from the moment it started
6. a transaction for 20k satoshi is sent
7. your /check page now shows 30k satoshi accumulated, 20k satoshi paid
8. you wait another day till next payout and the 30k satoshi is paid out too.

Getting a new server allowed us to reduce the time between points 2. and 5., which leads to more robust payouts. Previously it was usually about 3-6 hours (except for a last week or two before the migration, when it could reach even 24 hours...), now it's around 2-3 hours.

Is everything clear now ?

Kaz have you altered the way payouts are calculated from Faucetbox? I.E. not using the 'cutoff' in your daily accounting checks.

I seem to have been getting much prompter payments - and also getting the full amounts that I can see in my Faucetbox instead of the amount you guys 'approve'.

No, FaucetBOX.com is not an exchange.


Thanks for the report, I confirm there's a bug. It'll take us a while to fix it though, sorry.


No, 2 confirmations aren't enough. 2 confirmations can easily be reverted. Just check how often 1-block forks happen: https://blockchain.info/orphaned-blocks. Here even forks as long as 4 and 3 blocks are mentioned: http://bitcoin.stackexchange.com/a/4638 .

EDIT: To clarify, I don't mean that 2 confirmations can easily be reverted on purpose. I mean that they can be reverted by accidental blockchain fork.

Kazuldur.

Would be great if you decrease the need of 4 confirmations for 2 r 3 confirmations.

De deposits would finish faster.

2 confirmations are a good proof of that a transaction is done.

Just Nastyhosts? No...

Nastyhosts don't block a lot a VPNs and Proxies.

Take a look in these two topics to learn how to avoid malicious traffic:

https://bitcointalksearch.org/topic/updated-19jul2016-faucet-owners-against-scammers-and-bots-1200700

https://bitcointalksearch.org/topic/stop-bots-proxies-from-using-your-faucet-1211353

Good luck!

I am from nepal so I have change my time zone to NPT but there you can see, time difference between my site and my computer is 1 hour.

You can change it on the Faucetbox site.

Cheers

Can I send from Faucetbox Bitcoin address to address of litecoin in the same Faucetbox?