Tempo has no native Token — so what do validators earn as compensation, and how does the chain's economic model actually work?
This is exactly the most distinctive part of Tempo's design. Most Layer 1 blockchains rely on a native token to play three roles at once: paying gas fees, rewarding validators, and serving as a speculative asset attracting early participants. Tempo strips out the third role, keeping only the first two: users pay transaction fees using stablecoins they already hold, and through the built-in Fee AMM mechanism, that Stablecoin fee automatically converts into whatever denomination validators actually want to receive (different validators may prefer different stablecoins). Validators' compensation comes directly from these fees, with no need to subsidize operations by issuing a separate volatile token.
The deeper logic behind this design: Tempo targets enterprise and institutional customers (banks, payment companies, AI platforms) that typically have no need to "additionally hold a speculative token" — and may even be required to avoid one for compliance reasons. Having no native token means activity on Tempo is less easily classified as a securities offering or a speculative product, which is a deliberate business and legal consideration for infrastructure trying to partner with regulated institutions, not a technical accident.
Tempo is currently still a "permissioned" network — what practical limitation does that impose on users or builders?
Permissioned means the parties who can currently become validators and participate in the network's core operations are a set of invited institutions (like Stripe, Visa, Zodia Custody), not anyone with sufficient resources who wants to freely join. This stands in clear contrast to permissionless public chains like bitcoin or Ethereum, where in theory anyone can run a Node and participate in validation. The direct implication of being permissioned: Tempo currently has a lower degree of decentralization, and the network's continued operation and security depend, to some degree, on the trustworthiness and stability of this group of invited institutions, rather than being spread across a large number of mutually unaffiliated participants the way a mature public chain is.
For an ordinary developer or builder, this doesn't mean Tempo can't be used at all — the officially published RPC endpoints, documentation, and SDKs are all open, and anyone can build applications on Tempo (like Deel, mentioned earlier). The restriction mainly applies to the layer of "who can participate in validation and network governance," not the layer of "who can use this chain." Tempo's official roadmap has stated an intent to evolve toward a permissionless validation model, but there's no clear timeline for that transition yet — meaning in the short term, evaluating any application on Tempo should factor in "the underlying network is still controlled by a small group of invited institutions" as a risk consideration.
Specifically, what problem is the Machine Payments Protocol (MPP) meant to solve, and how does it differ from ordinary auto-billing?
Traditional auto-billing (say, a subscription service's recurring charge) is fundamentally a pre-set authorization for a fixed amount at a fixed interval, with a bank or payment platform automatically executing the same transaction each cycle. What MPP is trying to solve is a far more complex, dynamic scenario: when an AI Agent needs to autonomously complete a series of unpredictable, variable-amount small transactions (say, an agent automatically comparison-shopping, renting compute resources, or purchasing API services), a traditional fixed-authorization model simply isn't sufficient — if every single transaction needed its own on-chain transaction and manual approval, the efficiency of an agent operating autonomously would be severely bogged down.
The "session" mechanism MPP introduces lets a user grant an agent a pre-authorized total budget and scope of use upfront (say, "this agent can spend up to $50 this week on cloud computing services"). Within that authorization, the agent can continuously and in real time stream small payments to different service providers, without needing to generate a separate independent on-chain transaction record for every interaction, and without needing to go back for manual approval each time. This means the core problem MPP solves is "how to let an autonomous agent complete financial decisions at high frequency and low cost within a bounded authorization" — an entirely different tier of need from traditional auto-billing's "fixed amount, fixed interval, single recipient" model.
If I'm considering using a service built on Tempo in the future (say, business payments or a payroll wallet), what standards should I use to evaluate that service's reliability?
The first checkpoint is the underlying chain's operational stability: Tempo's mainnet has only been running since March 2026, a relatively short operating history so far — it's worth checking whether it's experienced any major technical incidents or security events, and how transparently the team has handled them. The second checkpoint is the validator roster: since Tempo is currently a permissioned network, who the validators are and those institutions' own reputation and financial stability directly affect the entire chain's credibility. Institutions like Stripe, Visa, and Zodia Custody joining is a positive signal, but it's still worth continuing to watch whether the validator roster expands and diversifies over time.
The third checkpoint is the independent risk controls of the specific "upper-layer application" you're actually using — the stability of the Tempo chain itself doesn't mean every application built on top of it is equally reliable, just as using a reliable highway doesn't mean every car driving on it is safe. You still need to separately evaluate a specific service provider like Deel — its own compliance track record, how it custodies funds, and its past operating performance. Understanding that "underlying infrastructure" and "upper-layer application service" are two separate risk layers helps you ask more precise questions when evaluating any service built on emerging blockchain infrastructure, rather than simply judging it safe purely because "it's backed by a well-known company."
On September 4, 2025, payments giant Stripe and crypto venture firm Paradigm jointly announced Tempo — a Layer 1 blockchain purpose-built for stablecoin settlement. Mainnet officially launched on March 18, 2026, alongside the release of the Machine Payments Protocol (MPP) on the same day. What's most striking about Tempo isn't what it does — it's what it deliberately doesn't do: no native volatile Token, no Airdrop rumors, no points-reward program. In an industry where most new chain launches come wrapped in speculative hype, Tempo chose the opposite path.
Tempo runs on the Reth execution client paired with Simplex Consensus (implemented via the Commonware framework), delivering roughly 0.6-second deterministic Finality (meaning a confirmed transaction will never be reorganized). During its testnet phase, it demonstrated throughput approaching 20,000 TPS, with an architectural target above 100,000 TPS. The most critical design choice: Tempo has no native volatile token of its own — transaction fees are paid directly in stablecoins (including USDC, USDT, and others), with a built-in Fee AMM mechanism automatically converting whatever Stablecoin a user holds into whatever denomination validators want to be paid in. Users never need to hold a separate speculative token purely for paying gas. This design maps directly onto Tempo's positioning — it isn't a general-purpose chain that happens to also handle payments; it's a chain optimized from the ground up purely for payments and settlement.
Tempo is led by Paradigm co-founder and managing partner Matt Huang as CEO, and though incubated by Stripe and Paradigm together, Tempo operates as an independent company. What's genuinely notable is the design-partner roster it accumulated ahead of launch: Visa, Mastercard, Deutsche Bank, Standard Chartered, Revolut, Nubank, Shopify, OpenAI, Anthropic, Ramp, and DoorDash — spanning traditional banks, card networks, fintechs, and AI companies. The significance of this roster goes beyond endorsement — it signals Tempo's attempt to get ahead of the market and establish a cross-industry shared standards layer for stablecoin payments before the space fragments into a mess of incompatible standalone solutions. In April 2026, Stripe, Visa, and Zodia Custody joined as Tempo's first external validators. The network currently remains permissioned, though the official roadmap explicitly states an intent to move toward permissionless validation.
Released alongside mainnet, MPP is the most forward-looking part of this launch — an open standard, not tied to any specific payment rail, that lets AI agents and autonomous software make payments on their own, without needing human approval for every single transaction. MPP introduces a core concept called "sessions": letting an agent obtain a pre-authorized spending limit upfront, then continuously stream small payments within that authorization without each interaction needing to generate its own separate on-chain transaction. As AI agents that can autonomously execute tasks — and even autonomously spend money — become more common, this kind of "machine-to-machine" payment infrastructure is viewed as laying groundwork ahead of the next wave of applications, which is also why AI companies like OpenAI and Anthropic show up on Tempo's design-partner list.
If you're not directly using any product built on Tempo today, this chain itself won't immediately change your daily experience — but it's worth noting that Tempo is already serving as the underlying infrastructure for other services you might actually encounter, such as the previously launched Deel payroll wallet (DLUSD) and its companion yield feature, Tempo Earn, both of which are built on top of Tempo. Understanding "which chain a service you're using is actually built on" gives you an extra layer of context when evaluating these services: Tempo having no native token means you don't need to worry about some speculative token crashing and disrupting the payment feature you're actually using. But at the same time, Tempo is currently still a permissioned network — its validators are a set of invited institutions rather than fully open participants — meaning its degree of decentralization currently isn't in the same tier as long-running public chains like bitcoin or Ethereum. That's a factor worth weighing when evaluating this kind of emerging payment infrastructure.