Standard representation of asset ownership vs token

If you have a token of, say MYTOKEN, we refer to it with capitalized letters. We’re lucky to have this standard as it makes XCP tokens stand out across crypto.

Since there is a unique “mytoken” asset ownership independent of the MYTOKEN tokens, I wonder how best to reference it in the least confusing way?

One way could be to use lowercase with a domain extension, e.g.
mytoken.xcp
or
mytoken.btc

Perhaps @ would be better?
mytoken@xcp
or
mytoken@btc

Then, of course, there are subasset owneships:
mytoken.subasset@xcp
or
mytoken.subasset@btc

Since subasset are case-sensitive, it could make sense to apply a soft rule that only low caps are allowed for aliases. That’s how namecoin domain works. On the protocol all three are allowed; d/bitcoin, d/Bitcoin, d/BITCOIN but only d/bitcoin is a standard .bit domain.

This is only brainstorming from me at this point. Curious to hear what you think.

1 Like