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.
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
Good ideas! Appreciate the feedback!
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"?
there's always room for exxtras!
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.
Planning to poach one or two slots for quiet ipfs notifications,
but far too distant to even consider much at the moment.
cheers !
