Skip to main content
Parly is a private stablecoin execution system built around a hub-and-spoke architecture. This page explains the major components, how they work together, and how Parly supports private execution, recovery, verification, relayer operation, developer integration, and AI-agent workflows.

​
High-level system design

Parly uses Tempo as the payment and settlement hub, with supported EVM networks connected through a spoke model. At a high level, the stack consists of:
  • the web application
  • on-chain contracts
  • zero-knowledge circuits
  • supported cross-chain route providers
  • Waku transport for private relay communication
  • the relayer runtime
  • the indexer
  • the SDK
  • the MCP server
  • optional analytics infrastructure

​
Network topology

The live network set is:
  • Tempo as the payment and settlement hub
  • Ethereum
  • Arbitrum
  • Base
  • BSC
Supported spoke networks route into Tempo for shielding and receive stablecoin payouts from Tempo on outbound delivery. This keeps private execution, recovery, and verification centered within one consistent operating model.

​
Web application

The web application is the user-facing product surface. It handles:
  • wallet connection
  • authentication
  • private-state recovery
  • shielding
  • execution
  • activity review
  • scoped receipts
  • verification handoff

​
Contracts and circuits

The contract layer holds the settlement logic for shielding, private execution, and hub-and-spoke routing. The circuit layer defines the proof system used for private execution and keeps the execution model bounded and predictable. Parly uses a fixed padded execution model so the app, relayer, SDK, contracts, and circuits can share one consistent execution shape.

​
Cross-chain routes

Supported cross-chain routes move stablecoin value between Tempo and connected EVM routes. Parly keeps private execution centered on Tempo while allowing supported networks to participate through a coherent hub-and-spoke model.

​
Waku transport

Waku supports private relay communication between users and relayers. It helps encrypted execution requests move through a transport layer without making direct user submission the only path for private execution.

​
Relayer

The relayer is the private execution runtime. It:
  • receives encrypted relay requests
  • decrypts only the requests addressed to it
  • validates and submits execution
  • tracks uncertain post-broadcast states
  • reconciles pending outcomes later

​
Indexer

The indexer is the public data layer. It serves:
  • activity history
  • verification queries
  • provenance joins where available
  • analytics surfaces

​
SDK

The SDK is the developer integration layer. It supports:
  • deterministic authentication
  • recovery identity derivation
  • note handling
  • execution flow construction
  • approval discipline
  • outcome handling

​
MCP server

The MCP server is the bounded AI-agent tooling layer. It allows:
  • note recovery
  • immediate private payment execution
  • session-shaped machine-payment flows through the MPP-compatible adapter when enabled

​
Public integration surfaces

Parly provides public integration surfaces for operators, developers, and agent builders, including:
  • the relayer repository for operators
  • the SDK repository for developers
  • the MCP repository for agent integrations
These surfaces allow teams and builders to operate, integrate, and extend Parly without rebuilding the private execution model from scratch.