Sunsetting Zebra V1
Learn more about how Zebra V1 was developed — and why we've decided to sunset it.
Last updated
Learn more about how Zebra V1 was developed — and why we've decided to sunset it.
Last updated
Our secure messaging platform is blueprinted with a Signal Java Server v12. The most modern in servers with a huge developer community behind. In time the servers will unbind to Hetzner post MVI 2.0 to strengthen our anonymity promise. Product feel is very important for us. We wanted to make sure the user interface has its own identity compared to its predecessors.
For MVI 1.0 we are using Electron for our Desktop Client. We picked a client first because it’s the most reliable for a secure and timely manner release. Once on the client website, a prompt to sign up will appear with either Wallet Connect, Metamask , Rainbow Kit, or also Coinbase Wallet.
Security of our application is important and people who have malicious intentions are stopped ahead of time. Not just any wallet is allowed to connect. Partners such as Ator, CSwap, & AIGPU community will have free accessibility to our application on day 1. A freshly made wallet that holds no zKML or the projects above will be barred network entry and account creation.
In the early vision of Zebra, we considered requiring wallets to have transactional proof of use in order to access the platform. This approach was intended to align with the ethos of real network participation and anti-sybil measures.
However, in the interest of wider adoption and smoother onboarding, we’ve decided to remove that requirement.
Instead, we’ve introduced email-based signup/login — fully encrypted and privacy-respecting — to make access more flexible, especially for non-crypto-native users.
This change allows us to reach more people, while still staying true to our core: privacy, security, and user sovereignty Learn more about Zebra V2 below