macgirvin at

It is currently and that's a known issue. I've got a few ideas for solving it, but time is short and it's doubtful I'll finish this while I'm still alive.  Basically do the same thing for identity hashes that we do for location. You can have more than one keypair and more than one resultant hash. In most cases we'll keep the old one and add additional hashes using the new key, but if you've been hijacked, you can choose to nullify one. The only trick is making sure that you're nullifying it and not the bad guy.  You can keep an offline private key to do this and prove you're the true account holder, but now you're getting into territory that average humans won't be able to grasp and will find too cumbersome or fiddly to deal with. 

Christopher Allan Webber likes this.

Christopher Allan Webber shared this.

Key change is implemented. Testing now. Bugger off.

macgirvin at 2017-07-25T02:14:41Z

Christopher Allan Webber likes this.

Any details on the decisions you made in implementing??

Christopher Allan Webber at 2017-07-25T02:42:11Z