Re: [ANN][COVEN]|33k.7 Supply|HexNode|StealthMsging|Multisig|SmartX|IoT|I2P|TOR|COV2
Quote
If you think I'm being out of line, the solution to this with the assistance of Bittrex would be like so.
1)Hey Bittrex; how many coins do you guys hold?
Bittrex XX,XXX
Okay, please update new codebase/wallet/provide new wallet address
Bittrex: Updated, heres addresss
Great, here are the new coins
Just take a snapshot at a given blockheight, and premine the new coins to the addresses that have funds. It takes no manual work at all on either your part or the coin holders.
And that is how it's done, dev - simple and clean. No need for sending wallet.dat files anywhere.
PS: Ensure that the current COV1 public/private key combos are still valid for COV2 when doing that. Also take care of trading to be halted on exchanges prior to taking the snapshot for the premine of COV2 (for obvious reasons).
@ bittrex/riechiela: As for the coins still deposited @ bittrex: So the COV addresses currently associated to bittrex accounts will also be associated for COV2 when taking this approach, right?
Unfortunately not, which is why I requested he turn it PoW so people can move coins out... Addresses are not associated with users.
To explain why it is so difficult, imagine that we have to keep track of all deposits/withdrawals, all addresses/privkeys, all associations between the current wallet and the trades that occur. New wallets mean new addresses with the same symbols. Its an extremely complicated task to back everything up and keep the same symbol so it jives with new and old addresses. That said, if you created a new wallet that was completely backwards compatible (ie with the wallet.dat file without needing me to import privkeys), it would be a trivial step to just upgrade the wallet.
I've tried to provide as much help and as many options as I can to help with this swap. I'm not a fan of taking a fee to perform swaps, but you have to understand that it is a time consuming and error prone process.
Thanks,
Richie
Oh right, I missed the part where you mentioned the need to move out coins.
I imagined you would probably simply dump all privkeys of the current wallet and batch import them into the new COV2 wallet if the keypairs were still valid. Plus some dirty SQL inserts and update statements. I haven't really thought this through, especially considering I only can imagine how your database model might look like. And my imagination is probably far off.
Afaik the chain was working fine with PoS prior to the wallet lock @ bittrex (or still is I assume), if I am not mistaken? If so reenabling PoW wouldn't even be neccessary.
Updating the sources to a new codebase with a hard fork (and not with a coins swap to a new chain) would have been my choice in the first place as I wrote earlier in this thread - but I am not the dev here.
