Most product marketers sell things people can see. A shoe. A car. An app. A feature. Zero-knowledge marketers sell things people specifically cannot see — by design.
A ZK proof works because it reveals nothing. The entire value proposition of the technology is its invisibility. Which creates a uniquely brutal marketing challenge: how do you get a market to care about something whose whole point is that it gives them nothing to look at?
This is the invisible utility problem. It's one of the hardest positioning problems in emerging tech, and it's the core challenge facing every ZK brand right now — from zkSync and Starknet at the infrastructure layer, to private payment protocols, to identity systems built on ZK proofs.
After working on ZK campaigns (including the Elastic House activation for zkSync at ETH Denver 2025), we've developed a framework for marketing zero-knowledge technology. This post breaks it down.
Why ZK is harder to market than most crypto
Crypto in general has a communication problem. ZK has a compounded communication problem.
A normal blockchain pitch goes: here's a database, but decentralized, and you can't cheat it. That's abstract, but it's mappable. People understand databases. They understand trust. The leap isn't huge.
A ZK pitch goes: here's a way to prove something is true without revealing what it is. The average person has no reference point. Even the average crypto-native user has a hazy one.
And the people most likely to understand it (cryptographers, mathematicians, engineers) are the people least likely to care about brand storytelling. They want technical papers, not campaigns or soft branding.
So the ZK marketer faces a three-way audience split:
- Technical experts who need technical rigor
- Decision-makers (founders, protocol heads, VCs) who need strategic clarity
- End users who need to feel something without needing to understand anything
Most ZK marketing fails because it tries to speak to all three at once. The result: papers that are too dry for builders, campaigns that are too thin for experts, and end-user messaging that collapses into generic "privacy" tropes that don't actually describe what ZK does.
The Invisible Utility framework
The way through is to stop trying to make the technology visible. Instead, make the consequences of the technology visible. That's what marketing ZK is really about: translating invisible cryptographic properties into visible human outcomes.
Here's the framework we use for every ZK client.
Layer 1: The technical core (for builders)
This is the paper. The benchmarks. The documentation. The commit history. The layer where technical audiences evaluate whether your ZK system is real and worth building on. You cannot skip this layer or fake it — builders will see through anything thin.
What works here:
- Published research papers, ideally peer-reviewed or backed by known cryptographers
- Transparent benchmarks (proof generation times, verification costs, circuit sizes)
- Open-source code with real commit history and contributor activity
- Developer documentation that respects intelligence, not condescending explainers
What doesn't work: hype content at this layer. Builders will trust you less, not more, if your docs lead with marketing copy.
Layer 2: The strategic narrative (for decision-makers)
This is where most ZK brands either win or lose funding, partnerships, and press. Decision-makers (founders, investors, enterprise buyers) don't have time to understand the cryptography. They need a clear, compact answer to three questions:
- What problem does this solve that nothing else can?
- Who's already proven it works?
- Why now?
The mistake most ZK marketing makes here is explaining how the technology works before explaining what it unlocks. The founder reading your pitch deck doesn't need to understand elliptic curves — they need to understand that your proof system makes a $10B market accessible that wasn't before.
Lead with the unlock. Follow with the credibility. Explain the mechanism only if asked.
Layer 3: The human story (for everyone else)
This is the layer that most ZK projects neglect entirely — and the layer that determines whether the technology ever crosses into mainstream relevance.
The human story is not about cryptography. It's about what happens when the cryptography works. A private vote. A transaction that can't be surveilled. A credential that proves your age without revealing your identity. A supply chain that proves authenticity without exposing suppliers.
The craft here is to build narratives around the moment of use — not the technology behind it. Apple didn't sell the iPhone by explaining capacitive touchscreens. They sold it by showing people what it felt like to pinch-to-zoom a photo. ZK needs the same treatment.
Good human-story ZK marketing:
- Shows scenarios, not systems
- Centers on individuals, not infrastructure
- Lets the technology stay quiet in the background
The ZK marketing playbook: 5 principles
After running ZK campaigns across protocols and ecosystems, these principles have held up consistently.
1. Positioning precedes explanation
Before you write a single piece of content, answer the positioning question clearly: in one sentence, what does this project do that nothing else does? If you can't, no amount of clever content will save the campaign.
What matters is that the positioning is clear to a non-expert and defensible to an expert. That dual requirement is the constraint that produces good ZK brand lines.
2. Treat the category before the product
ZK is still a category under construction. The average crypto-native user doesn't have a strong mental model of what it is or why it matters. Marketing your product alone is like marketing an electric car in 1998 — the product is only legible if the category is legible.
The strongest ZK brands invest in category-level content before they invest in product-level content. They explain what zero-knowledge enables at the category level, so their product becomes a logical conclusion, not a random offering.
This is counterintuitive. It looks like you're doing your competitors' work. But the first mover in a category earns a disproportionate share of the mindshare, and the second-best category explainer gets trapped in the first's framing.
3. Earn technical trust before reaching for mainstream
There's a temptation to go straight to end-user messaging — the "private by default" billboards, the consumer-friendly copy. Resist it until the technical layer is locked.
In ZK specifically, technical credibility is not optional. If the crypto community decides your tech is thin, no amount of clever campaigning will recover. And because the crypto community is on-chain and loud, that verdict travels fast.
Build the technical trust first — through open research, real benchmarks, known advisors, and audit transparency. Then, and only then, reach for mainstream relevance.
4. Design for the "aha" moment, not the explanation
When we planned Elastic House at ETH Denver, we didn't build a booth. We built an experience designed to produce a specific moment: the instant someone understands what ZK enables without anyone having to explain it.
That's the goal of every ZK activation, whether it's a live event, a product demo, or a landing page. The user should leave with an intuitive grasp of what the technology unlocks — not a technical one.
Intuition doesn't require understanding. It requires feeling. Design for feeling.
5. Let the community carry the technical story
The technical audience for ZK is small, tight-knit, and extremely vocal. If you earn their trust, they become an unpaid sales force. If you lose it, they become an unpaid opposition.
The best strategy with this audience is radical transparency plus genuine engagement. Respond to technical critiques openly. Publish internal decisions. Invite scrutiny. Don't try to manage the narrative — contribute to it.
The projects that do this well (we've seen it work with Celestia, ZKsync, and others) don't have a "community strategy." They have a culture that happens to generate community output.
A note on the end state
Here's the thing about marketing invisible utility: if you do it well, your technology becomes boring in exactly the right way.
The goal of ZK marketing isn't to make people think about zero-knowledge proofs. The goal is to make zero-knowledge proofs so obvious, so integrated, so quietly present that nobody thinks about them at all. They just work.
When a user logs in without a password and doesn't notice, ZK has won. When a voter casts a private ballot without a second thought, ZK has won. When a private payment happens and nobody refers to it as private — it's just a payment — ZK has won.
Selling the invisible is hard. Winning means it stays invisible.
Who we've worked with
Blokhaus has built campaigns for ZKsync (Elastic House at ETH Denver 2025), NEAR, Algorand, Solana, and other blockchain protocols. If you're building in zero-knowledge and trying to figure out how to talk about what you've built, we can help.
