Tempo has introduced a new “Zones” feature aimed at giving enterprises bank-like privacy on public stablecoin infrastructure, but the approach is already stirring debate across the crypto industry.
The payments-focused layer-1—developed with backing from Stripe and Paradigm—said Zones allow companies to conduct transactions in permissioned environments while still accessing liquidity on public blockchains. The feature is designed to address a key institutional concern: the exposure of sensitive data such as payroll, merchant volumes, and treasury activity on transparent ledgers.
However, some privacy advocates argue the model comes with significant trade-offs. Because each Zone is operated by an entity that can view full transaction data and restrict transfers or withdrawals based on its own compliance rules, critics say it introduces centralized trust assumptions more akin to a traditional exchange than a decentralized system.
The debate highlights a broader divide in crypto infrastructure, as projects balance institutional requirements with core decentralization principles. While Tempo is prioritizing usability and interoperability, competing approaches are focusing on advanced cryptography to ensure end-to-end transaction privacy.
Zones aim to shield enterprise activity
Tempo says Zones function as parallel, permissioned chains connected to its main network, tailored for use cases like payroll, fund management, and B2B payments. Within these environments, companies can transact privately while maintaining interoperability with the public chain, other Zones, and shared liquidity pools.
Each Zone is operated by a designated entity that controls access and can view transaction activity, while the public network validates batched updates and proofs. Tempo argues this hybrid design preserves the advantages of public blockchains while delivering the compliance and auditability enterprises expect.
The project also contends that cryptography-heavy privacy solutions can introduce unnecessary complexity and usability challenges.
Rivals push cryptographic privacy models
Tempo’s operator-driven approach has drawn criticism from some developers, who say it compromises both privacy and self-custody. If a single operator can access transaction data and control user activity, they argue, the model relies more on trusted intermediaries than on cryptographic guarantees.
Competing projects are taking a different route. ZKSync uses private chains anchored to public networks through zero-knowledge proofs, while Arcium is exploring distributed systems where data remains encrypted across nodes and only verified outputs are revealed. Zama, meanwhile, leverages fully homomorphic encryption to enable computations on encrypted data.
Ghazi Ben Amor, senior vice president of business development at Zama, said that although the underlying cryptography is highly complex, it is abstracted away for developers, who can build using familiar tools like Solidity without needing specialized knowledge.
He added that enterprises using the Zama Protocol “don’t even notice” the cryptography operating in the background, and argued that Tempo’s Zones resemble private blockchains—similar to centralized payment systems that have historically faced scalability limitations.
