CoinMarket.io | New, self-moderated support and news thread.

[mrstone]

Hi there. Glad to see everything's now up and running... Almost.

This transaction didn't get to my KDC wallet, would you please have a look?
Fri Mar 07 2014 22:30:46   159.9   KDC   173.245.49.180   confirmed
Transaction id: 0aeac3872a8a7d706bde83bd4517ea9906ac1197cba4ca67c3b84abe821fbff3

Thanks in advance!

[pablitos]

Withdraw successfully, in 7500 NOBL, 0.0016 BTC, and 5000 MINT. Withdraw ok of coinmarket...

[hellscabane]

CoinMarket.io status update

1. What happened?

We got exploited. Somewhat. The majority of coins were saved by cold storage and a quick reaction.
A couple of users abused a bug in the trading engine allowing them to create coins (increase balance) out of nothing.
Do you remember the day when KARM/BTC 24h volume was 400+ out of the blue? That volume came from those malicious users trading.
When we noticed the problem, we stopped all trading to investigate the situation.
Unfortunately, we failed to find the bug fast enough to resume normal operation and cover the losses from fees.
The new trading engine (rewritten) still suffers from this unknown-to-us issue, this is why we have not resumed any trading.
Meanwhile, we allowed all withdrawals to happen - because it was the right thing to do.
Because of high withdrawal volumes, the wallets ran out of normal unspent inputs and started to combine too many small inputs for withdrawals.
There is a limit of inputs/outputs in a cryptocurrency transaction.
If the wallet software (the official stuff that everybody uses) chooses or attepts to choose too many inputs,
the transaction will fail with "Transaction too large" or "Transaction creation failed" error.
It has nothing to do with insufficent balance. This problem was caused by miners who mined directly to the deposit address, creating tens of thousands of small inputs.
The default algo for choosing transaction inputs (coin selection) is not designed for exchanges. We need to create some code that does some raw transaction magic.
Also, some coins have landed on an invalid fork - because we were too busy with other issues. We will update all coindaemons tonight.
Everything has taken too much time because multiple problems hit us at the same time and debugging the situation was not so simple.

2. What is the solution? What are you doing now?

We have manually processed some withdrawals, but that process is too slow.
An automatic script will be running tomorrow - it will hopefully process the stuck withdrawals.
If your withdrawal status changes to "manual", it means that we manually processed it.
If your withdrawal status changes to "fixed", it means that the automatic routine processed it.
We will publish statistics when avalible - after the script runs.

Please stop any accusations and threats against Kenneth Bjørke - he is just hosting the web servers.
The hosting of coinmarket.io by Kenneth will be terminated when the dust settles and all possible withdrawals are processed.

We will be posting lists of withdrawals that got fixed.
We are deeply sorry for the inconvenience this may have caused to you.
More detailed information coming after the automatic process runs.

Just pushing this to the top of the stack. Gosh, damn DOG n00bs need to calm the frick down...

"Oh my gosh, I put all my allowance monies in an exchange and now I can't get them nice Nikes that I should have been able to get after I played with the markets. Wah!!!"

Okay, maybe that was a bit unfair, but I swear, most of the vitriol is coming from those who have only been here since the beginning of December. Maybe survive a few more insane market crashes and see some actual orchestrated scams before you go all crazy. Just saying...

[ontopicplease]

Okay, under point 2. coinmarket.io says to start processing the "stuck"withdrawels.
Personally I have 4 withdrawels with status "confirmed"that didn't arrive in my wallet.
Coinmarket can you explain what happens to these withdrawels?

[BKRTC]

User Name BTCKR242961
Sat Mar 08 2014 06:43:53  3495.83883014 UTC confirmed
No Transaction ID. I haven't received my coins. I'm waiting from 5 days, so please process my withdrawal.

[Cloudpost]

It's an obvious scam. This guy got really nervous when you found the Kenneth Bjørke name. Is it "BlockEruptor 2" scenario? I hope it is and he (Kenneth Bjørke) will return ALL COINS really soon, manually or via scrypt.

I don't have any funds on coinmarket, but I checked the site almost every day and was surprised that it takes so long to repair/fix it. It looks the same as GOX when it was "fixing problems".

[schiavonxv]

I can't found this transaction in USDE Blockchain.

e9eaf49c605e7dfbec8ec65c1d1ea63146e2e2f10a6121fc90671124ee84a18d

I sent 102000USDe, show CONFIRMED, but so far i can't see this transaction in block chain.

WHERE IS MY FUCKING COIN?

[tweaq]

I also have some stuck transactions. I have some deposited LEAF still pending (Transaction id: 4c780afbd9865868c770c8208def74c9380d07aa3a30f613a61b41457d5c0387) and a deposit of USDE (Transaction id: e24a09f3b10f72ebc1e9f67795b8b07aeb2fbe6fe943f642a70f99a20b23ca7d). The LEAF has been pending since Feb 28 and the USDE since something was reset, Jan 1 1970.  My withdrawls are fine, so far. Looks like withdrawing even fixed a pending NOBL.
thanks

[mystix]

It's an obvious scam. This guy got really nervous when you found the Kenneth Bjørke name. Is it "BlockEruptor 2" scenario? I hope it is and he (Kenneth Bjørke) will return ALL COINS really soon, manually or via scrypt.

I don't have any funds on coinmarket, but I checked the site almost every day and was surprised that it takes so long to repair/fix it. It looks the same as GOX when it was "fixing problems".

Ok we'll start now and see how long it takes you to write up a trading platform. The time is only surprising to those who haven't been in that kind of situation.

..and yes I know this opens me up to the huge population on here that have triple doctorates from MIT and coded 1/2 the NYSE, all while pregnant with your 4th child, and juggling your 3 full-time jobs. Spare me, because I know thats b.s.

[mystix]

I'll never understand the running silent part of what they are doing but I think they are still trying to fix things.  I'm guessing people are so pissed off by now that they figure nothing they can say would matter so they aren't saying anything at all.  I would suggest to the dev team to continue to post even if you have no idea how to fix whatever issues you are running into because the problem with running silent is people think you are just running away with their coins.

What are they going to say that fixing the site wouldn't say better?

Poloniex had a thread about their recent hack issues where the owner was open and honest, lined out the technical issues as well as how and why he intended to pay back. What did he get for that? Hate mail.. high up egotistical people telling him to shut down his business that he had no justification for running in the first place. Every point he made, while reasonable, was taken out of context to just generally be a douche because .. internet.

That kind of example is probably specifically why so many choose just to stay quiet and do what they're going to do. While there was some praise in that thread, there is here as well, in about equal measure. People who are going to be douches about this stuff are going to be either way, the rest of us are going to be patient, either way. May as well go with the one that gives your critics less ammo.

[cknightuniverse]

Dear CoinMarket.io Support,

I'm having some major problem with Reddcoin Withdrawal.  Please help me! I got this error message when I clicked the confirm link:

There was a problem with this withdrawal because the coindaemon is offline. All cases like this will be processed manually, please be patient.  

Here is the link:
https://www.coinmarket.io/confirm/9c6365877a673e5c4902fdb8c18ad503cc51d602d66ecd5859ef233f239228145a8e576add3f0a7529567381ccc7c6fb

From my account: Thu Mar 13 2014 23:47:09   51736880.88549999

In addition, please note NO transaction id was given.  

Could you please manually process the withdrawal for me?  Thank you in advance!

[dolph]

Hi,

I have three pending withdrawals dating back to Jan 25. The emails were never sent to my email address so I can't confirm them. 

Any ideas of how I can cancel these & update my email address?

[hunterwolf]

Fri Mar 07 2014 14:59:54    100866.49200908   USDE   1x.x.x.x   confirmed
Transaction id: a0ef224d385305aff18dede2879df8dc9bbb0dfd844b387616b3bbedb33db5bf

i'm still wait. please fix this.

[multibit]

It's an obvious scam. This guy got really nervous when you found the Kenneth Bjørke name. Is it "BlockEruptor 2" scenario? I hope it is and he (Kenneth Bjørke) will return ALL COINS really soon, manually or via scrypt.

I don't have any funds on coinmarket, but I checked the site almost every day and was surprised that it takes so long to repair/fix it. It looks the same as GOX when it was "fixing problems".

I think we should start digging out all the other scammers' name. They obviously are cooking up BS to steal our BTC.

[Snotty]

CoinMarket.io status update

1. What happened?

We got exploited. Somewhat. The majority of coins were saved by cold storage and a quick reaction.
A couple of users abused a bug in the trading engine allowing them to create coins (increase balance) out of nothing.
Do you remember the day when KARM/BTC 24h volume was 400+ out of the blue? That volume came from those malicious users trading.
When we noticed the problem, we stopped all trading to investigate the situation.
Unfortunately, we failed to find the bug fast enough to resume normal operation and cover the losses from fees.
The new trading engine (rewritten) still suffers from this unknown-to-us issue, this is why we have not resumed any trading.
Meanwhile, we allowed all withdrawals to happen - because it was the right thing to do.
Because of high withdrawal volumes, the wallets ran out of normal unspent inputs and started to combine too many small inputs for withdrawals.
There is a limit of inputs/outputs in a cryptocurrency transaction.
If the wallet software (the official stuff that everybody uses) chooses or attepts to choose too many inputs,
the transaction will fail with "Transaction too large" or "Transaction creation failed" error.
It has nothing to do with insufficent balance. This problem was caused by miners who mined directly to the deposit address, creating tens of thousands of small inputs.
The default algo for choosing transaction inputs (coin selection) is not designed for exchanges. We need to create some code that does some raw transaction magic.
Also, some coins have landed on an invalid fork - because we were too busy with other issues. We will update all coindaemons tonight.
Everything has taken too much time because multiple problems hit us at the same time and debugging the situation was not so simple.

2. What is the solution? What are you doing now?

We have manually processed some withdrawals, but that process is too slow.
An automatic script will be running tomorrow - it will hopefully process the stuck withdrawals.
If your withdrawal status changes to "manual", it means that we manually processed it.
If your withdrawal status changes to "fixed", it means that the automatic routine processed it.
We will publish statistics when avalible - after the script runs.

Please stop any accusations and threats against Kenneth Bjørke - he is just hosting the web servers.
The hosting of coinmarket.io by Kenneth will be terminated when the dust settles and all possible withdrawals are processed.

We will be posting lists of withdrawals that got fixed.
We are deeply sorry for the inconvenience this may have caused to you.
More detailed information coming after the automatic process runs.

I hope this means I'll get my DGB back... Don't just give hope and dissapear again, please. I've sent you a detailed PM about the issue, but I bet it's been burried in the huge pile of complaints and support requests.

[uzytkownik]

Hi guys!

HELP ME PLEASE!!!

I made 9 of withdrawals on 7 march 2014. Some of leafs and btc.
It was difficult to confirm becouse site was offline many times this day.
Finally all my withdrawals have status confirmed, but only 2 of 9 have
transaction id, and only 2 of them gone. Other 7 hangs somewhere.
I have no coins on my accounts and no on my wallets. Could you
help me please fix this big problem.

Best regards

[multibit]

CoinMarket.io status update

1. What happened?

We got exploited. Somewhat. The majority of coins were saved by cold storage and a quick reaction.
A couple of users abused a bug in the trading engine allowing them to create coins (increase balance) out of nothing.
Do you remember the day when KARM/BTC 24h volume was 400+ out of the blue? That volume came from those malicious users trading.
When we noticed the problem, we stopped all trading to investigate the situation.
Unfortunately, we failed to find the bug fast enough to resume normal operation and cover the losses from fees.
The new trading engine (rewritten) still suffers from this unknown-to-us issue, this is why we have not resumed any trading.
Meanwhile, we allowed all withdrawals to happen - because it was the right thing to do.
Because of high withdrawal volumes, the wallets ran out of normal unspent inputs and started to combine too many small inputs for withdrawals.
There is a limit of inputs/outputs in a cryptocurrency transaction.
If the wallet software (the official stuff that everybody uses) chooses or attepts to choose too many inputs,
the transaction will fail with "Transaction too large" or "Transaction creation failed" error.
It has nothing to do with insufficent balance. This problem was caused by miners who mined directly to the deposit address, creating tens of thousands of small inputs.
The default algo for choosing transaction inputs (coin selection) is not designed for exchanges. We need to create some code that does some raw transaction magic.
Also, some coins have landed on an invalid fork - because we were too busy with other issues. We will update all coindaemons tonight.
Everything has taken too much time because multiple problems hit us at the same time and debugging the situation was not so simple.

2. What is the solution? What are you doing now?

We have manually processed some withdrawals, but that process is too slow.
An automatic script will be running tomorrow - it will hopefully process the stuck withdrawals.
If your withdrawal status changes to "manual", it means that we manually processed it.
If your withdrawal status changes to "fixed", it means that the automatic routine processed it.
We will publish statistics when avalible - after the script runs.

Please stop any accusations and threats against Kenneth Bjørke - he is just hosting the web servers.
The hosting of coinmarket.io by Kenneth will be terminated when the dust settles and all possible withdrawals are processed.

We will be posting lists of withdrawals that got fixed.
We are deeply sorry for the inconvenience this may have caused to you.
More detailed information coming after the automatic process runs.

I hope this means I'll get my DGB back... Don't just give hope and dissapear again, please. I've sent you a detailed PM about the issue, but I bet it's been burried in the huge pile of complaints and support requests.

This is just another empty promise with loads of jargon to try to make to make you wait while they figure out how to steal and get away with it.

It seems like they are paying out small amounts and keeping the big ones. This way they piss off as little people as possible.

[dload.1]

I'll never understand the running silent part of what they are doing but I think they are still trying to fix things.  I'm guessing people are so pissed off by now that they figure nothing they can say would matter so they aren't saying anything at all.  I would suggest to the dev team to continue to post even if you have no idea how to fix whatever issues you are running into because the problem with running silent is people think you are just running away with their coins.

What are they going to say that fixing the site wouldn't say better?

Poloniex had a thread about their recent hack issues where the owner was open and honest, lined out the technical issues as well as how and why he intended to pay back. What did he get for that? Hate mail.. high up egotistical people telling him to shut down his business that he had no justification for running in the first place. Every point he made, while reasonable, was taken out of context to just generally be a douche because .. internet.

That kind of example is probably specifically why so many choose just to stay quiet and do what they're going to do. While there was some praise in that thread, there is here as well, in about equal measure. People who are going to be douches about this stuff are going to be either way, the rest of us are going to be patient, either way. May as well go with the one that gives your critics less ammo.

+ 1

[Snotty]

CoinMarket.io status update

1. What happened?

We got exploited. Somewhat. The majority of coins were saved by cold storage and a quick reaction.
A couple of users abused a bug in the trading engine allowing them to create coins (increase balance) out of nothing.
Do you remember the day when KARM/BTC 24h volume was 400+ out of the blue? That volume came from those malicious users trading.
When we noticed the problem, we stopped all trading to investigate the situation.
Unfortunately, we failed to find the bug fast enough to resume normal operation and cover the losses from fees.
The new trading engine (rewritten) still suffers from this unknown-to-us issue, this is why we have not resumed any trading.
Meanwhile, we allowed all withdrawals to happen - because it was the right thing to do.
Because of high withdrawal volumes, the wallets ran out of normal unspent inputs and started to combine too many small inputs for withdrawals.
There is a limit of inputs/outputs in a cryptocurrency transaction.
If the wallet software (the official stuff that everybody uses) chooses or attepts to choose too many inputs,
the transaction will fail with "Transaction too large" or "Transaction creation failed" error.
It has nothing to do with insufficent balance. This problem was caused by miners who mined directly to the deposit address, creating tens of thousands of small inputs.
The default algo for choosing transaction inputs (coin selection) is not designed for exchanges. We need to create some code that does some raw transaction magic.
Also, some coins have landed on an invalid fork - because we were too busy with other issues. We will update all coindaemons tonight.
Everything has taken too much time because multiple problems hit us at the same time and debugging the situation was not so simple.

2. What is the solution? What are you doing now?

We have manually processed some withdrawals, but that process is too slow.
An automatic script will be running tomorrow - it will hopefully process the stuck withdrawals.
If your withdrawal status changes to "manual", it means that we manually processed it.
If your withdrawal status changes to "fixed", it means that the automatic routine processed it.
We will publish statistics when avalible - after the script runs.

Please stop any accusations and threats against Kenneth Bjørke - he is just hosting the web servers.
The hosting of coinmarket.io by Kenneth will be terminated when the dust settles and all possible withdrawals are processed.

We will be posting lists of withdrawals that got fixed.
We are deeply sorry for the inconvenience this may have caused to you.
More detailed information coming after the automatic process runs.

I hope this means I'll get my DGB back... Don't just give hope and dissapear again, please. I've sent you a detailed PM about the issue, but I bet it's been burried in the huge pile of complaints and support requests.

This is just another empty promise with loads of jargon to try to make to make you wait while they figure out how to steal and get away with it.

It seems like they are paying out small amounts and keeping the big ones. This way they piss off as little people as possible.

Still, better than nothing. They've pissed enough people already..

[cryptoplayer]

6442.36467297 KDC withdrawal
Transaction id: 8bbef80c7b2705f1432fcaa6c29f061d25e72f10069be35ba14f0b576b8ec633

no coins for 7 days already
still got hope....