Given how quickly they got pissed off in the past by things people said here or in some chat (yes Hort, I mean you among others), I guess they have read this thread and decided to never reopen at all because we are all just bitches and don't deserve it.. (and I am only kidding 50% here... if you ever watched a dev saying something nasty to them followed by having them delist the coin within a day on no other base than "dev is an asshole" you know what I am about)

Anyway, should they reopen anytime, imagine the crypto bank run this will result in. From reading here and judging from my own impression, I strongly believe that everybody just wants to get his/her coins off there, so I have my doubts if we will be seeing them reopen at all - no matter what, there would be no liquidity there (and therefor no notable trading fees) for months or even years to come.

If I would be running this exchange and I would have been plannning to reopen and make again money with trading fees (for example to cover lossses from the hack) I would have made my best to keep my customers confident, informed and in good faith.
But all we've got so far (after more than 35 days) is only looking and feeling like a stiff middle finger from them pointing towards us all. So at this late point in time I have no choice than to come to the conclusion that they do not want to reopen at all or at least not within a foreseeable timespan. 

The best we all can do is to raise our right arm and move the hand in a waving manner.
(you are now waving your coins on Cryptopsya goodbye, you know you should have done this some 30days ago)

Block rewards have just been reduced once more from 5.3333 to 4.0 for POW and from 10.6666 to 8 for POS.

Happy mining and minting.

Website: https://cointelegraph.com/news/analysis-hackers-liquidated-32-million-in-tokens-from-cryptopia-hack
Title: Analysis: Hackers Liquidated $3.2 Million in Tokens From Cryptopia Hack
Byline and Date: Aaron Wood Feb 8, 2019 at 22:45 UTC
Archive link: archive.today

Thank you for your explanation and for updating us when we can withdraw. Staying tuned.

Is Novaexchange already swapped?
Meaning, can we withdraw now to the new wallet from above github and start staking?

TIA

Edited to add: Why are there already 30728 blocks on the new PoS chain? Seems like this chain launched on around 1.1.

As mentionned before, make sure you do not have a backup pool configured when trying to mine on a multi/profitswitching pool.

I could download it just right now with 25MB/s in less than a minute from home.
You must be holding it wrong  (or your providers pipe to amazon is a tad slow).

Website: https://www.coindesk.com/hackers-just-stole-another-180k-in-ether-from-cryptopia-exchange
Title: Hackers Just Stole Another $180K in Ether From Cryptopia Exchange
Byline and Date: Yogita Khatri Jan 30, 2019 at 15:15 UTC
Archive link: archive.today

Hard to say with only one deposit address to check, but I'd estimate a minimum of 20-30 mio SJW are still in their wallets, probably much more.

TFTFY

P.S.: Not making fun of your loss just pointing out the facts. I myself have had ~0.35 BTC in alts, BTC and LTC in topia when they went dark.

Good points, watching the debug.log for consecutive orphans/disconnects is probably best and easiest, I guess in its simplest form that are a few dozen lines of shell/python script.

Or instead of delisting coins out of nowhere, they could have asked them to implement the NLR feature that Ravencoin and Flo recently implemented which limits the number of blocks in a reorg. If they then set the required deposit confirmations twice as high they should be safe against any malicious reorgs.

I believe for many coins that are based on something more recent than Bitcoin core 0.8 this could be as easy as cherrypicking the commits from the Flo or Ravencoin repo. I wildly guess this could even be done unilaterally from an exchange without the support of the respective coins community, in worst case the exchanges wallet would just disagree with the rest of the network but would not credit transactions from later orphanized chains to their customers accounts.

Great news:

SJW is now listed on Freiexchange:

https://freiexchange.com/market/SJW/BTC

Ja, da ist gestern in der Tat was schiefgelaufen:

https://www.newsbtc.com/2019/01/15/breaking-crypto-exchange-cryptopia-hacked-police-starts-investigation/

HTH

Hi robotsoutofcontrol,

Has already been decided what happens with the swapped TIPS (i.e. burning them)?
I see on the richlist that one address has accumulated short of 30% of whole supply:

https://tipsbe.netcraft.ch/richlist

TIA

Noteably quite a long outage already today. I sincerely hope they don't go TITSUP*.

*Total Inability To Service User Portfolios

I moved a few blocks, hope this helps the coin survive.

Thanks for your swift reply, you are perfectly right with all, have a merit on me.
I am now back synched and look forward to mine the first auxpow blocks in ~2 days.

One thing I noticed is that the daemon doesn't start if you do not specify the rpcport in the conf file or as cmdline parameter (or have listen=0). I guess the culprit is  in this line:
https://github.com/sexcoin-project/sexcoin/blob/master/src/chainparamsbase.cpp#L35 :

which seems to conflict with
https://github.com/sexcoin-project/sexcoin/blob/master/src/chainparams.cpp#L142 :

I guess the first should read 9561 to stick with the previous RPC port number.

Upgraded from source, installed, started with -reindex-chainstate as advised by debug.log but was then stuck with 10 connections and 0 blocks (and naturally no balance).
Removed everything except wallet.dat, but still the node doesn't start synching, still 0 blocks after ~15mins (having currently 7 connections).

Also: At which block height will the fork to auxpow happen?
Sorry, it is in the release notes:

Thanks for any hints in advance.

If you mean by mixed mode 802.11b/g/n, yes that's the case on all AFAICS. Though no need to worry, I won't use WiFi, that just adds unnecessary delay und unreliability when ethernet is available just 1m from the miners.
In the meantime I tried "iwlist wlan0 scanning" in the shell and after an "ifconfig wlan0 down; sleep 3; ifconfig wlan0 up" I saw my networks. It might be that they are just shielded wifi-wise pretty good when standing on a metal surface as in my case with the antenna on the bottom. When I saw my networks on first boot they were in a different place on a wooden surface.

I believe something is messed up between UI and backend, because if you delete one pool, the backend often deletes another pool (not the one you clicked to delete). Might be that sometimes there are entries in the database with the same number in the 'index' field.

I also dislike that you can't edit them (nor can't copy-paste the entries), not even directly in the apollo itself - the only way I found is mounting the apollo disk via sshfs and running sqliteman against the db in /opt/apolloapi/. This was for me necessary since at some point after some trying to shuffle, re-add, delete from the UI I suddenly got litecoinpool and a multipool running in parallel which made the apollo freak-out pretty much.

On the positive side I finally managed to run them stable against a multipool, since 24hrs stable at 100MHs with ~1.6-1.9% errors. If you want to mine on profit switching pools / multipools, make sure you do not have a backup pool configured (unlike cgminer, bfgminer seemingly requires primary and failover pool to run on the same coin/network). For mine I also set the fans to 45% resulting in 56-58°C.

Worth mentioning is also the fact that these are the first miners in my hands that are IPv6 capable, according to bfgminer release notes this should allow the apollo to connect to pools via IPv6 and for later releases to allow full nodes to run dual-stack which gives much more connections to the coind.

However the Wifi doesn't work for me (tested just for fun, don't need it), I have 2 wireless networks (WPA2-PSK only) that the apollos should see but only saw them once upon "scan" and that was after the first boot of the image, since then I don't see them anymore on both apollos (and not even the dozen or so neighbouring WiFis that my notebook sees from the same location).