-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
This is MrData from CoinPayments.net confirming we will be providing escrow service for the TriForce ICO. This message is PGP signed and you can get our key at https://www.coinpayments.net/help-signed-emails
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJZ4hyiAAoJEHybuLdy8L+gSBMIALhhlmXR0R55hUMaGRQwS5cQ
A8K28DXcUDQhnG3YPMHW6j7hJacWJe9T2XBwEFDNRbwC0LYHFGLLY+IfaisZNDib
TRB7gA/YJPVRanLxw3EkXsDkQYdfFCPaQrjadkKwnerVvu7+G9FBFWvpl9UYpcmt
J5+UHyA22QCvZW/g4NUxaQyVYxdkkBEtiu9ijuD0jJes+uimSNTehuTIqAjwPfks
2xk6prBGzZYI61dMHSXIBwviDVc72jXxDyyp9QbW565w2GN9+PbNjrGnu1ftXWFO
B2OoRzK39bbarh1LTf5DPylxQFHGq+xXBHasAj5mDEW5G1HBecAn4o3jyslZ5L4=
=871p
-----END PGP SIGNATURE----- |
|
|
|
|
Yes, that seller received 2 scam complaints today and their account and domain were banned from CoinPayments.net.
|
|
|
|
|
If the support bot's answer doesn't help you you can just reply to reopen the ticket... however it is correct 99% of the time.
Make sure you read your emails you can see they are for 2 different payments, one that completed and one you didn't send funds for.
|
|
|
|
I recently send money to coinpayment (March 01) , from my cryptonator wallet , I had made 2 prior successful trans. of course as many of you use coinpayment to buy AdPacks , I had a confirmation of money sent from cryptonator to coinpayment ,
the transaction says timeOut / expired from coinpayment side , from cryptonator shows funds were sent successfully . I did get an email shortly from CoinPayment about notice of timeOut , and they stated we will send you a link to claim to those funds within 8 hours , so far never received that fuckin link, I contacted coinPayment and never had a reply from them, guess I will never see my $10 payment , how do funds get lost ? no one can send money to a non-existing bitcoin address , so obviously they received it , someone has figured out how to take advantage of the system . Scammers!
You haven't contacted us or you would have received a response, also note that all support is via our support ticket system so if you sent to a random email address or something else we wouldn't have seen it. You can find support at https://www.coinpayments.net/help-supportAlso note that if your Bitcoin TX doesn't have any confirms the time doesn't start until AFTER it gets confirms. |
|
|
|
|
Yes, we have always had the option to send your funds to any address you specify instead of to the CoinPayments Wallet.
|
|
|
|
just an update, coinpayments.net has made no effort to return the stolen btc ... they continue to operate as a selective SCAM SCAM SCAM. I would not trust coinpayments.net with more than 1 btc!
There is no way to reverse a Bitcoin transaction, since the withdrawals were made with legitimate API keys and are confirmed in the blockchain there is no way to get those funds back. We have been in communication with the actual account holder and gave them detailed instructions on how to report the theft to the authorities and improve their website and account security going forward. |
|
|
|
|
This is MrData from CoinPayments Support.
650 BTC, while a nice chunk of BTC, is not enough to destroy our reputation over. I told the account owner in their support ticket that they need to do a full security audit of the server, preserve all logs, etc., and report it to the appropriate authorities. We will be happy to provide the API and HTTP logs from our end showing the API requests that withdrew the funds to them as well. If the account owner gives us their permission in the support ticket we can post it publicly as well.
Time matters in these situations and I would highly recommend getting the evidence together and reporting it to the FBI cyber crimes division or your local authority ASAP versus blaming us for it. You have also made the addresses public so maybe someone in the community can help track the funds?
|
|
|
|
|
What are the details for the coin swap from the old to new chain?
|
|
|
|
Is there a tutorial how to add it in whmcs to accept payments?
If you download the plugin there are directions in the zip file (install.txt) |
|
|
|
|
You sent the info literally (and I do mean literally) 4 minutes ago, it takes longer than that to check it out.
Every company is going to have some bad merchants, we ban all HYIPs and investment scams as they get reported to us.
Update for the record: All of the addresses he provided are for payments that completed successfully. None of them are timed out/cancelled/refunds due except for the same one I mentioned in my 1st reply that he already got the refund for.
|
|
|
|
|
Hi,
This is MrData from CoinPayments Support. He has provided several of our internal payment IDs which I personally checked and none had received funds except for one that he has already received a refund for.
I've asked him 3 times to provide the address(es) he sent the coins to so I can check that way in case he had the wrong payment IDs but so far he hasn't provided them. One red flag I see in his post is that he says he sent them all to the same address but we use a unique address for every payment so that makes me wonder what is going on.
|
|
|
|
what happen to coinpayment.nets....the web is shutting down..scam???
Of course it's not a scam, we've been active since 2013. Our host was just DDoS'ed earlier, the site is back up now. |
|
|
|
|
To answer your questions:
1) The judges are staff members we trust, we have known and worked with all the judges since 2013.
2) pr0d1gy and I are the original founders of CoinPayments.net and still work there for the current owners. We haven't run with that money.
3) The coins are stored on separate servers from the website. If we end up with a substantial amount stored we'll also implement cold storage.
Thanks
|
|
|
|
|
If you unlock your wallet for staking only then you will get your PoS rewards but nobody who comes across your computer could send themselves all your coins since the sending functions are still locked.
|
|
|
|
That's nothing to worry about bennana. The code checks the block number for the last checkpoint hardcoded in the wallet and shows the warning if that checkpoint is considered a little old. The next update will have more recent checkpoints and as a result should sync faster  I'm not sure why people think that, that message is for the centrally broadcasted sync checkpoint being too old; nothing to do with the hardcoded checkpoints. If you start the sync node up the message should go away quickly. If you don't believe me then add a recent checkpoint and compile and you'll still see the message. |
|
|
|
|
Show Posts
