Someone bring me up to date on why not having the alert keys is a huge issue? I thought it just did alerts? Is there an embedded kill switch?
Also, whats so hard about just making a new set of keys and recompiling?
JJ
I can fork the source with a new alert key, if that's the issue. Just would need someone to build it, as I don't have a machine setup to build wallets right now.
i would ask if cryptovote wants to help.. he can do all needed things.
yes you can stop the network holding the keys. but that can be by passed with config file.
people who compile their own client can remove(change) the pubkey, and have clients safe
Thank you guys
just to say there is more things to fix at craves current code..
some files are not uptodate and safe.
niitassin did not find those and did not fix it.
i think there is only one dev who i can name who knows what is the issue...
he is playing with similar coin, way more safe one.
but his coins has issues of his own, not related to crave.
(that is not 8-bit dev who am i talkning about)
other good devs seems to be not so interested about masternode code,
and i see the reason why not.