if you want to fix this
revert code back to that market version.
update protocol every time you make a change.
you should revert version and pump protocol to 70001
atleast generate new key pairs to alert/checkpoint code.
(there are still 2 key pairs for spork and masternodes)
now the keys are in hands of icm, he can destroy the coin at this point if he wants.
Interesting... Could you please explain what this means? What do the 2 key pairs for spork and masternodes signify?
If ICM destroying the coin is indeed the danger, then I think these keys are a million times more important than changing the algorithm and forking Crave to be PoW, which I think is completely unnecessary.
But what would make this dev more trustworthy than ICM if the problem is the same - one person holds all the keys to destroy a coin? ICM may or may not be gone, but he at least made me a lot of money and never wasted my time. This dev made me lose over 1 BTC worth of Crave and has shown extremely erratic judgment (Nothing personal, he is probably very intelligent, but it will take a lot to regain my trust).
My erratic judgement is due to my panic problem.... I tend to panic (a lot)
I will solemnly try to gain back your trust. The keys were not changed because we thought there was no immediate risk...
If we change key(s), who will hold and keep them safe? Doesn't sound like a decentralized solution if one key holder can disrupt the system by activating an alert. Maybe this alerting functionality should be disabled or limit its capacity to disrupt the system. I don't think it was intended to keep this public alerting feature on or active after a coin matures but we have many version before Crave is mature.
I think adding the following functionality will help Crave:
1) Masternode consensus voting using a blockchain (like Dash). Proceeds used for dev direction and funding foundation projects.
3) Reputation System for the Urge market.
2) User name generation for the Urge market (charge a fee to create a name and own the key)
4) VanityGen so we can prefix our wallet addresses
5) HTML5 UI for the entire wallet.
I will be implementing all these for another coin but it will take me a LONG time by myself.