Skip to main content
REM designs, deploys, and operates dedicated Tempo Zones for institutional clients — private, EVM-compatible chains that sit alongside Tempo Mainnet. USDC settlement stays encrypted, compliance policies travel with the tokens, external observers see nothing. Built so payroll, treasury, and intercompany flows never hit the public chain.

​
Zone structure

Admission contract

Defines who can transact; anchored to a KYB decision from the operator.

Private state tree

Balances and transactions committed as opaque commitments; only Zone participants can resolve.

Bridge

Value enters and leaves through public stablecoin issuance; enforces admission and AML controls.

​
Three-step flow

1

Deposit

rem.zone.deposit() moves funds from Tempo Mainnet into the Zone. Sender and amount public; recipient and intent stay in Zone.
2

Transact privately

rem.zone.transfer() — transfers encrypted; external observers see nothing.
3

Withdraw

rem.zone.withdraw() — uses cryptographic commitments; REM cannot block legitimate exits.

​
Capabilities

  • Encrypted intra-zone transactions — opaque to everyone except Zone participants and the operator
  • Non-custodial — REM can view for compliance but cannot move, freeze, or confiscate
  • EVM-compatible — existing Solidity, wallets, and tooling work unchanged
  • TIP-403 compliance — policies defined on Mainnet replicate to the Zone automatically
  • Mainnet-interoperable — withdraw to Mainnet anytime; liquidity pools unified
  • Multi-token — supports any TIP-20 token (USDC and others) across multiple zones

​
Trust model

REM (Operator) CANREM (Operator) CANNOT
Sequence transactionsMove user funds
View tx details (operator-level audit visibility)Freeze or confiscate assets
Manage zone livenessBlock valid withdrawals (users exit with cryptographic proof)
Enforce TIP-403 policiesShare tx details outside compliance scope

​
Use cases

Corporate payroll

Pay staff in stablecoins without leaking salaries to the public chain.

Treasury management

Move balances between entities and counterparties without revealing positions.

Intercompany B2B settlement

Settle at scale across subsidiaries, with policy enforcement and unified reporting.

Agentic infrastructure

Private settlement layer for fleets of agents — pricing, behavior, and cashflow remain confidential.

​
Quickstart

import { REM } from "@rem-money/sdk";

const rem = new REM({ apiKey: process.env.REM_API_KEY });

await rem.zone.deposit({
  zoneId: "zone_acme_payroll",
  from: "wallet_treasury_mainnet",
  amount: "250000",
  currency: "USDC",
});

await rem.zone.transfer({
  zoneId: "zone_acme_payroll",
  from: "zone_wallet_treasury",
  to: "zone_wallet_employee_4781",
  amount: "8500",
});

await rem.zone.withdraw({
  zoneId: "zone_acme_payroll",
  from: "zone_wallet_employee_4781",
  to: "wallet_employee_4781_mainnet",
  amount: "8500",
});

​
Custom solutions

Tempo Zones are not a self-serve product. Every zone is a designed deployment — REM works with you on admission, governance, bridge integration, and operator tooling.

Zone design

Topology, participant model, governance, and admission rules tailored to the use case (payroll, treasury, B2B settlement, agent fleet).

Admission contracts

Custom KYB and access logic — including multi-operator setups, tiered participants, and revocation flows.

Bridge integration

Connect Zone liquidity to your existing treasury, core banking, or other Tempo Zones — including circuit breakers and rate limits.

Operator tooling

Compliance dashboards, supervised viewing, regulator access, sequencer monitoring, and incident playbooks.

Commission a Zone

Tell us the participants, the flows, and the regulator. We’ll come back with a Zone design and operating proposal.