Done, sorry, oversight, the correct link is on the website now

SOURCE IS: https://github.com/MojocoinV2/mojocoin

OP is up to date with regards to links

Windows-qt 2.1
MANDATORY UPDATE PLS DOWNLOAD AND UPGRADE TO VERSION 2.1 ASAP

All we are really doing with the fork is to activate PoW mining, so everything to do with addresses and private keys do not change so your wallet.dat should be fully compatible with the v.2.1 wallet. You may have to re-sync but no coins should be lost in this process. If you have lost coins after the hard-fork, just give it a day and PM me with details and we will see what we can do.

FURTHER UPDATE
1. I have informed Livecoin and Coinexchange and they are ready to update to version 2.1 so there should be minimal disruption if you are trading.
2. I have also contacted some pool operators to see if we can get some pools up after the hard-fork. You can also solomine (don't ask how, if you know how you know, if not please look it up).

Laters....

IMPORTANT

Prepare for a hard-fork tonight at some point GMT (London time) or latest tomorrow. We are currently building the new Windows-qt and the Mac will be released a bit later. So if you are running a Mac wallet please stop it and backup at the time of the hard-fork. If you keep staking you would loose any coins you stake after the hard-fork. Same applies for Windows users. Once the new hard-fork Windows-qt is announced then upgrade ASAP. You should not have to resync the chain. The current chain is moving so slow that this should not cause any issues. The wallet.dat / private keys are compatible with the new wallets, so worst case scenario is that you have to re-sync but it’s a short chain.

Once the Windows-qt v.2.1 is live I will link to it in the OP, the thread, the blog, the website and Twitter.

You MUST update to v.2.1 as soon as possible as any blocks found with the old wallets will be invalid. Any wallet with protocol version lower than 9000 will be disconnected from the new chain.

Masternodes will unfortunately have to rebuild from the updated source. Once I publish the links to the Windows-qt 2.1 assume that the source code is up to date as that is the one we have built from.

You will then be able to mine using an X11 miner w/ a 20 MOJO block award.

Any pool operators want to participate and set up a pool?

I get the same error, I can't withdraw my ERC. I have had my ERC in Staisybit for months without being able to withdraw. What is being done about that?

It was always as PoW coins, it's just that there was limit set in the code for when the network would stop accepting PoW blocks. Now, we open for PoW blocks again and give a mining award for 6 months that will create around 5 mill. coins and we 'burn' 5 mill coins to compensate. What we acheive is to get more users on the network and we will prevent any future block or network / chain stop. This will move the chain to around the 1 min block time set. We may reduce the min. stake time. We will see, so for 6 months at least we will be a PoW/PoS hybrid with masternodes on top.

IMPORTANT UPDATE

We realise that we are effectively stuck at the moment and that we will not be able to move the chain effectively so this is what we will do:
1. Update the protocol version with an immediate hard fork to activate X11 PoW blocks to move the chain.
2. We will burn 5,000,000 MOJO to take the total down.
3. We will activate X11 PoW mining with a block reward of 20 MOJO per block for 6 months and keep PoW enabled for a while as a backup measure to make sure we never end up with a stuck chain again.
4. We will remove the restriction that requires a master node to be running for other wallets to stake.

We have made a review of the code and believe that the MN system / PoS is correct and will work post hard-fork.

We expect to implement this on Tuesday 26/07/2016 evening time (GMT)

Since there is no moving chain and the wallet.dat will be compatible with the new post hard-fork wallets this should not present a problem for anyone.

This will ensure that we can drive The Mojocoin project forward and not get bogged down in issues like these. We can then focus on the utility of MOJO and move forward with the roadmap.

I will update the OP, Twitter, blog etc. shortly.

Links to new wallets will be up hopefully by Tuesday evening. Hang in there...

Thank you

I am fully aware of the situation and that the chain is stuck and we are working on solutions. We will not give it up and will find a solution to drive this forward. If MNs could please keep running for the time being that would be useful. I will update when I have something to update about. If anyone can read code and wants to help then please do, and if you find a problem please highlight but be specific.

We are working on this so there is little point in making complaint posts unless you have a specific idea or have found a bug.

I'm speaking to him as well, pls let the MN run for now, we are working hard to get this fixed.

Quick update:
1. I have the initial contractor reviewing the code and an additional dev. looking at the problem
2. I have put out an ad (on BCT) for an additional dev with in depth knowledge of PoS / MN to do paid work with the code
3. If this does not resolve our issues I will hire another freelancer with provable credentials for the job
We will make this work

delete

There are three running but no PoS blocks for a while, we are investigating if the PoS is working the way it should

My best guess is that they haven't been broadcast yet, wait for another few confirmations. The chain is moving slow but it is moving now.

We believe that you need to put 'staking=0' in the controller mojocoin.conf file and in the masternode.conf file:
alias <space> address <space> genkey output <space> outputs output <space> index number of outpus (usually 0 if single)

You have 200k collateral for both if you check the block explorer, the -0 and -1 is the output index number for the Tx hash, sorry read that wrong, I dont think the staking=0 affects the MN

Write me a method or link to a method

They don't split the collateral as before, what did you do diffrently

That's exactly what I want, who is running the Russian MN because it appears to be very stable and there may be some little things in the way it has been set up
ED: If one of you are able to run a MN as the three above contact me and prove that you run one (sign a message) I will contribute 200k collateral for you run another if you provide a method for how you set it up

All these MNs

root@mojo01:~/mojocoin/mojocoin/src# ./mojocoind masternode list
{
    "a0743510dc19b802aa47969c3f4e8e76cd6b1f38d60e1c7d12e58991c6c919b4-0" : "ENABLED",
    "da977953b56dd0ba52704adb51668312eeea8c8795c07135da2b85012d8a2245-0" : "ENABLED",
    "062a8afbb689a54ad271f48124002e3e3b3a5d16c79cec92389b7f346d623bd7-1" : "ENABLED"
}
root@mojo01:~/mojocoin/mojocoin/src#

are now beyond 24 hours and appears ok, any comments?