FinWiki
日EN中

Tempo vs Arc · 2 paths for institutional-chain validator design

Confidence: Likely Updated 2026-05-26 Review by 2026-09-22 Sources 4 Machine-translated Original (JA)
#systems#validator#tempo#arc#institutional-chain#poa
On this page

Wiki route

This entry sits under systems index. Read it against EigenLayer Support for New L1 Bootstrapping-Phase Security · Tempo/Arc Potential Route for peer / contrast context and fintech index for the broader system / regulatory boundary.

Key facts

  • Tempo external validator count = 4 (carefully selected institutions)
  • Tempo BFT fault tolerance = ⌊(4-1)/3⌋ = 1 (tolerates up to 1 malicious or offline nodes)
  • Tempo’s Nakamoto coefficient is extremely low, making regulatory single-point-of-failure risk prominent
  • Arc phase 1 = PoA (team + founding-institution whitelist)
  • Arc phase 2 = permissioned PoS (20-50 KYC validators)
  • Arc phase 3 = governance PoS (theoretical target, may not be achieved)
  • The three-phase template is cited by Kinexys / Mony

Mechanism / How it works

Tempo · 4 external-validator model: Tempo team internal validators + 4 carefully selected external institutions (major custodians / major staking service providers / sovereign-fund management / strategic partners). Each validator is bound by KYC + legal agreements → accountability is possible. No inflationary rewards; yield comes from protocol-fee distribution. No MEV (institutional OTC leads order flow). Design philosophy: a small number of highly qualified participants > numerical dispersion, sacrificing decentralization to secure performance and accountability.

Arc · three-stage evolution: Phase 1 PoA is centralized but allows rapid iteration; in phase 2 the KYC validator set expands to 20-50 社 and introduces staking economics, but entry remains controlled; in phase 3 governance decides validator-set expansion, with full decentralization as the long-term goal. Design philosophy: acknowledge that institutional chains must be centralized at launch, and earn ecosystem trust through a clear roadmap.

Comparison dimensions:

DimensionTempoArc
Validator count4 carefully selectedEvolving (PoA → 20-50 → ?)
Decentralization pathNot pursuedThree-stage progression
ConcentrationOpenly acceptedCovered by roadmap
BFT fault tolerance1/4 (fragile)Phase-dependent
Core trade-offPerformance + reliabilityCompliance launch + gradual opening

Origin & evolution

2024 Early permissioned pools from Aave Arc / JPM Onyx → “institutional chains must be permissioned at launch” became consensus. 2025.04 Tempo disclosed its 4 external-validator design → the minimum model became visible. 2025 Circle published the Arc three-stage roadmap → the progressive-decentralization template was established. 2025-2026 Kinexys / JPMD / Mony / many tokenized-deposit projects cited Arc’s three-stage template. The fundamental reason the 2 paths coexist: Tempo serves retail merchants (extremely performance-sensitive), while Arc serves institutional clients (extremely sensitive to the compliance narrative).

Sources