01 Executive Summary
Valygo Chat (VyoChat) is a wallet-native messaging application for the Valygo ecosystem. Users sign in with a supported crypto wallet — no traditional username or password required — and can message others by wallet address or readable .vyo name.
The mobile app (iOS and Android) implements top-level end-to-end encryption (E2EE). Messages, media, and voice notes are sealed on the user’s device before transmission. Valygo servers store and route ciphertext only — not readable message content.
Recent product updates include voice notes (hold-to-record, encrypted like messages) and profile photos (avatars in chat lists and contact info, tied to wallet identity).
02 Product Overview
Valygo Chat is designed for private, real-time conversation between wallet identities:
- Wallet login via WalletConnect-compatible wallets (MetaMask, Rainbow, Trust, Coinbase Wallet, and others)
- Real-time text messaging with optional device PIN lock
- Multimedia sharing: photos, videos, files, and contact cards
- Voice notes — encrypted audio messages in chat
- Profile photos — user avatars visible in chat lists and contact screens
- Voice and video calling from within conversations
- Optional .vyo domain names for human-readable identity
The primary E2EE security stack described in this document applies to the Valygo Chat mobile app (ValygoChatApp on iOS and Android). Browser extensions provide wallet messaging access but may not expose the full encryption feature set until equivalent client support is available.
03 Top-Level E2EE — Sealed Messages
End-to-end encryption means only the sender and intended recipient devices can read message content. Valygo cannot decrypt user chats. The implementation follows a seal → transmit → open model:
Zero plaintext on Valygo. Our infrastructure is designed to never hold readable copies of message text, photos, videos, voice notes, or file contents.
What “sealed” means technically
- Each device generates an X25519 encryption key pair stored locally on the phone
- Public keys are published so peers can encrypt to the correct wallet devices
- Outgoing content is sealed into ciphertext envelopes before API upload
- The server persists
encryption: e2e_v1payloads — scrambled data, not readable text - Photos, videos, files, and voice notes follow the same sealing model as text
Progressive encryption (compatibility)
Newer app versions support stronger session features (multi-device wraps, forward secrecy via ratchet sessions, and X3DH setup when both peers publish prekeys). When chatting with an older client that has not published prekeys, the app automatically falls back to classic single-device wraps so messaging continues to work across app versions.
04 Security Architecture
| Layer | What it does |
|---|---|
| Device keys | Per-device X25519 key pairs; up to 5 devices per wallet can publish keys for multi-device delivery. |
| Sealed messages | Text sealed on device; server stores ciphertext only. |
| Sealed media | Photos, videos, files, and voice notes encrypted before upload. |
| Safety codes | Numeric fingerprint derived from both parties’ public keys; users verify out-of-band and mark contacts as checked. |
| Key-change detection | If a contact’s encryption key changes, the app warns before sending until the user accepts the change. |
| Wallet-linked lock | Optional one-time wallet signature binds the device encryption key to the user’s wallet address. |
| Recovery backup | Password-protected export of device keys; user saves locally — never auto-uploaded by Valygo. |
| Device PIN | Optional local app lock; PIN never leaves the phone. |
| Call E2EE | Voice/video calls can use LiveKit end-to-end encryption when both sides support it. |
05 Chat Privacy & User Controls
The mobile app includes a dedicated Chat privacy & locks screen (Settings) with plain-language controls:
- Link lock to my wallet — prove your encryption key belongs to your wallet (one-time signature)
- Save a backup — export a password-protected recovery kit you store yourself
- Restore from backup — import keys on a new phone with the same password
- Safety code guidance — how to verify contacts from Chat info
- Simple privacy guide — what is protected and what still depends on the user
Per-contact safety codes are shown in Chat info. Users compare the code with their contact through a trusted channel (call, in person, etc.) and tap Mark as checked when it matches.
06 Voice Notes & Profile Photos
Voice notes
Users can hold the microphone control in any chat to record a voice note. The recording is treated like other message content: sealed on device before upload, delivered as ciphertext, and played inline in the conversation after decryption on the recipient’s phone.
Profile photos
Users can set a profile photo from Settings. Avatars appear in the chat list, conversation headers, and contact info screens — linked to wallet identity rather than a phone number or email. Contact profile images help users recognize peers in a wallet-native address book.
07 Encrypted Voice & Video Calls
Valygo Chat supports voice and video calls initiated from any conversation. When both participants use a recent mobile app version with published encryption keys, calls can use end-to-end encryption via LiveKit — a per-call secret derived from both peers’ keys and the call identifier. Call signaling may pass through Valygo/LiveKit infrastructure, but encrypted call media is not readable by Valygo when E2EE is active.
08 Safety Tools in the App
The mobile app includes user safety controls accessible from the chat list:
- Long-press a chat to open options: Report user, Block user, or Delete chat
- Delete chat removes the conversation and clears local cached messages; starting again begins fresh
- Block removes the peer from the user’s chat list
- Report notifies moderators for review
- Inside a chat, users can delete individual messages for themselves or (when sender) for everyone
These moderation tools are part of the Valygo Chat mobile app experience on iOS and Android.
09 Scope & Limitations
Valygo Chat E2EE is strong device-to-device protection, but users should understand honest boundaries:
- Not full Signal/libsignal — Valygo implements its own E2EE stack with progressive envelopes; it is not the Signal Protocol.
- Server metadata — Wallet addresses, delivery timing, and routing metadata may still exist for message delivery.
- Unlocked phone — Anyone with access to an unlocked device can read on-screen content.
- Device compromise — Malware or spyware on the phone is outside the scope of chat encryption.
- New device without backup — Historical messages may not decrypt on a new phone unless the user restored a recovery backup.
- Push notifications — Production defaults may include sender identity in push payloads until sealed-push mode is enabled across all clients.
- Network blocking — Censorship or connectivity issues may prevent the app from connecting in some regions.
10 Legal Disclaimer
This white paper is a public summary document produced by VALYGO Labs LLC for informational purposes only. It does not constitute financial advice, investment advice, legal advice, or a solicitation to buy or sell any financial instrument or digital asset.
Security descriptions reflect the Valygo Chat mobile application architecture as of the document version date. Features, encryption modes, and availability may evolve. Users are responsible for keeping the app updated and for safeguarding their wallet, device PIN, and recovery backup passwords.
Users must comply with applicable laws in their jurisdiction. Valygo Chat may not be available or appropriate in all territories.