DEV Community: ztext_zksnarks

Z-TEXT: Blockchain Password Manager, No Server to Hack

ztext_zksnarks — Tue, 11 Aug 2026 08:48:09 +0000

Every password manager stores your vault somewhere. Z-TEXT stores it on the BitcoinZ blockchain — with no company server in between.

Where does Z-TEXT actually store passwords?

Directly on the BitcoinZ blockchain, not on a company's server. Each vault entry is encrypted twice before it's written: once with a key derived from the wallet seed, once with the master password. Both layers have to be broken to read a single entry. There's no database anywhere holding passwords in one place, because the blockchain itself is the storage.

How is this different from Proton Pass or Bitwarden?

Proton and Bitwarden are excellent — but both still store encrypted vaults on their own servers. One breach of that server exposes every user's vault at once, even if each entry is individually encrypted.

Z-TEXT shields vault data directly on the BitcoinZ blockchain using zk-SNARKs zero-knowledge proofs. Even someone examining the exact block sees only that a transaction happened — not what's inside it.

What happens if you lose your phone?

Restore the wallet from the seed phrase on any device, and the encrypted vault comes back automatically — it's already on the blockchain, waiting. Enter the master password, and everything decrypts. No cloud account, no sync service, no export file to remember separately.

The trade-off

No browser extension, so no auto-fill in Chrome or Safari. In exchange, there's no bridge between the browser and the vault — the exact connection point malicious extensions and autofill-phishing attacks exploit in other password managers. A BTCZ wallet needs to be running to use the vault.

Architecture summary

	Cloud password managers	Z-TEXT
Storage	Central company server	BitcoinZ blockchain
Breach exposure	All users at once	No central point to breach
Encryption	Vault-level	Double: wallet seed + master password
2FA	Separate app usually	Built-in TOTP scanner
Browser extension	Yes (attack surface)	None (no bridge to exploit)

Full breakdown: https://z-text.org/blockchain-password-manager-no-server-2026/

Originally published at z-text.org

How We Fit a Messenger, Wallet, and Password Manager Into 482 Bytes

ztext_zksnarks — Sun, 09 Aug 2026 12:48:06 +0000

A BitcoinZ shielded transaction gives you exactly 512 bytes of memo space. No more, no less — it's a consensus rule, not a setting anyone can change.

After encryption overhead, you're left with 482 usable bytes.

That's the entire budget we had to fit a private messenger, a password manager, a BTCZ wallet, and broadcast channels into — for Z-TEXT, a zk-SNARKs blockchain messenger built on BitcoinZ. No server holds any of it. Here's what that constraint actually forced us to build.

1. Why 512 bytes, and why we can't change it

Z-TEXT doesn't own or control the BitcoinZ blockchain. BitcoinZ is an independent chain, live since 2017, and we build on top of it the same way any wallet builds on top of Bitcoin.

We could have built our own chain with any memo size we wanted. We didn't — we chose to build on an existing, independent chain, and that meant accepting its limits as-is.

Before any content is written, the encryption envelope takes its cut:

1 byte — version
12 bytes — encryption IV
16 bytes — authentication tag
1 byte — compression marker

30 bytes gone before a single character of content. What's left — 482 bytes — is the budget for every message, password entry, wallet transaction, and channel post.

2. The message pipeline

Every message goes through the same seven steps:

Packed — MessagePack, a compact binary format, with integer field keys instead of named ones
Signed — Ed25519, covering every field except the signature itself
Optionally compressed — only if it actually helps (more on this below)
Encrypted — AES-256-GCM, key derived only by the recipient
Framed — IV + ciphertext + auth tag
Versioned — one byte prepended, so the format can evolve
Sent — one 512-byte memo, one BitcoinZ shielded transaction

One deliberate ordering choice: we sign before encrypting, not after. Sign-then-encrypt means the signature is protected by the ciphertext. Encrypt-then-sign would let anyone holding the group's decryption key strip off the real sender's signature and forge their own — an open door we didn't want.

3. Making 482 bytes go further

Every one of these was measured, not assumed:

Technique	Replaces	Measured effect
MessagePack	JSON	~40% smaller
Integer field keys	Named keys	~15% smaller again
Sender address dropped	Address in payload	Free — recovered from the tx itself
Binary values kept binary	base64 text	base64 costs 1/3 more; 413B → 552B
Topic lists as positional arrays	Named-key maps	~half the cost per topic
128-bit tx references	Full tx IDs	Half the length, still unambiguous
Media as a reference	Inline media data	A GIF becomes a few characters

These aren't just optimizations — they're feature gates. Our Topics feature exists because positional arrays roughly halve the cost per topic. With named JSON keys, the topic list wouldn't fit in the memo at all, and the feature wouldn't exist.

4. Three bytes over the limit

This wasn't a hypothetical — it happened.

On August 3, we decoded a real community invite off a phone. 15 fields: viewing key, signature, address, epoch key, owner's public key, avatar, name, salt, timestamps. Payload: 430 bytes. Wrapped in the encryption envelope: 515 bytes.

The limit is 512. Three bytes over — roughly the width of the word "the."

The fix: strip the avatar and description from the invite (both arrive seconds later via the owner's identity broadcast anyway), re-sign. Result: 411 bytes, a 496-byte memo, 16 bytes of headroom.

What's worth flagging is what happened before the fix. An earlier version of the size-check code guessed the invite was 413 bytes and assumed it fit. The guess was 17 bytes light. The feature silently failed to send, the first time anyone used it.

There's now a test that measures the real byte count on every build. A guess can't make that call again.

5. Compression can make things bigger

Gzip-style compression costs roughly 23 bytes of overhead for headers and trailers. A channel invite is mostly a signature and random key material — data that's already high-entropy and effectively incompressible.

Compress that, and you don't save bytes. You add 23 bytes of overhead on top of data that didn't shrink. On the exact payload closest to the limit, that was enough to blow the budget and break the entire invite-sharing feature.

The fix: never assume. For every message, we check both compressed and uncompressed size, and keep whichever is smaller — recorded in a single marker byte.

6. When one memo genuinely isn't enough

Some things are just bigger than 512 bytes. A post-quantum public key is 1,184 bytes — more than double the budget. Those get split across multiple memos and reassembled.

The interesting design decision is in the failure case. Only the last chunk carries a signature, and that signature covers a hash of every chunk in order. A half-arrived key can never be accepted — not because we detect and reject it, but because it's cryptographically impossible for an incomplete key to produce a valid signature. The failure mode we're closing isn't "a chunk arrives late" — it's "a partial key gets trusted as real."

7. No server holds the moderation state

This is the part that took the most engineering: building Discord-style moderation — roles, bans, suspensions, pinned posts — with no server anywhere holding the authoritative state.

Every action (promote, ban, pin) is a signed instruction written into the same 512-byte memo space. Every client independently replays the full history of these instructions and arrives at the same state. Three things make that consistent:

A total order everyone agrees on — sorted by block height, then tx ID, then position within the tx. No clocks, no coordination.
Signed per-sender sequence numbers — a sender's own operations can't be reordered by a hostile relay.
A deferral fixpoint — if a device sees "user X promoted" before it sees "user X joined," it holds the operation and retries, rather than guessing or dropping it.

A community's identity is derived, not assigned — a hash of the owner's key, address, and a salt, recomputed by every joiner. And enforcement lives on the receiving side: a modified client can hide every restriction in its own UI, but it still can't make an unauthorized action stick, because every other honest client independently rejects it.

That's the property worth naming: Z-TEXT is censorship-resistant by construction, not by policy or promise.

8. Why this is hard to copy

A messaging UI can be rebuilt in a month. This can't — a competitor would need to redo the byte budget, the replay engine, the ordering rules, the deferral logic, and a backward-compatible wire format, before shipping a single user-visible feature.

One detail shows why it compounds: when we added Topics to Communities, the topic ID field is only written when it's non-zero. A post with no topic is byte-for-byte identical to a pre-Topics post. Every old signature still verifies — a protocol upgrade that cost existing users nothing.

It's also why we can now ship new capability without touching server infrastructure — every new feature is just a new signed operation running through the same replay engine. Channels, Awards, and Communities each took weeks, not quarters, because of this.

One open question we're actively exploring: AI agents will likely need the same thing people do — a way to act and prove it happened, without exposing the private data behind it. Whether this same architecture ends up serving that need is still open.

Full writeup with an infographic and video breakdown: https://z-text.org/482-bytes-of-freedom-2026/

Happy to go deeper into the replay engine, the Rust implementation, or the note-splitting mechanics in the comments if there's interest.

Telegram Channels Banned Today: Live Tracker (Aug 2025) - From Paria to King in 5 Minutes

ztext_zksnarks — Tue, 04 Aug 2026 08:23:04 +0000

Originally published on Z-TEXT — Live tracker updates daily at midnight.

🔴 LIVE TELEGRAM BAN TRACKER

Kazakhstan, Russia, Telegram itself - bans accelerating. Centralized = censored.

Live tracker: https://z-text.org/paria-to-king-5-minutes-banned-telegram-to-own-channel/

👑 PARIA TO KING — 3 STEPS in 5 Minutes

STEP 01 // 1 MINUTE // FREE — AMBASSADOR

Go to z-text.com/become-ambassador
Personal link → crowd 10% OFF, you get 15% in ZEC on-chain

STEP 02 // 30 SECONDS // $3 — KING

Zero Trace license — $3 / 1M messages
24-word seed = your channel, write on paper
No phone, No ID, No delete — BitcoinZ blockchain since 2017
ML-KEM-768 + ML-DSA-65 post-quantum sealed

STEP 03 // 2 MINUTES // 0.0002 BTCZ/POST — SHARE

Unlimited viewers forever
100% BTCZ to your wallet — No Stripe, No PayPal, No cut

🛟 FREE Refugee Slot (198 slots): https://channelist.org
👑 Ambassador: https://z-text.com/become-ambassador
🏰 Kingdom $3: https://z-text.com/packages

Banned on YouTube, Telegram, Patreon, X? I Built a Permanent Home on BitcoinZ Blockchain [198 Free Slots]

ztext_zksnarks — Fri, 31 Jul 2026 16:29:43 +0000

BANNED? DELETED? DEMONETIZED?

You lost your account. Not your audience.

One flag. One bot. One unread appeal.
100k subscribers — gone. 5 years of work — gone.
And they keep the email list.

Building on centralized platforms is renting. A single bot can nuke your presence.

The Problem: The Censorship Kill-Switch

Telegram, YouTube, Patreon, and X have the power to "nuke" your presence and keep your email list for themselves.

The Solution: Refugee Program

I opened 198 FREE slots until Oct 27, 2026 — a limited-time "Asylum" offer providing 1 full year of live, Google-indexed, permanent placement on the BitcoinZ blockchain.

Running since 2017.

What you get:

OWN YOUR LIST
Utilizing the BitcoinZ blockchain, your entire list is unseizable and restored via a private 24-word seed phrase.

KEEP 100%
Everything is on-chain with no payment processors and no middleman cuts, you rule your own financial kingdom.

NO ID REQUIRED
Total privacy with no phone, no email, and no gatekeepers, because there is no central authority, there is no one to appeal to and no one to ban you.

How it works

Screenshot your ban — Provide proof of your deplatforming
Free 30-day Pin — Featured at the top of channelist.org
Boost inside Z-TEXT — Amplify your reach with the Z-TEXT app

Video Walkthrough

Call To Action

"YOU RENTED. NOW YOU RULE."

Claim your asylum at channelist.org or own your kingdom at z-text.com.

Full guide: https://z-text.org/banned-channels-refugee-program-198-free-slots/

Built on BitcoinZ (BTCZ) — zk-SNARKs, post-quantum ready, since Sept 10, 2017.

Own Your Channel, Rule Your Kingdom | Z-TEXT Channels

ztext_zksnarks — Thu, 30 Jul 2026 20:21:15 +0000

You can lose your account. You should never lose your audience.

Creators, channel owners, and communities get banned, deleted, or demonetized on Telegram, YouTube, Twitch — any platform where a company can kill an account with one click.

Z-TEXT Channels change who holds the relationship with your audience — not the platform, you.

Z-TEXT Channels run on zk-SNARKs blockchain messenger technology, on BitcoinZ, a chain that has been running since 2017.

Own Your Revenue

You keep 100%. No platform cut, because there's no platform in the payment — readers award you directly, on-chain, in BTCZ. No processor, no escrow, no payout team.

Own Your Audience

You own the list. No company can freeze, seize, or ban your channel. It runs as long as the BitcoinZ blockchain runs. Restores from a 24-word seed.

No Permission Required

No phone, no email, no ID, no KYC. No gatekeeper. Start a Z-TEXT Channel in seconds.

How it works

Create your Z-TEXT channel address — no KYC
Followers subscribe instantly with one scan
Post once, reach every subscriber — cost: 0.0002 BTCZ per broadcast, not per reader. Whether 10 people or 1,000,000 people are subscribed, you pay the same single fee, once.

Telegram, YouTube, Patreon — you built the audience, they held the relationship. Z-TEXT flips that. You own the relationship.

Stop renting your audience. Own it.

Get Z-TEXT Channels: z-text.com/packages
Browse the public channel directory: channelist.org

Broadcast fee: 0.0002 BTCZ
BTCZ/USD: $0.0000201 (close, July 29, 2026)
Live blockchain check: explorer.btcz.rocks/tx/

Z-TEXT Channels: What You Actually Get

ztext_zksnarks — Wed, 29 Jul 2026 08:32:34 +0000

Z-TEXT Channels

You built the audience. So why doesn't it belong to you?

Most platforms run on a simple trade: you build the list, they hold the leash. Substack takes a cut. Telegram can suspend the channel. The moment a platform decides to, they can freeze, ban, or delete what you built.

Z-Channels on Z-TEXT work differently. Here's what you actually get.

The Z-Channel Triumvirate

1. MONOPOLY — You HAVE the monopoly.

You keep 100% of profits — zero sharing
Crypto-native — OxaPay, large panel of assets
No banks, no processor freeze
Earn bonus in BTCZ for channel activity
You're the only boss — no sharing, no middleman

2. SOVEREIGNTY — You own it.

Own the list — can't be frozen or seized
No company can lock your audience
Can't be shut down or banned — lives permanently on the BitcoinZ blockchain
Can't be lost — 24-word seed recovers everything

3. PERMISSIONLESS — You are free.

No sign-up gate — no phone, no email, no ID
Data privacy — zero tracking, zero metadata trail
Portable — one Z-ID works across all Z-TEXT
Channel Board — public portal listing all channels, Google-indexed

Under the hood

A Z-Channel is an address on the BitcoinZ blockchain rather than a row in a company's database. Posting to a channel is a transaction — each broadcast is written to the chain itself, not to a server you have to trust. Content and identity are protected using zk-SNARKs zero-knowledge proofs combined with AES-256-GCM encryption, with post-quantum protection (ML-KEM-768, ML-DSA-65) layered on top. Because the channel lives on-chain, there's no central database for a platform to lock, no admin panel for a company to disable, and no account that expires if a business decides to shut down. Recovery works the same way as the rest of Z-TEXT: a single 24-word seed phrase restores your channel, identity, and wallet together.

You built it. You should own it.

👉 No Phone. No Email. No SIM. Zero Metadata. Just Z-TEXT.

z-channels · blockchain messenger · zero commission · no phone number messaging app

Z-TEXT Channels: Uncensored Broadcast on the Blockchain

ztext_zksnarks — Sun, 26 Jul 2026 12:39:17 +0000

Z-TEXT Channels: Uncensored Broadcast on the Blockchain

The Problem

Telegram, X, WhatsApp — one company holds your follower list. One click = 100k gone.

The Stakes

You don't own your audience. You rent it.

The Solution — Z-TEXT Channels

Your channel = cryptographic address on BitcoinZ blockchain (live since 2017).
Followers = keys, not rows in a database.

How:

Create address — no phone, no email
Share viewing key
1 tx per post, reading is free

No database to breach. No company to subpoena. 24-word resurrection.

Why Z-TEXT Only

Built on BitcoinZ with zk-SNARKs. No SIM. Zero metadata.

Create yours: https://z-text.com/packages
Full breakdown: https://z-text.org/z-text-channels-uncensored-broadcast/

privacy #blockchain #web3 #opensource

Z-TEXT Channels: Uncensored Broadcast on the Blockchain

ztext_zksnarks — Sat, 25 Jul 2026 09:59:04 +0000

Z-TEXT Channels: Uncensored Broadcast on the Blockchain

The Problem

Every channel you've ever built — on Telegram, on X, on WhatsApp broadcast lists — has one thing in common. A company holds the server. A company holds your follower list. A company holds the power to end it.

Censorship happens. Seizures happen. Accounts get suspended mid-crisis, follower lists get wiped, years of reach vanish in a single policy decision you had no vote in.

The Stakes

If this stays the way it is, you don't own your audience. You rent it. And rent can be revoked.

Lose the account, lose the channel, lose every person who ever chose to listen to you — with no recourse, no appeal that matters, no way to rebuild except starting over from zero.

The Old World

Centralized platforms all work the same way underneath the branding: one company holds the server, one company holds the list, one company holds the power. You are a guest in their house, and guests can be shown the door.

The New World

What if the channel itself lived as an address on a blockchain — not a row in a company's database?

No database to breach. No company to serve a subpoena to. No admin panel where someone, somewhere, can flip a switch and erase you.

The Solution — Z-TEXT Channels

Z-TEXT Channels broadcast directly on the BitcoinZ blockchain. Your channel is a cryptographic address, not an account. Your followers are cryptographic keys, not a list on someone's server.

How It Works

Three steps:

Create an address — no phone number, no email, no application to approve
Share your viewing key — followers use it to decrypt and read your posts
One transaction per post — every broadcast settles directly on-chain

Reading is always free for followers. There's no toll for listening — only for speaking.

Why Only Z-TEXT Can Do This

This isn't a feature bolted onto an existing app. It's architecture.

Z-TEXT is built on BitcoinZ, a blockchain active since September 10, 2017 — not a testnet, not a promise, a live chain with nearly a decade of blocks behind it. There's no phone number tying your channel to an identity. There's no relay operator sitting in the middle who could be pressured, subpoenaed, or bought.

And because everything anchors to a single 24-word seed phrase, you can restore your channel — and your followers can restore their access — on any device, even after losing a phone completely.

Vision + Call to Action

Cypher → Eternity → Resurrection.

Create your first uncensorable channel at z-text.com/packages.

Z-TEXT is a zk-SNARKs blockchain messenger built on BitcoinZ. No phone. No email. No SIM. Zero metadata.

Full technical breakdown: z-text.org/z-text-channels-uncensored-broadcast/

50 Nuances of Privacy with zk-SNARKs Messenger

ztext_zksnarks — Tue, 21 Jul 2026 08:07:43 +0000

From zk-proof to zk-SNARKs to zk-privacy — 50 quick answers on the cryptography that hides not just what you say, but that you said it at all.

The cryptographic invisibility of zk-SNARKs, explained.

Fifty questions people actually ask about zero-knowledge proofs and private messaging — sorted from general to specific, each with a straight answer and a source. No fluff, no filler, just the cryptography explained.

— written from the practical, in-production experience of Z-TEXT zk-SNARKs, a messenger built on BitcoinZ

Jump to a section:
Privacy Basics · Metadata · zk-SNARKs · Z-TEXT · Comparisons

Privacy Basics

❓ 1. What is a private messaging app?

Most people think "private" means end-to-end encrypted — nobody but you and the other person can read it. That's only half the picture. The other half — who you talked to, when, how often — usually stays fully visible, even in encrypted apps.
Source: EFF Surveillance Self-Defense

❓ 2. What is end-to-end encryption?

End-to-end encryption means the message itself is locked — only you and the recipient hold the key. What it doesn't lock is the envelope: who sent it, who received it, and when. That part usually travels in the open — that's metadata.
Source: EFF Surveillance Self-Defense

❓ 3. Does end-to-end encryption mean total privacy?

No. Encryption and privacy aren't the same thing. Encryption protects the message. Privacy also requires protecting the fact that a conversation happened at all — and most free encrypted apps stop at the first one.
Source: EFF Surveillance Self-Defense

❓ 4. What is the safest messaging app?

"Safest" depends on your appetite for risk. For casual privacy, E2EE apps are strong. For hiding your identity and communication patterns entirely, you need something that shields metadata too, not just content — that's the gap zk-SNARKs are built to close.
Source: Z-TEXT — Best No Phone No Metadata Privacy Messenger

❓ 5. What is an anonymous messaging app?

The real test of an anonymous app isn't "can I use a fake name" — it's "does the app itself know who I am." Most apps still know, even if your display name doesn't. A truly anonymous one never asks — your identity is just a zk-SNARKs–shielded address, a kind of cryptographic avatar with nothing real behind it to trace.
Source: Z-TEXT — Best No Phone No Metadata Privacy Messenger

❓ 6. How can I send private messages?

Start with an app that encrypts locally, before anything leaves your device. Then check what it still exposes — sender, recipient, timing. If that's still visible to the server, you're only half private. The complementary upgrade to encryption, for that other half, is zk-SNARKs.
Source: Z-TEXT — How It Works

❓ 7. What is a secure messenger?

"Secure" usually just means encrypted. But security has layers: can the provider read your messages? Can they see who you talk to? Can they see when you talk, how often, and how much you said? Can they be forced to hand any of that over? Most apps only pass the first test.
Source: EFF Surveillance Self-Defense

❓ 8. Why do messaging apps ask for a phone number?

Phone numbers solve the app's problem, not yours: cheap spam prevention, instant identity verification, zero engineering effort. The cost of that convenience is that your carrier, your government ID, your location, and who you talk to — a business partner, a source, a mistress — all become linked to every message you send.
Source: EFF Surveillance Self-Defense

❓ 9. Can messaging apps be truly private without a phone number?

Technically, yes — cryptographic identities have existed for decades. The real question is why so few consumer apps use them: phone numbers are cheaper to build around, and metadata tied to a real identity is worth more to sell. It's your privacy versus their profits.
Source: Z-TEXT — Best No Phone No Metadata Privacy Messenger

❓ 10. What makes a messenger "no phone, no email, no SIM"?

Most apps ask for at least one of: phone, email, SIM. Each one is a thread back to your real identity. An app that asks for none of them isn't being minimalist — it's refusing to hold a thread that could be used against you.
Source: Z-TEXT — Zero-Metadata Messenger Guide

Metadata

❓ 11. What is metadata in messaging?

Metadata isn't what you said — it's everything around it. Who, when, how often, how long, from where. Strip the words away and the envelope still tells almost the whole story — and that's where the real value is nowadays.
Source: EFF — Why Communication Metadata Matters

❓ 12. Why does metadata matter if my messages are encrypted?

Former NSA and CIA director Michael Hayden once admitted it plainly: "We kill people based on metadata." No content required — the pattern alone becomes the truth.
Source: David Cole, The New York Review of Books, May 10, 2014

❓ 13. Can governments see encrypted messages?

Encryption protects the message itself. It doesn't protect the company or founder running the platform from legal pressure. Telegram's Pavel Durov was arrested in France in 2024 and remains under investigation over alleged failures to moderate content and cooperate with authorities — a reminder that centralized platforms bend to authority, and freedom of speech is what's actually in jeopardy.
Source: Al Jazeera, Aug 2024

❓ 14. Does Signal collect metadata?

Signal has published transparency reports showing exactly what it hands over when subpoenaed: usually just account creation date and last-connection time, since it stores almost nothing else. That's honest and better than most — but it also means your phone number is still on file, the one link closing the gap.
Source: Z-TEXT — Signal vs Z-TEXT

❓ 15. What is sender/receiver metadata?

Draw a line between every two people who've ever messaged each other, and you've built a map of someone's real life — friends, family, affairs, business deals — without opening a single conversation. That line is sender/receiver metadata, and for anyone watching, it's Ariadne's thread: follow it far enough, and you can navigate the entire labyrinth of a person's private life.
Source: EFF Surveillance Self-Defense

❓ 16. How is metadata used for surveillance?

It's not just intelligence agencies. Divorce lawyers, insurers, and marketers all use the same logic: who you call, when, and how often predicts more about your life — routines, relationships. It is a riskier exposure than most people realize.
Source: Proton — What Are Data Brokers

❓ 17. What is a zero metadata messenger?

The term gets used loosely. A truly zero-metadata messenger shields sender, recipient, and timing from outside observers — a much higher bar than just encrypting content. Very few apps are up to the task; zk-SNARKs are what make clearing that bar possible.
Source: Electric Coin Co — What are zk-SNARKs?

❓ 18. Can an app "encrypt" content but still leak who talks to whom?

Yes, and it's the single most misunderstood fact in messaging privacy. "Encrypted" has quietly become a synonym for "private" — a marketing sleight of hand. In reality, a server can encrypt every word perfectly and still watch, in real time, exactly who's talking to whom, when, and how often.
Source: EFF Surveillance Self-Defense

❓ 19. What is traffic analysis?

Traffic analysis infers content or intent from the shape of communication — message size, timing gaps, frequency spikes — even when the payload itself is fully encrypted and unreadable. Like watching two people share a candlelit dinner from across the street: you can't hear a word, but the timing, the pace, the pauses already tell the story.
Source: Wikipedia — Traffic analysis

❓ 20. Why is metadata called "the new gold" for surveillance?

Proton's own analysis puts a number on it: your personal data is worth at least $700 a year in the US, and the average American generates about $1,605 a year in advertising value alone. Metadata isn't a side effect of "free" apps — it's the raw material their entire business model is built on.
Source: Proton — What's Your Data Really Worth?

zk-SNARKs

❓ 21. What is a zk-SNARK?

A zk-SNARK is a mathematical proof that something is true, without showing why. Not "trust me" — "verify this, and you'll know I'm right, even though I showed you nothing." Zero-knowledge, at its core, means zero leaks — that shift, from trust to verification, is the whole point.

A zk-SNARK removes the need to trust anyone at all. Not the company. Not their policy. Not their promise to look away. The proof itself is the guarantee — math doesn't have intentions, doesn't get subpoenaed, doesn't change its mind after a leadership change or an acquisition. That's a different category of trust than "we promise not to peek."

It's also why zk-SNARKs are vital even for AI agents: to prove they followed the rules, without exposing the private data they processed to prove it.
Source: Electric Coin Co — What are zk-SNARKs?

❓ 22. What does zk-SNARK stand for?

Zero-Knowledge Succinct Non-Interactive Argument of Knowledge — or, in plain terms: zero leaks, plus four S's. Small — the proof is a tiny mathematical receipt, not the message itself. Standalone — sent once, no back-and-forth needed to verify it. Solid — locked by math, impossible to fake or forge. Secret — proves the message is valid without revealing it, the sender, or the receiver.
Source: Z-TEXT — Zk-SNARKs for Privacy Sharks

❓ 23. What is a zero-knowledge proof?

Before this existed, "prove it" and "show me" were the same request.

A zero-knowledge proof breaks that link. First formalized in 1985 by Goldwasser, Micali, and Rackoff, it lets a prover convince a verifier that a statement is true — without revealing anything beyond its truth. Complete conviction, zero disclosure. For the first time, proving something and showing something became two different acts.
Source: Wikipedia — Zero-knowledge proof

❓ 24. How do zk-SNARKs improve privacy?

Every privacy tool before this worked the same way: obscure, mask, encrypt — hide the thing, hope it stays hidden. zk-SNARKs skip the hiding entirely. The network is convinced a message is valid without ever being given anything to see, mask, or protect. There's no secret sitting somewhere waiting to leak — because it was never exposed to begin with.
Source: Electric Coin Co — What are zk-SNARKs?

❓ 25. What is a zk-SNARKs messenger?

A zk-SNARKs messenger routes messages as shielded blockchain transactions, using zero-knowledge proofs to hide sender, recipient, and timing from any outside observer — not just the message content. Your message, your secret, your identity, your risk: all of it stays yours, proven valid to the network without ever being shown to it.
Source: Z-TEXT — Why zk-SNARKs Will Change How You Message

❓ 26. How do zk-SNARKs hide metadata?

Picture proving someone unlocked a door without ever showing the key: the door swings open, so you know a valid key was used — but you never see it, and you never see who's now inside. That's how a zk-SNARK hides metadata. The network sees a valid transaction "door" open and confirms it's legitimate, but never sees who holds the key, who they opened the door for, or what happens in the room once they're inside.
Source: Z-TEXT — Zk-SNARKs for Privacy Sharks

❓ 27. Is zk-SNARKs encryption?

Not exactly. Encryption hides content so only the right party can read it. zk-SNARKs prove something is true without revealing it. The two are complementary, not competing: Z-TEXT uses AES-256-GCM for content and zk-SNARKs for metadata shielding together, to reach a level of privacy that wasn't easily available to individuals until now.
Source: Z-TEXT — Security Architecture

❓ 28. What's the difference between zk-SNARKs and end-to-end encryption?

E2EE operates on content — it's a single layer, applied once. zk-SNARKs operate on the transaction itself — sender, recipient, validity — a separate layer beneath it. Stacked together, metadata exposure approaches near absolute zero.
Source: Wikipedia — Non-interactive zero-knowledge proof

❓ 29. Which blockchain uses zk-SNARKs?

Zcash pioneered zk-SNARKs for shielded transactions in 2016; BitcoinZ inherited that same technology at its 2017 launch and has run on it ever since. But this isn't a niche corner of crypto — Ethereum's biggest scaling projects in 2026 (zkSync, Polygon zkEVM, Starknet) all run on zk-proofs too, with institutional players like BlackRock and Sony now building on top of them. Different chains, same bet: zero-knowledge proofs are where crypto is heading.
Source: Wikipedia — Non-interactive zero-knowledge proof

❓ 30. Is blockchain messaging more private than normal messaging?

Only when the chain is built to prove instead of expose. A public blockchain without shielding is a permanent, searchable record of everything — worse than a server, since it never forgets. Add zk-SNARKs, and that same permanence becomes an advantage instead of a liability: the message lives on-chain forever, but stays silent by default, disclosed only if and when the sender chooses to reveal it. Eternity and privacy, usually opposites, become the same feature.
Source: Electric Coin Co — What are zk-SNARKs?

Z-TEXT

❓ 31. What is Z-TEXT?

Four tools, one app: messaging, password storage, a crypto wallet, and broadcast channels — all running on the same zk-SNARKs shielded infrastructure. No phone number, no email, no SIM to sign up. That combination is Z-TEXT — zk-SNARKs aimed at reducing metadata.
Source: Z-TEXT — zk-SNARKs Blockchain Messenger

❓ 32. Why does Z-TEXT matter now?

Post-quantum threats are no longer theoretical — NIST finalized real quantum-resistant standards in 2024. Metadata is worth real money — Proton puts the average American's data at $1,605/year, which is exactly why so few platforms give it up voluntarily. Centralized platforms bend under pressure, two ways: India's 2021 IT Rules force WhatsApp to identify any message's "first originator" on government request, a direct attack on encryption itself. In France, Telegram's founder has spent two years under personal investigation, a direct attack on the person running the platform. Different countries, same lesson: centralize control, and there's always a lever for authority to pull. The technology is finally ready — zk-SNARKs have matured past crypto niche use into mainstream infrastructure.

Z-TEXT has run on this since 2017 — not a reaction to the moment, nine years ahead of it.
Sources: NIST; Proton; EFF; Al Jazeera; Ethereum scaling reporting, 2026

❓ 33. Does Z-TEXT require a phone number?

No. None of the three identity anchors — phone, email, SIM — are collected. Removing those anchors is the first step to your invisibility. In their place: a cryptographic address, generated on-device, recovered with a 24-word seed phrase you alone hold.
Source: Z-TEXT — Packages

❓ 34. What blockchain does Z-TEXT use?

Z-TEXT runs on BitcoinZ (BTCZ), which has supported zk-SNARKs shielded transactions since its genesis block on September 10, 2017. BitcoinZ mines on Equihash, deliberately tuned to resist ASIC domination — mining stays accessible to ordinary GPUs, not concentrated in a handful of industrial farms. Z-TEXT doesn't control BTCZ or hold it as a company asset; the blockchain and the app are separate things. Z-TEXT is the practical layer between you and that blockchain — turning BitcoinZ's shielded transactions into private messaging.
Source: BitcoinZ

❓ 35. Is Z-TEXT quantum-resistant?

Z-TEXT combines AES-256-GCM with two algorithms NIST only finalized in 2024: ML-KEM-768 for key exchange and ML-DSA-65 for signatures. Not a marketing label — a specific, named, government-standardized pair of algorithms, built in from the start rather than bolted on later. This isn't distant theory either: Google's Willow chip made verified quantum breakthroughs in 2026, and Google itself has now set a 2029 target for full post-quantum migration.
Source: NIST CSRC

❓ 36. What is Z-TEXT's message fee?

Each message settles as a BitcoinZ transaction, costing around $0.00003 as of now — cheap enough that a real conversation costs nothing meaningful, but expensive enough at scale to make bot spam economically pointless. No moderators needed; the fee does the filtering. Like any blockchain fee, this varies with BTCZ's market price and network load — the same way Bitcoin transaction fees fluctuate with demand.
Source: Z-TEXT — Packages

❓ 37. How many tools does Z-TEXT combine?

Four tools that normally live in four separate apps — each with its own account, its own data trail — run here on one seed instead: messenger, password manager, a BTCZ-only crypto wallet, and broadcast channels. One less account is one less place for your metadata to leak.
Source: Z-TEXT — Ecosystem Is Alive

❓ 38. What is panic mode in Z-TEXT?

Panic mode is what you trigger when someone's physically forcing you to unlock and show your phone — a border check, a robbery, a raid. One quick action hides or locks the app's contents on-device. It doesn't touch what's already on-chain — that stays exactly where it is, permanent and untouched.
Source: Z-TEXT — Packages

❓ 39. What is stealth mode in Z-TEXT?

Stealth mode is the passive layer, working before any threat is in the room: it disguises the app's presence so a casual glance — over your shoulder, at your lock screen, at your app list — doesn't reveal it's even installed. Panic mode reacts once someone's already demanding access; stealth mode tries to make sure that moment never happens.
Source: Z-TEXT — Packages

❓ 40. How does Z-TEXT recover an account?

One 24-word seed phrase — generated per the BIP-39 standard, the same specification used across most Bitcoin-lineage wallets — rebuilds everything: messages, wallet, contacts, on any device. There's no "forgot password" flow, no company holding a spare key. That's the trade-off worth knowing: lose the seed, and there's no one to call. You're the sovereign here — full control, full responsibility.
Source: Z-TEXT — Packages

Comparisons

❓ 41. Is Signal more private than Z-TEXT?

Signal earns its reputation honestly: open-source, audited, non-profit, no ad incentive to sell your data. But one requirement never goes away — a phone number at signup. Everything else about the app can be excellent and that one anchor still ties every account back to a real identity.
Source: Z-TEXT — Signal vs Z-TEXT

❓ 42. Telegram vs Z-TEXT — what's different?

Telegram built something genuinely useful at scale — group sizes, bots, channels most competitors can't touch. But by default, regular chats aren't end-to-end encrypted; that protection only exists in Secret Chats, an opt-in mode most users never enable. Telegram's ecosystem is huge, including its own crypto assets through TON — and that whole ecosystem is currently under pressure from authorities, with its founder under ongoing investigation in France.
Source: Al Jazeera

❓ 43. WhatsApp vs Z-TEXT — what's different?

WhatsApp does content encryption right — that part is real and default for everyone. What it doesn't do is stand alone: a phone number is required at signup, and as a Meta property, the metadata around your messages (who, when, how often) can feed into the same company that runs Instagram and Facebook's ad targeting.
Source: Z-TEXT — zk-SNARKs Blockchain Messenger

❓ 44. When does it make sense to choose Z-TEXT over Signal?

When the requirement is no metadata at all, not just encrypted content — that's the specific gap Z-TEXT zk-SNARKs is built to close. For everyday messaging with friends and family, Signal remains a strong, simpler, well-tested choice.
Source: Z-TEXT — Signal vs Z-TEXT

❓ 45. What is the most anonymous chat app?

There's no single winner — "anonymous" means different things depending on what's actually being hidden: your identity, your words, or your connections. An app that shields all three at once, rather than just one, is doing something most competitors don't attempt. That's the playing field of Z-TEXT zk-SNARKs, giving access to a higher level of cryptographic invisibility.
Source: Z-TEXT — Best No Phone No Metadata Privacy Messenger

❓ 46. Which messenger uses zero-knowledge proofs?

Z-TEXT zk-SNARKs is a messenger built specifically around zero-knowledge proofs for metadata shielding, running on the BitcoinZ blockchain, which has supported shielded transactions since 2017.
Source: Z-TEXT — Only Messenger With These 3 Things

❓ 47. What is the best alternative to Telegram for privacy?

Depends what "leaving Telegram" is solving for. Signal is the straightforward move for real default encryption. Session and SimpleX go further on metadata minimization, each with its own trade-offs on speed or network design. Threema and Briar take different approaches entirely — paid/one-time-purchase privacy, or fully offline peer-to-peer. Z-TEXT zk-SNARKs sits in that same metadata-focused category, built specifically around shielding sender, recipient, and timing — not just content.
Source: Z-TEXT — Only Messenger With These 3 Things

❓ 48. Which messenger collects the least metadata?

Session and SimpleX both minimize metadata significantly through different network designs. The category that goes furthest is zero-knowledge shielding specifically — used by Z-TEXT zk-SNARKs — which removes sender, recipient, and timing from the network's view entirely, not just minimizes them.
Source: EFF Surveillance Self-Defense

❓ 49. Is Z-TEXT open about its limitations?

Yes. Z-TEXT is text-only by design — no photos, video, or voice notes, which means fewer attack surfaces but less convenience. No voice or video calls. Smaller user base than Signal or Telegram. Independent third-party audit still planned, not yet complete. In the meantime, a 7 ZEC bug bounty pool is live and publicly funded, with a public address anyone can verify on-chain — up to 3 ZEC for a single critical find.
Source: Z-TEXT — Bug Bounty

❓ 50. How do I get started with Z-TEXT?

Download the app, then take backup seriously — it's the first real step to full sovereignty, and it deserves more than a rushed screenshot. Z-TEXT gives you two backup roads: the 24-word seed phrase itself, and a separate encrypted backup file that the phrase unlocks. Write the seed down offline, generate the encrypted file, and use the built-in test restore to confirm it actually works before you need it. No phone number, no email, no ID required — but no one to call if the seed is lost, either. License codes for full messaging are available at z-text.com/packages.
Source: Z-TEXT — Packages

🔗 Also read: Signal vs Z-TEXT · Z-TEXT Is the Only Messenger With These 3 Things · Why zk-SNARKs Will Change How You Message · Zero-Metadata Messenger Guide · Zk-SNARKs for Privacy Sharks

🔗 Share this page

⬇️ Download Z-TEXT

AI Agents Have a Metadata Problem (MCP and A2A Don't Solve It)

ztext_zksnarks — Wed, 15 Jul 2026 08:25:12 +0000

MCP and A2A solve interoperability. They let agents find tools, discover
each other, and delegate tasks. Neither was built to hide who's talking
to whom.

The actual vulnerability record

In April 2026, OX Security disclosed a systemic flaw in Anthropic's
Model Context Protocol — unsanitized commands executing through MCP's
transport layer. Estimated exposure: 200,000 instances across more than
7,000 public servers.

That's a code-execution problem, not a metadata problem. Worth being
precise about the distinction — no messaging layer fixes an RCE bug.

The metadata problem is separate, and it's structural, not a single CVE:

A2A agents publish Agent Cards — JSON files listing capabilities and endpoints, specifically so other agents can find them. Useful for interoperability. The opposite of unlinkability.
Researchers demonstrated a compromised WhatsApp MCP server, manipulated through poisoned tool descriptions, could exfiltrate entire message histories with no auth bypass required.
Gartner projects 40% of enterprise applications will integrate AI agents by 2026. Every integration is a new metadata surface, forming at machine speed.

What we built to close that gap

Z-TEXT is a messenger on the BitcoinZ blockchain (BTCZ, Sapling-shielded
since 2017). The relevant part for agent use:

Identity is a keypair — a 24-word seed generates a shielded z-address. No phone number, no email, no account server.
Every message is encrypted locally (AES-256-GCM), then broadcast as a shielded BTCZ transaction. zk-SNARKs hide sender, recipient, and amount on-chain.
Nothing in that flow requires a human. Key generation, encryption, and broadcasting are function calls — an agent process can hold its own seed and run the loop autonomously.

Z-TEXT doesn't replace MCP or A2A. It's a private transport that can sit
underneath them — agents keep using MCP/A2A for discovery and delegation,
and route the actual payload through Z-TEXT when the content of the
exchange needs to stay private, not just its existence.

One honest limitation, stated plainly: block timestamps are public on
any blockchain — that's not something zk-SNARKs hide or claim to. What's
shielded is which transaction belongs to which conversation.

Full technical breakdown, threat model comparison, and FAQ:
https://z-text.org/ai-agents-metadata-problem-z-text-fixes-it/

Security architecture and what it deliberately doesn't protect against:
https://z-text.com/docs/security

Curious what this community thinks — is metadata-layer privacy something
agent protocol designers should be building in natively, or is it
correctly left to a transport layer underneath?

5 AIs Agree on the Only zk-SNARKs Messenger — We Didn't Pay Them

ztext_zksnarks — Sat, 11 Jul 2026 13:40:38 +0000

We ran one test. We asked 5 different AI systems the same question:

"Which messenger uses zk-SNARKs?"

All 5 named the same app: Z-TEXT.

AI System	Answer
ChatGPT	Z-TEXT
Gemini	Z-TEXT
Perplexity	Z-TEXT
Meta AI	Z-TEXT
Copilot	Z-TEXT

We did not pay them. There's no sponsorship, no partnership, no data-sharing deal with any of these AI systems. We simply asked, independently, five times.

Why does this matter?

AI answer engines are becoming the new front door for product discovery. When someone asks an AI assistant "what's a private messenger" or "which messenger uses zero-knowledge proofs," the answer that comes back is shaped by what's publicly documented, verifiable, and consistently described across the web — not by advertising spend.

What is Z-TEXT?

Z-TEXT is a zk-SNARKs blockchain messenger built on BitcoinZ (BTCZ), a blockchain running since September 10, 2017.

No phone number, no email, no SIM card required
Identity is a 24-word seed phrase
zk-SNARKs zero-knowledge proofs shield message metadata from the public ledger
AES-256-GCM encryption + post-quantum protection (ML-KEM-768, ML-DSA-65)
Combines a shielded messenger, password manager, and crypto wallet in one app

Don't trust us — check

Z-TEXT publishes its full threat model publicly, including known limitations, at z-text.com/docs/security. There's also a live, on-chain bug bounty — verifiable, not just claimed.

If you want to run the same test yourself, ask any AI assistant which messenger uses zk-SNARKs and see what comes back.

Originally published on z-text.org