Early Access·Live now
Z-Text|Powered by zk-SNARKs & BitcoinZ Blockchain

Speak FreelyForever

An end-user messenger that delivers messages through BitcoinZ shielded transactions — AES-256-GCM encrypted on-device, metadata hidden by zk-SNARKs, and designed for censorship-resistant communication.

No phone number
No central message servers
No censorship
Chats
1.00349
Search conversations...
All
Work
Friends
Family
Barbara9:41
I love this app so much right now 😭❤️
2
Rok9:32
Best payment app I never knew I had 😂
Cryptoqueen9:22
Safe travels! Nobody will know 🕵️
1
Marcelus8:55
Blockchain vault > cloud vault, no debate
CryptoRex8:41
Free speech AND free money. Can't stop either 🌍
3
Haruto8:15
Wait you just sent me money mid-conversation?! 🤯
Chats
Contacts
Wallet
AES-256 + zk-
Authenticated encryption plus shielded metadata
No IP Logging
The app itself keeps no IP logs
1–5 sec
Average delivery time
On-chain
Encrypted, recoverable from your seed
Verify, don't trust

Don't take our word for it

Z-Text's core claims are public and checkable. Here's how to confirm them yourself in under a minute.

Read the threat model

See exactly what Z-Text defends against — and what it can't. Published in full, no hand-waving.

Read security docs

Verify the bounty on-chain

A 7 ZEC bug-bounty pool, funded at a public address. Check the balance on any explorer.

t1bV6TkNwWBGBPtGhJCNEQZChpGVivHhHGEView on explorer

See how it works

Install, create a wallet, send a message — no phone, no email, no server. Follow the walkthrough.

Getting started

Why Ztext?

Built from the ground up for one purpose: unstoppable, private communication.

No central message servers

Messages route through decentralized BitcoinZ nodes — no company can read, store, or delete them. No central point of failure.

No phone number

Your identity comes from your wallet seed. No SIM, no phone number, no tracking — true anonymity.

No IP logging

zk-SNARKs hide sender and recipient on-chain. The app keeps no IP logs, and recipients never see your IP. Add Tor for network-level anonymity.

Fully decentralized

There is no Z-Text server in the message path. If Z-Text Ltd vanished tomorrow, messaging keeps running on the public network.

Blockchain stored

Encrypted messages settle on the BitcoinZ blockchain. As long as the network exists, your history restores from your 24-word seed on any device.

AES-256-GCM encryption

Two layers per message: AES-256-GCM authenticated encryption on your device, plus Sapling-family shielded transactions on BitcoinZ.

Quantum-resistant

No persistent public-key exposure for shielded identities, plus AES-256 payload encryption — Grover-safe at roughly 128-bit effective security, shrinking known quantum attack surfaces.

Spam resistant

Your Z-address is shared only when you choose — never listed, scraped, or sold. Messaging needs a mutual cryptographic handshake, and each message costs ~$0.00003 on-chain: invisible to you, too expensive for bots to scale.

Panic mode

An emergency PIN wipes keys, messages, and contacts in one action. Stealth mode re-skins the app so it doesn't look like a messenger — for when privacy is life or death.

On-chain vault

No signup, no email, no cloud. Credentials are AES-256-GCM encrypted on-device and derived from your seed — restore on any device with your 24-word mnemonic. Your seed, your data.

About the Protocol

Z-Text, BitcoinZ, and zk-SNARKs

Z-Text is the messenger client and application-layer protocol. BitcoinZ is the base blockchain network used for shielded transaction delivery and settlement. zk-SNARKs are the zero-knowledge proof system used by shielded transactions to hide transaction metadata. Z-Text is not a separate layer-2 chain: it writes encrypted message payloads through the BitcoinZ shielded transaction layer.

Technical Specifications

Product type

Privacy messenger application

Z-Text client and messaging protocol

Base network

Layer-1 blockchain settlement

BitcoinZ blockchain

Privacy layer

Sender, receiver, and amount shielding

Sapling-family shielded transactions using zk-SNARK proofs

Payload encryption

Local end-to-end message encryption

AES-256-GCM authenticated encryption before broadcast

Key exchange

Recipient-only decryption

X25519 contact key exchange

Identity model

No phone number or email identity

Shielded z-address generated from the wallet seed

Message delivery

Near-real-time encrypted delivery

G-stream mempool push, typically 1–5 seconds before block settlement

Message network fee

Economic spam resistance

Approximately $0.00003 per on-chain message at current BTCZ fee assumptions

Storage model

No central message database

Encrypted payloads settle on the BitcoinZ blockchain

Recovery model

Self-custodial recovery

24-word seed phrase rescans wallet, messages, contacts, and vault data

Trust Model

Trust nobody — pick your tier

Three privacy tiers, your choice. Each tier moves the trust boundary closer to you. Signal, WhatsApp, and Telegram architecturally cannot offer the self-hosted tier — there is no protocol-level option for the user to remove the company from the loop.

Default

Official lightd

Connects to the official lightd server.

What lightd sees

A shielded transaction was submitted.

What lightd cannot see

Sender, recipient, amount, message content. zk-SNARKs hides all of it.

The message recipient never sees the sender's IP.

Tor

Official lightd over Tor

Same client, routed through Tor.

What changes

The lightd operator no longer sees the user's IP.

What still holds

Same shielding as Default — sender, recipient, amount, content remain hidden by zk-SNARKs.

Add Tor when the operator's view of your IP also matters to you.

Self-hosted

Your own lightd or full BitcoinZ node

User runs the server software.

What any third party sees

Nothing. There is no third party in the loop.

Including Z-Text Ltd

We have no visibility into your activity. There is no relationship to compromise.

Architecturally, Signal, WhatsApp, and Telegram cannot offer this tier.

Pick the tier that matches your threat model. You can switch tiers without losing your messages — the on-chain data is the same; only the path to it changes.

Why Not Signal/Telegram/WhatsApp?

Great apps, but they rely on centralized infrastructure. We identified 15 privacy failure points and measured 10 points of centralization — here's how each network compares.

15 Privacy Failure Points

Recipient never sees your IP (architectural)
Ztext
Signal
Telegram
WhatsApp
Session
End-to-end encrypted by default
Ztext
Signal
Telegram
WhatsApp
Session
No phone number required
Ztext
Signal
Telegram
WhatsApp
Session
Truly decentralized
Ztext
Signal
Telegram
WhatsApp
Session
No metadata collection
Ztext
Signal
Telegram
WhatsApp
Session
On-chain (recoverable from seed)
Ztext
Signal
Telegram
WhatsApp
Session
Recover ALL data from seed
Ztext
Signal
Telegram
WhatsApp
Session
Integrated crypto wallet
Ztext
Signal
Telegram
WhatsApp
Session
Economic spam prevention
Ztext
Signal
Telegram
WhatsApp
Session
Censorship resistant
Ztext
Signal
Telegram
WhatsApp
Session
zk-SNARKs privacy
Ztext
Signal
Telegram
WhatsApp
Session
Perfect Forward Secrecy
Ztext
Signal
Telegram
WhatsApp
Session
No separate token required
Ztext
Signal
Telegram
WhatsApp
Session
Open source
Ztext
Signal
Telegram
WhatsApp
Session
Quantum-resistant design
Ztext
Signal
Telegram
WhatsApp
Session
Privacy criteria addressed
Ztext15 of 15
Signal5.5 of 15
Telegram0.5 of 15
WhatsApp3.5 of 15
Session7 of 15
Supported
Partial
Not supported

10 Points of Centralization

Message routing
ZtextDecentralizedBlockchain
SignalCentralizedCentral servers
TelegramCentralizedCentral servers
WhatsAppCentralizedMeta servers
SessionDecentralizedService nodes
User identity
ZtextDecentralizedSeed phrase
SignalCentralizedPhone number
TelegramCentralizedPhone number
WhatsAppCentralizedPhone number
SessionDecentralizedSession ID
Key management
ZtextDecentralizedLocal only
SignalPartialSVR enclaves
TelegramCentralizedServer-held
WhatsAppPartialBackup keys
SessionDecentralizedLocal only
Message storage
ZtextDecentralizedOn-chain
SignalCentralizedServer queues
TelegramCentralizedCloud stored
WhatsAppCentralizedServer queues
SessionPartialSwarm nodes
Network discovery
ZtextDecentralizedP2P nodes
SignalCentralizedCentral directory
TelegramCentralizedCentral directory
WhatsAppCentralizedCentral directory
SessionDecentralizedDHT lookup
Push notifications
ZtextDecentralizedNot needed
SignalCentralizedGoogle/Apple
TelegramCentralizedGoogle/Apple
WhatsAppCentralizedGoogle/Apple
SessionCentralizedGoogle/Apple
Software updates
ZtextDecentralizedManual/F-Droid
SignalPartialApp stores
TelegramPartialApp stores
WhatsAppCentralizedApp stores only
SessionPartialApp stores
DNS / domain
ZtextDecentralizedNo domain needed
SignalCentralizedsignal.org
TelegramCentralizedtelegram.org
WhatsAppCentralizedwhatsapp.com
SessionDecentralizedNo domain needed
Payment / funding
ZtextDecentralizedCrypto native
SignalPartialDonations
TelegramPartialAds + premium
WhatsAppCentralizedMeta funded
SessionDecentralizedToken funded
Metadata protection
ZtextDecentralizedzk-SNARKs
SignalCentralizedSealed sender partial
TelegramCentralizedNone
WhatsAppCentralizedCollected by Meta
SessionDecentralizedOnion routing
Centralized components
Ztext0 of 10
Signal8.5 of 10
Telegram9 of 10
WhatsApp9.5 of 10
Session2 of 10

The trade-off — Z-Text is text-only — no files, pictures, or videos. Pure encrypted text. Only real secrets.

Want to Earn with Z-Text?

Join our ambassador program — share Z-Text with your community and earn crypto commission on every sale.

Become an Ambassador →