Skip to main content

What Parly is

Parly is a privacy protocol for stablecoin movement across supported networks, with Tempo as the privacy hub. It enables users to move supported stablecoins into private balance, execute private payouts, and verify disclosed payment lanes when independent confirmation is required. Parly is built for private stablecoin execution with a clear operating model. Its public product surface is centered on shielding, private settlement, deterministic recovery, selective verification, and integration for developers and agent-driven systems. At launch, Parly supports direct shielding on Tempo, spoke-origin shielding into Tempo, private same-network payouts on Tempo, private cross-network stablecoin-only payouts to supported spoke networks, third-party private relay execution over Waku, self-relay fallback, a public verification portal, a developer SDK, an MCP server, and an MPP-compatible adapter at the SDK and MCP boundary.

Assets and settlement model

Parly is stablecoin-native. At launch, the core product supports private stablecoin movement using supported stablecoin pools such as USDC and USDT, with Tempo serving as the privacy and settlement hub. This gives users and operators a clear model for shielding, execution, recovery, and verification.

Supported networks and routing model

Parly uses a hub-and-spoke topology with Tempo as the privacy hub. At launch, the supported network set is:
  • Tempo as the settlement and privacy hub
  • Ethereum
  • Arbitrum
  • Base
  • BSC
Supported spoke networks route value into Tempo for shielding and receive private stablecoin payouts from Tempo on outbound delivery. This keeps privacy state, recovery logic, and verification logic centered within one consistent operating model.

Privacy and recovery

Parly’s recovery model is designed so access to private state does not depend on a single browser session or a single device. Private state is tied to a deterministic wallet-derived recovery identity together with the on-chain note and envelope data emitted during shielding and execution. Browser storage may improve convenience, but it is not the source of recovery truth. Parly uses encrypted note envelopes so that a user can recover live notes from chain-visible history on a future device. The envelope is created for the intended owner, and only the owner with the matching recovery private key can open it. This keeps recovery anchored to wallet control rather than device memory.

Verification and selective disclosure

Parly includes a public verification flow designed for selective disclosure. A user can disclose one payout lane without exposing the wider execution set. This is useful for counterparties, exchanges, auditors, finance teams, and reviewers who need confidence in one payment without requiring visibility into the rest of a private treasury graph. Verification is intentionally scoped. It is designed to confirm the disclosed payout lane clearly and independently.

Developer and agent integrations

Parly supports developer and agent integrations through a public SDK and an MCP server. It also supports MPP-compatible integration at the SDK and MCP boundary. This allows Parly to fit into machine-payment and agent-driven workflows while preserving a clear core settlement model.

Reliability and execution clarity

Parly distinguishes clearly between submitted, pending, confirmed, and failed states. Private relay execution stops at encrypted submission until execution is actually confirmed. Direct browser execution should only be presented as successful once a confirmed result exists on Tempo. When an outcome is still uncertain, Parly keeps that uncertainty visible.

Current support at launch

Parly currently supports:
  • stablecoin-only private pools
  • Tempo as the settlement hub
  • shielding on Tempo
  • spoke-origin shielding into Tempo
  • private same-network payouts on Tempo
  • private cross-network stablecoin-only payouts to supported spoke networks
  • private relay over Waku
  • self-relay fallback
  • selective verification
  • developer SDK
  • MCP-based agent integration
  • MPP-compatible integration at the SDK and MCP boundary only
  • off-chain removable shield-mining analytics where enabled

Next steps