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.
This sucks. I want this test/attack to be over with.
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?
I myself wouldn't trust referer headers as they could be fabricated.
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.