This is a thought experiment to see how an application protocol like Memo.cash could migrate to using the Bitcom decentralized prefix scheme.
bit init
bit useradd
which sends the following OP_RETURN (Note: all in UTF8) thereby registering the app on the Bitcoin blockchain:
OP_RETURN $ useradd [ADDRESS]
bit echo nemo to name
bit echo https://nemo.cash to website
which creates the following OP_RETURN:
OP_RETURN $ echo nemo to name
OP_RETURN $ echo https://nemo.cash to website
memo.cash uses 2 byte prefixes starting with 0x6d
, such as:
OP_RETURN 0x6d01 Johndoe
OP_RETURN 0x6d02 Hello
With the new Nemo scheme, assuming that the generated address was 17yyXL4raLZFU95ixkRESa2ZBPSSYxSsS5
, it would be:
OP_RETURN 17yyXL4raLZFU95ixkRESa2ZBPSSYxSsS5 0x01 Johndoe
OP_RETURN 17yyXL4raLZFU95ixkRESa2ZBPSSYxSsS5 0x02 Hello
The only thing that's changed is:
- Added the address as prefix
- stripped out the
6d
because the address will uniquely identify the protocol from now on.