> For the complete documentation index, see [llms.txt](https://zkml.gitbook.io/zkml/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zkml.gitbook.io/zkml/products/zebra/sunsetting-zebra-v1.md).

# Sunsetting Zebra V1

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.

## Stack used :

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. \
\
\&#xNAN;***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.***<br>

## 🔄 Change of Access Model

**In the early vision** of Zebra, we considered requiring wallets to have <mark style="color:blue;">**transactional proof of use**</mark> in order to access the platform.\
This approach was intended to align with the ethos of **real network participation** and <mark style="color:blue;">**anti-sybil**</mark>**&#x20;measures**.

<mark style="color:blue;">However</mark>, in the interest of **wider adoption** and **smoother onboarding**, we’ve decided to **remove that requirement**.

Instead, we’ve introduced **email-based signup/login** — <mark style="color:blue;">fully encrypted</mark> 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** :point\_down:

{% content-ref url="/pages/C4IB6BnQgxrtVpryaKjE" %}
[Zebra V2: Back in Stripes](/zkml/products/zebra/zebra-v2-back-in-stripes.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://zkml.gitbook.io/zkml/products/zebra/sunsetting-zebra-v1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.