Post
Topic
Board Announcements (Altcoins)
Re: [ANN][X11] NinjaCoin PoW/PoS LAUNCHED - Ninja Launch - 29 GH/S reached - Bittrex
by
richiela
on 16/06/2014, 17:14:45 UTC
I compiled the new source code on my Mac.  Deleted all files except wallet.dat and reopened, but it seems to be stuck on block 14000.
Yes, this is what must be done. Just KEEP YOUR WALLET.DAT and remove everything else.
Start the new wallet and we are on block 14000, or maybe 1 or 2 more.

Bittrex and pools should update, we are on a new fork. All what has been done after block 13999 is cancelled, don't panic.

This is an unfortunate case where the dev screwed up and/or screwed us all.

We will NOT be taking a fork of this coin.  The damage is already done here.  Our systems worked as designed and our balances match including checking the moneysupply.  I would like to remind everyone that Bittrex is an exchange.  Our responsibility is to ensure that when you trade xxx A for yyy B, that it happens safely.  We do not police what is being traded.

Again, we will not be taking a new wallet or fork of this coin.  The damage done is irreparable and would have been after the first trade.  The market will remain open and we will let this die its natural death like so many coins before it.

Thanks
richie@bittrex


Yes but your exchange has no catches for this shit? Well that would be poor untested code. How is it possible a coin is meant to have 19 million total supply, but your exchange allows more than that to be deposited? Currently your exchange is allowing over 500 million coins to be deposited.. Don't you think your system should pick up on this and suspend the market immediately?  Not very secure for your clients. Polo is by far the best exchange now. Don't get goxed guys, pull your coins from Bittrex.

Using what as a supply guideline?  Random text in an ANN that we can't parse or the moneysupply value which is cryptographically sound?

*EDIT* Cryptographically sound is probably the wrong term since honestly a dev can return anything to us;  but it *should* be cryptographically sound.  Obviously malicious code is malicious.