|
| 1 | +name: Zynexa |
| 2 | +categories: |
| 3 | + - infrastructure |
| 4 | +usecases: |
| 5 | + - operating-systems |
| 6 | +ecosystem: |
| 7 | + - solana |
| 8 | +description: >- |
| 9 | + We use client-side encryption, private Solana routing, and a decentralized |
| 10 | + identity system so every action and every piece of data stays fully in the |
| 11 | + user’s control. All information is processed locally, never stored on |
| 12 | + centralized servers, and cannot be accessed by anyone except the user. |
| 13 | +
|
| 14 | + Zynexa is a privacy-first operating system for Web3, offering encrypted tools, |
| 15 | + wallet-based login, and more private on-chain interactions. Users choose |
| 16 | + Zynexa because it gives them complete control over their identity, |
| 17 | + communication, and data in the simplest and most secure way. |
| 18 | +product_launch_day: 2025-12-22T17:00:00.000Z |
| 19 | +nickname: ruggedon |
| 20 | +sunset: false |
| 21 | +assets_used: |
| 22 | + - sol |
| 23 | +have_token: false |
| 24 | +tokens: [] |
| 25 | +links: |
| 26 | + web: https://zynexa.io/ |
| 27 | + blog: "" |
| 28 | + github: https://github.com/zynexalabs/zynexa-core |
| 29 | + forum: "" |
| 30 | + docs: https://docs.zynexa.io/ |
| 31 | + whitepaper: "" |
| 32 | + block_explorer: "" |
| 33 | + governance: "" |
| 34 | + twitter: https://x.com/Zynexaproject |
| 35 | + discord: "" |
| 36 | + telegram: "" |
| 37 | + lens: "" |
| 38 | + farcaster: "" |
| 39 | +project_phase: mvp |
| 40 | +project_status: |
| 41 | + live_status: true |
| 42 | + mainnet: false |
| 43 | + testnet: false |
| 44 | + version: mvp |
| 45 | +blockchain_features: |
| 46 | + opensource: true |
| 47 | + upgradability: |
| 48 | + enabled: false |
| 49 | + asset_custody_type: non-custody |
| 50 | + encryption: We use a combination of modern cryptography and privacy |
| 51 | + technologies, including Ed25519 (Curve25519) for secure signatures, BIP-39 |
| 52 | + mnemonic wallets, and NaCl Box (Curve25519) end-to-end encryption to protect |
| 53 | + user data. Our communication layer is secured using X3DH key exchange and |
| 54 | + the Double Ratchet Protocol, ensuring forward secrecy and private messaging. |
| 55 | + For on-chain privacy and identity abstraction, we integrate ZK-SNARKs, |
| 56 | + allowing users to verify actions without revealing sensitive information. |
| 57 | + Together, these technologies create a fully private environment where |
| 58 | + identity, messages, and interactions remain secure and unlinkable. |
| 59 | +storage: {} |
| 60 | +privacy_policy: |
| 61 | + defined: false |
| 62 | + link: "" |
| 63 | + data_usage: We do not use or resell any user information. No tracking, no |
| 64 | + analytics, no data gathering. All sensitive data stays on the user’s device, |
| 65 | + and nothing is stored or processed on our servers. |
| 66 | +compliance: "" |
| 67 | +tracebility: |
| 68 | + kyc: false |
| 69 | + tracked_data: We do not collect personal data such as IP addresses, location, |
| 70 | + e-mail, or identifiers. All encryption keys and sensitive information stay |
| 71 | + on the user’s device. The only thing the system interacts with is the user’s |
| 72 | + wallet address, strictly for authentication — and even that is not stored or |
| 73 | + linked to any activity. In short, we collect no personal data, store nothing |
| 74 | + on servers, and everything remains fully client-side and private |
| 75 | + sign_in_type_requirments: |
| 76 | + - seed |
| 77 | +default_privacy: false |
| 78 | +audits: [] |
| 79 | +third_party_dependency: "" |
| 80 | +social_trust: "" |
| 81 | +technical_spof: "" |
| 82 | +team: |
| 83 | + anonymous: false |
| 84 | + teammembers: [] |
| 85 | +funding: [] |
| 86 | +history: [] |
| 87 | +id: zynexa |
0 commit comments