ZK Proven is a supporting expression of the H33 ZK Platform applied to network connections. It produces a zero-knowledge proof that the tower or network your device is connected to is genuinely what it claims to be — proving the channel is authentic while revealing nothing about your traffic. It exists because a phone can show the right carrier and full bars while actually talking to an IMSI catcher; ZK Proven proves the channel instead of trusting the name on the screen.

🚗 YOU

📡 THE ATTACKER

🛡️ H33 ZK PROVEN

You're driving. Verizon. Full bars.

Q: When should I use ZK Proven, and when not?

Use ZK Proven when you need to prove a live cellular or network channel is authentic without exposing or inspecting the data on it. Do not use it when you need to compute over encrypted data (that is the FHE Platform), or when you need to prove a statement about stored data rather than a live channel (use the general ZK Platform). ZK Proven proves the channel; it is not an antivirus or content scanner.

Q: Does ZK Proven produce portable evidence?

The ZK Platform generates the proof; H33-74, the 74-byte post-quantum evidence primitive, anchors it as portable, independently-verifiable evidence a third party can carry and re-verify offline. Proof generation belongs to the ZK Platform; evidence anchoring belongs to H33-74. Proof systems such as STARKs and SNARKs are external constructions H33 uses and verifies against, not owns.

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

You're on the highway. Your phone is connected to Verizon — the same tower it's used for the last 20 minutes. Four bars. LTE. Everything is normal. You've got Maps running, Spotify playing, a few Slack notifications, and your banking app in the background.

Here's what's on your phone right now

Every app on your phone holds an active session. Each one is a key. Here's what someone gets if they intercept your connection.

Banking app SESSION TOKEN

Transfer your money. Change your password. Lock you out permanently.

Email AUTH TOKEN

Read everything. Reset every other password you own. Become you.

VPN LOGIN CREDENTIALS

Access your entire company network as you.

Maps / Location LIVE GPS DATA

Know exactly where you are, where you live, where your kids go to school.

Work messages SESSION COOKIE

Read confidential deals, strategies, conversations with your CEO.

Someone just drove past you in a van

Inside: a device called an IMSI catcher. It broadcasts a stronger signal than the real Verizon tower. Your phone switched to it automatically. Still shows Verizon. Still shows four bars. Everything looks normal. Nothing is.

Rewind. Same road. H33 ZK Proven is running.

ZK Proven checks the connection 5 times per second. It doesn't read your messages or data. It just proves whether what your phone thinks is Verizon actually is.

Trust Score

FAKE TOWER KILLED

4.4 SECONDS

Attacker harvested: 0 bytes · IMSI catcher location reported

The difference

	Without ZK Proven	With ZK Proven
Connection showed	Verizon — full bars — no warnings	Verizon — full bars — no warnings
Was it actually Verizon	No — but there was no way to know	No — and ZK Proven caught it in 4.4 seconds
Attacker harvested	Location · Bank · Slack · VPN	Zero bytes
Your company network	Compromised	Never touched
You knew anything was wrong	No — still don't	Yes — immediately

Your phone said Verizon.

It was right — it was Verizon.

The signal was real. The tower was fake.

ZK Proven proved the channel. Not the name on your screen.

Start Free — 1,000 Ops

What ZK Proven Is

ZK Proven is a supporting expression of the ZK Platform — H33's capability that proves without revealing — applied to network connections. It produces a zero-knowledge proof that the tower or network your device is connected to is genuinely what it claims to be, revealing nothing about your traffic. It exists because your phone can show the right carrier and full bars while actually talking to a fake tower. ZK Proven proves the channel instead of trusting the name on your screen.

Use it when

You must prove a live cellular or network channel is authentic without exposing or inspecting the data on it — mobile, WiFi, device-to-device, cloud-to-cloud.

Not for

Computing over encrypted data (that is the FHE Platform) or proving a statement about stored data rather than a live channel (use the general ZK Platform). It is not an antivirus.

Concept boundaries. The ZK Platform proves without revealing — it does not compute on encrypted data; that boundary belongs to the FHE Platform. The portable, offline-verifiable evidence of a proof is produced by H33-74, the 74-byte post-quantum evidence primitive: ZK Proven generates the proof, H33-74 anchors it as portable evidence. Constructions like STARKs and SNARKs are external cryptographic systems H33 uses and verifies against — never owns.

When should I use ZK Proven, and when not?

Use it to prove a live cellular or network channel is authentic without exposing or inspecting its traffic. Do not use it to compute over encrypted data (that is the FHE Platform) or to prove a statement about stored data rather than a live channel (use the general ZK Platform).

How is ZK Proven different from the FHE Platform?

ZK Proven proves without revealing — it proves the channel is authentic without reading your traffic. The FHE Platform runs computation over encrypted data (ciphertext) without decrypting it. ZK proves a statement about data or a channel; FHE computes over ciphertext. Complementary, not substitutes.

Does ZK Proven produce portable evidence?

ZK Proven generates the proof; H33-74, the 74-byte post-quantum evidence primitive, anchors it as portable, independently-verifiable evidence a third party can carry and re-verify offline. Proof generation and evidence anchoring are distinct roles.