# Practical Privacy Has a Home -- Part 2

**Published by:** [Horizen Blog](https://blog.horizen.io/)
**Published on:** 2026-07-20
**Categories:** privacy, horizen, building
**URL:** https://blog.horizen.io/practical-privacy-has-a-home-part-2

## Content

The Builder Case: EVM-native, privacy-architecture neutral Horizen is a privacy-first ecosystem built on Base, designed for private applications, confidential financial activity, and real economic use. Unlike other blockchain privacy projects, Horizen is EVM-native, which means developers can build with familiar tools and users can connect with the wallets and assets they already hold. The chain itself stays open and verifiable. Privacy lives at the application layer, where builders can design confidentiality around what their users actually need. Building on Base infrastructure means Horizen inherits the security, tooling, and reach of one of the largest ecosystems in crypto. Operating as an OP Stack L3, Horizen publishes transaction data and state commitments to Base's data availability layer. That anchors Horizen to the same security assumptions Base itself relies on (without reinventing the wheel). Builders do not have to choose between privacy and liquidity. They can deploy familiar Solidity applications and add the privacy controls their users need, without leaving the environment where activity already happens. Keeping privacy at the application layer is a deliberate choice. It means each application can define the confidentiality its users require, and pair it with the disclosure its situation demands. A private trading venue has different needs than a payments tool or a compute platform. App-layer privacy lets each of them get it right, while the underlying network remains open. While Horizen at the chain-level is public, one of its primary builder advantages is its close proximity to privacy tooling from Horizen Labs including Vela, an emerging TEE-based private execution platform that acts as confidential co-processor, as well as zkVerify, the universal zero-knowledge proof verification and attestation protocol. Builders reach for TEE-based execution, ZK verification, or app-level patterns depending on what they're building, with room for other primitives as they mature. This tooling, combined with developer support for their integration, offers meaningful differentiation and a resource base for builders that make a real difference in their success. Compliance also sits at the application layer. Transaction-layer screening tooling is available today, but selective disclosure and auditability are design decisions builders make for their own application. Privacy and compliance don't have to be at odds when they're designed into the application itself. That's a direction the whole ecosystem is building toward, and a philosophy that shapes how every product gets made. The role of ZEN in Horizen today Coming next week in Part 3, we’ll unpack how ZEN sits at the center of Horizen’s new economic engine.

## Publication Information

- [Horizen Blog](https://blog.horizen.io/): Publication homepage
- [All Posts](https://blog.horizen.io/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@horizenofficial-2): Subscribe to updates
- [Twitter](https://twitter.com/horizenglobal): Follow on Twitter