Skip to main content

Tempo vs Arc vs Plasma: Payment Chains Side by Side

Tempo, Arc, and Plasma are Layer 1 blockchains built around stablecoin payments. Here is how their consensus, gas tokens, launch status, and privacy plans compare, using each chain's own documentation.

Written by Eco
Tempo vs Arc vs Plasma: Payment Chains Side by Side

Tempo, Arc, and Plasma are three Layer 1 blockchains designed around stablecoin payments. They share an EVM execution model, but they differ in how fees are paid, how consensus works, and which privacy features are live. Tempo charges fees in USD stablecoins with no native token (Tempo fee specification), Arc uses USDC as its gas token (Arc Docs, Connect to Arc), and Plasma currently takes fees in its native token, XPL (Plasma Docs, Connect to Plasma).
​

This article compares the three chains side by side. Every fact comes from the chain's own documentation or blog. Where a chain's own pages do not state something, this article leaves it out. It does not rank the chains or recommend one over another.
​

What are Tempo, Arc, and Plasma?

All three are payments-focused Layer 1 networks that run EVM-compatible smart contracts. Each pairs a BFT consensus layer with an Ethereum-style execution environment, and each has added payment features at the protocol level rather than leaving them to applications (Plasma Docs, Overview; Arc Docs, System Overview; Tempo Docs).
​

Tempo describes itself as infrastructure for real-world payments at internet scale, and its mainnet went live on March 18, 2026, alongside the Machine Payments Protocol, an open standard co-authored by Stripe and Tempo (Tempo blog, mainnet). For more background, see What is Tempo blockchain.
​

Arc's documentation states that Arc is available on both testnet and mainnet, and its changelog lists "Arc mainnet is live" under a September 16 entry (Arc Docs, Welcome to Arc). Arc's docs route developers to the Circle Faucet for testnet USDC and to Circle wallets for connecting (Arc Docs, Connect to Arc).
​

Plasma calls itself "a payments-focused Layer 1 blockchain designed for financial products," and names Plasma One as the flagship consumer product built on the network (Plasma Docs, Overview).
​

Tempo vs Arc vs Plasma: comparison table

The table below collects the core network facts each chain publishes. Chain IDs and network names are taken from each project's connection page, and consensus details from each project's architecture page.
​

Attribute

Tempo

Arc

Plasma

Consensus

Simplex BFT via Commonware (Tempo Docs)

Malachite, a Tendermint BFT implementation (Arc Docs)

PlasmaBFT, a pipelined Fast HotStuff implementation (Plasma Docs)

Execution

Tempo EVM; supports standard Ethereum JSON-RPC methods (Tempo Docs)

Reth; targets the Osaka EVM baseline (Arc Docs)

Reth-based client (Plasma Docs)

Fee token

USD-denominated TIP-20 stablecoins; no native token (Tempo fee spec)

USDC (Arc Docs)

XPL live; multi-token fees planned (Plasma Docs)

Finality

Deterministic, sub-second (Tempo Docs)

Under 1 second (Arc Docs)

Deterministic, typically within seconds (Plasma Docs)

Validator set

Permissioned (Tempo Docs)

Permissioned Proof-of-Authority set of regulated institutions (Arc Docs)

n/a in Plasma docs

Mainnet chain ID

4217 (Tempo Docs)

5042 (Arc Docs)

Network status

Mainnet live since March 18, 2026 (Tempo blog)

Mainnet and testnet (Arc Docs)

"Plasma Mainnet Beta" (Plasma Docs)

Privacy

Zones live on mainnet (Tempo Docs)

Arc Privacy Sector on roadmap, not yet available (Arc Docs)

Confidential payment flows in development (Plasma Docs)

How do gas fees differ on Tempo, Arc, and Plasma?

Tempo has no native token and charges fees in USD stablecoins. Arc charges gas in USDC. Plasma charges fees in XPL today and is building a protocol paymaster so apps can let users pay in other tokens.
​

On Tempo, users can pay gas in any TIP-20 token whose currency is USD, as long as that token has enough liquidity on the enshrined Fee AMM against the validator's preferred token. Fee fields are specified in attodollars (10^-18 USD) per gas (Tempo fee specification). When no fee token is set, the protocol falls back to pathUSD, which is covered in What is pathUSD. Questions about a Tempo token are covered in Does Tempo have a token.
​

Arc's docs state that USDC is the gas token and that Arc "uses USDC for gas fees, not ETH." Its Fee Manager "stabilizes gas fees using USDC as the unit of account" (Arc Docs, System Overview). Arc lists several runtime differences from Ethereum, including native USDC with 18 decimals rather than 6 and a 20 Gwei maxFeePerGas floor in the mempool (Arc Docs).
​

Plasma uses the standard EVM gas model, and its docs say most standard transactions cost less than one cent. Plasma is building custom gas token support through a protocol-maintained paymaster that does not charge a fee, so apps can register whitelisted ERC-20 tokens for gas (Plasma Docs, Network Fees). For now, the connection page lists XPL as the only live fee token (Plasma Docs, Connect to Plasma).
​

How does consensus and finality compare?

All three use a BFT-family consensus protocol with deterministic finality. Tempo and Arc both document sub-second finality, while Plasma's docs say finality is typically reached within seconds. Tempo and Arc both describe permissioned validator sets.
​

Tempo uses Simplex BFT, implemented by Commonware, and produces blocks approximately every 600ms under normal conditions. Its docs state that finality is deterministic rather than probabilistic and that the active validator set is permissioned (Tempo Docs, Consensus and finality).
​

Arc's consensus layer runs Malachite, which Arc describes as a high-performance implementation of the Tendermint BFT protocol, with a two-phase pre-vote and pre-commit process. Its validator set is a Proof-of-Authority set composed of regulated institutions (Arc Docs, System Overview).
​

PlasmaBFT is a pipelined implementation of Fast HotStuff that runs the proposal, vote, and commit steps in concurrent pipelines. Plasma's docs say this design increases throughput and reduces time to finality, and that the roadmap includes dedicated payment lanes and faster finality (Plasma Docs, System Overview).
​

Which chains offer private payments?

Of the three, Tempo's docs describe a privacy feature as live on mainnet today (Tempo Docs). Arc lists its privacy module as a roadmap item, and Plasma says it is developing confidential payment flows.
​

Tempo Zones are "private stablecoin ledgers that use Tempo for deposits, withdrawals, and settlement." A Zone keeps balances and account activity private, and other users and public block explorers cannot browse the Zone's ledger (Tempo Docs, How Zones Work). Tempo's docs state that Zones is live on mainnet (Tempo Docs).
​

Arc describes a planned confidential execution environment for Solidity contracts that composes synchronously with the public EVM. Its docs state that the Arc Privacy Sector (APS) "and Stablecoin Services are on the roadmap and not yet available on Arc" (Arc Docs, System Overview).
​

Plasma's overview says it is developing protocol-maintained infrastructure for privacy-preserving transfers and confidential payment flows (Plasma Docs, Overview). The pages reviewed for this article do not give a launch date.
​

How do I connect a wallet to each chain?

Each chain can be added to an EVM wallet as a custom network using its chain ID and RPC URL. The values differ by network, so use the ones each project publishes.
​

Tempo Mainnet uses chain ID 4217 (Tempo Docs); RPC details and upgrade history are in Tempo mainnet launch date, chain ID, RPC and upgrades. Arc Mainnet uses chain ID 5042 with USDC as the currency and the RPC URL rpc.mainnet.arc.io; Arc Testnet uses 5042002 (Arc Docs, Connect to Arc). Plasma Mainnet Beta uses chain ID 9745 with currency symbol XPL, and Plasma Testnet uses 9746. Plasma notes its public RPC endpoints are rate limited and not meant for production (Plasma Docs, Connect to Plasma).
​

Frequently asked questions

These short answers restate points from the three chains' own documentation, covered in more detail above.
​

Do I need a native token to pay fees on these chains?

On Tempo, no; fees are paid in USD stablecoins (Tempo fee spec). On Arc, gas is paid in USDC (Arc Docs). On Plasma, XPL is the live fee token today, with multi-token fees planned (Plasma Docs).
​

Are Tempo, Arc, and Plasma EVM compatible?

Yes, with caveats. Plasma says contracts behave as on Ethereum mainnet (Plasma Docs). Arc says most contracts deploy unchanged but some runtime behaviors diverge (Arc Docs). Tempo publishes a separate page on how it differs from Ethereum (Tempo Docs).
​

Which chain is better for payments?

This article does not make that call. The right fit depends on the stablecoins, fee model, privacy needs, and network status a project requires, and each chain's documentation is the place to confirm current details.
​

Did this answer your question?