Tempo Mainnet is live, but this episode isn’t really about just another chain launch. It’s about a bigger claim: that AI agents are about to need native money, and that the internet may need a new payment layer to support them. Georgios Konstantopoulos and Brendan Ryan join Bankless to unpack why Tempo launched with agentic payments front and center, what MPP actually is, how it compares to x402, and why they think machine-to-machine commerce could reshape everything from paid APIs to the business model of the web itself.
---
📣SPOTIFY PREMIUM RSS FEED | USE CODE: SPOTIFY24
https://bankless.cc/spotify-premium
---
BANKLESS SPONSOR TOOLS:
🔮POLYMARKET | #1 PREDICTION MARKET
https://bankless.cc/polymarket-podcast
🪐GALAXY | INSTITUTIONAL DIGITAL FINANCE
https://bankless.cc/galaxy-podcast
🏅BITGET TRADFI | TRADE GOLD WITH USDT
https://bankless.cc/bitget
🎯THE DEFI REPORT | ONCHAIN INSIGHTS
https://thedefireport.io/bankless
🐇MEGAETH | 1ST REAL-TIME BLOCKCHAIN
https://bankless.cc/megaeth
---
TIMESTAMPS
0:00 Tempo Mainnet goes live
1:18 Why the launch is focused on agents
3:58 What MPP actually is
6:30 MPP vs x402
15:28 Why agentic commerce matters
20:08 The “original sin” of the internet
26:04 MCP, NLWeb, and the emerging agent stack
34:07 The onboarding flow: wallets for agents
37:11 How Tempo’s wallet security works
40:11 Tempo chain design and specs
51:13 Why build an L1 instead of an Ethereum L2?
56:10 The Ethereum tension
1:05:01 Agent identity, reputation, and ERC-8004
1:06:53 TIP20, stablecoins, and what can be built on Tempo
1:12:36 Builder opportunity in the agentic web
---
RESOURCES
Georgios Konstantopoulos
https://x.com/gakonst
Brendan Ryan
https://brendanjryan.com
---
Not financial or tax advice. See our investment disclosures here:
https://www.bankless.com/disclosures
No summary for this episode yet.
I'm here with George Eos Constantopolis. He's an engineer at Tempo, and also joined with him is Brendan Ryan, another engineer at Tempo, Brendan, George Eos. Welcome to Banclas. I'm going to be with you guys. Big day. We can't. Yes. So, congrats on the Tempo launch. What does, I want to know what just like the launch actually looks like, you know, day one or just in the near term, the short term. What are some of the first movers that are coming online? And then also just like kind of the first categories of activities that that's happening on Tempo. What is just like the launch kind of look like?
We've been building Tempo since August with a lot of wonderful partners. We're working with Tripe on this. The goal is to make stable coins and web scale payments to work finally using a lot of crypto blockchain technology that we've been building over the last few years. Today's launch is focused on AI agents using the machine payments protocol to pay for things on the web autonomously. And we're continuing to push on our work on the enterprise, work streams around pro-border payments, remittances, and things which really are truly what attracted us to the crypto world in the first place, 24-7 borderless finance and payments.
So there's more to come on that in the next few weeks and we'll continue sharing on that. But today's launch was all about the agent payments all about agent payments. Well, I mean, there's main net, right? But I do notice that there is just like a very large emphasis on this MPP thing, which I think we'll go into. Tempo is known in the crypto industry as like you guys do stable coins. You guys talk about remittances, tokenized deposits. If somebody wants a stable coin, they might go to Stripe and Tempo and get a stable coin minted on Tempo. But it really seems like that wasn't really the focus of today's main net launch, really the focus, the emphasis is on this machine payments protocol MPP, which I think kind of gets us into the topic of agent commerce.
That's what I'm reading into. That's what you just said. Why the focus on agent commerce as like a primary, just like part of the actual main net launch? The main net as it launch today supports all the use cases that you mentioned. So we already have some flows live on it, which are for a particular normal payments, for example, bridge has already bridge. The the Stripe company has already gotten some found on Tempo and we're working on further expanding support for that. So this continues to be a lot of the focus. At the same time, the AI payments world seems to be happening. So all of our people on the team, we use cloud and codex all day.
And we're already seeing that even to us as developers, it's kind of too much to go and log into a service off ad card, get API key, put that API key back. It's just too much when we're just super charged with these new tools. So this really came out of our own need in a way for, okay, guys, it looks like this AI agents want to do more, but they're not able to. They get bottlenecked on the human or just to give you another example. Let's say I have my deep research agent and I'm browsing around. It can many time just improve its quality of response. If you had access to some piece of content that was pay world, for example, New York Times article or anything else.
So we just thought, hey, what if we didn't have to do anything around that and what if we just gave the agent a wallet and we just let it rip. And we really went with that thesis that, okay, we have the enterprise stable coins things. This is a very important. We should continue doing them, but we cannot ignore this wave that's coming, this tailwind about which could affect materially the focus for everyone in the crypto payments industry. And there's ails out that we decided to really put a lot of energy, make the launch be focused on this and then continue with the rest of our work because it was just too important to not make a move on this.
We've already mentioned something called MPP. Can you describe what that is and how is that different from other agentic payment standards that we've seen something like X402? MPP or machine payments protocol is a open and payment method agnostic protocol or machine machine payments. And I think the best way to think about it is it is like the payment form for agents. So today, I think all of us are very familiar with going on a page. You see kind of a standard payment form. It's all the same layout, but you can plug in hundreds of payment methods into that. If it's cards, clarina, even payment of crypto, all of that plugs into that and it's humans are used to that UX.
It's very efficient. But if you expand that, I think this is why we are so interested at tempo about machine-to-machine payments, is we just see it at a huge velocity and a huge compounding number, month-to-month growth. So we think is that velocity increased is you just need more efficient interfaces. So MPP is we view as a payment method interface, which agents can interact with really, really efficiently. We've done much of benchmarks to make sure this is true and allows them to transmit payments over multiple payment methods seamlessly in HTTP requests. So we just see this today. A lot of the API services, people ordering sandwiches today, you can use it in MCP servers, but you can also use it even for if you just wanted to host a video or of some content, kind of this classical micro payments for content use case that people have been talking about since the 90s, but really hasn't been feasible just because of the interface it's exposed to.
And people talk about it at the time. This status code was created in the core HTTP stack, but never really formalized. And we think MPP is the formalization of it. And we have designed it in such a way that is entirely neutral payment method, currency and elastic works with web standards. And we actually submitted it to the IETF this morning in order to be the true spec for 402. And we think it's the best chance for a total neutral approach. Wait, be the be the spec for 402. I guess maybe the question is so we've definitely heard this story before and we're excited about it. But we've heard it more in the context of another emerging standard, which is X4 or two coin basis champion that cloud fair flare has been behind it.
I also thought somewhere in the world like Stripe was involved as well, just to be clear, is this like a competing standard to that or is it some sort of superset like how is it similar versus different? How much is it competitive with X4 or two versus collaborative? What does it look like in contrast to X4 or two? With regards to the cloud firm and Stripe component, cloud firm and Stripe are both companies that are on the record that they want to be neutral and want to be supporting all of the systems. So today, Stripe has support for both MPP and for X4 or two clouds for the same cloud for this morning added in MPP proxy GitHub repo where you can use to make any service MVP enabled.
So from their perspective, all these platforms, they will just adopt everything and they will allow their users to choose what they want to choose based on other reasons that the protocol to differentiate on. Now, how do they actually differentiate on? I think it's three reasons. One is performance. Two is developer ergonomics. Three is platform support and let me unpack them. With regards to developer ergonomics, David Ryan, we've been in many podcasts like this together. Our team is a team that shipped the Foundry project which is the thing that powers all of the 100 billion in defi that has existed over times.
We know how to build, how to test developer tools for backend developers. Our team also has built Wadmi and VM, which are the most used front end frameworks right now for any Web3 crypto app. It's used probably by 90% of every crypto website right now. So we really know developers and I think that really manifests in our API design, in our library design, how ergonomic and how intuitive things are when they're built. And when we looked at their ergonomics of, like for doing other things on the market, just were unsatisfied. So we thought it's just easier for us to go back to first principles and think, okay, what's the simplest developer friendly ergonomic API I could use?
And the way that I saw it is let's go back to the basics. What is the most basic thing that we're doing here? We're doing off. That's literally what we're doing. We're just saying instead of authorizing with an API key, let's authorize with a payment. So we went back and we looked at all their literature, our basic oath, bear oath, all of that. And that was what informed the original design of the first iteration we did for MVP, which is actually in a funny way, what made it so easy to make it payments method agnostic versus if you look at X4 or 2 or whatever other approach, X4 there is a bit tied to the facilitator, which is a very specific implementation detail almost, which never be surfaced all the way up to the protocol.
So we had a different approach and we said, okay, this will be too much effort to make it work without why don't we do it with our own and see how that could work. And the history of the web, it always has been better to have more than one solution because then there's two solutions or many more solutions than they end up iterating to what's optimal for the consumer. So yeah, I think there are like two different approaches that you can use to use agentic payments. And I think it's going to be a beautiful step-by-step on evolution of how do people make it work. But to be clear, it's competing standard then, to X4 or 2.
You think it's better, but it's competing. I think they could compete. I think there's a world where they converge. I think either could happen. You could, well, technically because MPP is more general, you can express X4 or 2 in MPP. And we had a draft that we hope to publish soon about this. I don't think you can express MPP in X4 or 2 terms. Okay. So MPP could be a superset and you say it's more broad. Does that, when you say it's more broad, I noticed like visa integrating it, for example. So it's not just stablecoin smart contract types of payments. It's also some of the traditional type payments.
Is that what you mean by more broad? Like, you know, it works with a visa card. And Ryan, to be clear, I want to steal man the X4 do side, which there is a blog about X4 to V2, which specifies that, okay, it will be more payments method agnostic and so on. That's fantastic. But what we have right now is live and it works with, and it works already with a bunch of like other methods. The methods that we support right now are on temple, which supports both one time charge payments and sessions, which we should talk about in a second. We support Stripe where the interesting thing on Stripe and Brennan used to be at Stripe, so he can say more about how that works.
It works with anything that Stripe supports. So we could be doing clarina over MPP to do payments. It supports visa cards. So visa wrote an extension to MPP. And we also have Bitcoin Lightning support, which I think is just remarkable that we spoke this part team with just gave them the spec and same day or the next day they had proof of concept reposed or extension to spec just one shot. Of course, their agents did a lot of work. But I think I was just remarkable. And I just showed how easy this thing is to to extend. So may the best standard win. I guess that's where we are right now. Can MPP be exported to other chains besides tempo, other EVM chains?
Absolutely. And again, we just didn't have time to do integration games are just so hard because somebody will always say, hey, you didn't do my integration. So of course, yes, it can. And we want to do it. I actually think I have a pull request draft up about that. Or maybe it's a thread in a reagent. But yeah, it works because it's just call API, get response back, respond back with a sign transaction. There's work everywhere. The thing that works nicer on tempo is that you can pay fees in any stablecoin, for example, without having to do more work just because the chain supports it. But yeah, of course, it works anywhere because what is an agentic payment just assigned payload that says, hey, transfer five bucks to Ryan.
That's absolutely it works anywhere. And even the sessions things that we're going to talk about in the second also works anywhere. So because it's just a smart contract that can be deployed anywhere and we know how to do these things for many years. Yeah, I can be deployed on any chain, it can be deployed on EVM, SVM, whatever you want. We started with the tempo transactions because that's what we're working on. We're not going to do everyone's integration work upfront. But we do want to expand into more things. So whoever wants to work with us, feel free. Markets are reacting to a world that feels anything bestable.
Inflation is sticky. Geopolitical risk is rising and capital is moving between crypto commodities, equities, and currencies faster than ever. A universal exchange like big get is built for this kind of environment with a major app upgrade. Big get now gives tradfights own and dedicated tab in an navigation. One click gives you access to stocks, gold, forex, and other global markets all inside the same platform you already use for crypto. You can get 90% off trading fees on stock perps and you can trade gold and silver without the fee burn. One app, one account, trade crypto and traditional assets side by side without bouncing between platforms.
No scatter tools, no login, juggling, just a unified trading experience built for speed and flexibility. When gold is reacting to global risk, crypto is moving on liquidity and macro headlines can shift markets overnight. You need a platform that keeps everything in one place. This is big gets universal exchange vision in action. If you're the kind of trader who adapts as the world changes, big get is built for you. Start trading crypto and tradify in one place. Click the link in the show notes. This is not investment advice. Galaxy operates where digital assets and next generation infrastructure come together, serving institutions and to end.
On the market side, Galaxy is a leading institutional platform providing access to spot, derivatives, structure products, defile ending, investment banking and financing. With more than 1600 trading counter parties, Galaxy helps institutions navigate every phase of the market cycle. The platform also supports the long term allocators through actively manage strategies and institutional grades, taking and blockchain infrastructure. That scale is real. Galaxy has over $12 billion in assets on the platform and average a $1.8 billion loan book in late 2025, reflecting deep trust across the ecosystem.
Beyond digital assets, Galaxy is also building infrastructure for an AI-powered future. Its helios data center campus is purpose-built for AI and high performance computing, with more than 1.6 gigawatts of approved power capacity, making it one of the largest sites of its kind. From global markets to AI-ready data centers, Galaxy is serving the digital asset ecosystem end-to-end. Explore Galaxy at Galaxy.com, LiveBankless, or click the link in the show notes. Zero of what kind of seems like the AI arms race, at least on the United States side of things, the domestic side of things. I think maybe when we look back, the transition from 2025 to 2026 will be remembered as the time in which society went from chatting with their AI as a chatbot to chatting with their AI as an agent.
The agentic word is a huge buzzword these days, and we're just kind of imbuing our agents with capabilities as we develop them. Agents got memory recently, and the MCP protocol was issued, and that was like communications, and with the whole agentic commerce side of things, both X for O2 and MPP, the standards that you guys are issuing, this is like the tool that we were adding to the agentic toolbell, is like, you guys can pay for things now. This is like, you guys now have money, and you guys have a native way of paying for stuff on the internet, and not just also receive money too, yeah, like send and receive.
Can you just kind of illuminate industry expand on just like the agentic commerce side of this story, which is the thing that I think the AI arms race is really focused on right now, is like trying to unlock that part of the agent tech tree. When we do unlock that, which is seemingly being unlocked, what comes out of that, like how big of a deal is like agentic commerce broadly in your mind? I think it's huge. Why? Something about it, like I use my agent to do things more than I click around in Chrome, Brave, whatever, but in itself means that I want to make bookings, I want to buy things, I want to do all sorts of web crawling, auth into various services, like people in our Slack, they want to use, for example, 11 labs, but to them, even the friction of going to log into the service and get billing set up, it's kind of painful.
They just don't have the attention span or the patience to try out new things. Why? Because we're just in a world where we move fast. The world is fast these days. Yeah, and so people just have low patience to do things, and so while they're trained now to be doing things in their agents, what this means is that they want their agents to be equipped with money, and such that their agents can then go and do payments on the web for that. So for sure, I think this makes sense from the user side. Now, from the seller side, and I think David will write on you guys in directly with like this Ben Thompson blog that they shared the other day.
It's spectacular. Yeah, where the inside there for the seller side is that basically as a seller, your website has to become an API, ace up, not just a UI. Why? Because you want it to be served to the agent in the best way possible, such that they go and buy things from you. Why? Because the user isn't going to like go and click around. It's going to be a machine, making payments to another machine, can't see the name. And so in these cases, like Ben makes a very interesting case about ads, which I don't know if that will play out or not because there's many ways this can play out, but he says, hey, if like way less people are browsing the web with their eyes, then way less people are going to be converting from ads.
And maybe that means that this forces all of the sellers or of the people running websites to actually switch to pay the APIs. Why? Because, well, they need to monetize somehow. This is already the case, by the way, on Cloudflare, where Cloudflare is adding like methods on their endpoints to like fend off the bots. I think there's something more beautiful here, which could be, hey, just embrace the bots, just browsing and like golfing the web and just say, hey, to get through this, just paint it. And so I think there's just like such a strong tailwind to agentic payments that just wasn't there, frankly, last year, where you just give five bucks to your agent and we showed that in the demo that we did with Brandon, you know, launch video where we gave our agent some bucks with molded search, gender image upload send email.
I've never myself used any of these services alone, but because it could you know, just crawl the web of services, it could then go and do a multi-step paid workflow across everything, almost like a map review, sort of waterfall, however you want to visualize it. And then that's beautiful. You just give your machine money and it can do amazing things that you never thought were possible. For people who aren't familiar, maybe with that, that's a Stratekery article. I wonder if you guys could summarize that. I know, David, you sent it to me, or like, uh, this week and you said, this is one of your favorite articles in Georgia.
So you just tweeted it out. I just skimmed it. And it's called the agentic web and original sin will include it in the link in the show notes in my retelling of it. And you guys tell me if I left something off, basically back to Mark Andreessen's idea that the internet as we created it and he was there in the early days of Netscape and Mosaic and the internet had this original sin, which is we didn't have a payment standard, you know, a 402 type of standard of his left blank. And we didn't work with credit card companies effectively anyway. And because of this original sin, the entire model for the internet was an ad-based model that we still have today that we still maybe suffer through today.
I think Ben was talking about that and saying, well, you know, it had to be that way because with the human web that like the, the, the most logical business model was always going to be ad-based anyway. So it wasn't just because you forgot to add a standard. It was just always destined to be this way. But he's saying that the agentic web has, I think, I think what he's saying is it has the potential to completely rearchitect the business model of the internet. And so if the human is that this sin is now, it wasn't sin, but if we don't do the payment things now, that's the sin. But he's also saying I think that the agentic web will drive a different business model in that AI is scanning different websites.
They're not going to click in on banner ads. They don't care. They're not going to be persuaded or be distracted. Okay. But they will want good content and we need good content. We need an incentive mechanism for good content. And so the natural business model that falls out from that is AI agents paying for data providers, paying for content, creating incentivization mechanisms. So the new web actually is kind of this AI agentic web where AI agents are paying directly for content. And it's no longer ad funded. And maybe the human web, you know, just kind of is legacy that's that's in our past.
Is that basically what he's saying? What did I leave out? I think you that wasn't impressive scheme. That's kind of exactly what he's saying. I think there's a bit of jury's out on ads. And I'm by no means an ad expert. There's jury's out on how ads will evolve on this because, you know, the whole thesis that ad revenue doesn't convert in the agentic web why because agents got no eyes. So they don't care about like what number you're on a list or like whether it's surface or not because you just tell your agent, hey, focus on like the actual not on the ads. Kind of like a native ad blog kind of thing.
I think jury's out. Why? Because ads may evolve into prompt injection style things where, hey, you have the website and the ad is, you know, text on the website prompt injection. So it could go anyway. So I mean also the jury's out too in that the some of the AI companies seem to be looking at advertising as a way to monetize and as a way to grow, you know, most of the open AIs is very much leaning the structure whereas whereas maybe anthropic is saying, hey, no ads. That's our special feature. I don't know if you guys agree with this, but let me throw out a statement that it would be a much healthier future for the agentic web and for the next internet to be an all of AI to be payments funded rather than ad funded.
And here's why I say that because I get very worried about a super intelligent force. I'm telling all of my life's problems to knows me better than I know myself and has a super ability to glaze me and persuade me to do things. I worry about that super intelligent agent who's my best friend being able to upsell me things all of the time and basically manipulate me into whatever it wants to do, including buying all sorts of things. Maybe I didn't I don't need. Okay, I get very worried about that model. And so it's it's more comforting to me to look at a model where, you know, it's actually paying for things.
I know it's going on in the background. So I would contend that world is a better world and something that we actually want. I don't know if you guys agree with that, but that's your episode where they have like a newer link style chip on a person's brain, the freemium model. Oh my god. No, I haven't seen this. It's a crazy view. It's really reframes your thinking on, you know, a lot of things. Yeah, the idea is that you're you have a chip on your head. And in the freemium model, every now and then you say something that's an ad to your if you pay, you don't know that. So I think that's the first day then what you're saying.
I think people want to feel safety when in the when telling people their secrets, right? And it's true that people use the agent or the chat GPT or whatever interface as a more trusted confidate that you know, the Google search bar or maybe you know, the Google search bar of course itself is evolving. So yeah, I think that's a first statement. But again, I think it's too early to tell how things will evolve. And the best thing we can do right now is observe, understand and try to have a notion of preparedness. But as David said, then absolutely, we're in San Francisco. Things are crazy, things are moving really fast.
It's hard to make predictions about things, you know, even a year out from now, it's really hard to make predictions. And I think the people that can adopt the fastest are the ones that are going to be the most then prepared. Yeah, yeah, yeah. This next part also came from the strategy, a strategy article. But George, you say this hard to make predictions, but it's easy to spot the trends. As you just said, people really trust their chat GPT interface or their cloud interface, the things that come out of that, the text that I read, I'm like generally trusting of. And I either I realize that, oh, I typed the wrong prompt or I can actually realize that like this is actually hallucination, but like it's intuitive to me either way.
So like I trust, I trust these websites much more than I do when I go and I see like a Facebook ad, for example. Now, there's there's two other technologies that are very related to this. There's MCP, the model context protocol produced by Anthropic. And this protocol is basically just how agents talk to services once it allows an agent to basically read a website. And then there's also NL web. This one came from from Microsoft. And excuse me, this is the one where agents can like read a website. MCP is communication. And so like NL web for Microsoft is like the agent's eyes. MCP is the communication between agent.
So this is all agent to agent stuff or like a native internet to an agent and vice versa. And now with MMP or X for O2, now we also have pay. Then we just had Ilya from near on the show. He's one of the also one of the authors of the the transformer paper. And he said his one is one of his early predictions is that, you know, in the future, you're just never going to go to a website ever again. There is no more internet actually. Like the websites are gone. You're just going to talk to your AI in the same way that who's the name of Iron Man? What's the Iron Man guy? Tony Stark. The same way Tony Stark talks to Jarvis.
And there's no more internet anymore. And I can see the internet. Yeah, the internet is in the background. And I can see the face changes, right? And you could easily imagine building a browser right now that actually doesn't care about the JavaScript DOM. I think Brenna, I forget if I told you about this crazy idea. Like we could build like a browser that just doesn't care about rendering the web in the proper way. You know, people say web browsers are really hard build wide because we support all of the JavaScript facing all of the whole web, you know, gigantic test suite. But what if you just didn't and you just said, hey, give me row HTML back.
So you don't even need the browser. The interface is no longer the browser. You just don't interpret even the row HTML and you just tell the agent, hey, parse this into like a interface that I would like. And then you get that, you know, maybe you're Tony Stark or maybe you're Tom Cruise in minority part doing doing things. Yeah, we view and we really intentionally designed MPP as a composable standard that works well a lot of other things. I think you see this today where you can plug MPP yes it works in the standard HTTP request file, but it also works in MCP it works over JSON RPC and so you can do all these various transports.
But we think what the things that people are really excited about next and what we do often developers is like, okay, how do I translate identity? How do I translate things like reputation? How do you track that across? And we don't intend MPP and potentially designed it where we're not going to try and jam all these things together. We want to compose with just as we compose with multiple different payment methods by design. We're going to compose with multiple components of what are other things that people and machines need to do and are useful. So we see a bunch of identity proliferation, there's a lot of different standards for discovery, et cetera.
And we want to work with as many of those as possible. And that's why we designed the protocol to be as simple as possible and as neutral as possible because it's a massive tailwinds for its genitals. Very nice to humble to share this, but here's also written like a great discovery proposal for MPP co-authored within Merit Systems Team, which are good friends of ours and we're very closely. And the idea is that every MPP service can define its schema via, again, very well owned literally. There's a got well-known path that is a well-established web standard to be discovered by services. We're not building a search engine ourselves or we're just building the ways for people to plug into their own search engines.
The MPP library is they support MCP or you can just call them over a standard rest. So again, it's not perspective about these things. These are just layers on top. And there's other things, for example, there's UCP, I forget the acronym by Shopify, there's A2A by Google, there's AP2, there's a bunch of things and they all do different things, but none of them really nails the pay handles. So we've made it so that you can do the payments based on the things that we talked about earlier and then you can compose a driver you want with whatever is on top. What I hear there is that you guys don't have an opinion about the direction of the internet.
If the Ben Thompson Ili outcome of just like, there's just your AI and it renders the internet for you to visually appeal to how you like it, maybe that's great, maybe natural forces point us that way, maybe the MPP or agentic payments is like a very important puzzle piece to get us there, but you guys are unimpininated about where it goes after this. I think though it's hard to draw a specific like long term bet. I think like we'll look at the structural trends is there is just going to be more things you see. I'm getting a more code being generated than ever before. There are more services going live on strike than ever before.
There are more people just building things and building things that produce valuable work. And we think that those things should agree value because they're providing value. So that's really the purpose of payments. You just think there's going to be more things. They're going to have pearl for it. They're going to get built faster. And that very much is why I work. Excited about tempo and especially machine payments. I tempo is because it draws to the natural conclusion of like, okay, what is the fastest way to get started today as a developer, spin up a service, start monetizing it and provide value and get discovered.
We think that is MPP and specifically MPP on 10th of today because you don't need to touch a single API key. This is really the dream of stablecoins of crypto is I just been up a website integrate MPP, host it and start getting payments in stablecoins immediately and not have to go through large set of flows. You only need to do that for offering team deep learning versions, which we're really excited about. So we just want to see more things in the world, different ways to monetize. And we've been super excited to see like new things evolve because I'm not building. So the interesting thing about MPP then is that it's great from the least sci-fi to the most sci-fi scenario.
The least sci-fi being just a paid API. The most sci-fi being open-close, run the internet and they all have wallets. Actually, there's millions of open-close in so many of them that they all just non-stop page other. And there's a lot of between-between stuff that is exciting, which is all of the agents crawling the web and paying for services. And I think we're not in the least sci-fi. I think we're definitely in a bit sci-fi world, basically another AI tailwinds that we're experiencing. And I think the very sci-fi world is actually not out of reach. Yeah, I mean, to give an example of this.
So in the announcement post for tempo, right, there's like one of the first things you can do is go create a wallet. And so I kind of expected to go see, okay, there's a wallet, maybe tempo is rolled at it. So you know, it's own wallet or maybe there's a link to like whatever in Metamask or Phantom wallet or everything I'm used to. That's not what happens here. What happens here instead is I'm greeted with pages as supercharge your agent. It's almost like about spinning up a wallet for my agent instead. And there's a button I could click called try with your agent. I'm not sure what that does.
I haven't tried that out. But if it's going to connect into my my cloud or my open AI or what. But you know, the way to use this is kind of like it's a chat type interface. Find me a hotel and flight to a conference in New York, December 28th to 29th. No red eyes, keep it under $700, that's the example that you're supposed to send to your agent. And I guess it gets a wallet, it spins it up and it does this work and it pays for things. So even your onboarding floor is like agentic, right? Absolutely. So and the thing that so we've sent is demo flow to a lot of people and they all get this wow moment.
So yesterday we actually told one of our colleagues, hey, install the tempo skill. So every agent agents now have a thing called skills, right? Where the skills are just prompts for how to use the thing. So we literally told one of our colleagues to say, hey, tell your open clothe on telegram, tell it, hey, install the tempo skill and then all George is a number. Yeah. And like we gave it my number like a phone number. I kid you not, it called me. What is it? What did I say? Like to like see what going on? Like insane to see that, hey, like somebody literally just gave it a prompt. Yeah, nothing about tempo.
It literally, so the thing that you said, like that you read from the website, it's a good word. So we don't have our own chat interface. I don't think we'll like by the doubt that we would do one. Sure. So just copy that prompt. You put it in your agent. Your agent could be unplug codex, open flow, whatever, whatever you want. Yeah. And we'll install the tempo skill. It will download the tempo wallet in the background without even knowing about it. It will create a wallet. It will tell you to fund it where you can fund it with Apple Pay, with cross chain deposits from any chain with a QR code flow or with a referral code.
So afterwards I can just send you a five or more dollar referral code to play around. And it just goes and then sees, hey, what services do I have available? And then just does it on its own. It's really, it's really magical. It gives you an incredible. So when this open claw instance was calling you, did it have to go pay for something in order to call you? Did it pay for a service service that we have created, which lets you do text to speech. Voice over IP type call or text to text to speech type thing. Okay, cool. Where are that when it's setting up the wallet? Where are the private keys?
Are they smart by machine? Great. So the thing that we've done in all wallet is pretty novel, I think, and it deserves a good explanation, which is when you create a tempo wallet, it kicks you to the website. The website that you were just in. In the website, it tells you to face ID to use your iOS biometric auth to create a wallet. Now, once that wallet is created, it's using your phones secure and cleave, which means that that is not stored on your phone or your desktop, whatever you want. It's using task keys, which is a well established technology for doing this thing. It creates the wallet or you sign back into your wallet.
So there's never a private key in this case. But when you call into it from your agent, it authorizes, it creates an call it a femoral private key, call it a scope, the access key, that's the naming that we use. It generates a small private key that can only access up to a certain number of your funds. So if your wallet has, say, a hundred bucks, when you log in and when you do the flow, kicks you to the website and it says, hey, authorize your agent to spend up to 10 bucks or 10 bucks a day or whatever granularity you want to do, which is, by the way, the same primitive that we use to support subscriptions in MPP.
So your agent locally gets a private key that's safe to lose, which is very useful here. It means that if you lose that private key, you're covered and if some of these steals that private key, the losses are cut, which is very useful if you think about, hey, I just want to let my agent rip, but my wallet has, you know, $5,000, like I don't want it to go and lose all my money by accident. So in this case, yeah, if you log in, it creates a private key, it authorizes it and then you can let your agent rip while feeling safe about it. So is it accurate to say that the kind of the master private key, right?
Not the the sub kind of pesky or private key that the agent gets. The master private key is like that's a pass code, secure enclave on my phone, or does it exist? Do you guys have a copy? Is it shared at all? Like, I hope you read it. It's a self-custodial wallet. Okay. It doesn't use any third party. It uses peskies, which let you, so in tempo, we have added the native pesky type. If you're, if you have seen all of the account obstruction wallets in the clearing world, they all have this feature, but it always requires an extra component called a bundler, a relayer, whatever you want to call it.
Whereas in tempo, we pulled that in the in the tempo transaction format, which we have published about, which means that you can use peskies without an intermediary to, you know, go and transact with the chain and this peskies stored on your device. And it's also if you're using iCloud keychain or if you're using one password, we also sync it across devices. Okay. Cool. All right. Now I feel like we need to go back to tempo and the thing that was launched and we've done episodes on tempo before. So bankless listeners may be somewhat familiar, but I think we need a refresh. So this is what? This is a layer one.
It is EVM. I think the, I'm sure the breath client is involved somewhere, Georgios, knowing you. Can you just lay out the specs of this thing and what it is and kind of throughputs? What's what assets are on it? Just kind of some of the details that somebody from the crypto world would want to know. tempo is a layer one blockchain focused on payments. We're making opinionated tradeoffs to optimize for the payments use keys. Tempo is permissionless, meaning that anybody can run a node and anybody can validate the state transitions of the chain. Tempo is live with 11 validators. Most are operated right now by tempo and we have some external running and we're onboarding more validators on this in the next few weeks, external from a jail distributed cluster so that we have in Europe, US and so on.
You're, you're, it's permissionless to run a node, but you are onboarding more validators. How do you square those two things? It's permissionless to run it. Imagine that you're alchemy, for example. You can just run a node and like serve RPC traffic or you're an indexer like album and you want to like index the chain or just a normal cipherpunk user that wants to not trust and verify everything. Running a node is a two command process. So everyone has listened at the ability to listen to tempo, but not everyone has the ability to write to tempo. Is that correct? No, it's singular. In Ethereum, like to become a validator, you need to state 32.
Well, we don't have that and everything else is the same. It means that anybody can run a valid, anybody can run a normal node, anybody can knit transactions, anybody can create a wallet. There's no special case and no black lists anywhere. But running a validator is still permissioned in tempo. Running a validator is still permission. We're in the early days. We're still figuring out what the right way to expand this validator set is. I think we have a pretty promising roadmap in the next few weeks, but we need to be very thoughtful about how to execute on this. And there's 11 right now validators right now there's 11 and we don't have a dashboard yet on the blog explorer.
We need to like make that happen. But there's a validator manager contract in the in the blockchain that you can check from our docs, which if you query gives you the full list and you can do the validators have to stake something or they're just going to wait. We have we have a multi-state that controls what the validators are. Okay. Okay. All right. So so please continue then. We were just you know what else should we know? Yeah. So the node is built on the red client where the red client is a project that we've been building at paradigm for the last four or years at this point or more where red is built as an extensible client, which means that we're simultaneously able to support a theorem L1 for the normal use cases that people in the theorem L1 world use it for normal RPC nodes for validators for MED bots and all of that.
It also supports layer 2s like base for example, which is running rest underneath or the rest of the L2 ecosystem. And we're also building temple with red. Why are we doing that? Because we have a stable foundation, which means that we have all of the EVM JSON RPC developer tools they just work. The node is the highest performance node as of like the last few weeks or month plus something on the theorem L1. And it's generally very fast, very stable, well tested. It just needs sense for us to use that as our foundation. So that's on the execution layer side. The node has features for payments.
For example, we have a pre compile that's a NRC 20 contract with permissions enabled in it, where if you're a, which is generally targeted at stablecoin issuers, for example, that want to have say various rules or let's say your tether or usdc and you want to instead of like rebuilding all of the permissioning features from scouts would just have them available out of the box. Then node also features think called the payment lane. Where the payment lane is something very valuable, for example, if you remember, the late last year when one of the big market volatility events fees everywhere spike.
I think everywhere except Solana, which was fantastic and congrats for doing that. And the idea is that you don't want defy related spikes to be affecting your normal payment activity. So what we do, we just said there's a zone, there's a part of the blog that's reserved only for payments transactions and there's a part of the blog that's allowed for anything. And the payments section of the blog is going to always have predictable stable fees that you're not going to feel anxious about. The rest of the blog, you know, the things that we're familiar with can help. And the big shout out to the commonwear team by Patu Gradian Folt.
Temple is basically combining the best of the rest project on the execution side and the best of commonwear consensus on the consensus side, which is what lets us then like executing this ambitious global validator set roadmap that we're going to be executing in the next few months. How about, you know, throughput transactions per second and also validator node requirements to like run these things? Yeah. So for gas per block, I believe it's 500,000. So half a giga gas per block. And then block time floats from 400 to 600 milliseconds. It depends on networking conditions at any given time. Okay.
And then so half a giga gas does that translate to something like, you know, 5,000 transactions per second? Or are we even able to translate? Does that distinction not matter? Colleague 10. Colleague 10. That was the transaction. In our last benchmark, that was what we could hit. So call that like as of last week, I believe that's whatever last benchmark. The thing we're doing, we're going to be publishing a bench or perf.tempo.exe because I take the hard thing about benchmarks is that, you know, we're going to talk about them and then in two weeks, they're going to be outdated because in the background, we have an agent that just looks at all of our stuff and like it conveniently optimizes them as, you know, it's crazy, it works.
Like we just have like an agent that looks, runs benchmarks all the time. And in part, that's why the red flag got so much faster in the last like month and a half. Wow. Yeah, it's really remarkable. So David, you were saying again, much earlier about urgency, performance, all of that. Like they, I has really transformed how we work on all of this stuff. So really fast block times, as you said, you said 400 milliseconds, really fast block times, finality, single slot, because we use simply consensus, half a gigas, throughput, or just sorry, half a gigas per block, which translates to, if you count like a thousand, a hundred thousand gas per transaction, like you can do the math.
And then what am I missing out? Net work, no requirements. Well, we are actually super excited about this because we've, because we're building it on RATH and we've been optimizing RATH for the HTML1 use case, which is really about like trimming requirements as much as possible. We just published a new minimal mode for RATH, where the theorem main net itself is 150 gigabytes, and imagine I theorem main, it has like lots and lots and lots of stuff in it. The running a tempo node on commodity, normal at home software, a node hardware is possible right now. If you open your laptop and you after this and you take, say, point it to the docs and run me a tempo node, I'm promising to you, it will work.
It will download the snapshot, the snapshot is tiny right now. It will get bigger over time, but it will be small because it's gas pricing or state growth to be good. Yeah. But to participate as a validator, like, is that going to require some beefy bandwidth? I think I saw a number of like 10 gigabits per second or something like that, is it still primarily, if you're participating as a validator, let's say, we're just like running maybe like a serious node. Are you still going to have to run that in a data center? Are you guys trying to get this down to, like, running your home? Absolutely not.
So there's no intention for the again, I don't think about values and non-value is different. I think it's all the same to me, networking wise and node requirements and so on. The node operators will require, will work on commodity hardware, normal residential connections, shouldn't need gigabits upload. In part, why this is going to be possible is because of the common wear stack, which you should go and look at what they've done recently, where they can use a racer coding to make the networking on a per node basis to be much lighter. So yeah, I think it's going to be really exciting. I think there's a lot of players that are racing towards bandwidth efficient consensus that's also very high performance.
Big shout out to the monet team because that amazing work on that with Raptor Cast, I think the Shalan Alping Glow work is also really strong on that. So I think it's going to be, I don't know, I think like the world where we thought of low block time, high throughput and, you know, again, I think like to go to 10,000 TPS, everybody, or maybe like a bit more, like, people are covered on a jet-distributed network. I think not an interesting thing that web payments world is like, how can we do a million, like, a billion payments per second, and not these are like an open question, a lot of people are going to do that.
Our answer is the MPT sessions, where you can bypass going to the chain every time, but I think that for few tens of thousands of transactions per second, like in the next, you know, even now, like, I think the world is in a good spot, like with this temporal Shalan Amon, I'm saying, off the top of my head, it's like the high performance decentralized blockchains, I think like people are covered. I think the requirements have gone down so much, they know the operator experience has gone in so much better. It's been a question, I think, since tempo was announced in sort of the crypto circles, as to like, why an L1 rather than an L2?
And I noticed just yesterday, you tweeted this, Georgios, the thing I learned early in my crypto journey is that to really scale decentralized network, you have to avoid consensus. That's what drove me to L2 scaling. You talked a bit more about, you know, state channels and L2s. This seems to indicate that you're still kind of L2-pilled. And yet, as one of the, you know, the architects and engineers on tempo, you guys went with an L1. I think a lot of people are like, probably listening to this and scratching their heads and saying, why? Like, why an L1 rather than an L2? I think the simplest answer is just developer velocity and being able to self-express and being able to do the things that we want.
That's one, we didn't want to be bound by the DA that the Ethereum world would provide us. At the same time, of course, we're continuing to serve the Reth project as normal for Ethereum L1s and L2s. But for our ambitions, we felt like we had to like, kind of like be able to self-express in all of these ways. And I think that's the most of it, right? I think being able to just own your fate and own your stack and being able to customize as you want is just so important. What do you think this means for the L2 roadmap that Ethereum has, you know, set off with, you know, four years ago, is that sort of dead?
In your mind, you think L1s are the way to go, or do you think there's a future for L2s? I don't think these are intentions. So there's two questions here, right? Like, A, like, what do I think about like L2s in general, or maybe for 10.2, what do I think about L2s in the Ethereum context? So I can answer the Ethereum context one first, and then let me tell you what we've been doing. So I've spent basically all my career building L2 technologies for the Ethereum world. I think these are the best, the most credible way, like, do real scale on Ethereum. Again, even if we make Ethereum scale on L1, we will need to like roll some kind of like L2 technology in it.
And it can be done, you know, as a P-stack arbitrary base, you know, all of these things, or it can be done in a shrine way. There's this whole native roll-ups roadmap that has come out recently. I think all of these are valid and good. So by no means, no, I don't think L2s are dead. I think L2s are necessary for a decentralized system to scale. I think Ethereum has this like very cipherpunk core that is important to protect all costs. And I love the Dalek's recent cipherpunk warrior arc. I think that's the right thing to be doing. So I think for Ethereum, absolutely, you need L2s. And I would definitely not make changes to that.
I think there's things that in the Ethereum world, we need to figure out around tensions, around branding, you know, the whole L2s competitive to the L1 and all of that. People disagree. I don't know what the right thing is there, but I would absolutely classify, you know, L2s as a necessity in the roll-up sense that people have been doing. In the temple context, I think there's like, again, like a few interesting things. Well, A, MPP has two ways to interact with. One is the charge method. The other one is the stream method or the session. The charge is every transaction goes on chain, which is just a normal payment session or the streaming method is actually opening a one-way payment channel with a server, which is like an old-school layer 2 technology from, you know, before most people heard about precursor technology to layer 2s, yeah.
Absolutely. It was like kind of like the grand client of a lightning network. Like a one-hop, one-direction payment channel just says, hey, Ryan, I'm opening a tab with you instead of settling with you on every, you know, query, which is a charge method, which is how we're used to doing crypto payments. Right down on your notebook, you know, what is my score? And then I'm going to settle with you at the end when I leave the, when I want to close out the tab. And this means that I can use like an old-school layer 2 technology in temple for the specific use case of client server payments, which fits beautifully, right?
Yeah, I guess like that. I just want to sing that in that like the layer 2 technology that we have, we literally just deployed the layer 2 technology this morning on temple. Why? Because even if the chain support, whatever, many throughput latency constraints, their demand the AI world is going to bring is just 100x that, or it's just unknown how much it will scale that it's going to just hit the physical, like to support it, you would need 10 gigabits or 100 gigabits of uplink or whatever. And we're not, I don't think we want to go there. Yeah, I read actually a post on that by Liam Horn, who I think works on the tempo project as well, and he was kind of the forefather of state channels and kind of exploring that in Ethereum originally.
And maybe I want to ask again about that, that kind of cypherpunk thing versus what tempo is doing, because as you know, bankless is like primarily a podcast for crypto natives. I think for a lot of crypto natives, they see tempo and they have mixed feelings. I can say even me going to this episode, I have mixed feelings. Like on the positive side of things, I, it's very exciting to see like obviously a world class engineering team go execute against this vision towards a real world use case like agents start applying that to the agentic web and kind of winning payments over to blockchain technologies.
And do you see what you're doing with respect to decentralization? At the same time for crypto native, it's like a lot of our heroes, right? Like Georgios among them, originally the loom L2 like scaling Ethereum, Liam Horn, who I mentioned Dan Robinson, who pioneered, you know, Uniswap, and a lot, even even Dan Krad this morning, he tweeted about tempo, right? Now he's on the tempo team. So these are kind of some of the crypto native heroes on this crops type mission, right? censorship resistance, open source, private and secure the Ethereum track. And now they're doing all of this in tempo. And some people are scratching their heads and they're saying, okay, like is tempo now just taking the Ethereum vision?
Let's say in this whole cypherpunk vision and corporatizing it or just executing it in a different way? And I don't know if they feel kind of like lost by that or they feel like there's a competitive threat or they feel like it's just the open source thing that we once had and the decentralized thing that we once had in the crops thing that we once had. Now the corporations are here and they're taking over and they're engineering us and maybe out executing us. And so there's some sense of like feeling left behind there. I don't know. It's a jumble of feelings that I think people are probably having as they're listening to this conversation.
How do you square these things? How do we think about tempo in the context of Ethereum being cypherpunk, but maybe now it's it's a lot smaller than we once thought it would. We thought at one time it would take the payment to use case and these would be L2s. And now it seems like that's happening outside of the Ethereum ecosystem. Of course, you know, you're still at wrath. You're still co-developing on Ethereum. I'm sure that's going to be open source. So it's not like Ethereum doesn't benefit. And yet it's not benefiting in the same ways we originally thought it would. The question is all of the good stuff that was happening with Ethereum.
Is it going to be happening not on Ethereum and how should we question that we like people feel? It's like why not do all of this on Ethereum, right? Why do this on an L1 chain in tempo with a separate kind of thing, separate standards, separate maybe future token base? Why not do this on Ethereum instead? Well, I think it would be hard. Well, again, look at the niches, right? Like the payment niche just requires so much capacity and so much specialization. And I replied this to someone on Twitter also, I think earlier today, I think, was Alan who said that, are there any approaches that you're doing to pre-compiles, for example, which is a technical detail in what we're doing that Ethereum would not do?
And I'm like, yeah, of course, because Ethereum is a general-purpose platform that empowers developers just self-expression the most general-purpose way and doesn't really discriminate, or a particular use case, which is what makes Ethereum so beautiful. At the same time, when you're doing the payments use case, it's not just the performance stuff. There's like all sorts of specific functionalities that you want to add into the system just wouldn't happen. On Ethereum, they just would never go through the governance process, it would take too long. So that's one point. I think the other point is that high-value defy will continue happening on Ethereum, right?
Yeah, I guess maybe there's a question which is sort of what you think Tempo's intent is, which is, is Tempo's intent to kind of eat Ethereum's lunch, or is it to sort of expand in a different direction? The goal for Tempo is to make the stablecoin native payments world happen, and I don't think that's intention with Ethereum being a large successful forest for the world. Keep going on the thread. There's the timing that has happened with the Tempo Minute launch day, timed with the EF Mandate document last week. There's like a tale of two cities here. My read on that document was that Ethereum is like a sanctuary technology.
It's technology to make a sanctuary for people, and also not much more than that. If the Ethereum broader community wants it to be more than that, then the onus is on them to do it, but the EF, as it relates to that, it's not interested in doing the agentic commerce, agentic payments thing that is going to change the future because it's not about changing the future, it's about being a sanctuary for the people that need it the most. There it has been just kind of like a shift, like with some of the people that Ryan has mentioned, like Georgios, Donkrad, there's been like a vibe shift of, I think people who are interested in growth is maybe something that I will characterize it as.
If you were previously in the Ethereum camp, but you were really into growth, economic growth, and being more than a sanctuary and doing kind of just whatever's on the technological frontier, the AI arms race, you kind of found your way into the tempo ecosystem, and so there's like, while it's, while tempo isn't intention with Ethereum, it does seem to represent a different vibes, polarity than Ethereum does, that is kind of like equal and opposite, and in equal. There's no question here, Georgios, I'm just wondering if you kind of like agree with the assessment. I admit, I did not have the time to read the dog, I believe it was 38 pages, and there's a lot of anime in it.
My attention span is right there, of course, as well. I think there is a fair take around the vision tensions, maybe, how different visions rally different people. I think at the same time, I believe in both, which is, well to me, it has expressed in a weird way where we've made Rhett the library and any changes that we make tempo faster or make tempo more robust or more feature stable and whatnot. It just flows naturally to the Rhett upstream library, foundry as well, so we announced tempo like one of the core points that we wanted to land and people was that, all the work that we're doing, yes, it's making tempo work, but these are the same code bases, so the same people that are working on the new code base are also working on the last code base, why?
Because they depend on it literally, it's like a pain dependency in the code base, so that's why to me, I don't, while I empathize with what Ryan said, and I totally understand, yes, somebody might feel like, hey, like some people that were doing good work are no longer doing that work with our other friends, I don't feel that tension as much because we just do both, and it might be hard for everyone to understand, but we're just doing both from our end and we're good in, and we think we can do both very well. Some exciting news, we are launching a new podcast to help people figure out the crypto cycle, how to navigate it.
The best crypto cycle investor I know, his name is Michael Nado, he runs the DeFi report. This is the guy that sent me a cell alert before the 1010 price drop happened. His cycle analysis has been absolutely on point, I've been following him for years, and this year we started recording weekly podcast episodes, each one we get into his portfolio, what he's holding, the market structure, entry targets, fair market value, Bitcoin ether, and where we are in the cycle, there's new episodes that are released every Wednesday, they're 30 minutes, they're short, they're punchy. I think this crypto cycle is harder to navigate than most, so let's do it together, go subscribe to this podcast, search the DeFi report, wherever you get your podcast, YouTube, Apple, Spotify, or find a link in the show notes, there's a new episode waiting for you now.
I've got to just say a handful of questions I just want to ask, just lose ends, it can kind of be like a lightning round, just to kind of talk about the last little topic, says it relates to tempo and agents and all that kind of stuff. Not terribly long ago, ERC A004 was introduced in the Ethereum land, this is agentic identity and reputation. What's your take on just like the need of reputation for agents, is that like talk about the role that that plays in this whole agentic commerce vision? I think it's going to be very big, I think we're very excited, like if you look at what we just last said about the future of Ethereum as this extremely decentralized, reliable place, we think reputation and registry and discovery will live in multiple places, and for the most important, the most decentralized agents, we're really excited about things like A004, how can you push reputation back?
How can you say, I attest to this thing? But we think there's going to be multiple and we don't know how that's going to pull her for eight, so that's why we're really looking at a lot of things, we're just trying to see what are people building, how do we get the right solution for them, and how do we support as many things A004 among that? So the idea, the concept of reputation for agents, valid idea, important for the future of the internet, totally going to happen, unsure how we get there, but eventually we'll fast forward a few years, and then you'll be like, oh, there is totally reputation for agents, you're not in your head and agreement, it sounds like.
Exactly, so I think it's very much inequitable. And I believe we're, Brandon, we had that chat with David Ered around one of Walker's on that, where we shared some of our ideas on discovery, some thoughts on ERC A004 and so on. So we like Eredia, we don't know, I don't know if it's like the right way to do it yet, because people are just going to do things, but we're talking to the people about it, and we're just giving them our thoughts. A quick question on assets, so what assets are available right now on tempo, and what do you think that'll look like, say, in 12 months from now? So there are really two main types of assets on tempo.
One is our special stablecoin standard that George O's talked to called the tip 20, which is an extension of ERC 20 plus supports a number of things that we just found stablecoin issuers need, like policies, like controls, you can sponsor gas fees. It also integrates really well with our stablecoin decks, which is an enshrined primitive in tempo. So in a lot of cases, and we use this really heavily in MDP, if I'm a server, I am broadcast business service, and I want to get paid in USDC, but in agents might hold some other currency, but it's also USD dominated. We can handle swaps automatically and do so in a very efficient way that's controlled by the protocol, and really just pull it for as many stablecoins as possible through tip 20.
Also on top of that, anybody, tempo is a permissionless network, so you can deploy any token that you want, but we have made to George O's point before, like conscientious engineering decisions, so that stablecoins via payment lanes via other primitives are more efficient to operate. I'm tempo that your random run of the mill ERC 20. Does that also mean that permissionlessness, does that also mean anyone can deploy some kind of smart contract outside of a token, any kind of defy primitive that they want they can deploy that? Memcoins? Yeah. What about offensive meme coins? Gross, discussing offensive meme coins.
Can I deploy some of those on tempo? They're already nice. Nice. Nice. David, you into those, you into this, you in a choir. How about you mentioned kind of a dex being sort of part of the core protocol in some way and has some special status? How about identity? Is there kind of a native identity type engine? Is everything AML KYC or how are you handling that piece? No, AML KYC built into the chain itself, if you're using chain analysis or whatever else in your app, you're free to do so. We were considering whether we wanted to add a feature that's not for AML KYC, but it's like a cosigner feature on every transaction, which the first use case would be fee sponsorship.
So we already have fee sponsorship, David, natively into the transaction, but we're thinking, hey, maybe we can generalize this in a way that you can do not just this sponsorship, but also security scanning, for example, like blockade as part as a cosigner or your transaction, or if you wanted to add the chain out or something, we haven't done that yet. So nothing for sure, nothing like in the chain around KYC AML, it is like app layer concern on a per app basis, but we are thinking about, hey, can we allow people to poke on things more easily to make the app layer better? All the existing EVM based smart contracts could those be directly deployed to tempo, and then also kind of the other infrastructure.
Me, the user infrastructure, I mean, will MetaMask pretty much work with the right RPC out of the box? So all of the smart contracts work out of the box. There is the feet, so on MetaMask, there's a, well, MetaMask, they don't show stablecoins as your native balance, so that's something that we're working on with the team with the MetaMask team on. Okay, but all the EVM wallets, they will shortly work with tempo then basically. They work, but sometimes there's edge cases because they're not programmed to show you your stablecoin balance, right? They're programmed to show you your eth, and for example, if I have any of the stablecoins that we deploy via the stablecoin factory that people are using, and anybody can interact with anybody can deploy a stablecoin.
And by the way, it's like, we're calling it a stablecoin factory already, but the tip 20 factory is really just a generalized one, so it can be for any kind of fungible token. You might deploy something and say it's a stablecoin, but it might not be backed by anything. So just treat it as a normal ERC 20 that's pre-compiled and more efficient has hooks on it, but yeah, because wallets just don't take all of the stablecoins that you have configured and they don't just sum it up and say, hey, this is your wallet dollar balance. They are programmed to show, hey, what's your eth balance? And that's the main thing that we've been trying to make work.
The other thing is because you're paying fees in any token, and tempo lets you pay from any of your, like, for example, if you're transferring USDC, you can pay fees in USDC. If you're transferring USDT, you can pay fees in USDT. And this happens via an abaked into the chain primitive, the Dandromitron invented called the FAMM. It means that wallets have needed to do some custom work to allow you to pay fees in stablecoins, which is actually also happening the theorem world because as the account abstraction wallets are gaining traction, they all basically need to expose that primitive to the wallet.
And there's some nice ERC standards that we're also following, which are basically such that it works the same similar to how the theorem world is doing the ERC427 stuff. Guys, going back to this very big vision of the future of the internet between AI, micropayments, agentic payments, what the cosmetically what the internet look like looks like is changing, potentially changing, potentially critically changing. Like the idea here is there's going to be like, you know, trillions of microtransactions being passed around, you know, any given day, money's just going to be flying around the internet much faster.
And it kind of makes me think that we're opening up a opportunity, a field of opportunity for brand new types of value to be expressed, brand new types of developers to build apps, new opportunities. So if you were to give advice to some young entrepreneur coming out of college, he's hungry, they're ambitious, they want to go do something, and they want to catch some of that money that we think is going to be flying around from all these AI agents. How would you best steer them in the direction of casting the right net in the right location to catch some of the money that's going to be flying around?
Yeah, I think the most efficient thing that we see is figure out like one, use the tools a lot and say like, okay, what are what are they doing? Where are they getting stock? And wherever you're getting stock or wherever there's friction, we think there is value to be accrued. And just build services that unblocked developers, unblock these machines that are increasingly compounding across every single vertical we see now from code deployment to even just people doing administrative work at their office and figure out where they're going to stock, what's the work that they're doing and make that more legible to them.
And we think value will naturally flow to those services. And that's why we really developed MPP. We think MPP is the most efficient conduit to broadcast services and to have machines interact with them. I think like we've seen this all where it's like, Claw is so good and all these agents are so good at just calling like the basic, you mix commands that have existed since the 70s. And we think the same thing applies where it is extremely intuitive and we've got this intestine to call the exact same commands, HCTP paint it off to perform payments because it is just so baked in and so natural and all the tools that might take would be just build paid APIs.
Like figure out, for example, David, I bet you and Ryan you guys got like a giant corpus of like interesting files with notes, you know, your prep or all of this like wonderful episodes that you've been doing for so long. You could pretty easily just tell your agent, hey, expose this as a service. And instead of like and Ryan having to get queried directly by things, why don't these people just talk to my service? Well, you don't want to come on the show anymore? Is that a paid service by the way? You could do it as a paid service, you could do it. You could say, oh, you get like five, three queries and then to go more, you know, you need to do more.
I just think there's so many, you know, of these, hey, I have like some private knowledge base or some private or whatever information I want to like share the world, but I kind of like don't want to put it out there for free or maybe the hosting costs. I cannot cover the hosting. What's I don't want to talk about them? And like one of our colleagues Shane had said that earlier on, which is like you can just build the service that kind of like pays for itself in a very way. I think a viral article on Twitter a few weeks ago about that as well. And in a funny way, these are like the self-sustaining, self-building, autonomous things where you can just say, hey, here's some data.
Okay, start making money on it. When you've made some money on it, then, you know, go build new things with that money. And there's actually a very well established concept about that. It's called the Bonnoi Mun Pro, which is like the spacecraft goes and builds more versions of itself. So I think like basically the advice I would give would be like get into that mindset of like you got something, put it out, take the API service, figure out how to make it pay for itself, and then figure out how to make it expand, which literally is like starting a business. But instead of being like a business business, it's like, hey, you know, take this thing put in an API and it doesn't need to be anything crazy.
You don't need to like think about if you guys can just be like text files like sales spreadsheets. Simply, it's how you think about the world, all of these things. So we've got a lot of that. We have like seven or eight Google docs that are each respectively, like 700 pages long. And because these are our notes for our podcasts. And then once we realize that like the the doc performance is going so slow, we just fork it and make a new one. And we've done that like eight or nine times now. Oh, that's why your dog that stuck earlier. Yeah, exactly. That's exactly right. So like say we take all the transcripts from the bankless podcast.
We take all those notes. We take everything we've ever produced. We clean it up. I don't know what that would look like, but we just clean it up and make it just more accessible. And we put it behind a paid API. And that's our value that we've had. The corpus of bankless knowledge, which is like, you know, going off for six years now. So a lot of value in there about anything we've ever wanted to talk about ever. How do I tell the agents about it and that it's useful to them and that they should pay me for it? How do they? How does discovery work? Well, by the way, if you're down to do this, we'll happily call this on install.
Everything we need to make it work for you. So we can talk about that offline. Yes. Yeah, but if you wanted to make it like we support way to discover paid services via MVP today, you would just say like you register, you could spin up your API and just say, Hey, here are the endpoints you can call. This is the cost. These are the ways which you can't email. Here's the currency. I want to be paid in. And you can do that. Not only on tempo, but across a variety of payment methods. So it could be like, if you want to put in your card details, put in a bunch of other stuff, you can do that there too.
And then we, by registering the schema, you can make it discoverable to agents. And we see a number of services, which are just now even ingesting these demos to build like they're calling it like, okay, what is the paid rank for productive work and to figure out like, okay, how do we build that? I think that's also part of like the version like what's the search engine, reagents almost like what's a search engine? Also, how do you price this content? It feels like there's a lot of, I mean, I mean, yeah, like, do you want to ingest like thousands and thousands of lines or you do have a small query?
Like, how do we rank the size of your story? I have no idea how much the bank lists like knowledge base is actually worth, right? And who's going to pay for that? It seems like, yeah, not very much probably. It's like, it almost like there would need to be a bidding process to discover what the actual market price is here, right? I'm sure there's a lot to be done in that area. We had them so early on. So, you know how like, OpenAI has like normal pricing and search pricing for the API. We're just as search pricing. You can do all sorts of things where you can just say, hey, instead of me figuring out the price, what if I just say, hey, you have, I I'm giving 10 API, you know, you said Dan Robinson like that because like there's like exactly that Dan Robinson, which is like, I got 10 queries on selling 10 queries, you know, this is like my data.
Go run an auction, figure out the price. I can figure out the price. That would be valid. We haven't done that out of the box yet. I think it's a good point. You know, the question of the consumer or of the person wanting to do a PD API, it's two questions. It's like, hey, how do I price my stuff? How does my stuff get discovered? I think then how do I price my stuff? I think the answer is either you know what the price of the data is and maybe charge some premium on it for convenience or whatever else. And to the discovery point, I think right now what you can do is like publish your schema, but where do you publish it?
And what does the search engine look like? I think that's open ground right now. And I think people are going to race for it. If that is the next page round, right? I think that's going to be beautiful. I think there's going to be so many competitors for this brand and hopefully we can just sit below all of that inlet that competition happen. So much stability here guys. Very exciting. The agentic web. I think it's going to be a pretty big deal and to have, you know, kind of blockchain crypto beat the payments layer for that. It just seems like it's got to be the future. Congrats on main net, Georgios Brennan.
Thank you so much for joining us today. Thank you. Thank you guys. Bankless Nation got to let you know. Of course, crypto is risky. You could lose where to put in, but we are heading west. This is the frontier. It's not for everyone, but we're glad you're with us on the bankless journey. Thanks a lot. You