Tempo introduced its payments-focused blockchain on September 4, with Stripe and Paradigm as incubators and banks, fintechs and technology companies helping shape its design. The project is aimed at businesses that want to move stablecoins without building their payment operations around a volatile network token.
The launch announcement describes a network intended for transfers such as payroll, international payouts and payments between software agents. Design partners include Deutsche Bank, Standard Chartered, Visa, Shopify and OpenAI. Their participation is a development role; it does not establish that all of them are already processing customer payments on Tempo.
Fees and records designed around money movement
Tempo plans to let users pay transaction fees in different stablecoins. Its design includes an automated exchange mechanism for those fees, alongside a dedicated payments lane intended to keep payment traffic from competing with unrelated blockchain activity.
Transfer memos are another practical feature. A business sending money needs to connect the payment with an invoice, employee or other accounting record. A transaction hash alone does not provide that context. Tempo also describes access lists and optional privacy features for organizations with restrictions on who may receive funds.
The chain is compatible with the Ethereum Virtual Machine and uses the Reth execution software. That gives developers a familiar starting point for contracts and tools, although each application still needs testing on the new network.
A specification, with adoption still to prove
Tempo advertises a design capable of more than 100,000 transactions per second and sub-second finality. Those are the project’s stated performance goals, not independently measured production results in this announcement.
Its proposed uses extend to tokenized bank deposits and small machine-to-machine payments. Whether those uses become practical depends on more than block speed: participating issuers, liquidity, wallet support and operational controls must also be available.
The governance plan calls for a diverse validator set and eventual permissionless validation. The September announcement describes that direction without demonstrating that the final model is already in place.
