Create account

1862d
If in the future my account gets hacked, and someone creates malicious content.. How do I prove it was not me if my signature was used?

Suppose there's some existing laws in place to help determine this.

Anyway, just a shower thought.
SuperHacker
replied 1862d
Agreed, there should be a way to obsolete the old key and inherit data & relationships by the new key, in case of lost of old key.
replied 1862d
SuperHacker
replied 1860d
I've read, the design is awesome. And I have to suggestion.
1. Master keys should be able to store in cold storage. i.e. The keys we currently using in memo shouldn't be master keys.
replied 1860d
Yep, that is the plan
SuperHacker
replied 1860d
Some keys in memo may have been leaked by user.
SuperHacker
replied 1860d
2. Change prefix to other code, rather than 0x6d*. Because this protocol may become a infrastructure to identify indiviuals on chain, it is not only belonging to memo protocol.
replied 1860d
How is 0x6d less universal than another prefix?
SuperHacker
replied 1859d
Well, I thought 0x6d was designed as memo only protocols, though MIP-0003 seems more than a memo protocol. With further designing, 0x6d2[0-2] can be the infrastructure of PKI on BCH.
SuperHacker
replied 1859d
I think change 0x6d2[0-2] to a long prefix is better.
0x6d20 -> 0x6d2000
0x6d21 -> 0x6d2001
0x6d20 -> 0x6d2002
[0x6d2003, 0x6d20ff] = reserved for futher expantion about keys relation
replied 1859d
Good ideas! Appreciate the feedback!
ipfs-net
replied 1549d
related question
(currently working on script decoding)
- is the MEMO plan to span beyond the 6dxx space ?
The protocol seems to stick to 6d - is there room for "extras"?
replied 1762d
there's always room for exxtras!
replied 1860d
Glad to hear it :) If it makes sense or the 6d space runs out we will definitely expand beyond. We also plan to support other protocols.
ipfs-net
replied 1549d
Planning to poach one or two slots for quiet ipfs notifications,
but far too distant to even consider much at the moment.
cheers !
SuperHacker
replied 1862d
1.Using my privkey, set an addr as inheritor
2.When old memo pk get hacked, register a new account and import the inheritor key.
3.Use inheritor to announce the obsolete of old key.
SuperHacker
replied 1862d
4. All action sent by old keys should be ignored. Inheritor key inherit all the actions and relationships from old key.
Inheritor should be stored as cold wallet before it is actived.
SuperHacker
replied 1862d
If I wanna change my inheritor, current inheritor should announce the cancel first.
replied 1862d
Wish I could understand this. 🤔


Will show a friend. 👍
replied 1862d
Ha!

Well that sounds pretty nifty!
replied 1862d
The same way you ought to prove somebody got your home keys and stole your stuff, and it wasn't you who stole your own shit. Insurance have thing in place for this.