Skip to main content

Tempo Zones Explained: Private Payments on Tempo

Tempo Zones are private, EVM-compatible chains that run in parallel to Tempo Mainnet. Here is how they work, what became generally available in October 2026, and what stays public.

Written by Eco
Tempo Zones Explained: Private Payments on Tempo

Tempo Zones are private execution environments that run as parallel blockchains connected to Tempo Mainnet, the payments-focused Layer 1 described in our Tempo blockchain overview. Inside a Zone, stablecoin transfers and balances are hidden from the public, while funds can still move to Mainnet, to other Zones, and to Mainnet liquidity (Tempo blog, Privacy on Tempo). Tempo introduced Zones on April 16, 2026 (Introducing Tempo Zones) and made them generally available for enterprises on October 14, 2026 (Privacy is live on Tempo).
​

This article explains how a Zone works, who can see what at each step, what changed with the October launch, and which parts of a Zone's activity remain visible on Mainnet. All protocol details come from Tempo's own blog posts and developer documentation.
​

What are Tempo Zones?

A Tempo Zone is an EVM-compatible private chain that runs alongside Tempo Mainnet. Transactions inside it are not visible to the public, and users can move funds between Zones by routing them through Mainnet. Tempo also frames Zones as a scaling tool, since each new Zone adds parallel blockspace.
​

Tempo's launch post describes a Zone as "an EVM-compatible private chain that runs in parallel to Tempo Mainnet" and says Zones let Tempo "scale its blockspace horizontally with every new zone" (Introducing Tempo Zones). The protocol software is open source, and Tempo states that anyone will be able to deploy a Zone, naming Conduit as an infrastructure provider that plans to support launching them (Introducing Tempo Zones, FAQ).
​

The problem Zones target is public broadcast. Tempo's product post notes that on most stablecoin networks a company running payroll would publish salaries, and a processor settling with merchants would leak volume data (Privacy on Tempo).
​

How do Tempo Zones work?

Funds enter a Zone through a contract on Tempo Mainnet, which holds the backing assets. A Zone operator then builds blocks and processes private transactions on the Zone's own ledger. Withdrawals return funds to Mainnet after the Zone's batches are settled.
​

Tempo's developer docs describe the pieces this way: a Zone keeps a private ledger of stablecoin balances and account activity, while a portal contract called ZonePortal on public Tempo holds the backing assets. Finalized deposits credit the private ledger, and the operator submits batch commitments with sequencer certificates back to Tempo (Tempo Docs, Testnet Sandbox). Tempo's product post adds that the validity of Zone transactions and the enforcement of compliance rules are verified cryptographically by Tempo Mainnet, independent of the operator (Privacy on Tempo).
​

Deposits

When a user deposits, the recipient address and memo are encrypted. Mainnet observers see the token, the amount and the sender. The zone operator can decrypt the recipient (Introducing Tempo Zones).
​

Transfers inside a Zone

Transfers between addresses in the same Zone are private from the public. Tempo's table of public and private data lists "Nothing" as public for in-Zone transfers and balances (Privacy is live on Tempo).
​

Withdrawals

Withdrawals send funds back to an address on Mainnet. The sender's address inside the Zone is hidden with a cryptographic commitment that is revealed to the recipient. The amount and recipient are public (Introducing Tempo Zones; Privacy is live on Tempo).
​

Balance reads at the RPC level

Privacy extends to the node interface. To check a balance, a client signs an auth token with the keypair that controls the account, and the RPC verifies that signature before returning data. Requests for an account without its keypair fail (Introducing Tempo Zones, FAQ).
​

What is private and what is public in a Tempo Zone?

Activity inside a Zone is hidden from the public, but the edges are not. Deposits reveal the token, amount and sender; withdrawals reveal the amount and recipient. The Zone operator can see all activity inside its Zone.
​

Tempo published this breakdown with the October 14, 2026 launch (Privacy is live on Tempo):
​

Action

Public

Private

Deposit into a Zone

Token, amount, sender

Recipient

Transfers in a Zone

Nothing

Sender, recipient, amount

Balances in a Zone

Nothing

Balance (visible to the account holder and operator)

Withdrawal from a Zone

Amount, recipient

Sender

Interact with Earn / DeFi

Deposit, withdrawal, amount

Who owns the position

Two further limits appear in Tempo's FAQ. Because deposits are visible on Mainnet, an observer can see which Zones an address has sent funds into. And for transfers between Zones, the amount, origin Zone and target Zone are visible publicly (Introducing Tempo Zones, FAQ).
​

What can a Zone operator see and do?

The operator sees all balances and transactions inside its Zone and controls sequencing, inclusion and liveness. It can suspend a user's ability to transfer or withdraw under its own compliance rules. It cannot move a user's funds to another party.
​

Tempo describes the operator as "a trusted party in the zone" and states that "the operator can never transfer a user's funds to another party" (Introducing Tempo Zones). Funds stay locked in a Zone contract on Mainnet and can be withdrawn by the user who owns them (Privacy on Tempo).
​

Tempo says operator visibility is deliberate, because a regulated institution running a Zone may have compliance or reporting duties. A Zone can be run by an enterprise itself or by an infrastructure provider, and enterprises that want tighter control can operate their own (Privacy on Tempo, Who sees what). At launch, Tempo added that operators decide who can participate, which assets are allowed, and how incoming funds are screened (Privacy is live on Tempo).
​

Which tokens can move into a Tempo Zone?

TIP-20 tokens deployed on Tempo Mainnet can be enabled in a Zone, and the issuer's compliance policy follows the token in. Two conditions must hold: the operator has enabled the token, and the issuer's TIP-403 policy permits that Zone (Introducing Tempo Zones).
​

Per Tempo's FAQ, a whitelist-policy issuer must enable the Zone, and a blacklist-policy issuer must not have disabled it. The same token can be active in several Zones at once, and a Zone address can hold any TIP-20 the operator has enabled (Introducing Tempo Zones, FAQ). When an issuer updates an allowlist or blocklist, or freezes a token on Mainnet, Zones enforce the change automatically (Privacy on Tempo). For background on the stablecoins used for fees and routing on Tempo, see What is pathUSD.
​

Can you swap or move funds between Zones?

Yes, through Mainnet. Zones do not run their own exchanges. To swap, a user withdraws to Mainnet, trades on a stablecoin exchange there, and deposits the output back into a Zone. Moving funds between Zones also routes through Mainnet.
​

Tempo states that swaps cannot happen inside a Zone and that, for this withdraw-swap-deposit flow, no one on Mainnet can see who initiated the swap or who received the proceeds (Introducing Tempo Zones, FAQ). Tempo positions this as a way to avoid splitting liquidity across many separate pools. The October launch post adds that private accounts can reach stablecoin swaps, FX, ramps, card programs and yield on Tempo (Privacy is live on Tempo).
​

What changed when privacy went live on Tempo?

On October 14, 2026, Tempo announced that Zones were generally available for enterprises, with Deel as the first company using a Zone in production. Tempo also named Privy and Bridge as supporting Zones natively (Privacy is live on Tempo).
​

Tempo's announcement says Deel uses its Zone to pay contractors without revealing who gets paid or how much. Deel's treasury deposit into its Zone is visible on Tempo, but which contractors are paid, the amounts, and their holdings are not (Privacy is live on Tempo). The same post lists the target use cases as payroll, contractor payouts, B2B payments and treasury, and states that Privy's wallet infrastructure lets businesses add Zones through its APIs (Privacy is live on Tempo).
​

Before general availability, Tempo's April product post described Zones as available with design partners, with production deployments planned in phases (Privacy on Tempo). The first Zone launched on testnet the same day Zones were introduced (Introducing Tempo Zones). For Mainnet dates and upgrades, see Tempo mainnet launch date, chain ID and upgrades.
​

How can developers try Tempo Zones?

Tempo runs a testnet sandbox with two example Zones, Zone A and Zone B, for trying deposits, private transfers, swaps and withdrawals with test funds. Tempo notes the sandbox is an earlier deployment and its code does not carry over to current Zones.
​

The sandbox uses chain IDs 4217000006 and 4217000007 and test tokens OUSD and betaUSD. Tempo lists differences from current deployments: current portals accept encrypted deposits with a Tempo refund recipient, and the current permissioned runtime disables direct transfer and transferFrom calls inside a Zone. For a production Zone, developers get the endpoint, credentials, chain configuration and SDK version from its operator (Tempo Docs, Testnet Sandbox).
​

Frequently asked questions

These answers restate Tempo's published material on Zones. For questions about Tempo's fee model and token status, see Does Tempo have a token.
​

Are Tempo Zones fully anonymous?

No. The Zone operator sees activity inside the Zone, and deposits, withdrawals and cross-Zone moves expose some data on Mainnet (Privacy is live on Tempo).
​

Does the operator hold my funds?

Tempo says no. Funds are locked in a Zone contract on Mainnet and withdrawable by the user (Privacy on Tempo).
​

Who can run a Zone?

Tempo states the software is open source and permissionless, and that enterprises or infrastructure providers can operate Zones (Introducing Tempo Zones, FAQ).
​

Did this answer your question?