Quote from: CovenDev on July 01, 2015, 02:03:54 PM

Quote from: wurstgelee on July 01, 2015, 12:33:28 PM

Quote from: CovenDev on July 01, 2015, 10:29:54 AM

But what do you mean "turn on POW".. Proof of Work ended with mining , bit confused here.

That means: Fork the current codebase to reenable PoW (probably with a low reward to not unneccessarily bloat coin supply) at current chain height to get it moving again.

Once again:

There is no need for manually sending wallet.dat files to you and no need for you manually transferring coins as well. Take a snapshot at a certain height of the COV1 chain and simply premine the amount each address holds to the same addresses in the new COV2 chain.

- Ensure that the current priv/public keypairs are still valid in the new COV2 chain when taking that approach.
- Ensure that all COV markets on exchanges are halted (disabling wallets is not sufficient for obvious reasons) prior to taking that snapshot.
- Check with the exchanges if they would follow that approach - if not give people enough time - with a moving COV1 chain - to transfer their COV1 coins to local wallets prior to taking the snapshot.

Very well; if this is what you guys want, I'll do so.

It's one approach.

Or update the codebase with a hard fork while keeping the current chain. That would be even better and comes with a lot less administrative overhead. As richie said wrote earlier, bittrex could simply update the bittrex wallet then.