Origin network protocol interoperability with other DApp Tokens #191
Description
If there's a token community that wants to leverage Origin's Protocols for its Marketplace, one piece of the ecosystem, what would be the way do so transparently for the users?
How an application that uses one token at the app layer can interact with Origin token at the protocol level. I am very interested in exploring it and making sense of tokenomics at the 3 levels:
Infrastructure uses Ether
Protocol uses Origin Token
App uses App Token
It's similar to gas UX topic/issue we have today in Ethereum where a user cannot pay gas with tokens, they need Ether, which is really lame from a UX perspective. I know of some efforts in the direction of letting the token operator pay the gas, but AFAIK they are very early in development and have difficult security challenges.
Perhaps in origins protocol mechanisms that can be taken into consideration, A standard way for other "token operators" to use origin in a way that still makes sense in tokenomically. Otherwise forking/implementing the protocol with your own token is probably what will end up happening.
I'm interested in exploring ways to support other ERC-20 tokens transparently so that Origin is usable on other token economies without forking. Perhaps some sort of embedded DEX protocol or even a simple guidelines page for DApps developers with "recipes" to support other ERC-20 tokens at the DApp level.