Frequently Asked Questions (Protocol & Security FAQ)
Clear, honest answers regarding ZChat’s WebRTC architecture, zero-database memory models, $ZCHAT tokenomics, security boundaries, and audit roadmaps.
1. General Access & Architecture
Do I need to create an account or provide a phone number to use ZChat?
No. ZChat requires zero registration, no telephone numbers, no email addresses, and no passwords. When you open the terminal at zchat.live, an ephemeral cryptographic identity is generated locally in your browser memory.
Which web browsers and operating systems are supported?
ZChat runs natively on any modern browser supporting WebRTC standards: Google Chrome, Mozilla Firefox, Apple Safari, Microsoft Edge, Brave, and Opera across Windows, macOS, Linux, Android, and iOS. No app download or browser extension is required.
How do I start a conversation with someone?
Simply open the terminal, click “Create 1-on-1 Invite” or create a timed “Burner Room”, and copy the unique invitation ticket link. Share that link with your friend or counterparty via any external channel. Once they open it, your browsers establish a direct P2P connection.
2. Privacy, Cryptography & Threat Model
Does ZChat store my messages or media files on a server database?
No. Unlike standard messaging platforms, ZChat operates with zero central database storage for messages. Data packets travel directly peer-to-peer via encrypted WebRTC DataChannels. In-memory message states reside exclusively in volatile browser RAM and are completely destroyed when the room timer expires or when you close the tab.
What data does the signaling server see?
The signaling server facilitates initial network handshakes. It observes:
- Client IP addresses (required for TCP/WebSocket connections).
- Connection open and close timestamps (for sliding-window rate limiting).
- Session negotiation data (SDP offers, SDP answers, and ICE candidate network mappings).
The signaling server cannot see message text, image attachments, or audio/video streams, nor does it hold decryption keys.
Can my chat partner see my IP address?
Yes. Direct WebRTC connections require peer browsers to exchange packets directly, exposing public IP addresses to connected peers unless a VPN or TURN relay is used. If peer-level IP privacy is required, you must route your connection through a reliable VPN or Tor proxy prior to entering a room.
What does the Panic Wipe feature do?
Pressing the Esc key three times in rapid succession immediately severes all WebRTC channels, flushes all message history from browser memory, and redirects your browser to an external website.
3. $ZCHAT Tokenomics & Utility
What is the $ZCHAT token and what is its supply?
$ZCHAT is a fixed-supply utility token pre-deployed on Polygon PoS at address 0x9D9fefb494EA7cc2a3FE18D8CEF3dD198c172bEE with a strict non-mintable cap of 100,000,000 tokens. The token is designed for protocol utilities: escrow fee discounts, relay node rewards, token-gated room admission, and governance signaling.
Is $ZCHAT an investment or security?
No. $ZCHAT is strictly a cryptographic software utility token. It conveys no equity, ownership, dividends, or profit shares in any enterprise. Token acquisition involves significant volatility and risks. Please read our Risk Disclosure.
What are the public presale terms?
40,000,000 $ZCHAT (40% of total supply) is allocated for public presale, with 50% unlocked at TGE and 50% vesting linearly over 60 days.
4. Escrow & Security Audits
Is on-chain escrow currently live on mainnet?
No. The Solidity smart contract code is developed (ZChatEscrow.sol), but multi-chain on-chain deployment across Polygon and Base is scheduled for Phase 3 (Q1–Q2 2027) Planned.
What is the current cybersecurity audit status?
The protocol is currently not yet audited by an independent third party. An external smart contract security audit and bug bounty program are scheduled for Phase 3 (Q1–Q2 2027) Planned.
How is DEX liquidity locked?
Post-presale QuickSwap liquidity will be locked under transparent smart contract terms: Locker Provider {{TODO_LIQUIDITY_LOCK_PROVIDER}}, Lock Duration {{TODO_LIQUIDITY_LOCK_DURATION}}, and Treasury Address {{TODO_TREASURY_WALLET_ADDRESS}}.
Still Have Questions?
Reach out to our core team directly or inspect the source code: