No, for many reasons that were already pointed out in previous thread.

1. we can't just send individual transactions because of the network fees. We send bulk transactions to ~500 addresses and it takes time to gather enough of them.
2. calculation takes time. We have hundreds of thousands small payouts daily and we validate all of them during withdrawals. It sometimes takes even hours.
3. our wallets are encrypted and passwords aren't saved anywhere, so we must confirm each withdrawal manually.

When did you lower it? Because if you lowered it less than 48 h ago then you have to count from that point...

I can't cancel, transactions are already being calculated. It will be sent to the address.

New transactions are still calculating, so it may be a little late. However it's weird that you didn't get payout yesterday. Have you changed your threshold in last 48 hours?

48 hours didn't pass yet here.


You've 545000 satoshi accumulated. If you sum up payouts from the top you'll that you've reached the threshold with this payout:

100000 satoshi - 2015-07-10 20:52:21 CEST   

It's 19:56 CEST now, so again: 48 hours didn't pass yet.


We're processing transactions right now, be patient.

Follow these instructions: https://faucetbox.com/faq#missing_payment

If they never programmed before they would need a couple of days just to understand the basics.

That looks like a decent tutorial: http://www.dwuser.com/education/content/quick-tip-adding-a-favicon-to-your-website/

Standard script doesn't have such a feature. I believe that Minifaucet does: https://bitcointalk.org/index.php?topic=333748.0 . However read past few pages of this thread first, as this script probably has security issues.

Looks like we're under a relatively small (D)DoS attack. I'm working on mitigating it.

EDIT: it should be better now.

You can always try just hardcoding it in the template file, bypassing the admin panel.

I have no idea how did you setup your server. However in most cases it's too restrictive configuration of modsecurity. Do you use it?

It's a XSS protection of your hosting. It probably blocks all POST requests with <script> and <iframe> tags. Contact your hosting about that.

They got confirmed. Finally .

It's easiest to use another site to get your account accepted and then simply embed ads on your faucet too. You only need to get one site approved and then you can use AdSense on all of them (if they don't break the ToS of course);

Take this transaction as an example:
https://btc.blockr.io/tx/info/03d6e645fba49e07f3a4d8f173dce3ae590a5e0b06f28b367e29d7e64926019d
has 0.00339447 BTC fee for 15164 bytes, and it's almost 6% of what was actually transfered to users (0.05664565 BTC).
So the fee is ~0.0002260 BTC/kB

Another one is:
https://blockchain.info/tx/1d8e35cbcad0c7814fde8c0e775259107e5adc32900263d9cc1358626a0ecb0b
0.0052392 BTC fee for 17561 bytes, so it's ~0.00030819 BTC/kB

Now example that didn't get through:
https://www.biteasy.com/blockchain/transactions/e9ee41881cb7d38308ac80bb204b55da3877d7b64084872b7d78a4fc9aa9747e
0.00194831 BTC fee for 17426 bytes, so it's ~0.00011460 BTC/kB.

What matters is the fee/kB and you can see that we increased fees ~2-3x.


We continuously rebroadcast it. We would rather avoid reverting it though, as it could get messy. What's more plausible is that we'll just send double-spends with increased fees. Does anyone know a tool that'll make that easier? I don't want to mess around with raw transactions by hand

I believe that's not related, it was happening since the beginning of FaucetBOX.com (only that earlier Blockchain.info simply showed 'Transaction not found' message) and it looks like it's Blockchain.info's not-standard behavior. Other nodes relay our transactions just fine, while Blockchain.info only acknowledges our transactions after they're included in block.

It was already mentioned in this thread. It's because of the spam attack on Bitcoin network: https://www.reddit.com/r/Bitcoin/comments/3cfext/bitcoin_under_attack/ . It should get confirmed as soon as the number of unconfirmed transactions drops to something sane: https://blockchain.info/unconfirmed-transactions .

If you control someone's browser, why bother with CSRF? You can just attack directly . HTTPS isn't a problem, referrer will be correct on the site itself and possibly not set/empty when coming from other sites (then one just assumes it's invalid). If someone's browser doesn't send headers, too bad. It's not perfect solution, it's just easiest. You should generate a token, save it in session, add it as hidden input in form and compare it on request. But that require more changes, while referrer check will be sufficient for most.

Still no P2SH for Litecoin yet. No ETA either.

It's more because of the new floating fees than the stress test, which I think is long gone now.

EDIT: I know see that it's happening again: https://www.reddit.com/r/Bitcoin/comments/3ck5z9/80000_unconfirmed_transactions_right_now/ . Also here: https://bitcoinfees.github.io/#3h . Does anyone knows anything more about it?


While I didn't trust them too for FaucetBOX.com, how could they be fabricated in context of CSRF? If I were to attack you using CSRF I wouldn't be able to force your browser to fake the referrer.

We are experiencing issues with transaction confirmations due to the recent change in Bitcoin network fees. We're working on it, but transactions can take a long time to confirm for now.