Why it matters
As onchain games mature, builders are turning their attention to identity, reputation, and privacy. In Episode 3 of Code, Clout & Crypto, panelists from Holonym, MEW, Soulbound TV, and Ontology explored how soulbound tokens (SBTs), zero-knowledge proofs (ZKPs), and modular interoperability could redefine how players build persistent, meaningful identities across game worlds—without sacrificing privacy.
Read the full recap @ Crypto Sapiens Newsletter
Featured Speakers
- Daniel – Holonym
- Catman – MEW
- Muaz – AlphablockZ & Tenset
- Marcello – Soulbound TV
- Humpty, Geoff & Polaris – Contributors at Ontology
Five core takeaways
1. SBTs are meaningful—but must stay flexible
Soulbound tokens help record untradeable achievements, affiliations, and milestones—like a Web3 version of Xbox trophies. But they need nuance: players should be able to evolve without being locked into outdated affiliations.
“Soulbound should empower reputation, not trap you in your past.” – Muaz
2. ZKPs bring privacy to portable identity
Zero-knowledge proofs allow players to prove skill, humanity, or access without revealing personal or historical data—perfect for pseudonymous play in onchain environments.
“You don’t need to leak your whole history to verify one thing.” – Daniel, Holonym
3. Interoperability should focus on proof, not items
Rather than pushing for fully portable assets, the panel leaned into portable proofs—like proof of play, contribution, or trust—allowing each game to interpret identity in its own way.
“We need to think less about fully portable items, and more about portable proof.” – Catman, MEW
4. Identity systems must balance permanence with privacy
With SBTs and ZKPs working together, players can build a reputation that travels, while still maintaining the ability to reset, grow, or protect sensitive aspects of their identity.
5. Composability is cultural as well as technical
True onchain identity will require collaboration across protocols, not just APIs. Reputation, trust, and playstyles need to be modular—so each game can read from shared identity layers without breaking its own narrative or balance.
Bigger pictur
As Web3 gaming evolves, so do its foundations. This episode highlights a future where players can carry identity and trust across ecosystems, but selectively. With soulbound tokens, zero-knowledge proofs, and composable profiles, onchain games can become persistent, interoperable, and player-first—without repeating Web2’s surveillance-heavy playbook.
What’s next in the series
Episode 4 closes the series with a dive into narrative systems, lore co-creation, and emergent storytelling in onchain games.
TL;DR
SBTs, ZKPs, and profile-level interoperability are creating a new model for Web3 games—where players earn recognition, not baggage, and carry their identity across ecosystems on their own terms.
Related Reading
- Episode 2 Recap – The Role That Social Systems Play in Onchain Games
- Episode 1 Recap – How Digital Identity Is Shaping the Future of Onchain Games
- Full series @ Crypto Sapiens
Subscribe to the Crypto Sapiens Newsletter to get future episodes, guest insights, and deeper dives on identity, privacy, and the future of play in Web3.
In this special Twitter Space, Ontology explores one of the most promising and misunderstood technologies in Web3: zero-knowledge proofs (ZKPs). Joined by leaders from ZKPass, Veera, and Orange Protocol, the conversation dives deep into what ZK really enables—from private onboarding to secure reputation—and why the most powerful cryptographic tools work best when users don’t even notice them.
Read the full post @ CryptoSapiens Newsletter
Featured Speakers
- Francis Berwa – ZKPass
- Sam Noble – CPTO at Veera
- Humpty Calderon – Ontology
- Geoff – Ontology
- Polaris – Ontology
Five takeaways
1. ZK is a “yes-or-no” machine
Instead of revealing data, ZK lets users answer questions like “Are you over 18?” with a simple yes—without showing ID or personal documents. That’s the core utility: validation without exposure.
2. Sell the benefit, not the cryptography
Users don’t care about protocols—they care about privacy, speed, and trust. Like SSL in your browser, ZK should work quietly in the background, solving real problems without technical friction.
3. ZK is already in consumer products
- Veera uses ZK to reward users without tracking
- ZKPass enables private eligibility proofs for finance, telecom, and more
- Orange Protocol brings privacy-preserving credentials to DAOs and DeFi apps
4. Proof replaces access
The future of verification isn’t about sharing your entire data set—it’s about attesting to what matters, like income, age, or balance thresholds, without exposing everything else.
5. ZK will soon be boring (and that’s good)
The most transformative tools—like HTTPS—fade into the background. ZK’s future lies in invisibility: embedded in browsers, dating apps, and onboarding flows where privacy matters most.
Bigger picture
Zero-knowledge technology isn’t just a blockchain breakthrough—it’s a universal privacy tool for Web2 and Web3. As data collection and AI surveillance increase, ZKPs offer a safer model: one that puts users in control, builds trust, and quietly rewires how we prove things online.
Where ZK Might Show Up Next
The panel shared future use cases where ZK could power real-world experiences:
- LinkedIn → Verify job history without exposing all past roles
- Tinder → Match based on verified traits without revealing full profiles
- Airbnb → Verify hosts/guests without exposing personal documents
- Calendars → Show availability without leaking event details
- Immigration → Prove income eligibility without full financial access
- Gaming → Cross-game reputation without doxxing behavior
TL;D
Zero-knowledge proofs let you prove more while revealing less. And that’s exactly why ZK is poised to become the next HTTPS—quiet, powerful, and essential for the next generation of secure digital experiences.
Want more like this?
Follow Ontology on X for future conversations on ZK, identity, and privacy.
Connect with the speakers:
Recommended Reading
Check out the latest updates to DID & Privacy
]]>