Vol. 1 · 7 Jun 2026

Side by side

Machine Payments Protocol (MPP) vs Reth

Machine Payments Protocol (MPP) and Reth both operate in the Protocol & Core part of the Tempo ecosystem. Machine Payments Protocol (MPP)An open standard for machine and AI-agent payments, co-authored by Stripe and Tempo.. Reth The Rust EVM execution client Tempo runs on..

Machine Payments Protocol (MPP) logo

An open standard for machine and AI-agent payments, co-authored by Stripe and Tempo.

Co-authored by
Stripe and Tempo
Sessions
Open + settle in 2 on-chain transactions via a signed voucher
Payments Directory
Launched with 100+ integrated services
Reth logo
Rethmainnet

The Rust EVM execution client Tempo runs on.

Developer
Built by Paradigm.
Repository
Open-source at paradigmxyz/reth on GitHub.
Implementation language
Written in Rust.
What it is
A production-ready Ethereum execution-layer client and modular blockchain SDK/node.

The record

How they compare

FieldMachine Payments Protocol (MPP)Reth
Typeprotocol componentprotocol component
CategoryProtocol & CoreProtocol & Core
Statusmainnetmainnet
ChainsTempo
WebsiteYes
DocsYes
GitHub
Confidence85%92%
Sources14

Keep exploring


Answers

Machine Payments Protocol (MPP) vs Reth: questions

What is the difference between Machine Payments Protocol (MPP) and Reth on Tempo?
Machine Payments Protocol (MPP) is An open standard for machine and AI-agent payments, co-authored by Stripe and Tempo.. Reth is The Rust EVM execution client Tempo runs on.. Both sit in the Protocol & Core part of the Tempo ecosystem.
Is Machine Payments Protocol (MPP) or Reth live on Tempo?
Both are live on Tempo mainnet. Machine Payments Protocol (MPP) is mainnet and Reth is mainnet.
Should I choose Machine Payments Protocol (MPP) or Reth?
It depends on your use case — both serve the Protocol & Core role on Tempo. Compare them on type, status, chains, integrations and source-backed confidence (Machine Payments Protocol (MPP): 85%, Reth: 92%), then read each full profile before deciding.