Dan Romero Clarifies MPP Protocol Misunderstandings, Emphasizes Multi-Chain and Multi-Payment Method Compatibility
Odaily News Dan Romero posted on the X platform to clarify common misunderstandings about the Multi-Party Payment Protocol (MPP), emphasizing that MPP's design goals are simplicity, scalability, and cross-chain compatibility, eliminating reliance on any single platform or payment method, including:
1. Not Limited to Tempo: MPP supports any payment method, including cryptocurrencies and fiat currencies. It has been extended to the Bitcoin Lightning Network, and there is a draft for Solana extension.
2. Fees Are Not Fixed at 1.5%: MPP itself has no inherent fees. Different payment methods may charge varying service fees, similar to existing payment systems.
3. Openness: MPP supported four payment methods from Day 1: Tempo (stablecoin), Stripe (multiple payment methods), Visa (credit card), and Lightspark (Bitcoin Lightning Network). Any party can quickly extend it. It has been submitted to the IETF to become a web standard.
4. Not Session-Only: MPP supports both per-request payments and session-based payments (payment channels). The latter is suitable for multiple small consecutive payments, which can reduce API round trips and improve speed.
5. Not Designed Solely for Tempo/Stripe: MPP has a simple, easily extensible structure. It does not rely on specific smart wallets, stablecoins, or blockchains. It achieves separation between secure HTTP communication and payment channels, enabling rapid integration by Visa and Lightspark.
