Skip to main content
Parly is designed as a focused privacy execution stack rather than a single frontend with hidden assumptions. This page explains the core system components, how they relate to one another, and why the product is structured this way.

​
High-level system design

Parly uses a hub-and-spoke model with Tempo as the privacy hub. At a high level, the stack consists of:
  • the web application
  • on-chain contracts
  • zero-knowledge circuits
  • the relayer runtime
  • the indexer
  • the SDK
  • the MCP server
  • optional analytics infrastructure

​
Network topology

The live network set is:
  • Tempo as the privacy and settlement hub
  • Ethereum
  • Arbitrum
  • Base
  • BSC
These supported spoke networks route into Tempo for shielding and receive stablecoin payouts from Tempo on outbound delivery.

​
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 at launch. That stability matters because frontend, relayer, SDK, and contract boundaries all need the same execution shape.

​
Relayer

The relayer is the private execution daemon. 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 mirrors:
  • deterministic authentication
  • recovery identity derivation
  • note handling
  • execution flow construction
  • approval discipline
  • outcome handling

​
MCP server

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

​
Repository and deployment posture

Parly maintains one private canonical monorepo as the internal source of truth. Public code distribution is split by role into:
  • a public relayer repo for operators
  • a public SDK repo for developers
  • a public MCP repo for agent integrations
A realistic production deployment is not frontend-only. Depending on the operated surface, the broader stack may include the web app, relayer runtime, indexer, MCP server, and optional analytics services.