
Arc
Institutional
Tempo
How Payment Blockchains Handle Validator Performance and Finality
Payment blockchain finality on Tempo and Arc takes under a second, but only while two-thirds of validators stay online. What happens when they go offline?
NOV 17, 2026
Last updated NOV 17, 2026 · V1
Payment blockchains finalize stablecoin transfers in about a second. What happens to settlement when validators slow down or drop offline?
TL;DR
- Payment chains such as Tempo and Arc settle stablecoin transfers in under 1 second, which cannot be reversed.
- Settlement continues at that speed while at least two-thirds of validators are online.
- If more than one-third go offline, the chain pauses and resumes once enough validators come back online.
- A pause delays new payments, and payments that were already final stay settled.
- Tempo and Arc choose their validators by invitation and neither chain slashes stake; Plasma cuts rewards for misbehavior.
- Payments teams need a written plan for a chain pause and a way to monitor validator status.
A card payment is approved in seconds, but the merchant usually receives the money days later. A payment blockchain reverses that order: a stablecoin transfer on Tempo or Arc is fully settled in under 1 second.
That speed comes from the validators, the operators who confirm each block. For teams comparing stablecoin payments with card networks, the obvious follow-up is what happens to settlement when those validators slow down or go offline.
It depends on the chain’s consensus rules and on the procedures dictated by a payments team. Banks and payment networks integrating stablecoins into their products need to plan for both.
What does “final” mean for a stablecoin payment?
A payment is final when the network can no longer reverse it. On a payment blockchain that happens a finalized transfer is considered as settled within about a second.
A transaction goes through two stages. It is first confirmed, meaning it appears in a block, and then finalized, meaning enough validators have signed that block for the network to treat it as permanent.
On general-purpose blockchains, finality takes longer. Bitcoin payments become harder to reverse with each new block and are usually treated as final after about 1 hour, while Ethereum reaches finality in about 14 minutes.
Payment chains use deterministic finality, which removes that wait. Once a block is finalized on Tempo, its transactions can no longer be reorganized out of the chain.
The practical rule for integrators is to credit a customer at finalization. A transaction that has only been confirmed can still be dropped if its block does not collect enough validator signatures.
On Tempo, no extra confirmations are needed after finality. An integration asks the node for the latest finalized block through the eth_getBlockByNumber call with the finalized tag.
For treasury teams, this means consensus itself confirms settlement, and a finalized transfer can be booked as received cash. It also makes atomic settlement at T+0 possible, where payment and delivery complete in the same transaction.
How Tempo, Arc and Plasma reach finality
These chains finalize a block as soon as more than two-thirds of their validators agree on it, using a class of protocols known as Byzantine fault tolerant (BFT) consensus. The chains differ mainly in who is allowed to validate and how they handle validators that misbehave.
| Chain | Consensus engine | Validator model | Who can validate | Finality | Status (November 2026) | Slashing |
| Tempo | Simplex BFT via Commonware | Permissioned, no stake or native token | Approved operators, including Visa, Stripe, Zodia Custody and MoneyGram | Deterministic, under 1 second; blocks about every 600 ms | Public mainnet since March 18, 2026; T13 live since November 3, 2026 | None; no stake to slash |
| Arc | Malachite BFT | Permissioned PoA | Circle plus 11 founding institutions joining in phases | Deterministic once more than two-thirds of validators commit; under 1 second | Public mainnet since September 16, 2026 | None under PoA; PoS under review for 2027 |
| Plasma | PlasmaBFT (Fast HotStuff in Rust) | PoS, trusted validators first | Trusted validators; expansion and permissionless phases planned | Deterministic, within seconds | Mainnet beta since September 25, 2025 | Reward slashing only; no stake slashing |
Tempo (Simplex BFT)
Tempo is the stablecoin payments chain developed by Stripe and Paradigm, with public mainnet since March 18, 2026. It uses the Simplex BFT protocol built by Commonware and produces a new block about every 600 ms.
The validator that proposes each block is picked at random, which makes any one proposer harder to target. The first external validators joined on April 14, 2026. Validators are approved by invitation and take part without posting any stake or holding a native token.
Arc (Malachite BFT)
Arc is Circle‘s stablecoin-native Layer 1, secured by the Malachite consensus engine and a validator set of approved institutions. This model is called proof of authority (PoA): validators are trusted because of who they are, without any stake at risk.
Public mainnet opened on September 16, 2026, with 11 founding institutions joining Circle in phases. The founding group includes:
- BlackRock
- DTCC
- ICE
- Mastercard
- Visa
Arc charges network fees in USDC, as set out in the Arc network documentation, while Tempo has no native token at all. That difference in fee and token design also shapes how each chain pays its validators.
Plasma (PlasmaBFT)
Plasma uses PlasmaBFT, its own version of the Fast HotStuff protocol. In normal conditions, a block becomes final after 2 rounds of validator votes, and finality arrives within seconds.
Like Tempo and Arc, Plasma needs more than two-thirds of validators to agree on each block. Conflicting blocks can only both become final if more than one-third of validators act maliciously.
What happens when validators slow down or go offline?
A payment chain keeps settling transfers while at least two-thirds of its validators are online. If more than one-third go offline, the chain pauses until enough of them come back.
The chain is built to keep moving (liveness) and to never record 2 conflicting versions of the same payment (consistency).
On Tempo, the chain stays consistent while fewer than one-third of validators are faulty or malicious, so a network of 4 validators can lose 1, and a network of 10 can lose 3.
| Condition | Network behavior | Effect on payments |
| Network partition | Block times may increase; finalized blocks stay final | Slower confirmations, no reversals |
| Validators offline within the one-third threshold | Network continues with the remaining validators | Settlement continues |
| More than one-third of validators offline | Network halts and resumes when the threshold is restored | No new finalized blocks; outgoing payments queue |
Tempo is designed to halt when the threshold is lost: Simplex consensus stops before it would finalize conflicting blocks, and payments that were already final stay settled during the pause.
Solana sets a different threshold in its Alpenglow design. Its 20+20 model tolerates up to 20% malicious stake plus another 20% offline, which lets it finalize blocks in one voting round.
Payment chains keep the standard one-third threshold. For a payments team, that makes the halt point easy to estimate: count the validators and divide by 3.
Validator location also affects how often a chain pauses. If a group of them share one cloud provider or region, one outage can remove one-third of the voting power at once, a pattern seen in geographic clustering of validators.
How payment chains keep validators accountable without slashing
Payment chains enforce validator performance by deciding who is admitted and removing operators who underperform. None of the three chains takes away a validator’s stake as a penalty today.
On public proof-of-stake (PoS) networks, a validator that signs 2 conflicting blocks loses part of its stake. Operators on those networks build key management and failover controls to prevent slashing.
Tempo admits validators by invitation. It publishes procedures for rotating validators and managing their lifecycle, so the network can replace an operator without a token penalty.
Arc validators are known institutions admitted under a proof-of-authority model. Each one works under set governance rules and performance and compliance standards.
Plasma uses proof of stake with reward slashing only. A validator that misbehaves loses block rewards and keeps its staked capital, and going offline carries no penalty.
When institutions operate the validators, the consequences of misbehavior are legal and reputational. A bank or card network that operates a validator answers to its regulators and its contracts, which discourages misbehavior.
The trade-off is concentration. A small group of known operators is easy to coordinate, and also easier to pressure or to take offline together.
Concentrated or coerced validator sets can lead to censored or stalled stablecoin payments. Stablecoin issuers and integrators reduce that exposure by tracking how voting power is spread across a chain’s validators.
How payment chains plan to open validation to more operators
All three chains plan to open validation to more operators over time. Finality would stay deterministic, but the operators who make up the two-thirds majority would change.
Circle minted 10 billion ARC tokens in September 2026 as a technical step and is exploring a move from proof of authority to proof of stake in 2027. Whether the ARC token launches publicly is still undecided.
Tempo has said it will keep adding validators until validation is permissionless. It had not published a date for that step as of November 2026.
Plasma plans to open up in 3 phases:
- Trusted validators at mainnet launch.
- A larger validator set, tested under heavy load.
- Open participation for any qualified operator.
Under permissionless PoS, the two-thirds majority is counted in stake. A chain with a small number of large stakers could then pause or stall if those few operators go offline together.
Institutions that want to operate a validator can prepare before access opens. White-label validator infrastructure lets a bank or custodian operate a validator under its own brand on managed infrastructure.
With Validator-as-a-Service, a specialist team takes over day-to-day node operations. The institution keeps the validator identity, and the operator keeps the node online and up to date.
What validator operations show about payment-chain finality
On a payment chain with a small validator set, each operator holds a large share of the vote. One operator’s outage moves the whole network closer to the one-third pause threshold.
Operators sometimes have to choose between maximizing uptime and protecting the validator key. A paused validator can rejoin the network, while a double-signed vote is a permanent record of misbehavior, so professional operators put key protection first.
Everstake, a non-custodial validator and staking provider with 130+ networks to date, describes this approach in its guide to validator uptime and key protection.
Everstake keeps only one live copy of each validator key, an approach known as a single-active-signer setup. Anti-slashing databases and hardware security modules (HSMs) back that setup, so switching to a backup node cannot produce a double-sign.
Everstake spreads its infrastructure across regions and providers, and sentry nodes handle public network traffic so signing machines have no direct public connection. A regional or provider outage is therefore less likely to take a validator offline.
Prometheus and Grafana dashboards monitor every node, and a 24/7 DevOps team responds to incidents. Software updates are deployed through automated CI/CD pipelines without taking validators offline.
Everstake offers these controls to financial institutions and payment providers through its institutional staking infrastructure.
Integrator checklist for payment-chain settlement
Payments teams can keep settlement predictable on a payment chain with 5 controls.
- Credit only finalized blocks. Book a payment as received once its block is finalized, using the chain’s finalized block tag.
- Monitor validator status. Track the active validator set and the chain’s status page, and set an alert for when block production slows.
- Write a chain-pause procedure. Decide in advance how outgoing transfers queue and what customers see when a payment is delayed. Name a backup payment channel for time-critical transfers.
- Follow the upgrade calendar. Tempo schedules its T14 upgrade for mainnet on November 24, 2026, and node operators must upgrade before it activates.
- Reconcile with memos. Attach a reference to each transfer so finance teams can match it to an invoice, as described in reconciling stablecoin payments with on-chain memos.
Everstake provides validator and staking infrastructure for tokenization platforms and payment providers.
Operating stablecoin settlement or planning to validate on payment chains? Talk to Everstake‘s institutional team.
FAQ
Is finality on payment blockchains irreversible?
Yes, once a block is finalized on a payment chain, the network cannot reverse the transfers in it.
What happens to payments if a stablechain halts?
New transfers wait in a queue until at least two-thirds of validators are back online, and payments that were already final stay settled.
Who operates the validators on Tempo and Arc?
Both chains use invited institutional operators, and Visa operates a validator on each network.
Do payment blockchains slash validators?
Tempo and Arc have no stake to slash, and Plasma withholds rewards for misbehavior while leaving staked capital untouched.
How fast is finality on Tempo, Arc and Plasma?
Tempo and Arc finalize in under 1 second, with Tempo producing blocks about every 600 ms, while Plasma finalizes within seconds.
Can institutions operate validators on payment chains?
Yes, Tempo and Arc admit validators by invitation today.
Share with your network