Helius CEO Mert Mumtaz breaks down Stripe and Paradigm's Tempo L1: legitimate move, but 'payments-only' claims won't hold up permissionless

Summary

Stripe and Paradigm's Tempo is a new layer-one blockchain aimed at payments and stablecoins, backed by Paradigm co-founder Matt Huang and Stripe, with a team of 15. Mert Mumtaz, CEO of Helius, a developer infrastructure platform for Solana, says the move makes strategic sense for Stripe — but takes issue with some of the claims around it.

The steel man first. Mumtaz thinks Stripe is right to build its own chain rather than pay rent to Solana or Ethereum. Owning the full stack, with Paradigm's technical depth and Stripe's distribution, is a defensible position. He'd probably do the same.

The payments-only claim won't hold permissionless. The core problem Mumtaz raises is definitional. A blockchain is permissionless by design, meaning anyone can deploy anything on it. The moment Tempo opens up, it becomes impossible to ring-fence it for payments. The only ways to actually enforce a payments-only scope are to build a non-Turing-complete chain like Bitcoin, where you literally can't do anything else, or to keep the chain permissioned. Tempo is launching permissioned, with design partners likely to be large banks and payments companies as the initial validator set. Mumtaz says that's fine for now, but the stated plan to go permissionless later is where things get complicated. Once you open it up, he argues, you get HFT operators, MEV farms, and meme coin launches competing for block space — the same dynamics that stress every other public chain.

Permissioned chains and the database question. Mumtaz is blunt that permissioned blockchains occupy uncomfortable territory. The moment you control who accesses block space, the gap between a blockchain and a fast database narrows significantly. There are residual benefits — transparency, auditability, shared standards, and a path toward progressive decentralization — but JPMorgan already runs a permissioned chain, and that precedent hasn't reshaped global finance. Tempo's early architecture may look more like a distributed ledger than a public blockchain.

Token and gas design. Because the initial validator set will be permissioned and run by institutional partners, Mumtaz says Tempo doesn't actually need a native token at launch. Proof-of-authority, rather than proof-of-stake, can secure the network when you already know and control who the validators are. Stripe has indicated gas fees will be payable in any designated stablecoin, which removes the volatile-token UX problem. A native token becomes relevant only if Tempo genuinely pursues permissionless operation and needs to bootstrap an open validator set.

User-facing implementation. Tempo almost certainly won't be consumer-branded. Mumtaz expects the blockchain layer to be abstracted entirely, similar to how ACH or Fedwire operates invisibly behind a Visa transaction. The most visible expression at checkout is probably