Search content
Sort by
Showing 20 of 48 results by christmas
Re: CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available
I'm responsive to emails from borrowers, in fact I've just agreed to 2 loan modifications (Projects & user not on bitcointalk) and these should be repaid soon.
Quick note: Legal threats will not result in getting repaid faster, however if you would like to propose an alternate arrangement / settlement for your CL balance email me - I will agree if I believe this will benefit other CL creditors.
Quick note: Legal threats will not result in getting repaid faster, however if you would like to propose an alternate arrangement / settlement for your CL balance email me - I will agree if I believe this will benefit other CL creditors.
We ALL want to avoid legal action, but the lack of transparency is very troubling. Better communication and a spreadsheet of assets/liabilities like Namworld has for BTC-BOND would go a long way. We know your situation is bad, but if we had more info we could help. DumbFruit settled which I'm sure removed a large liability and several have offered interest free loans.
Idea: Give a 30 day window for CL users to log in and set up a payment address. Then, every Wednesday after Asicminer (or other investments) pays dividends, pay out to the addresses on file and decrement the amount from the CL balanace. That would give users an idea of the rate we gets paid back without diclosing all your investments. We would also feel much better about seeing something being returned. Also, send out an E-Mail letting users know this and anyone who doesn't provide a payment address in the allotted timeframe forfeits repayments until they do.
+1
CL要將錢Liquidate都要時間，TF手上持有大量ASICMINER，還要是Direct的。如果他能找到人去收購這些ASICMINER就能賠款了。CL始終包涵大量不同借款和資產，流動性比較低。一下子要拿錢出來，除了JustDice這些投資以外都沒那些。
耐心等候他的電郵吧。你多多抱怨都沒用，結局已定。除非你希望FBI那些流氓能夠找到TF,把它的錢跟資產都挾持吧，到那時CL就真是分毫都沒得賠。
确实，现在只能耐心等了，有些事也只能顺其自然了。耐心等候他的電郵吧。你多多抱怨都沒用，結局已定。除非你希望FBI那些流氓能夠找到TF,把它的錢跟資產都挾持吧，到那時CL就真是分毫都沒得賠。
+1 等。。。
Re: Inputs.io | Instant Payments, Offchain API, Secure Wallet, 235k+ BTC transferred
Just got an e-mail back, quote :
"Because the hack occurred neraly 2 weeks ago and the public announcement was only made now?"
This makes no sense, why did TF let people use a COMPROMISED wallet for two more weeks?
"Because the hack occurred neraly 2 weeks ago and the public announcement was only made now?"
This makes no sense, why did TF let people use a COMPROMISED wallet for two more weeks?
Why its now public and not before 2 weeks?
Since Boelens have decided to only selectively pick responses, after the 4K btc compromise I cloned the disk image as soon as I could (after disbelieving and in horrendous shock), investigated the scope of the breach, regenerated all credentials, and have been exploring any options that allows Inputs users to not lose any money.
You let users send good money after bad. You continued to take deposits and didn't come clean. You should of shut the site down while you "investigated". Anyone who has deposited ANYTHING for the past 2 weeks should be 100 percent refunded.
I think so !
Re: CoinLenders Script :: Bitcoin Bank (Borrow+Deposit) Software :: Demo Available
If 4100 BTC were stolen, which address were they sent to?
Publish the blockchain info for the stolen coins, otherwise it's safe to assume there were no stolen coins.
Publish the blockchain info for the stolen coins, otherwise it's safe to assume there were no stolen coins.
Here you go.
http://blockchain.info/tx/9536feebe3a50b94f85ca27d56e669a7209bd4188385d55c5b97227c95cf7f74
The stolen coins are still unspent in https://blockchain.info/address/1EMztWbGCBBrUAHquVeNjWpJKcB8gBzAFx
it's happened 2 weeks ago !!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Two hacks totalling about 4100 BTC have left Inputs.io unable to pay all user balances. The attacker compromised the hosting account through compromising email accounts (some very old, and without phone numbers attached, so it was easy to reset). The attacker was able to bypass 2FA due to a flaw on the server host side.
Database access was also obtained, however passwords are securely stored and are hashed on the client. Bitcoin backend code were transferred to 10;15Hd@mastersearching.com:mercedes49@69.85.88.31 (most likely another compromised server).
What about my coins there? If you stored more than 1 BTC, send an email to support@inputs.io with a Bitcoin address (preferably, an offline, open source light/SPV wallet like Multibit or Electrum). Use the same email you're using on Inputs. Please don't store Bitcoins on an internet connected device, regardless of it is your own or a service's.
I know this doesn't mean much, but I'm sorry, and saying that I'm very sad that this happened is an understatement.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJSeuZ9AAoJEB7FawRj3T8Th5QH/iapt2DUuyy1j7t51y1N1LOk
+Gu5fdIAV8molXnv+InMQvxtfxWfc7zKiROSP6Zv1cXdvMrCyzKP+SnTEFshIa+0
j2FYOgLeMNmsPSw8yeR1O8vJieYlK+7imEZL4nRKA+O+mjqCT1nTCtBUAVcYQ8Uu
O6BoNLkgT8z/1ZTfw+OK4t2kw9KcC317JOv3yVugfA3xCn4HbKPRP2yFIKR49C7L
w7C2h3L1jHqLerQNjbowcyKH83BFJ2IB0cFZFFCLBI+8NQcUIcIFymxrxUV73Rqa
xlMPX2rPFcIj6yz0ABl1t2rwY2DGOvc33MYCzX82CumLx/qAXCd2uF/jG6fzQ5M=
=Ip/9
-----END PGP SIGNATURE-----
inputs.io上的，不过有人说这个PGP 签名不是TF的，不是2E67C3DF，不知道真假了
Hash: SHA1
Two hacks totalling about 4100 BTC have left Inputs.io unable to pay all user balances. The attacker compromised the hosting account through compromising email accounts (some very old, and without phone numbers attached, so it was easy to reset). The attacker was able to bypass 2FA due to a flaw on the server host side.
Database access was also obtained, however passwords are securely stored and are hashed on the client. Bitcoin backend code were transferred to 10;15Hd@mastersearching.com:mercedes49@69.85.88.31 (most likely another compromised server).
What about my coins there? If you stored more than 1 BTC, send an email to support@inputs.io with a Bitcoin address (preferably, an offline, open source light/SPV wallet like Multibit or Electrum). Use the same email you're using on Inputs. Please don't store Bitcoins on an internet connected device, regardless of it is your own or a service's.
I know this doesn't mean much, but I'm sorry, and saying that I'm very sad that this happened is an understatement.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEcBAEBAgAGBQJSeuZ9AAoJEB7FawRj3T8Th5QH/iapt2DUuyy1j7t51y1N1LOk
+Gu5fdIAV8molXnv+InMQvxtfxWfc7zKiROSP6Zv1cXdvMrCyzKP+SnTEFshIa+0
j2FYOgLeMNmsPSw8yeR1O8vJieYlK+7imEZL4nRKA+O+mjqCT1nTCtBUAVcYQ8Uu
O6BoNLkgT8z/1ZTfw+OK4t2kw9KcC317JOv3yVugfA3xCn4HbKPRP2yFIKR49C7L
w7C2h3L1jHqLerQNjbowcyKH83BFJ2IB0cFZFFCLBI+8NQcUIcIFymxrxUV73Rqa
xlMPX2rPFcIj6yz0ABl1t2rwY2DGOvc33MYCzX82CumLx/qAXCd2uF/jG6fzQ5M=
=Ip/9
-----END PGP SIGNATURE-----
inputs.io上的，不过有人说这个PGP 签名不是TF的，不是2E67C3DF，不知道真假了