Web3.0 is not only about blockchain, because there are many parts of Web3.0 are not use blockchain technology. A simple example, peer-to-peer encrypt email/message system is the most important part of Web3.0, but it’s not a blockchain use case. Another example, password-less login system (like webauthn from W3C) is also the most important part of Web3.0, but there is no blockchain elements inside.
Blockchain is not only about EVM-compatible. It couldn't be more obvious even if EVM-compatible has the most powerful ecosystem at this time. Bitcoin, Litecoin even Dogecoin also has it’s own ecosystem, not to mention the new public chains that have a huge number of users, such as Flow, Solana etc.
If there is no MetaMask Protocol, there is no such prosperous EVM-compatible ecosystem. By MetaMask Protocol, users can easily access EVM applications through wallets which was a MetaMask-compatible. MetaMask Protocol is good enough for EVM-compatible ecosystem, but it’s only for EVM-compatible actually, it can not adopt to whole Web3.0 world. Other kind of Web3.0 applications also need some interface standards to be easy to use.
That’s why we design UniSign Protocol. We need such a protocol to coordinate all Web3.0 applications and all web3.0 private-key managers to build a prosperous Web3.0 ecosystem together.
We called it as Signer, which managing user’s private-key and implement all UniSign Protocol’s interface. UniSign Protocol defined a group interfaces and how Signers should implement it and how applications should use it. These interface includes two parts, one part describe how to sign messages, one part describe the current status of Signer. By these interfaces, Web3.0 application developers and private-key manager developers can easily work together.View Protocol Docs →
UniSign Browser Extension is a open-sourced simple implementation of UniSign Protocol. It’s aim to guide developers to develop their own product which implemented the UniSign Protocol. It’s audit by the security company - ShowMist.