What I'd like to see to take this a step further is build a standardized JSON format that can be used irrespective of the codebase. (Similar to how ETH does it). This way we could implement wallet providers in entirely different codebases that are still interoperable without complicated translations or "glue code" between the SDK and a domain specific implementation. A practical example of this is I have a desktop app that uses Hive Auth RPC (tm), and a website that wants to use the desktop app for authentication/signing. The SDK (within browser) already understands the format the desktop app uses and interoperability is trivial once communication is setup. This shouldn't be too complicated to do and would work well along side other projects needing to do a similar thing.
You are viewing a single comment's thread from:
💯