Due to recent events regarding Mt.Gox and Bitcoin attack.
I have checked technical bit of it and figured that the issue is only with non-confirmed/pending transactions when being resent. Luckily for us all, LeaseRig.net does not perform any kind of resends, so it is not possible for anyone to issue such attack on LeaseRig.net.
Additionally to that, I must say that 6 confirmations are needed for all deposits, so the paying out BTC is 100% validated and correct.
I have been noticing that there have been odd working in BTC network for past few days - some transactions were sent with 0 fee, some took half a day or even whole day to complete.
I received 0 reports of any provider not being paid and I received 0 reports of any customers missing funds. By this statistics I can say that
LeaseRig.net is operating unaffected by the reported issue.
This post is somewhat most understandable to all and also explains you why LeaseRig.net is not affected:
The flaw isn't so much in Bitcoin as it is in exchange-systems. Many exchanges use the tx-id to uniquely identify transactions, but as it turns out, an attacker can change the tx-id without changing the actual transaction, rebroadcast the changed transaction (effectively creating a double-spend) and if his altered transaction gets accepted into a block instead of the legit transaction, the attacker receives his coins and can complain with the exchange that he didn't. The exchange will then check their db, fetch the tx-id from it, look it up in the blockchain and not find it. So they could conclude that the transaction indeed failed and credit the account with the coins.
A simple workaround is to not use the tx-id to identify transactions on the exchange side, but the set of (amount, address, timestamp) instead. If a user complains about not receiving their withdrawal, support can look it up using these 3 variables. It takes a little bit more work from support, but it prevents this attack from succeeding.
While it'd be nice if the tx-id isn't malleable, blaming this problem on a flaw in the protocol is quite a stretch.
LeaseRig.net does no saving of TXID into database. If there was an error with no payment being sent, then these would be solved manually. But a big exchange cannot afford to solve such issues manually thus having automated system for resolving them.