Bankless Podcast Summary
Episode: Tempo Mainnet: The Race to Agentic Commerce
Date: March 19, 2026
Guests: Giorgios Konstantopoulos, Brendan Ryan (Engineers, Tempo)
Host/Co-hosts: Bankless Team
Episode Overview
This episode marks the mainnet launch of Tempo, a new blockchain L1 focused on payments, agentic commerce, and machine-to-machine (M2M) transactions. The conversation centers on Tempo’s Machine Payments Protocol (MPP), the rise of agentic AI (autonomous agents with spending power), the future architecture of the web, and the implications for stablecoins, payments, and developer experience. The episode contrasts Tempo’s novel approach with existing standards (notably X402), explores strategic decisions (L1 vs L2), dives into technical and philosophical questions, and looks ahead to the "agentic web" era.
Key Discussion Points & Insights
1. Tempo Mainnet Launch and Initial Focus
- The launch centers on enabling AI agents to make autonomous web payments (“agentic payments”), moving beyond classic stablecoins and remittance use cases.
- Initial partnerships include working with Tribe and integrations with Stripe, Visa, and Bitcoin Lightning.
- Quote (B, 00:33):
"Today's launch is focused on AI agents using the machine payments protocol to pay for things on the web autonomously…today's launch was all about the agentic payments."
2. Why Agentic Commerce?
- Engineers themselves found it inefficient to manually deal with logins, API keys, and paywalls. Enabling agents with wallets solves this friction directly.
- There’s a massive tailwind in giving AI agents payment capabilities, predicted to transform commerce on the web.
- Quote (B, 02:05):
“…this AI agents want to do more but they're not able to. They get bottlenecked on the human...we cannot ignore this wave that's coming.”
3. The Machine Payments Protocol (MPP)
- MPP is introduced as an open, payment-method-agnostic protocol for machine-to-machine (M2M) payments.
- Designed for composability and performance, MPP can support crypto, credit cards, and other methods.
- MPP is positioned as more general and developer-friendly compared to X402 (backed by Coinbase/Cloudflare/Stripe), with aspirations to become the standard for web payments (spec submitted to IETF).
- Quote (D, 04:04):
“MPP...is a payment method interface which agents can interact with really, really efficiently.” - On Competition (B, 10:10):
“Technically, because MPP is more general, you can express X402 in MPP...I don't think you can express MPP in X402 terms.”
4. Interoperability & Ecosystem Support
- MPP and X402 can coexist; Stripe, Cloudflare, and Visa are integrating both.
- MPP is already live on Tempo but can work across EVM and other chains.
- Quote (B, 12:03):
“...Absolutely...it can be deployed on any chain. It can be deployed on evm, svm, whatever you want.”
5. The Agentic Web, Business Models, and Internet Evolution
-
Discussing Ben Thompson’s Agency and Original Sin article, the speakers highlight how past lack of payment protocols led to an ad-driven Internet; the agentic era can shift this to direct pay-for-content among AI agents.
-
Quote (B, 17:31):
“...people just have low patience...they want their agents to be equipped with money...so their agents can then go and do payments on the web.” -
Risks of agents in an ad-based future vs. payments-funded models are debated, with consensus that payments-based is healthier and safer.
-
Quote (B, 24:31):
“...people want to feel safety when telling people their secrets…people use the Agent...as a more trusted confidant than...the Google search bar…”
6. Key Related Standards & Protocols
- MCP (Model Context Protocol) from Anthropic (agent–service communication).
- NL Web from Microsoft (enables agents to ‘see’/interpret websites).
- MPP/X402 close the loop by enabling agents to pay.
- The future: “You never go to a website again; you just talk to your AI” (paraphrasing Ilya from NEAR, 27:21).
7. Developer & User Experience
- MPP is designed for developer ergonomics: payments as easy as basic REST/auth calls; no API key hassle.
- Tempo’s onboarding is agent-first–spinning up wallets for agents, with seamless biometric/passkey security. Users authorize agents with spending caps.
- Demo Highlight (34:08–36:22):
- Install Tempo skill in your agent; agent is given wallet, pays for services, can even make voice calls.
- Wallets use biometric/passkey secured enclave with scoped ephemeral keys for safe spending.
- Wallet Security (B, 38:43):
“It doesn't use any third party. It uses passkeys...you can use passkeys without an intermediary to go and transact with the chain.”
8. Tempo Tech Stack & Chain Details
- Built on the high-performance Reth client (same as Ethereum L1/L2s), leveraging modular EVM infrastructure.
- Special features:
- Payment Lane: Dedicated block space for payments, ensuring stable, predictable fees.
- Validators: 11 at launch; permissioned set, with plans to decentralize further.
- Throughput: ~10,000 TPS in recent benchmarks, sub-second block times (400–600ms), single-slot finality.
- Node requirements: Intentionally low, can run on commodity hardware; leveraging Reth’s minimal mode and Commonwealth consensus/erasure coding for bandwidth efficiency.
- Quote (B, 46:21):
“The AI has really transformed how we work on all of this stuff.”
9. L1 vs L2 Debate
- Despite deep backgrounds in Ethereum L2s, Tempo is an L1 for “developer velocity and self-expression”–payments require customizations difficult to achieve within Ethereum’s governance/process.
- L2s necessary for Ethereum’s cypherpunk goals, but for targeted payment scaling and custom features, a purpose-built L1 is more feasible.
- Tempo already incorporates L2 techniques, e.g., payment channels (sessions).
- Quote (B, 50:49):
“The simplest answer is just developer velocity and being able to self express...We didn't want to be bound by the DA that the Ethereum world would provide us...for our ambitions, we felt like we had to...self express…”
10. Tempo’s Ethos, the Cypherpunk Paradox, and Ethereum
- Acknowledges tension in the community as core “heroes” (builders) move to Tempo, yet sees Tempo and Ethereum as parallel, complementary.
- Work on Reth and infrastructure is open source, benefiting both ecosystems.
- Quote (B, 62:09):
“...all the work that we're doing, yes, it's making Tempo work. But these are the same code bases...So that's why to me, I don't know. While I empathize...we just do both...”
11. Future of Reputation and Discovery
- Agent reputation (e.g., ERC-8004) expected to be crucial; Tempo is monitoring/participating but not prescriptive.
- Quote (D, 64:57):
"I think it's, it's very much inevitable..."
12. Tempo Asset Strategy
- TIP20: Stablecoin-specialized ERC20 extension with issuer-focused features and protocol-level DEX (for auto-swaps, fee sponsorship).
- Permissionless deployment for any token/memecoin/DeFi contract.
- Native support for EVM contracts/wallets, with ongoing efforts for stablecoin UX in wallets like MetaMask.
- No on-chain KYC/AML; up to app layer.
13. Advice for Builders in the Agentic Web Era
- Build paid APIs and services that reduce friction for agents and developers.
- Monetize knowledge/data/services through API endpoints using MPP; agents can discover and pay for services automatically.
- Opportunities for new models in content pricing, API search engines for agents, and self-sustaining “von Neumann probe”-like businesses.
- Quote (B, 73:16):
“My take would be just build paid APIs...get into that mindset...figure out how to make it pay for itself, and then...expand..."
Memorable Moments & Quotes
- On the Agentic Shift (16:49):
"I use my agent to do things more than I click around in Chrome...I want to make bookings, I want to buy things...I want their agents to be equipped with money..." — Giorgios (B) - On Payment Protocol Wars (11:55):
"So may the best standard win. I guess that's where we are right now..." — Host (C) - On the End of Websites (27:22):
"The same way Tony Stark talks to Jarvis...the Internet's in the background..." — Host (A) - On Codebase Shared With Ethereum (62:09):
"We're just doing both from our end and we're good and we think we can do both very well." — Giorgios (B) - On the Future of Startup Opportunity (71:54):
"Figure out, what's the work that they're doing and make that more legible to them...we really developed mpp...the most efficient conduit..." — Brendan (D)
Timestamps for Important Segments
| Timestamp | Segment / Topic | |-------------|--------------------------------------------------------| | 00:15 – 03:57 | Tempo mainnet launch focus: agentic payments & AI | | 04:04 – 07:02 | What is MPP and how is it different from X402? | | 12:03 – 13:17 | MPP’s chain-agnostic potential | | 16:49 – 22:06 | Agentic commerce: end of ad-based web? | | 27:21 – 31:16 | Agents replacing browser/website interfaces | | 32:48 – 36:12 | Tempo agent onboarding, wallet setup, security UX | | 40:02 – 47:50 | Tempo architecture: L1 stack, throughput, validators | | 50:05 – 54:54 | L1 vs L2 roadmap and rationale | | 63:32 – 64:57 | Agentic reputation & ERC-8004 | | 65:22 – 70:56 | Assets, DeFi, stablecoin UX, wallet support | | 71:54 – 79:08 | Advice to builders & economic opportunity |
Conclusion
Tempo’s mainnet launch signals a new phase in blockchain and AI convergence: AI agents are being equipped with wallets, native payments, and the infrastructure (MPP) to participate directly in commerce. This “agentic web” enables new business models beyond advertising, powers robust developer experiences, and gives rise to entirely new forms of value exchange and economic activity.
The Takeaway
Tempo’s team sees itself as both continuing the cypherpunk “open infra” tradition and racing towards an AI-powered, machine-payments future. The protocol wars (MPP vs X402), the evolution of reputation, developer ergonomics, and the potential for trillion-transaction economies all point to a transformative moment for web3.
Final Thoughts (A, 79:08):
“So much to build here, guys. Very exciting. The agency web, I think, is going to be a pretty big deal. And to have kind of blockchain crypto be the payments layer for that. It just seems like it's got to be the future. Congrats on mainnet.”
