Topic: Cryptopia Cryptocurrency Platform Services and Development - page 224. (Read 174220 times)
Real professional of the Cryptopia staff to ban SIGT holders from their discord! Clock is ticking! Release the coins. I can promise you that your exchange will completely fold if this is not done immediately. This should be your #1 priority.
Accept the fact you couldn't fix the issue and handle the questions and simply blame SIGT for the mistake on your side. Their DB is "tested with up to one billion 100-byte entries, i.e., ~100GB". Read it for yourself https://github.com/signatumd/source/blob/master/src/leveldb/NEWS. And FYI, Bitcoin and Litecoin uses the same DB. What reason are you going to come up with now?
https://bitcointalksearch.org/topic/m.21956220HOLY SHIT!
looking at the few wallet addresses posted here, looks like they did use SIGT wallet for internal transactions as well!
Of course it will not work, no other coin will work either... I am guessing they had the most number of transactions in SIGT.
What happens on a decent exchange?
Exchange gives you an address "deposit address" and go track it on coins explorer.
- deposit coins to "deposit address"
- once they are confirmed, they are immediately moved to "exchange address"
- the amount you deposit, own, sold and bought all are recorded in an internal DB, Most exchanges use redis for good reason, a few uses mysql, oracle and postgres
- blockchain is never used after that point unless you request a withdrawal
What were they thinking when they used wallets to hold real coins... I have a feeling most of their currencies will fail to import if their transactions/deposit/withdrawal counts increase.
Holy Shit Indeed ! In 20y as software engineer I rarely saw such incompetence.
How much time your wallet team need to update source at UNIFY? It's already 2 weeks, Novaexchange did it in 2-3h... Your team is on holiday or what?
Status shows it is waiting for Unify Dev Team - not Cryptopia
Status is the same from the beginning, we sent the source code 2 weeks ago...
Accept the fact you couldn't fix the issue and handle the questions and simply blame SIGT for the mistake on your side. Their DB is "tested with up to one billion 100-byte entries, i.e., ~100GB". Read it for yourself https://github.com/signatumd/source/blob/master/src/leveldb/NEWS. And FYI, Bitcoin and Litecoin uses the same DB. What reason are you going to come up with now?
https://bitcointalksearch.org/topic/m.21956220HOLY SHIT!
looking at the few wallet addresses posted here, looks like they did use SIGT wallet for internal transactions as well!
Of course it will not work, no other coin will work either... I am guessing they had the most number of transactions in SIGT.
What happens on a decent exchange?
Exchange gives you an address "deposit address" and go track it on coins explorer.
- deposit coins to "deposit address"
- once they are confirmed, they are immediately moved to "exchange address"
- the amount you deposit, own, sold and bought all are recorded in an internal DB, Most exchanges use redis for good reason, a few uses mysql, oracle and postgres
- blockchain is never used after that point unless you request a withdrawal
What were they thinking when they used wallets to hold real coins... I have a feeling most of their currencies will fail to import if their transactions/deposit/withdrawal counts increase.
Accept the fact you couldn't fix the issue and handle the questions and simply blame SIGT for the mistake on your side. Their DB is "tested with up to one billion 100-byte entries, i.e., ~100GB". Read it for yourself https://github.com/signatumd/source/blob/master/src/leveldb/NEWS. And FYI, Bitcoin and Litecoin uses the same DB. What reason are you going to come up with now?
Craptopia has made themselves look like completely incompetent fools.
NEVER again will I involve myself with their crap exchange.
Your handling of Sigt is disgusting.
NEVER again will I involve myself with their crap exchange.
Your handling of Sigt is disgusting.
Now I see this message:
SIGT / BTC market is closing
SIGT is being delisted due to ongoing wallet issues that remain unresolved, please withdraw all your SIGT before 2017-10-19
What does that mean? Am I able to get back all my SIGT coins? Coz my coins are stuck at "pending withdrawal", so I can't withdraw anymore
SIGT / BTC market is closing
SIGT is being delisted due to ongoing wallet issues that remain unresolved, please withdraw all your SIGT before 2017-10-19
What does that mean? Am I able to get back all my SIGT coins? Coz my coins are stuck at "pending withdrawal", so I can't withdraw anymore
How much time your wallet team need to update source at UNIFY? It's already 2 weeks, Novaexchange did it in 2-3h... Your team is on holiday or what?
Status shows it is waiting for Unify Dev Team - not Cryptopia
Cryptopia has been holding my SIGT coin hostage since end of August. On 30 August, I was trying to withdraw the coins and it says "pending withdrawal", until today.
The problem is that I'm unable to trade the coins since it's in withdraw status. I have already sent a support ticket to request to cancel my withdrawal so that at least I can trade the coins on the exchange. But, as usual their support person's response is exactly the same as the rest posted here, a mere copy & paste job.
So, all my SIGT has been stuck in limbo state, thanks to their incompetence to solve the issue. This has caused a lost to me since I'm unable to trade or move the coins.
How long more do we have to wait till this issue gets resolved? Days? Weeks? Months? Totally unacceptable!!
The problem is that I'm unable to trade the coins since it's in withdraw status. I have already sent a support ticket to request to cancel my withdrawal so that at least I can trade the coins on the exchange. But, as usual their support person's response is exactly the same as the rest posted here, a mere copy & paste job.
So, all my SIGT has been stuck in limbo state, thanks to their incompetence to solve the issue. This has caused a lost to me since I'm unable to trade or move the coins.
How long more do we have to wait till this issue gets resolved? Days? Weeks? Months? Totally unacceptable!!
This sigt wallet failure is something that I expect to happen at times, however it should only take days not weeks to correct. I opened an account at Cryptopia solely for sigt. After this show of incompetence, I will never use the services of cyptopia again. Cryptopia has permanently damaged their reputation at this point. I'm not interested in selling my sigt, I just want to move it to my own wallet for staking.
I think that when this coin becomes PoS, if Cryptopia has not corrected the wallet issue, they will be facing legal consequences, and I'll be onboard.
And as far as threats to delist sigt.....go for it, I'm sure we can get another exchange far more competent to handle our transactions.
I think that when this coin becomes PoS, if Cryptopia has not corrected the wallet issue, they will be facing legal consequences, and I'll be onboard.
And as far as threats to delist sigt.....go for it, I'm sure we can get another exchange far more competent to handle our transactions.
Haha,we know the SIGT value.Because we have yobit. The cryptopia will cry and have a huge compensation. cryptopia please keep your broken wallet. when SIGT go to moon,cyringtopia will go to prison. Because they lost a billion SIGT and no money to pay .
I guess soon enough we will find out whether Nova or Yobit have solved the issue already or simply not encountered it yet.
If there is scaling problems, why not to create 2,3,4 wallets instead of one? Sigt is just another fork with standard leveldb implementation. What kind of bullshit about enterprise level you talking about? And POW stage will end in 11 days, so amount of micro transactions from miners will drop.
How much time your wallet team need to update source at UNIFY? It's already 2 weeks, Novaexchange did it in 2-3h... Your team is on holiday or what?
Can you folks confirm that our SIGT is safe in your exchange? Even if it might take some time to resolve the issue?
did you try asking yobit how they solved this? or novaexchange?
60% of the total Signatum is traded on Cryptopia
Yobit trades 35% and yobit has issues with stuck coins https://bitcointalksearch.org/topic/stuck-coins-on-yobit-running-list-2081826
Nova trades 4% and nova have their own issues https://bitcointalksearch.org/topic/novaexchange-hacked-or-scam-2118683
Guess they haven't had a wallet crash yet.
Different exchanges run on quite different platforms and coding.
Cryptopia - I have always liked the general feeling of Trollbox developing transparent funds and encouraging shareholders.
Exchange is much easier than helping a lot with daily deals
DOT it is a great business coin and can be used by the services on the site
Exchange is much easier than helping a lot with daily deals
DOT it is a great business coin and can be used by the services on the site
I guess soon enough we will find out whether Nova or Yobit have solved the issue already or simply not encountered it yet.
@dodopool - We've been working with the SIGT team to deal with these problems which are with SIGT and not with Cryptopia. The SIGT wallet wasn't designed to work on an enterprise level and so it has major problems no matter what kind of hardware we put on it. You're right that your wallet with a few addresses and a handful of transactions will sync in a manner of hours. But if you have tens of thousands addresses with over a million inputs and you're wallet was involved in up to 50 transactions per block since it was listed... then it's a slightly different story. Since 2 of the 3 wallets that were importing our keys have corrupted their leveldbs, we're assuming plan A isn't going to work. Plan B is to gonna be to import the keys a few hundred at a time so we can consolidate the inputs back into our hot wallet so that users can withdraw and we can delist.
did you try asking yobit how they solved this? or novaexchange?
these problems which are with SIGT and not with Cryptopia
I am fairly certain when it works on other exchanges and not cryptopia, it is a problem with your excange
@fusionfoto - We're getting there, we had some hardware cause us some issues for us; some of the wallets themselves or some of our integrations have had issues recovering from this. Cryptopia has to balance getting everything running smoothly again while not cutting any corners to make sure everyone's money stays safe.
@flashdix - I had to go and cleanse sections of your support ticket from our DB because you included your API key and API secret in the support ticket for whatever reason (NEVER give your API key/secret to anyone, ffs). Your has been unlocked based on my assumptions your bot will be less dumb in the future. If you want to spam the mempool of a coin, do it from your own wallet and not ours.
@theincrediblevictor, @chickenbacon, @hoan281, @Icefrag - Some of the aforementioned problems have queued a bunch of wallet work up, most of which is manually checking and reprocessing transactions. We can't just get some temps or some interns and hand them root access to our hot wallets. This seems like it would be pretty low hanging fruit though, so I'll ask.
@Mindin - sorry for the hassle, glad support helped you
@dodopool - We've been working with the SIGT team to deal with these problems which are with SIGT and not with Cryptopia. The SIGT wallet wasn't designed to work on an enterprise level and so it has major problems no matter what kind of hardware we put on it. You're right that your wallet with a few addresses and a handful of transactions will sync in a manner of hours. But if you have tens of thousands addresses with over a million inputs and you're wallet was involved in up to 50 transactions per block since it was listed... then it's a slightly different story. Since 2 of the 3 wallets that were importing our keys have corrupted their leveldbs, we're assuming plan A isn't going to work. Plan B is to gonna be to import the keys a few hundred at a time so we can consolidate the inputs back into our hot wallet so that users can withdraw and we can delist.
@Lisk_beginner, @wacko - accounts locked this way are locked for 24 hours at which point they unlock - and we know you're right, the confirmation box is coming soon.
@flashdix - I had to go and cleanse sections of your support ticket from our DB because you included your API key and API secret in the support ticket for whatever reason (NEVER give your API key/secret to anyone, ffs). Your has been unlocked based on my assumptions your bot will be less dumb in the future. If you want to spam the mempool of a coin, do it from your own wallet and not ours.
@theincrediblevictor, @chickenbacon, @hoan281, @Icefrag - Some of the aforementioned problems have queued a bunch of wallet work up, most of which is manually checking and reprocessing transactions. We can't just get some temps or some interns and hand them root access to our hot wallets. This seems like it would be pretty low hanging fruit though, so I'll ask.
@Mindin - sorry for the hassle, glad support helped you
@dodopool - We've been working with the SIGT team to deal with these problems which are with SIGT and not with Cryptopia. The SIGT wallet wasn't designed to work on an enterprise level and so it has major problems no matter what kind of hardware we put on it. You're right that your wallet with a few addresses and a handful of transactions will sync in a manner of hours. But if you have tens of thousands addresses with over a million inputs and you're wallet was involved in up to 50 transactions per block since it was listed... then it's a slightly different story. Since 2 of the 3 wallets that were importing our keys have corrupted their leveldbs, we're assuming plan A isn't going to work. Plan B is to gonna be to import the keys a few hundred at a time so we can consolidate the inputs back into our hot wallet so that users can withdraw and we can delist.
@Lisk_beginner, @wacko - accounts locked this way are locked for 24 hours at which point they unlock - and we know you're right, the confirmation box is coming soon.
Holy crap, I think I've done the same. Also had my account locked today and was wondering why, and just now realized that it was probably myself that clicked that button in the e-mail. Bad design really, "Lock my account" shouldn't be the first button in the mail, it's the one you intuitively click when the login confirmation e-mail arrives. And it just locks you straight away, without any "are you sure?" dialogs. 
Jump to: