Stablechain Architecture Reference
Purpose-built blockchains for stablecoin settlement. Compliance embedded at the consensus layer. The compliance-depth thesis, visualized.
Compliance depth at a glance — Arc · Tempo · Ethereum
The Thesis
A stablechain is a purpose-built blockchain designed from the ground up for stablecoin settlement. Unlike general-purpose chains where compliance is bolted on at the application layer, stablechains embed compliance mechanisms at the consensus and execution layers — making them impossible to bypass.
01
Stablecoin-native gas
Pay transaction fees in USDC or USDS — no need to hold volatile tokens. Simplifies accounting and removes friction for institutional users.
02
Instant finality
Sub-second transaction finality via BFT consensus. No waiting for block confirmations. Payments settle as fast as they clear on traditional rails.
03
Gas-free transfers
Dedicated payment lanes and sponsored transactions mean end users never see gas fees. The chain operator absorbs or bakes costs into the settlement.
04
Compliance hooks at L2–L3
KYC gates, transfer policies, AML screening, and confidential transactions enforced by the chain itself — not by middleware vendors that can be bypassed.
05
EVM compatibility
Full Solidity support means existing DeFi tooling, wallets, and developer skills transfer directly. Compliance is additive, not a rewrite.
The Migration
Over six years, compliance mechanisms have migrated from the application layer down toward consensus. Each generation embeds rules deeper, making them harder to circumvent and easier to audit.
2020 — L5 Application
Manual KYC vendors, wallet-level screening. Compliance lives entirely in the app. Switch wallets, bypass checks.
2022 — L4 Middleware
Chainalysis APIs, Circle compliance APIs, CCTP. Better coverage, but still opt-in — protocols can choose not to integrate.
2024 — L3 Execution
ERC-4337 programmable validation, Token-2022 Transfer Hooks. Compliance encoded in smart contracts — harder to bypass, but still at the application's discretion.
2025–26 — L2 Consensus
Arc permissioned validators, Pharos ZK-KYC, Tempo invited validators. Compliance is part of the consensus itself. No block gets produced without it.
The Chains
Arc · Circle
Arc
Institutional-grade stablecoin L1. Malachite BFT consensus with permissioned validators. Confidential transfers via TEE.
Tempo · Stripe / Paradigm
Tempo
Payments-focused L1. Simplex BFT with invited validators. Dedicated payment lanes, enshrined DEX, TIP-403 policy registry.
Pharos
Pharos
RealFi-focused L1 with ZK-KYC and programmable AML at the consensus layer. Zero-knowledge identity proofs.
Base · Coinbase
Base (L2)
OP Stack rollup with AgentKit OFAC/KYT and x402 at L4. Inherits Ethereum consensus. Strong middleware compliance.
Ethereum
Ethereum
General-purpose L1. Open PoS consensus. Compliance at L3–L4 via ERC-4337 and third-party APIs. No consensus-level gates.
Solana · TRON
Solana & TRON
General-purpose L1s. Open consensus. Solana has Token-2022 hooks at L3; TRON has minimal compliance — wallets only.
Proof of Concepts
Each POC demonstrates a unique compliance mechanism with running code and architectural visualizations.
POC 1
Arc Confidential Transfers
TEE-shielded amounts with regulatory view keys. Privacy and compliance coexisting at L3.
POC 2
Tempo Payment Lanes
Dedicated payment blockspace with guaranteed inclusion. TIP-403 issuer policy registry.
POC 3 — Centerpiece
Stablechain Comparator
Side-by-side Stack Diagram comparison. Place any two chains next to each other and see the depth thesis.
POC 4
MPP ↔ x402 Bridge
Protocol interoperability between Tempo's Machine Payments Protocol and Base's x402.