Anyone still holding this coin and have not sent it to YObit yet?

If you have bought Cygnus on YObi lately, this does not count, as those coins are on a bogus chain.

I would like to get enough nodes together to fix the proper chain.

My wallets run behind more than one NAT firewall.  I would not recommend the above suggestion, especially if you are running on Windoze or stock Ubuntu.

DMZ setting in the router are for the network savvy.

You only need to mine with one algo.  When mining at a pool, you point your miner to the port that supports the algo you choose.

It is the same as a single algo, each pool is competing to find the solution first.  The only difference is the solution may be found using 6 different algos each with its one difficulty setting.

If you have an X11 ASIC miner you choose the port that supports BATA x11.
If you have a SCRYPT ASIC miner you choose the port that supports BATA SCRYPT.
etc.
 

Are you building the full wallet with the Qt gui, or just the daemon?

The SpaceCoin project will continue to progress with or without Cryptopia exchange.  Although this does affect the liquidity of the coin we will continue to look at options to keep the coin liquid.

With so many scams and opportunists out in the crypto market, the exchange's listing requirements are getting tighter and more demanding to protect their customers.  It also means that it will become more expensive and burdensome to the developers of real cryptocurrency projects to  keep the crypto on the market.

I think the days of community supported new coins and technologies are disappearing, and only profit driven projects will continue.

I have submitted a ticket to Cryptopia about the delisting.  It seems very sudden that they would delist the SPACE coin.

We will look for other exchanges to list the coin.  YObit is the last on the list, they have a lot of coins hostage on their exchange, and not just SPACE.

We will keep you up to date on what is happening.

SPACE COIN is still alive and still supported.

Things are quiet, but not dead, for certain.

I am hoping that the market will pick up again, so we can see more innovations in the future.

I have confirmed that the YObit wallet is running a bogus blockchain.

Transactions that occured during that last time YObit wallet was online (back in Nov 2017) those transactions are no longer on their current blockchain.

The total coin supply does not match what was on the existing chain.

To fix this situation, the solution is to update the wallet and change the version to reject the YObit version of the blockchain.

We will need at least 10 to 20 wallets running to make this happen.  But we will lose YObit as the only exchange left that is trading CYG and will need to find another exchange or 2 to start trading CYG.

Do not transfer coins onto or from YObit exchange.  If this moves ahead, you will lose all you CYG coins.

Let me know by direct message if you are interested in helping and running a CYG wallet.

Wrong 'Token'.

This is Cygnus as in Symbol CYG.  An X11 coin on its own blockchain.  Not the ETH token.

So I archived the blockchain that the rest of us were running and sync'd with the blockchain from YObit.  The YObit chain was tinkered with.  The coin dev has over 91% of the coin supply.  The coin supply on the chain we had was approx 22 million coins, the current YObit chain has 199 million coins.

I resync'd my Block Explorer with the YObit blockchain take a look for yourselves:
http://cyg.midnightminer.net/richlist

Definitely a rigged blockchain from the original.

Yobit wallet for CYG is back online.

So you can either buy and xfer you CYG to your wallet for staking or send what you have in your wallet and cash it in.

If the exchange has not updated the wallet, then you will not see the transaction or the coins.  If they are not on the correct version, then they are not on the right chain.  When the exchange upgrades their wallets the coins will still be in the exchange wallet.  Hopefully!

*** IMPORTANT ***

Do not move coins unless you are certain both parties are on the current version.  You may lose your coins!

Yes.

Jump on Discord and we can work through the issue online.

How many peers do you have when it is sitting at 25 hours behind?

Yes there are two chains and the new chain (protocol version 70716) is pulling ahead of the old chain (protocol version 70715).  It was bound to happen since this was a post hard-fork fix, and as enough clients and MNs moved on to the new protocol and ignore old clients.  The node I had running to keep the different version of clients in sync is no longer needed as the new chain is running on its own.  

This means that if you have not upgraded to the new wallet version 2.5.0.1 by now, you will need to reload the blockchain from the start (delete the blockchain, chainstate, and database directories. Might as well delete mempool.dat, mncache.dat, and peers.dat, as they will be stale).

My 4 nodes are all on the same block height that is higher than the Cryptoid BE.  So I assume that the BE client has not been updated yet.

Jimmy you were on the latest wallet from a week ago (and it was suppose to be v2.5.0.0 but the labels did not get updated), however that wallet did not disconnect older nodes with the wrong Masternode Reward.  So this caused a lot of orphan blocks and forking of the chain.  Yesterday (Saturday), I released an updated wallet v2.5.0.1, that shows the proper wallet version, and this wallet will ignore older wallets to stop the orphan blocks and failed payouts.

I recommend you update your local wallet right away.  If the wallet synchronizes and you are on the same height as the Cryptoid Block Explorer then go in the Tools -> Wallet Repair -> Rescan blockchain files to rescan the wallet for your transactions.  You will see all of your successful rewards.

If your wallet does not synchronize or is not at the same block height as the block explorer, then shutdown your wallet and delete the blocks, chainstate, and database directories in your %APPDATA% directory and start the wallet again.  The wallet will synchronize the blockchain from the beginning.

As for your VPS, I did compile the Linux binaries, so you should be able to copy them to your VPS and replace the current binaries.  On the VPS shutdown your wallet, move or delete the old wallet binary, copy the new wallet onto the server and then start the wallet.  You may need to issue the masternode start command for that masternode or it may continue to show ENABLED.

I added 2 more seed nodes:

45.32.233.198
68.235.184.24

That looks good Dennis.  This is the beginning of the changeover, so until Masternodes and more wallets are updated the wallet will keep up to date on the blocks but will not fully synchronize.

Depending on how quickly everyone updates their wallets and Masternodes it could take a couple of days before the network is stable again.  This is unfortunately what happens when a protocol change happens after the hard-fork.  The network is fragmented and this new wallet is attempting to herd the cats back together.

I didn't have time to get a Block Explorer up and running, but I am watch the Cryptoid BE to make sure we stay on the good chain.  The faster people upgrade the better chance we have of getting stable again.

I was waiting for VegasGuy to test this out and approve first but we need to get the fixed up wallet version out.

https://github.com/Vegas-Guy/LasVegasCoin2/releases/tag/v2.5.0.1

Because the protocol version is increased, this wallet will not connect to previous versions to stop the orphan and forking of the chain from happening.

*** IMPORTANT ***
 1) After you shutdown your current wallet, go to your %APPDATA% directory in Windows ( .LasvegascoinV2 in Linux) and delete the peers.dat file.

 2) Start this new version of the wallet and it will find the peer nodes with the newer version.

*****************
If you are not sure how to do this, the alternative is to enter the following command in the Tools Windows - Console ->
This node is configured to allow the new wallets to find peers with the new version and sync with previous version wallets.

For VPS Masternodes:

VPS users can go to there directory that they did a 'git clone' (from the Vegas-Guy/LasVegasCoin2 GitHub repo) and run 'git pull' in that directory to download the latest source.  Then run:


Your new binaries will be in the src directory.

I will be around on the forum and on Discord to help.

The changes have all been put into a Pull Request to LIMXDEV GitHub to Synchronize the repos.