If crypto wins without privacy, did we actually win?
In this episode, Ryan sits down with Aztec co-founders Zac Williamson and Joe Andrews to unpack their eight-year quest to build a private world computer for Ethereum, covering the Aztec ignition chain, zero-knowledge-powered “private intents,” and how you can route trades across L1 and L2s without exposing your strategies or balances. They dive into ZK Passport (turning your NFC e-passport into a proof of personhood), the coming breakdown of selfie KYC in an AI world, holistic on-chain identity, Aztec’s one-shot move to a fully decentralized L2. Along the way, Zac and Joe get candid about the regulatory risk of building privacy rails, echoes of the early SSL wars, and what keeps them grinding after nearly a decade of R&D to ship Aztec Alpha
---
📣SPOTIFY PREMIUM RSS FEED | USE CODE: SPOTIFY24
https://bankless.cc/spotify-premium
---
BANKLESS SPONSOR TOOLS:
🔵 COINBASE | ETH & BTC BACKED LOANS
https://bankless.cc/coinbase-borrow
🪙 FRAXNET | MINT, REDEEM, & EARN
https://bankless.cc/fraxnet
🦄 UNISWAP | SWAP ON UNICHAIN
https://bankless.cc/unichain
🛞 MANTLE | MODULAR L2 NETWORK
https://bankless.cc/Mantle
💤 EIGHT SLEEP | IMPROVE YOUR SLEEP
https://bankless.cc/eight-sleep
---
TIMESTAMPS
0:00 Intro
6:00 The State of Privacy on Ethereum in 2025
9:47 Identity as the Missing Piece of Privacy
11:52 AI Deepfakes Just Broke Web2 KYC
20:19 How ZK Passport Plugs Into Aztec (and the Token Sale)
23:04 Holistic On-Chain Identity: Bottom-Up, Not Top-Down
30:54 From Private Bitcoin to a Private World Computer
36:36 Private Intents: Using Aztec as Ethereum’s Privacy Router
43:15 Compliant DeFi with ZK Identity in the Loop
48:37 Does This Actually Solve Privacy on Ethereum?
50:38 Ignition Chain Launch: Stage-2 Rollup with Decentralized Sequencers
56:19 One-Shot Decentralization, Alpha/Beta, and Security Model
1:05:37 Scaling a Private Rollup: TPS, Fees, and the Aztec Stack
1:11:40 Noir, No VM for Private State, and New DeFi Primitives
1:17:08 Selective Disclosure and ZK Receipts for Regulators
1:21:29 Privacy vs Nation States: The Second Crypto Privacy War
1:29:45 Why Keep Building Privacy After 8 Years?
1:33:37 Token Sale, Fair Auctions, and Running an Aztec Node
1:37:33 Closing Thoughts: The Most Cypherpunk L2 Since 2016?
---
RESOURCES
Zac Williamson
https://x.com/Zac_Aztec
Joe Andrews
https://x.com/jaosef
Aztec
https://x.com/aztecnetwork
---
Not financial or tax advice. See our investment disclosures here:
https://www.bankless.com/disclosures
No summary for this episode yet.
Welcome to Bankless, where we explore the frontier of private internet money and internet finance. This is Ryan Sean Adams, just me today, so I'm here to help you become more bankless. There's been this recent refrain in crypto, it almost rings out like a complaint. Where have all the cipher punks gone? I'm pleased to say I have two of them on today's episode, and honestly talking to them was like a breath of fresh air. The promise of their project, Aztec, is to bring privacy to Ethereum, without cutting any corners. They're trying to ship a private layer too that truly extends Ethereum grade decentralization with privacy on top, private transactions for all of DeFi.
Now I know it's still early, but honestly, I think they may have done it. Zach and Joe have been working on Aztec for so long that I think a lot of people in crypto have expected this thing would never ship. Yet, it's here. The Aztec network is live, it's producing blocks. These are private Ethereum secured blocks, and they're just months away from an alpha main net. To me, this is probably the most cipher punk project to launch in crypto since maybe 2016, and maybe it won't be successful. After all the critics keep telling us that the world doesn't care about decentralization, that crypto is now just a whole bunch of ETFs and corporate chains and BlackRock and compliant stablecoins, I think they might be wrong about this.
The world may not care about privacy and decentralization, but the world definitely needs it. Now more than ever, and crypto needs more cipher punks, like Zach and Joe. We'll get right to that episode, but before we do, I want to thank the sponsors that made this possible. You can now borrow USDC against your Ethereum and Bitcoin on Coinbase. Crypto-backed loans on Coinbase make assessing liquidity seamless for crypto-hodlers. Powered by Morpho, Coinbase crypto-backed loans gives you direct access to on-chain financing, allowing you to take out loans at competitive rates using your crypto as collateral.
Over $1 billion in loans has been opened through Coinbase to date. On the Coinbase app, eligible users can borrow up to 1 million USDC using Bitcoin or Ethereum as collateral. Users can convert their USDC into Fiat to make down payments, refinance debt, or cover urgent expenses, and more. The benefits are numerous. Interest rates are variable, typically between 4 and 8% and respond to market conditions. Loans are approved in seconds without credit checks, repayment schedules are variable, meaning there are no fixed deadlines. The kicker? Coinbase will not treat borrow transactions as taxable events.
Managed loans directly in the Coinbase app with ease. It's currently available to US customers except New York, and additional collateral types and increased loan limits are coming soon. To learn more, click the link in the show notes or visit Coinbase.com slash borrow. Introducing at Frax USD, the genius-aligned digital dollar from Frax. It's a secure, stable, and fully backed by institutional-grade real-world assets, custody by BlackRock, SuperState, and Fidelity. It's always redeemable one-to-one, transparently audited, and built for payments, DeFi, and banking. The best of all worlds. At the core is FraxNet, an on-chain fintech platform built to align with emerging US regulatory frameworks, where you can mint, redeem, and use Frax USD with just a few clicks.
Deposit USDC, send a bank wire, or tokenize treasuries, and receive programmable digital dollars straight to your wallet. FraxNet users have benefits from the underlying return of US treasuries and earn just by using the system. Whether you're bridging, minting, or holding, your Frax USD works for you. Frax isn't just a protocol, it's a digital nation, powered by the Frax token and governed by its global communities. Join that community and help shape Frax Nation's future. We're going to Frax.com, slash R, slash bankless, Frax designed for the future of compliant digital finance. Zach Joe, welcome to bankless today.
Thank you so much for having us, so much for having us. Really excited about this, so it's been five years almost since we've had you on bankless. This is actually a screenshot from a very young babyface looking David, I think, from one of his many places he's lived around the world, and the two of you guys from five years ago, four months or four years and eight months ago, I guess, starting the question out, what have you guys been doing over the past five years? Well, I guess the obvious one is I've regretted some hair, and this was in the depths of COVID, I think. And yeah, we hadn't seen each other all the team for a while, so we all went a bit crazy in the UK and COVID, but apart from that, we've been chipping away and bringing privacy to Ethereum.
I think, since we, since we last spoke, we had a roll up on Ethereum called Aztec Connect. We've now built a brand new version of that that brings, you know, fully programmable privacy to Ethereum, and it launched its ignition chain last week at DevConnect, so lots of them happening. We've been kind of keeping beating on the same drum of bringing privacy to Ethereum, and yeah, it's been, it's been crazy to kind of see the progress. So Zach, how do you explain your hair situation back then? There's an all-covid. And you know, how things, yeah, don't care if it's pretty hard. Joe and I, we took the opposite approaches, Joe was like, I'll cut my own hair, I was like, I won't bother having a hair.
And yeah, you know, I was going on research benders back then trying to figure out how to like fix certain existential issues with, with privacy tech, so I don't know maybe the hair helped the channeling, channeling Albert Einstein. Are those things fixed now? Well, I mean, I think we'll fix it. But we'll find out, because we're going to be completely devoid of our network early next year. And the issues I was trying to figure out was effectively, how do you actually take a smart contract, platform like Ethereum, programmable blockchain or world computer, how do you make that fully private without destroying the user experience, the developer experience?
And that's a hard problem. Stickers are all to solve. It's why we've been building for five years, but we're pretty confident we've solved it. We're building there's so much to get into today. I guess I'll give listeners some context. So the Aztec ignition chain is a newly launched chain. It's not fully launched. It's in one of the launch phases. We'll talk about that. I'm actually at the time, about five years ago, we were talking about one of the first Ethereum rollups, which was a rollup that Aztec team had come up with. And you guys deployed that. And then I believe that went into legacy maybe a few years later.
But we'll talk about the story of that and now where we are with this new ignition chain and what all of the features and all of the things that you've built up into that chain in a moment. But I guess I want to start with the high level here. So as you think in about 2025 and going into 2026, can you describe the state of privacy in Ethereum today, like have we made any progress? Where are we right now? This has clearly become more of a core value with Ethereum. People care about it. People talk about it. The quality of privacy that you have today versus five years ago, not a huge amount has changed to be honest.
You know, we're starting to see the seeds of that. But ultimately Ethereum is a completely transparent network. When you send transactions through Ethereum, everybody can see what you're doing. They can see who you are. They can see who you're recipients are. They can see the smart contracts you're calling the programs you're using. The amount of money that you're sending around. And this is hugely restricting on what you can actually do with Ethereum. Just purely being able to not being able to hide your balances is a big problem if you want to use Ethereum for anything competitive or professional, for example, if you have a portfolio on Ethereum and you've hedged it and you're trading, well, people can see your hedges and so they can undermine those.
And we've seen demonstrated tax against that that have happened on Ethereum. They've happened on Hyperliquid. It's also extremely limiting the lack of identity on Ethereum. But I think I can go into that in a separate topic. So how is the case act that over the past five years, we've made almost, like, has there been any progress made? I mean, there are some privacy protocols out there right now. So there's rail gun, I mean, to know the cash is no longer sanctions. I believe it's no longer considered a terrorist by the American government. You have a lot of toolkits available that could be used to build products as well.
Kahaku is something which has been developed by Ethereum Foundation. That's a wallet that uses rail gun, I believe. But ultimately, and there's been a lot of technological innovation. The reason for the lack of the limited progress in terms of user-facing products and services is just it's an extraordinarily hard problem. We crack this a few years ago, like, how do you do private token balances? How do you transfer them around? Do you use e-cash with pioneers? Then you have things like rail gun, you had asked to connect. But the challenge is, how do you add probability into that? Because if you want to do anything really advanced with privacy, you need an understanding of who somebody is.
Because you probably need to be able to distinguish reaching good and bad actors just somehow, given current climates, given user preferences, given the basic, basic needs to create legitimate systems. And that question, who are you? That's very hard to answer in a permissionless, fairly decentralized network without having to rely on centralized third parties. Is that something that the ignition change has kind of cracked? Who are you talking to about that? Ah, interesting. Yeah, so I think at a high level, like, the way we've kind of solved identity is actually, it doesn't just happen to be on kind of the ignition chain.
It's more about kind of, in general, the state of CK technology. There's kind of teams now building proof of identity. And previously that was kind of, you know, credentials signed by kind of third parties like five years ago. Now we can take your passport and we can verify on chain that it's a valid passport issued by the UK or issued by the US. And you can effectively do a proof of personhood using your existing passport or identity card with a smart contract. And you can selectively disclose any information you want to the chain in that, in that check. So I could prove I'm above 18 or I could prove I'm not from the sanctioned country or my name's not on the sanctions list.
And so we're now in this world where you can take a zero knowledge proof, send it to a smart contract. And instead of getting privacy through kind of centralized intermediaries, you can just directly interact with the blockchain and make a compliant application that effectively knows that you're not someone. And that's a huge breakthrough. And so that's powered by a lot of the technology we've been building over the last five years. We were programming language called MLA, which makes that very easy. And Aztecs kind of the default place where you can now deploy these applications. And so I think it's more like, as I was saying, the core tech has come on a long way, but we're still seeing kind of maybe the, maybe the industry catch up.
There was a bit of a chilling effect that came into effect around tornado cash and kind of the ban of privacy in the US, which I know you guys are fighting for as well on the front lines. I think that has maybe slowed down where privacy adoption could be relative to kind of why it isn't the background. But we feel very confident that the tech now is ready to kind of make a breakout because we have these amazing tools like ZK Possible that can put it front to the center again. Let's talk about ZK Possible for a minute in this idea of identity because I do think you're right. Privacy and identity seem to coexist or at least grow together in some way.
And I think the lack of identity solutions, private identity solutions has maybe prevented us from scaling privacy in the way that we want to scale it. I was looking at a lot of bunch of tweets on my timeline over the past few days that looked something like this. And I think this is a tweet from Martin over at the NOSSAF project. And he's tweeting a picture of a Google Gemini AI generated deep fake of somebody with a passport. Actually, this is him with a passport. He's using an AI prompt to basically deep fake AML KYC Gemini style. I think everyone listening to this has probably signed up for some sort of digital bank online, maybe an exchange, and there's some sort of AML KYC type of service.
And the way this goes is usually take a picture of your driver's license or your passport and you send it in. And then there's a proof of personhood type real-time checker where you take a selfie of yourself. You might look into the camera, you might stare left, you might stare right. And it signifies that this is a human, that this is Ryan S. Adams and we can let this person in because he's not on a sanction list. It's interesting that AI is going to break this completely. Is it not? I mean, the ability to just deep fake this. It's like, and I don't know that world governments or existing compliance regimes have caught on to how fast this is going to happen and it has already started now.
That method is basically broken. Can you talk about this and how is something like ZK passport a change from this regime? Yeah, maybe I can start. I think I've got a few good analogies here. So I think since about 12, 15 years ago, I can, who are the kind of civil aviation kind of body, started creating e-passports and they created the standard that means that kind of all modern passports and identity cards, they have a chip in them. And that chip can be read by an NFC scanner and inside it it has data that's signed by the issuing authority. So your government who issued the ID card, you know, you may not trust fully, but if you live in that country, they're a good source of trust as kind of like a trust authority.
And so what ZK passport does is it uses the same tech that lets you enter through an e-gate when you scan your passport in an e-gate. What's interesting is they're reading that chip. They're kind of using the, there's a decryption key embedded into the image. They're decrypting information in that chip. And they're making a zero knowledge proof that that's valid. So you can hold on for a second here, Joe, so an NFC chip inside of a nation state password. Is that counterfeit resistant? Is that tamper resistant? Completely. Yeah. And then see, it's kind of all of the chips. There's a big kind of like tree of trust.
And so at the top of that tree, there's a private key stored by a nation state. And then you can verify that every chip that's issued and the sign has been signed by that key. So unless you can get hold of a nation state's private key, you can't issue and verify a fake passport. And so this is how we let people into countries. This is how e-gates work. And what we're doing kind of in ZK passport is we're taking that same signature that's embedded inside your passport. And we're verifying it in zero knowledge and getting Ethereum to say, hey, is this valid? So you can kind of think of like Ethereum is now an e-gate for transactions.
And you know, the same with the same security as you have to enter the US or the UK or any kind of country we can now get the same either station that you're not on a scientist list or you're from a certain country. Which is crazy that this is going to never happen before. And all of the web two companies are still using kind of pictures of your ID and aliveness check. And so yeah, we're very bullish on this as being kind of a much more private way of doing things. It takes a little bit of a mental model switch because at first when people hear about privacy they're like, oh, I don't want to put my ID into something.
But that's because Ethereum's fully public. Now we have like strong zero knowledge proofs and a way to kind of actually encrypt that information and send it to the blockchain. You can start to send this information as part of transactions and prove interesting things about it. So I think that shift is going to start to come and I think it's really the only way we have to kind of resist against kind of deep fakes. So it's going to be exciting 2026, I think. You can make sure I understand the user flow for ZK Passports. It's been on my list to go, you know, try this and check this out. And I know it's kind of integrated into the part of the onboarding experience of AsTech which we'll talk about in a minute.
But so you're saying basically I take my government issued passport. I have one from the US. Let's say it has an NFC chip in it. And what do I do? My phone, like my iPhone with the ZK Passport app can actually has the ability to scan an NFC chip and validate it. Yeah, I can run through it totally. So you know, you tap your passport to your phone. It'll scan the chip. What's going to happen is it's good. So that chip will give your phone a digital signature of like all the possible data, like your photo, your passport number, your data birth, your name, blah, blah, blah. Stuff you don't want to share with the world and what's going to happen is ZK Passport uses our technology to create a zero knowledge proof saying here's a hash of all this data, like an untouchable hash.
I'm not going to tell you what's inside it, but I can prove to you two things. A, you know, it's like this person is not from a sanctioned list. And B, this is quite important. This person's phone has like what it asks the app is you do is it asks you to take pictures of your face and your phone's secure on clear that little secure chip in this will say, this photograph that I've taken, it lines up, it matches the face of the, it matches the face of the passport. And so that's also wrapped into the proof. So you don't just know that somebody possesses a passport from a certain region. You know that they're also like their life is in like the person holding the passport is the person running the app.
Okay, so the ZK Passport not only verifies that I have a passport in my possession and FC chip, but it also does that like as well with my face and sort of matches that. But that information stays effectively within the secure enclave of my phone. It doesn't leave your phone because the secure enclave creates a digital signature going, yeah, this is good. And then that signature is validated within the ZK Passport proof. So that's, you know, I think is that works. You basically, you know, like, yes, they're like, there's a, there was a live this check formed by like an iPhone or an Android phone.
Of a photo that somebody that matches the photo in the passport. And that passport is like from a certain region or not from a certain region. And that's the data that gets broadcast. So the things that your photograph, your name, data, birth, that stuff, that stays, stays on your phone. Wow. Okay, so I mean, even that alone, I know this is a powerful application of ZK. And it's broader than Aztec. But that alone with the advent of basically AI deep fake coming out over the next six to 12 months. I mean, don't all Web2 companies, doesn't the entire financial system, doesn't like everything need to de facto adopt that?
Like, what's the alternative? Everything happens in person again? Like that can't be what we do. Zach keeps saying the privacy is eating the well, but I think this is a clear case of like, like, where is it? It has to ride a minute. It's like, I think otherwise we have to stop doing things on the list. Right. We're just, you rely on social third parties, right? Like, everything the ZK passport app does. Yeah. You could get the same effect if you just send all your data to a server. And then that server has your passport data. And that's often how it works today. And then you get those servers get hacked and your passport if it gets leaked and it's a nightmare.
Yeah. But doing it the zero knowledge way is to secure Web doing it for sure. Okay. The ZK passport piece of this. And I guess that that works very natively inside of a crypto system, right? Because then you know that, you know, this person is who they say they are and maybe they're not sanctioned. Just briefly though, how is ZK passport related to the Aztec project? Is it sort of just an adjacent type of application that can is useful for privacy or are you guys tied into it? So a few ways. So it's a team we funded in our ecosystem. So that's kind of the main, main kind of relation. But beyond that, there's a few other places where there's overlaps.
So you can take ZK passport proofs. You can verify them completely off chain. It's a kind of like proof of age on kind of websites. You can verify them in this Ethereum smart contracts or you can also verify them natively inside Aztec transactions. And so you can take the zero knowledge proof and Aztec is kind of like the best place to verify these proofs. So that's kind of one area where they're also related. And then secondly, we're also using this in our token cell, which is happening at the moment. So we've been able to convince Swiss regulators that using a zero knowledge proof of non-sanctions is a valid form of sanctions check.
So if you want to participate in token cell, you can go and use ZK passport. And I think for the first time, you can use this kind of zero knowledge proof to prove to an Ethereum smart contract that you're not on the sanctions list, which is incredibly exciting. You can obviously go and do the old way of doing KYP or KYC if you want to, but there's now a privacy preserving alternative. And the last way it's related is it's also using is written under the hood in this programming language we've built called NOAA, which is going to very develop a friendly language for writing zero knowledge applications.
So because ZK passport team is in our ecosystem, they've been building this in NOAA for the last kind of 12 or so months, which is exciting to see. So for the ICO, the coin sale that's ongoing right now, ZK passport is effectively used in lieu of a traditional AML KYC check just to make sure that the entity has not been sanctioned and is eligible for the token sale. That's correct. Yeah, we were able to get the Swiss regulators to kind of first do you know? This was like a valid form of sanctions check for individuals, so it's pretty exciting. But will individuals need like later when we go form a net and start, you know, and users start using the Aztec chain?
Will they need ZK passport in order to interact with the rest of the protocol or is that part completely perishing? That's completely perishing. You know, from day one on Apple's permission is decentralized. We have account abstractions. So how one chooses authorised account? That's up to up to anyone, but, you know, we weren't to be stressed, we wouldn't be using ZK passport for that because it's not what we don't think uses will application develop as well because it's not convenient to carry a passport around everywhere to log into a Web 3 account. But if I could segue a little bit, this kind of touches on something with quite a core issue and value proposition in it inside Aztec, which is, how do you know somebody who somebody is?
Let's say you're building an application like a private stablecoin and you need some understanding that like, for example, like, you know, the person isn't North Korea, right? Because funds are not, if you can't see what's going on, you need some understanding you're not about. It's also very important for us to ask Aztec as a network that we give application developers the tools and the resources to program their applications such that they can give guarantees to their users that their users are not facilitating bad actors. You know, we don't mandate any of this, we just want to make it possible.
And so this ties into something which we're very, very keen on pursuing with Aztec as an Android ecosystem, which we're calling holistic identity effectively. Right another way the world works when it comes to identity is, you know, you have some centralized third party comes up with some kind of standard that's like 200 pages long and that it gets implemented and it doesn't change because changing it's just too much effort. And it means that, you know, this, this kind of identity standard is very rigid and flexible and can't get used by a lot of applications that could benefit from it. What we want to do in Aztec is the complete opposite instead of top down as bottom up, the idea is let's say you're an app developer, maybe have some identity needs.
Well, it should be very easy to program those like checks and checks into your application. You know, we'll provide the libraries and resources. And in doing so, that application developer is effectively issuing a credential on chain like an NFT or a token, which is a testing something about a user. It might be as simple as, you know, this user has a Twitter account with over 100 followers so they're probably not a bot. It could be this user has received an email from a certain company. So I know they have an account for that company and you can use the K, not zero knowledge as you can email our technology to prove that.
If you have enough of these people participating in that with building these applications, building these credentials, issuing platforms, then you can start to create meta credentials on top of that. You can start to wrap a lot of these tokens so that you consistently more concrete about an individual. And in doing so, I think you can end up in a while. We have very strong identity checks. I didn't understand this, but what's happened is twofold, two things. First of all, it's all using ZK. So none of the data is leaving the user's device, right? There's no actual data on chain on the network that is telling you about what somebody is.
It's all encrypted. But the other important thing is, there's these credentials are not being issued by centralized third parties that can exert a lot of control over a few participants in the network. The idea is, we don't want like one identity provider saying, oh, you're Ryan, you're Joe, we want smart contracts to be able to go, oh, yeah, you're probably Ryan, but that knowledge has come from possibly hundreds of different sources all on chain. That are issued by hundreds of different counter parties so that you have a fully genuine decentralized commission with a network that can provide strong identity, strong privacy benefits.
In that world, the nation states and government and passport issuers are just one more tester essentially. And they're able to attest citizenship and some other things with some certainty. But there are many hundreds of attesters. This has been kind of a promise that Ethereum has made for quite a while. There's kind of like an Ethereum identity protocols that have been proposed. How come we've not gotten this on Ethereum already? And what is Aztec specifically doing to bootstrap, ZK, attestation, to be able to provide richer identity services? I think the main thing is that the early versions of this required an intermediary.
So it was like, hey, give your data to the service. Then they'll sign a message saying you did the thing. So it could be that you control this email account or that you have this money followers on Twitter, but it was all intermediated. Then there were some projects. I think probably one had a project around kind of like ZKID, but a lot of it, like the credentials that you want use Web2 cryptography, which notoriously is very hard to kind of prove things about in ZK. And so we needed some breakthroughs in the kind of cryptography technology to actually make this possible. So I think like now we're in a world where it is possible.
It's always been the promise, but I think we haven't been there today because either the tech wasn't fast enough to prove things locally on your device, or it was just done through intermediaries before and that didn't really catch on. It was going to be against the whole thesis of Ethereum, which was like removed into intermediaries. And so I think those two reasons are why it hasn't happened in Aztec. I think the main reason why we think it's going to take off is because every transaction is a ZKID proof. So there's no way for you to kind of like leak this information. You can bring in all different types of data sources into one transaction on Aztec and verify them all succinctly and cheaply when you send that transaction to the blockchain.
So I think that alone should encourage developers to start experimenting, and we should just see this take off naturally as much as we can expand on that as well. One other key thing is you really need a fully private by default blockchain for any of this to work, and this concept of private composability, basically. I can write a private smart contract and I can just code it up like in a regular normal looking programming language, like noir, and my contract can call other private smart contracts written by other people and they can call other private smart contracts. And this all gets bundled up into in a single transaction that user sends.
It just works. That's not possible anywhere else. I'll give an example of why it doesn't work on Ethereum right now. Let's say you want to build some kind of identity standard system on Ethereum, right? You need ZK because that data can't be transparent. You can't, you know, you're not going to put passport, number, social security numbers on a public ledger. So you do something in ZK. And that right now on Ethereum, because Ethereum doesn't have default privacy requires you writing some complicated ZKID circuits and providing some complicated ZKID software for users to generate this required proofs sent into Ethereum.
So now let's see if someone's built that and now I come along and I have an app and I'm like, well, I need a slightly different concept of identity. So I've got to build my own and I've got to do this for again. And I've got my own ZK system stuff and my own ZK software and let's see if there's a third app, which is like some exchange or an AMM in it and it says, okay, well, I want to interface with these two identity platforms because I need both of them to interoperate. Well now I have to inherit their complicated tooling and software on my end. And if anybody wants to incorporate my app, they have to do the same.
And you have this kind of explosion of complexity because every privacy solution on Ethereum has to be its own like hand-coded circuit with its own tool chain. That's not the case on Aztec, right? You can code up your whatever your program's doing, it was doing identity or games or whatever it's doing. You just code it and not and your contract has an interface that gets exposed, right? And then you can just ask your nodes to call the contract and it just works. So you can actually start to build these composable private systems with a real network effect. One of the things that I feel like has always been central to the Aztec project as you've moved through different iterations of what this looks like is actually bringing privacy to Ethereum specifically.
And I think maybe the reason for that is because you want to make privacy programmable. So privacy does exist in pockets. You have a chain like Zcash, for instance, which tries to accomplish kind of a Bitcoin transactional UTXO model style chain and provides privacy around that. We also have things like rail gun or tornado, which maybe allows for privacy pools and kind of like shielded transactions in some small form. I think the main thing behind Aztec and why I've long thought that this was sort of the promise at least is the Holy Grail is actually bringing Ethereum's Turing complete programmability, which implies all of DeFi and everything that can be built on top of Ethereum, bringing privacy to that.
You talk about that. Is that still kind of the mission behind Aztec? I think part of my question going to this is like, okay, this took a long time. I know you guys have been hard at work. I know it's not like you've been slacking off for the past five years playing with meme coins. You've been hard at work on this. Is that the big thing? Is that why it took so long is because you needed to preserve the programmability? Maybe talk about that. Why is that the mission? And why was that so hard? Yeah, 100%. So that does definitely still the mission and we're going to get there in two ways. I think the first way I think is to maybe look back at what we talked about last time on the podcast, which was kind of how we can bring privacy to existing DeFi.
And that was with a product we called Aztec Connect. And what we had with Aztec Connect was a way to effectively have Cache style transactions for any ERC20 on a roll-up with built, but we gave that roll-up the ability to interact with other Ethereum smart contracts. So if you send a transaction from the kind of Aztec Connect to back then, you could bridge funds effectively to any DeFi on layer one. We have built that functionality into kind of every smart contract on the new Aztec chain. And so by default in this chain, you can now bridge funds from many Ethereum smart contract and any Ethereum out to smart contract.
And the reason this works is because Aztec's block space is differentiated. If you send a transaction from Aztec, the block space is private. And so you can bridge funds to base or to arbitrary or to optimism, can bridge an intent to those networks. And you can interact with existing pools of DeFi without having to rebuild Uniswap or are they on Aztec itself, which is really exciting. And the reason it's taken so long is exactly kind of what you were trying to say earlier around preserving composability. When we had the old version of Aztec, we wrote all the smart contracts that existed inside Aztec.
Effectively, there were three smart contracts. There was an account contract, a joint split contract for transfers and a DeFi contract. And we had to kind of audit them all against each other. They were all written in C++ and composability was a nightmare. What we realized kind of with that old version of Aztec is that in order for this to take off, we had to build programmability and composability between smart contracts into the protocol and have it such that a smart contract could call another smart contract without the core team having to kind of audit it and write it. So that was the big breakthrough that took many years to get right.
But effectively, what it means now is that you can have this programmable composability within Aztec. And each Aztec contract can call five contracts within Aztec, the L2. And then you can also have the result end up on another L2 or Ethereum. And you get incredibly strong privacy guarantees as a result. So we kind of view also a bit like a privacy left for all of Ethereum. And it doesn't matter kind of where the transaction ends up because you're kind of moving funds as a user through Aztec, you get privacy as a result of doing that. It's a private world computer, right? Right. Right. Like our goal of being a private Ethereum, yes, you know, that privacy check, I think, right now, before Aztec, I know there's been some years away from this, but as largely in terms of the applications you can use, it's private Bitcoin.
That's what it really is. And we want to make it with privacy tech, private Ethereum. That programmable world computer is the thing that really captured us in the early days. You know, the idea that you can write any kind of software you can write like a decentralized bank, you can do assets, you can do finance, you can do derivatives, you can do voting, you can do governance. It makes Ethereum, it's not just a financial technology like Bitcoin. It's a social technology. It's a way of organizing people and organizing communities and getting them to like coordinate and collaborate on shared projects.
And that's that side of Ethereum, I think, is very constrained and limited because of the lack of privacy. The financial side is limited by the lack of privacy. It's all limited by privacy. You know, we came into this looking at privacy, thinking, well, this is like the missing ingredient to make Ethereum really big, really, really big, you know, like the world-spanning financial infrastructure. So yeah, we've been obsessed with it for years. The private world computer bringing privacy to all of Ethereum, the Aztec ignition chain is a layer two. And Joe, when you were talking about this, you were using terms like composability.
And I think the experience that users have with layer two is not quite composability. In fact, they might use the term fragmentation instead. So the typical experience of using a layer two is it almost feels like going to a separate country, you know, a separate chain, right? So like, I take my whatever asset on Ether and if I want to go trade it for an asset, on Ethereum rather, if I want to go trade it for an asset on base, I have to go through this whole process of like bridging to this layer two and there's a different set of liquidity and there's kind of a different UX. I feel like I'm in a different land altogether.
How does, I guess, how does Aztec in because it is a layer two, how does it blanket existing Ethereum with privacy and preserves from that composability? It would be helpful here is if you took listeners through a typical flow. Let's say they have Ether as an asset and they want to get some USDC, okay, and they want to make a trade, exchange my ether for USDC and they want to do that privately, okay? Do they have to go through this process of I got to go bridge my ether all the way to Aztec? I get to Aztec and there's limited liquidity for USDC. I'm getting worse trade execution and I'm in this Aztec world and by the way, it took a long time to bridge and it's a pain in the ass and then when I want to move my USDC back to Ethereum someday, then it's a whole nother process, is that the user experience or can we do something better?
When you said composability, I was hopeful for a feeling that I'm still on layer one but I'm somehow in my wallet, I'm being able to click a button that says like do this incognito or do this transaction privately and it just seamlessly happens for me. Is that a world we could live in? I think the answer is yes and no, under the hood, bridging still has to occur. It depends on how much you abstract that from the user. To walk through the flow, there's two ways it can work. One way is the user moves their funds to Aztec and you do have to go for a bridging flow but when you do the bridging from Aztec, you can pick any destination chain, you can pick which liquidity you want to trade against and you get privacy as a result of doing it.
It's like you take the existing bridging flows which can suck but you're at least giving them a reason to go through them because when they go through them from Aztec, you will get privacy by default. That's one flow and maybe let's just make it up. If I'm bridging and I want to go to base, you're saying I can go through Aztec first and then I'm starting from privacy, so the private instance of base. Aztec is your pass through chain. That's the best way to think about it. It's a bit like the whole intent meta, near intent is a great example of what's happening going up with near intent on Zcash.
Effectively, as an Aztec user, you would have, let's say, you have ten-eat on Aztec and you decide you want to switch it for the USDC on base. We use a transaction on the Aztec out too that says, I want to swap ten-eat on base for USDC and the world sees someone on Aztec wants to swap ten-eat for base on USDC and they want the funds to be sent back to Aztec. What happens under the hood is a relay comes along and they pick up that intent, they fill it for you and they return you the funds and they can return the funds to Aztec, they can return the funds to a brand new account, a transaction account on base that's controlled by Aztec, they could even return the funds to a Ethereum mainnet if they wanted to.
There's lots of different ways this pans out, but effectively because the user who's doing the transaction is not known inside Aztec, you get a degree of privacy doing this. There are other ways to do this directly from your Ethereum wallet, but that requires a little bit of adoption on the L1 wallet stage, which obviously hasn't happened yet because Aztec is brand new, but over time, I think there will be ways to streamline this under the hood, so you may not even know that you're bridging when you do this and there's a lot of work going on in the Ethereum space right now to try and unfrag my Ethereum and that will just make it even easier for us to bridge privately to other chains.
I think it's going to be exciting to see this bridging or private intent play out and the way I think about Aztec in the short term is kind of what percentage of transactions on all these L2s would like to have some privacy, and I think a decent percentage of users will be about those transactions through Aztec as a way to maintain some of their privacy. You can go a step further as well and say that when you route through Aztec, you can enforce logic ahead of those transactions, so let's say you have now a real world asset pool on Arbitram where only people in the UK can interact with the pool.
You can put as the passport proof ahead of the transactions on Aztec and say, okay, well we want to enforce the only users who have UK passports can interact with this pool and the same flow as possible and what you would see in public was someone on Aztec who has a UK passport wants to trade with this pool and you would have a guarantee from Aztec backed by Ethereum because we're now too that kind of rolls up to Ethereum that this is true and so you get this incredibly strong privacy credentials as a result and then over time we will see let new defies start to be created on Aztec, but I think that will mostly be, we won't be recreating Uniswakura, we'll be building defy that requires privacy built into it to function and a good example is maybe the difference between an AMM and an OTC desk.
So there will be kind of new defy parameters built to Aztec because privacy expands the design space, but in the short term we'll see a lot of this kind of private intent flow to kind of bring privacy to all of Ethereum. Fascinating, okay. So the private intent flow is really part of the unlock here that really allows Aztec to blanket the rest of Ethereum and all of the layer 2s, the L1 and the layer 2 with privacy rather because I think a lot of people listing might be stuck in the paradigm of rollups from 2023, 2024 and even 2025, which is if you start a new rollup, the number one thing you have to do is you have to go copy paste all of the existing Ethereum defy protocols.
So I need my version of Ave, I need my version of Uniswak, I need all of the different primitives that I find on Ethereum and they have to copy and paste this and then bootstrap the liquidity and of course these ecosystems need to port their contracts and that gives me a little containerized ecosystem, right? That's the way maybe I was thinking about Aztec going in or some listeners are thinking about it going in. You're saying that's not the case. Effectively, the entire Ethereum ecosystem, all the layer 2s, all of the defy protocols on Ethereum mainnet, they can using private intents basically tap into Aztec privacy on demand, you know, at request and I guess, you know, maybe talking about the user experience of that, if that's painful at first because it's not directly integrated into wallets, I don't know if that causes additional transaction fees or delays, but the idea is you're able to link at the entire Ethereum ecosystem and everything in defy all of the liquidity with privacy rather than having to copy and paste and start from scratch.
Am I understanding this correctly, Joe? Yeah, definitely. All we need kind of when the chain, like transactions are enabled on the chain is one UI that enables you to deposit a Ethereum wallet and you could have, because we have really a native account abstraction features, you could just go to that UI, that data, and it can give you access to all of the Ethereum privately. So that's like one smart contract on Aztec, which enables all of that. And obviously, you could have much more expressive contracts and so we're excited about the design space kind of expanding, but it was one simple kind of bridging contract and we have, I think, two teams have built them already.
The one whole team and a team called, let's get their name for now, but the one whole team is photo bridge and yeah, that basically gives you that functionality for free and you don't need to bootstrap any new liquidity. You just need users to kind of decide they want privacy, which I think most people do. And that should be a very compelling use case. So in my wallet, I want privacy for this particular swap transaction. This is in the far future, maybe, and I click the make my transaction private button. Will this require additional fees from user perspective, does Aztec kind of take a cut? And what about the time, right, like to bridge to get the kind of the water filled, all of that.
Will that add some delay to my transaction as well? Yeah, it does add some fees. You have to send a transaction through Aztec, but we're led to some like most other transactions will have kind of two to five cent transactions, so there'll be some, some fee you have to pay to Aztec, it's fairly nominal and a fixed fee. And most of these use cases require one block on Aztec and one block on the destination chain to kind of fulfill. So there's a little bit of latency, but with block times coming down to be kind of like some Ethereum blocks, like it should be, it should be kind of a pretty great UX in the near future.
I think it's, you know, from, from a kind of, when the transactions confirm to when actually settles, there's a difference there, but from a user perspective, they should just send the transaction and it's kind of set up for you to add to that. I think it's, I think it's a substance lapse in train and the other other engineering partners that we're tapping to, that we're working with. I think it's just a true, like high level, like the fundamental reason why we are doing this, what we can do this is because, like, bridging into an out of Aztec, in my opinion, is very positive sum and it's quite unique because most, most delties are parasitic to their L ones because, you know, you want your own liquidity, as you said, it's fragmented.
That's because of the incentives, right? Every protocol wants to send a legal system and they're all largely undifferentiated, right? They all have AMMs, they all have lending markets, they all, they all have the same stuff and so they're all trans-compute with the same liquidity. With Aztec, there's a very unique distinction, which is that there is value in bridging not assets, but information into an out of Aztec, where if a transparent network wants to either, like, do some kind of permission request that requires knowledge of a user, they can send a request into Aztec going, hey, is this person who they came to be, are they allowed to do this?
And then, yes, the network can perform the checks encrypted in an encrypted way and then send back guests or no, or you can use intense perform bridging to get access to private funds for DeFi. By the way, the assets, they're long, some home is on some other network. What's happening inside Aztec is really information processing, but we get fees from that. So we're happy as an network and the other L2s and L1s are happy because they get added value from connecting with Aztec. So I think you're going to see a very different dynamic between Aztec and the rest of the ecosystem that you don't see with transparent L2s.
So is this it? Does this solve privacy on Ethereum? Like, are we done? And here, once I know Aztec isn't fully made net, we'll talk about that, but once it is, once Wallace integrated, we have private transactions for everything in DeFi, correct? Is that it? Or is there is there something that Aztec doesn't solve here? Well, I'll try and be, it's more I know, I mean, it does largely solve it on my opinion. I think that the challenges execution, right, we know a lot of app developers that grind to the call face to build these systems. We need to look like we need work from Wallace developers to integrate.
But fundamentally, yes, we're way, basically, when Aztec launches where Ethereum was in 2015, but for privacy. So we have a lot of work to do, like we're not going away, we're going to keep pushing the boundaries because we want the network to scale. We want it to be faster, more throughput, we want it to be cheaper, but we want it to be more seamless, faster block times. So there's all sorts of work we can and I'm are going to do that. But the fundamental primitives of what you can do, yeah, they'll be, they should be possible. You know, feel free to call me and jump out on this in 12 months time, right?
If you can't do this stuff, if you can't bridge privately, you can't tap into Ethereum, if I privately call ourselves on this because this is our goal, this is our dream. Wow, that's amazing. So this is not live yet completely, let's talk about what is live. So there was a mainnet launch of the Aztec ignition chain, but I think this has been described to me as almost like a beacon chain type launch, whereas it's, it's available for sequencers or maybe call them validators, I wanted to find that role to just sort of get involved in the network and help run some of the infrastructure. It's not available for users yet.
It will be available for users, I think in 2026, all of the flows that we talked about will be possible. You talk about what has launched specifically right now and what is yet to be launched, we're waiting kind of last week at 1am in DevConnect for the ignition chain to launch decentralized. So we don't run a single node, the community runs all its nodes, so it's very easy to run a node. So if there are people listening who are kind of home-stakers, there are things you could do today whilst you're waiting, you can go and help secure the ignition chain and test it out. So you just need some Aztec tokens and you can stake as a sequencer and validator at the same meaning on Aztec and you will be elected for a committee and you can help produce blocks.
The difference between kind of the ignition chain and kind of what's happening next year is just that the gas limit right now is set to zero. So it's actually the same full execution environment Aztec is built, we're just waiting for some audits to complete and we want to ensure that, you know, as one of the first layer tools to launch fully centralized, we want to ensure that everything runs as intended on mainnet, we've been running this on testnet for many months, but the final missing piece was kind of economics and making sure this works in a mainnet setting with spending actual eth on gas and sequences and proofers getting Aztec tokens as incentives on the network.
And so the ignition chain is kind of that running on mainnet. It's been running flawlessly for the last week, four to five days now and yeah, at some point early next year, there will be a governance vote by those sequences to turn on transactions and then all of these flows we talked about will be possible. So it's really exciting to kind of see decentralized decentralization in action and see this thing come alive. I think kind of we're targeting the audits to be complete kind of early to mid-February and so that will be kind of when the change fully goes live and the gas limit gets raised from zero.
First layer two to launch that's fully decentralized. What do you mean when you say that? I think when I think of a layer two being fully decentralized, I'm thinking of layer two beats and it's gotten to maybe stage two, all of the requirements there. And then if I'm thinking even beyond that, maybe the full sequencing is also decentralized as well and that's fully permissionless for everyone to participate. So of course, layer two's consensus happens on Ethereum, I suppose, but they're using layer two's use some sort of a sequencer to kind of order blocks and fully decentralized to me would mean also decentralizing the ordering of blocks into some sort of permissionless network.
But Joe, when you said that, the first layer to to be fully decentralized, what do you mean? What's your definition here? Yeah, it's all of that and more. So yeah, as I think of it as a stage two roll up, it's kind of not stage two's doesn't have transactions, but it will be once it launches. So we have we have decentralized sequencing. So anyone can be a validator is fully permissionless to sign up and be a validator as currently about 600 validators on the main net. And we should see many more comment over the validator is a sequencer. Those are one and the same in a sec because you have two roles as a someone who's taking your sequencing when you're when it's your turn to produce a block and you're validating when you're helping other people make blocks.
And the reason we have the distinction is because we as a as a layer two on a theorem, we need to we need to basically submit the validity proofs to a theorem every kind of 20, 30 minutes. That would be a terrible UX if we had to wait for that to settle. And so the kind of sequences and validators can run ahead of a theorem to give good UX to users. And so if you have these two roles that that kind of when you stake as token, you fulfill. So that's kind of on the validating side, so we take that box. The second kind of thing in being fully decentralized in my definition is decentralized proving.
So a lot of chains kind of maybe started to think about decentralizing the validator set moving away from like a single kind of team validator or sequencer. And that they still have a centralized proving system. So we also had to kind of decentralize that. It's fully permissionist to be a prover in the Aztec system. And then the final kind of metric is around governance and ownership. And I think this is the one that's usually forgotten. Like if you have the first two done, but you know, the core team controls the protocol, they can decide what upgrades happen, they decide kind of what happens on the network and the community doesn't own the network, then you haven't really decentralized.
And so we've tried to achieve kind of all three of those. And the initial chain is kind of that in action. And the kind of ongoing token sales are attempt to decentralize the last one, which is governance and ownership in the network. So I think we are the first kind of fully decentralized there too. And I think the reason for that is that privacy just shouldn't be owned by anyone. It's not owned by anyone on the internet. We kind of take that for granted when we kind of use as a sale transactions, like this podcast is encrypted. Like the way we send this information over the internet is it's not going over a public connection.
It's encrypted. And so we want to make sure that when this amazing kind of privacy comes to Ethereum, it's not controlled by one entity or one team. And so we have we took decentralization very seriously as a result. How did you guys? How the world did you guys have the confidence to completely one shot this? All right. So we've got we've got all of these rollups right now going through stages of decentralization right and kind of graduating. It's taking a long time. Part of the reason for this is there could be bugs. There could be issues. You need some sort of centralized tax task force to step in and you'll fix something.
You know, some of the technologies right here and your Aztec is and you guys are one shotting this all the way to kind of stage two where correct me if I'm wrong. But you you can't there's no security can't counsel. You can't shut this thing down. You can't censor. You can't steal funds like it's a decentralized network in the way Ethereum was at launch essentially. And you guys are starting all the way there at the finish line and basically leapfrogging everybody. I thought there were good reasons for this not to be one shot and for this to be some sort of progression. And yet Aztec is starting at the at the end.
I can feel that. I mean, there's two things going on here. One of them is just the reason for this progressive decentralization out there is fundamentally misaligned in centers. If you have a fully transpired layer to then your value proposition is your transactions are cheaper and they're faster. And this creates a bit of a race to the bottom because adding in decentralization will have a mix of transactions slower and more expensive because you have higher coordination costs. So why do you centralize? Save your running an L2 in your sequences collecting all the fees. So there's a misaligned in centers that we don't have an Aztec because we're privacy in network.
We really need to be a fully neutral network where participation is permissionless where we're not just like responsible for like forwarding and examining your traffic. So the incentives were aligned. And as you said, you know Ethereum did it back in the day, so it's not impossible. There are never the relics, this technical risks that we need to mitigate because we're fully decentralized, you know, bugs, we can fix bugs, but it's not the fastest process in the world because we need to get our sequences to upgrade the network. And so we're doing, this is why we're doing a phase drawlats. You know, when we, we're starting with ignition, but when we turn on transactions, a next year, that's going to come with a lot of health warnings.
We're going to be very open and transparent about this that this network is not, we cannot guarantee it secure. We will have performed extensive internal audits, we will have performed external audits, we will have done everything we can to ensure that it's secure, but we can't rule out the probability of bugs. And the only thing that really demonstrates a network of secure is time, time in production where there are no bugs where it's not being exploited. And so in the, in the early days of the network, we're going to have a very generous bug value. We're going to be very open about people saying, hey, this is, like, this is going to be a dangerous network for a while.
So don't, don't go nuts, don't, don't, don't ape in with, with all your money. It will be at risk. And then when we hit second security milestones, I believe they are, if we go three months without a critical or serious bug report, and we have 99% network up time, we'll be like, okay, now we're comfortable calling us something more than just purely experimental. Now we think it's a bit more set, it's a bit safer, but we're going to have, it's going to be quite a, quite a long rollup process before we are probably saying, hey, this network, like we have confidence in it and it is completely safe.
You can do whatever you want with it. That's going to take some time. What's nice, I think, from my perspective, too, is I don't, I guess as a user, I don't have to start by moving all of my assets essentially to Aztec, right? So the use case, Joe, you were talking about, it's basically I could use kind of private intents to get privacy on a specific transaction. And I'm only at risk of some sort of, you know, bug, major failure in Aztec for a brief moment of time, that would be different than storing my value on Aztec. So that's kind of a nice way to start and gives me the privacy effectively I'm looking for as a DeFi user without risking it all inside of an early network like Aztec.
Am I understanding that correctly? Yeah, that's exactly what I was going to say is that because we don't have these pools of capital being built on day one, those kind of early users who are kind of bridging funds through and the assets manned up on base or somewhere else as a result once they're out of Aztec again, they're kind of not, they're not at risk. And so you're only at risk for that period whilst assets are in flight. The other interesting side as well, which we haven't talked about yet, is that for private smart contracts, you can't see the funds that are inside them. So the attack surface of a fully private smart contract is actually reduced compared to a public smart contract because it's fully private smart contractor.
That would be something that was built natively on inside of Aztec using your VM, your programming language. Yes. Yeah, correct. So there's kind of two types of applications that are quite safe at Alpha. There's kind of fully private applications where the source of value is either native to Aztec or it's off chain value or kind of these inflight kind of privacy requests, like bridging bridging kind of privacy to other altos. The only thing that's kind of very risky in the early stages is like large public balances inside Aztec because those could be attack services. So I think the attacker doesn't know how much is in any of these things, right?
So they don't know to prioritize one versus the other would be much more difficult for them to tell. If there was a bug, they could potentially do this on lots of private smart contracts, but the key thing about Aztec native assets or off chain assets is that if the source of truth is off chain, then it's a bit like the USDC kind of situation with Ethereum. Like if there was a bug on Ethereum, USDC can kind of choose where the funds are. And so it's only kind of assets that are Ethereum backed that are very susceptible to kind of bugs in the early days. So there's ways to also work around this is kind of where I was trying to get with this.
And I think for the basic DeFi use cases as well, you should be able to use this for kind of smaller medium, kind of like DeFi transactions, payment is a great use case like the age-old, hey, we've been to DevConnect and I want to pay you for dinner. We can suddenly start to do that without leaking my entire wallet history to have one who's incredible. So those ones I think we should be fine with in the early days. Ethereum's layer two universe is exploding with choices. But if you're looking for the best place to park and move your tokens, make your next stop Unichain. First, liquidity. Unichain hosts the most liquid Uniswap V4 deployment on any layer two, giving you deeper pools for flagship pairs like ETH USDC.
More liquidity means better prices, less slippage, and smoother swaps, exactly what traders crave. The numbers back it up. Unichain leads all layer twos in total value locked for Uniswap V4. And it's not just a deep, it's fast and fully transparent, purpose-built to be the home base for DeFi and cross-chain liquidity. When it comes to costs, Unichain is a no-brainer. Transaction fees come in about 95% cheaper than Ethereum maintenance, slashing the price of creating or accessing liquidity. Want to stay in the loop on Unichain? Visit Unichain.org or follow at Unichain on X for all the updates.
Imagine a world where traditional finance meets the power of blockchain seamlessly. That's what mantle is pioneering, with blockchain for banking, a revolutionary new category at the intersection of Trad5 and Web3. At the heart is you are, the world's first money app built fully on chain. It gives you a Swiss iBand account blending fiat currencies like the Euro, the Swiss Fronk, the United States dollar or the Remembee, with crypto, all in one place. Enjoy real world usability and blockchain's trust and programmability. Transactions post directly to the blockchain compatible with Trad5 Rails and packed with integrated DeFi features.
You are Transforms mantle network into the ultimate platform for on-chain financial services, unifying payments, trading and assets like the MI4, the MEs protocol, and functions FBTC. Packed by developer grants, ecosystem incentives, and top distribution through the UR app, reward stations, and buy-bit launch pool. For M&T holders, every economic activity in UR drives value back to you, embodying the entire stack and future growth of this super app ecosystem. Follow mantle on X at mantle underscore official for the latest updates on blockchain for banking. That's x.com slash mantle underscore official.
Crypto is risky, your sleep shouldn't be, eight sleep submission is simple, better sleep through cutting edge technology. Their new pod 5 is a smart mattress cover that fits on the top of your bed. It automatically adjusts the temperature on each side so you and your partner can both sleep the way that you like. It's clinically proven to give you up to one extra hour of quality sleep per night. Eight sleeps pod 5 uses AI to learn your sleep patterns, regulate temperature, reduce snoring, and track key health metrics like HRV and breathing. With a new full body temperature regulating blanket and built-in speaker is the most complete sleep upgrade yet.
Great year sleep and recovery with a sleep use code bankless at eight sleep dot com slash bankless to get up to $400 off the pod five ultra during their holiday sale. That's eight sleep dot com slash bankless. You also get 30 days to try it risk free link in the show notes for more information. Other stats on the roll up itself. So this is, it's using ZK for privacy, but it's also a ZK roll up as well. So it's using, it's not an optimistic roll up, so it's all ZK proofs correct? Yeah, correct. So we actually ever use this transaction as kind of a ZK proof. Our contracts can have private and public components, developers get to choose.
The public component has its own kind of ZKVM and then those are all aggregated up into one single proof that's submitted on Ethereum and once that proofs verified, we get kind of the economic and kind of censorship properties of Ethereum for all of the Aztec transactions that were inside that. So yeah, we're full, full L2, we inherit all the properties from Ethereum and that's one of the main reasons we were on Ethereum is that kind of consensus and also the kind of capital and developers that I did in Britain. So with our Ethereum aligned here on the Aztec side, in order to provide the privacy blanket for all of Ethereum, of course, you're going to have to support some throughput.
Some of these later too are getting pretty high in terms of the amount of transactions per second that is available in those ecosystems. Let's sort of throughput, can the Aztec ignition chain support, are you in the hundreds of transactions per second? Not yet. So this is one thing where things are going to get much better at a time quite quickly because our focus right now is on launching and on security. So we're not at 100 TPS yet, but there's no fundamental reason why we can't scale to that with engineering improvements alone inside the network. I think beyond 100 to getting to thousands of TPS that will be challenging as an L2 because privacy does increase coordination costs because the data that you're broadcasting is now encrypted, which means it's more of it.
The transactions has their own proofs, which need to be verified, which makes peer-to-peer coordination a little bit harder. So we're never going to get thousands of TPS on the L2, but this is where the Aztec stack comes in, which is something that we are going to be developing with gusto, a slow launch, basically because our network, because of our private state model, if you have a block that just has private transactions, because we're a hybrid system, so you can have private and public stuff, but if you just have private transactions, that block can be commuted with massive parallelism because you don't have any race conditions, you don't have multiple transactions modifying the same state, and so in theory, you can process this block extraordinarily quickly, particularly if you get rid of the overheads of sequence of coordination of data availability and posting to blobs, and so it's something we're going to be doing because effectively building out an application-specific rollup stack.
So if you are building an app where you have some trust assumptions, like let's say you're doing micro payments or you know, agentec, AI payment systems where, you know, the values are very small, you saw more privacy, but you're willing to trust a central assigment, so you're willing to let somebody handle data as a third party. The idea is that you can build your application with Aztec's tooling, but when you deploy, you don't deploy to Aztec, you deploy to some, you know, locally hosted entity as an effective in L3, and then you post your, you settle your rollup blocks onto Aztec, and so you kind of get the best of all worlds, you know, you get full privacy, you get very fast transactions, very fast transactions, but also you can get private on and off-boarding into your network via the Aztec L2, which if you need privacy, you probably care about, and so that's our plan for tackling the very high throughput application use case.
So will that be the main constraint? Let's say this is maximally successful, right? So 12 months from now, there is that button inside of my favorite crypto wallet to send this transaction or execute this trade with privacy, and it uses Aztec, right? I imagine that that could be very popular if this is across all of Ethereum, and if transactions per second are not yet in the measured in the hundreds, there could be some congestion there. And as we've seen on other chains, congestion, of course, increases fees. I imagine maybe a similar thing would happen with Aztec where, okay, if it's $10 transaction over dinner, I don't necessarily want to care about paying a dollar to Aztec for privacy of this transaction, but if it's $10,000, maybe that matters a lot more to me, and I'm willing to pay a few dollars, and so my transaction goes through because I'm willing to pay more fees.
But this would be a similar situation that Ethereum has found itself in, which is it's kind of a victim of its own success, and what it has to do is scale. Is that similar to how you expect things to play out on Aztec in a success type of scenario? It's exactly the same. So on the fee model we've implemented, it's the same, the IP 1559. So the base fee will increase once we get above a certain kind of congestion limit for each block, and under the token is burned as a result to try and regulate supply and demand of Aztec transactions, but if it turns out the 50% of all of L2 users want privacy on their transactions, then we need to be more expensive.
That's kind of, I think, is a good problem to have, and we'll be able to scale that in different ways as we start to kind of address that, I think, right now I think actual, it's unclear how much of the L2 transaction volume is real transactions versus kind of just random transactions. So I think we could also see Aztec as a proxy for where are the real users on Ethereum actually transacting, like doing things that require privacy. And so, yeah, I think we could run into that limit, but I think it's probably more than we think it is right now. Right. So that limit could be, this could be just high value privacy transactions or the thing that goes through Aztec.
So Aztec layer two as well, it's not EVM, correct? It's something that you guys have developed from the ground up. So maybe I talk about that for a moment. It's not as simple as if I was to take sort of existing AVE code on the EVM. I wouldn't be able to redeploy that as a smart contract developer. I'd have to rewrite this in R, is that the programming language effectively, can you talk about the VM? So you're right, you would have to rewrite it in R, and so this kind of it, this very much influences who we're targeting as our first users, developers of the platform, basically people who are building up the cases that need privacy because the thing about privacy is that the model for programming, a blockchain changes radically because you have private states and encrypted information that you need to work with, and you need to be sensitive about what gets broadcast, what doesn't get broadcast.
And so the metal model is already slightly shifted, and so I don't believe that requiring to learn any language is actually that much of an additional barrier to inertia because it's rust like it's pretty as very easy to use. And a system metal model of like, oh, it's private now requires a bit of thinking about. So with Aztec, the full private parts of like transactions, we don't actually have a VM at all. What happens instead is that your program that you're writing in August directly converted into a zero-in-allage circuit, and then that gets, and then that gets like, when you're executing a transaction, right, like your smart contract address is derived from that circuit verification key.
And so yeah, you don't actually need a VM for the private stuff. That's a choice you made to maximize speed and efficiency, because these proofs that contain all the sensitive data, you need to make them look for your new device. So we're talking about potato hardware here, and VMs add overheads that we didn't want to pay. So yeah, so it's a very different design architecture to other altos. Well, what are some of these totally private native applications that you guys are working with at launch? Of course, the big value proposition for everyone listening who uses crypto and uses Ethereum and uses DeFi is Aztec is through kind of private intents, potentially able to provide privacy for all of your transactions, everything you do.
And then also there will be some Aztec native applications that you're talking about that are just full stack privacy. What types of things can you imagine here? And what types of things are maybe people working on? The mental model I have is what we have on public Ethereum was designed in a pure public execution environment. And when you add privacy, you get a much larger and very different design space. And so the types of applications we're seeing that require privacy, they can't exist on other chains. So they look a bit different, perhaps what you see on Ethereum or other altos, because it's just not possible to make them there.
So the ones I'm most excited about are both in the trading side, so dockholes and OTC desks. Those are kind of types of like dexes that if you were to build a dex that requires privacy, you may not be able to construct market maker like UD swap. Like that's a fantastic mechanism for a public kind of execution environment. But if you have kind of complete privacy, you can do things very differently. And OTC desks and kind of traditional financial kind of auto book style exchanges work very well in that context. So we have a few teams building different types of decentralized exchanges where if you're hiding the participants of your trade or you're hiding kind of the total flow going in out of exchange or just recreating kind of OTC desks, that's one area.
Underclass tries lending and consumer finances. So when I'm most excited about though, I think for a long time on Ethereum, we haven't had proper consumer finance. Some teams have tried this, but it hasn't really taken off because what I can do in most Western financial ecosystems is get alone based on who I am. The inflows and outflows of my bank account. And in order to do that on Ethereum, I have to put that information onto the blockchain. As Zach was saying earlier, that's a credential. Like I want to be able to create a credential, which says, my income is above 5K, my outgoing below 2K, and I have a certain credit worthiness.
And you can start to do that on Aztec by feeding kind of bank statements into a zero knowledge proof, proving information about them. And then as a result, you can do underclass drives lending, like a loan based on me being Joe, not alone based on me overclassurizing, eat into a CDP like we get with kind of traditional defy. So it's just a different mental model. And I think one that's more centered on around even information asymmetries or kind of identity being a core part of the transaction. So those are the two I'm most excited about. There's also a lot of games being built as well, which everybody is exciting.
Part of the power of the CK technology as well as as we were talking about in the ZK passport use case earlier is the ability for me to selectively disclose some of my information, and this could come into play with financial transactions as well. So I'd imagine if I did do that trade from ETH to USDC, and years later, let's say, the IRS and I had some dispute that said, you know, I had different numbers than what I was declaring maybe in my income statement. Be very nice for me to be able to say, nope, I have ZK proof, so I can selectively disclose that this was the trade amount on this date.
You could see I'm right, IRS. Is that ability exist within the Aztec ecosystem? Can I disclose things for compliance reasons or to third parties for whatever reason? Is that fairly easy? It's possible. We still need to get build out tooling to make it easy, but it's possible. And the intention is to, okay, there's no reason why it shouldn't be easy. The hard part is then the area, getting the IRS to go, oh yes, I accept this proof and not saying, what is this random junk you've given me? I don't care about this. I need a balance sheet. So that's fair. It's going to be the real battle, because you can do so much better than the existing financial system with blockchains, with privacy, where you can basically do preemptive compliance.
So normally the way the financial work works is you want to do transaction, you perform your transaction and then you gather up all your paperwork to say, oh yes, I'm not a terrorist. I'm an architect. And then you send it off to the, after the radio. And that is terrible model, it doesn't work because it does like that. There's loads of innocent activity happening in the real world. And on chain, you can do things much better. You can say, by definition, the only way this transaction can be executed is if me and my counterparty are following the rules are compliant, you know, ZK passports or whatever, but using ZK proofs.
The problem is that we don't live in a world where that's actually accepted as being valid regulation. The regulator will be like, no, I want to see everything. I don't care about these proofs. So we've got to get that to change. But building applications and demonstrating this tech works is step one. To slightly circle about, like, run you asked earlier about like an example transaction show over how this works. And I'd like to just to highlight one because you know, this podcast is called bankless, right? So let's talk about how a debank might work on as tech. So let's say there is a, there is an organization that is putting say, I don't know, like mortgages or equities or some kind of real asset, they're putting it on chain and issuing, issuing like liquid tokens that are being traded in a, in a dark pull on as tech.
And I want to use my debank app to buy some, I have some private USTC and I want to buy it. So what would happen on chain, right, is the entry part would be my account contract. And because we have account abstraction, this account contract, instead of having a public private key and checking, checking a signature, it could say, check the Google authorization flow. So basically I'm signing in with my Google account. And you know, Google gets a request that you want to log on, which is a slight centralization factor. But nobody on chain looking at your transaction can see that you got this account as a Google account.
Once that happens, your transaction gets forwarded to the dark pull contract, which will then trigger trades between your USTC contract and this, let's say, this like real asset contract. And then that real asset contract will say, well, hmm, who's this person, are they allowed to hold this asset? Like, they need to, they need to prove they're American, for example. So then that contract would make a call out to an identity contract like CK Passports which would just say, hey, does this person have an NFT that gets issued if they have a USDK pass or proof? And then you'd be like, yep, they do.
That gets returned all back to the dark, well, they're well, then call that triggers the token contracts, the trade, you lose your USTC, you gain your real asset token and then the transaction ends. And that is all an atomic singular transaction, further use it, right, where the proof separately is being generated client-side and just executed in one shot. And sorry for rambling, but the one last thing is, what does an observacy looking at the blockchain? What do they see from all this? They don't know who you are. They don't know the smart contracts you're interacting with and they don't know what data you've modified.
So they see absolutely nothing. Very cool. Zach, since you were talking about kind of regulators in this being actually in many ways, an improvement from the existing system of regulation, both for users, but potentially for compliance officials and regulators as well. We talk about this for a minute. They don't yet understand privacy and crypto, okay? And there have been many cases that we've seen recently, you guys were referring to the tornado cash developers, there's some privacy devs in the Bitcoin community who are actually facing prison time. I know it's a different model, completely different sort of thing that we're doing here, but even tornado cash.
I mean, there's intense regulatory scrutiny at the nation state level for anything involving privacy and financial transactions. How about you guys? Are you concerned about this? I mean, is there a level of like, we live in fear that regulators and the nation states might not understand what we're trying to do here and might persecute us, prosecute us in some way. And we ever considered like giving up this project as a result of that. I just, from my perspective, I do not yet see any bright lines and maybe you guys do, but it feels like nation states are very much trying to figure this out and even those that bend in the direction of freedom and, you know, civil liberties may make mistakes on the way to getting there and it could be catastrophic for crypto privacy developers involved.
How do you guys think about that? I think like the bright lines we have is that privacy on blockchain should be the same as privacy on the internet. We take that for granted today, but that was a battle that was fought on one by, in the last privacy wars, around SSL and net scape of kind of pioneers in that regard, like getting the privacy, we enjoy the powers most of the internet was not just kind of walking the bark exercise, it was something that was fought for and one and so I think as a result, we now can enjoy car payments of the internet, like accounts have passwords, most of the internet under the hood is powered by a form of encryption under SSL certificates.
So I view it very similarly to kind of that debate and there's always going to be push and pull with regulators. I think the reason why things got kind of dicey and kind of people were kind of prosecuted when we first had this technology is because we had a very weak form of it. We had a very small sprinkling of privacy. All we could do was encrypt a balance and basically hide it from the world. And that in its own is actually quite dangerous because you can't do the important thing which is tie your identity to that cryptocurrency account. So I think now that we've got to kind of like hopefully a higher degree of functionality, we've kind of gone to like hopefully a local minimum or maximum in terms of what you can do.
I think it's actually more useful to be able to convince regulators that this is actually a force for good, not a lot of force for bad and teams like Zheepar Sport can help convince them. Ultimately it's going to be up to application developers though some apps will require very strong degrees of compliance and regulation based on what they're building and others may not. Like if you're building low value game that's just kind of no cryptocurrencies, like you need a very different compliance tool chain than if you're kind of trading kind of equities on on a public blockchain. And so the goal with Aztec is just to make a kind of neutral infrastructure layer that powers all those use cases and gives developers the tooling they need to make those decisions.
So I think that making it be neutral and going to not compromising on on that fact that we don't control the network is hopefully how we win because it means that the the next is point is on the application developer, not the network. And I think that's how Ethereum survived all these years as well with teams like tornado cash like Ethereum was on the target, it was it was the application. Well, that yes, but also we want to make sure that you know application developers can can build in the tools and resources to protect themselves, you know, ultimately, yeah, yeah. So to directly answer your question, are you asked, basically, am I worried that regulators weren't understand technology were building a come-off choice?
And also that does know I'm actually worried that regulators do understand what we're building and they come after us because I think the last few years have shown us something as that regulators can often act in extraordinary bad faith that you have the desired mandate of a regulator, which is to protect consumers, which is very legitimate, and then you have the de facto mandate of the regulator, which is in my opinion to protect incumbent economic and financial elites. And this is why the Gensurism was so hostile to crypto, it's because of the threat. I mean, you can even see with the genius act right where banks were doing that absolute damnedest to try and make that stable coins unable to pass on treasury yields to the stable coin holders, and they're absolutely incensed that products that achieve the same outcome are being developed.
If asset succeeds, you know, it's creating a network where the barriers to entry for providing financial services crush through the floor, you know, you no longer need these giant information notes, enormous pools of capital access to elite networks of knowledge and privilege. Instead, you can build these decentralized financial systems on Aztec that compete directly with the centralized versions where you can get your equity from the blockchain networking. You can get your market from the blockchain network. You get distribution basically without having to counter to financial elites. And I think it was a class where they're not going to like it and they're going to dress up their concerns that were in the language of privacy and safety when in reality, what they're upset about is that they're losing money.
That's my concern. Are you guys prepared? So if that concern is, you know, strong enough, I mean, I think there's, it's a scary time for open source privacy developers. I mean, does that ever keep you up at night back? It makes me more angry than scared to be honest. I think that's, you know, we're doing, we have unfortunately, we have a lot of precedents we can observe to guide our actions very unfortunately. So I think that, you know, we are, like, it is going to be a very, very tough battle for anybody to come after Aztec because we're doing everything right. And, you know, you get some really dark precedents set.
If some, some judge wants to claim that there's no legitimate use case to something like Aztec, you can very, very easily extend that to saying there's no legitimate use case for the internet. I'm not worried, personally, you know, I just think that this is, I said this years ago that this is going to be a long grinding battle of attrition. Where there's too much value on the table to destroy this technology, to destroy blockchain, to destroy privacy, there's too much value on the table. And the first, like, trusted environment that actually embraces us is going to, is going to generate so much advanced economic advantage that the others will have to fall, all the other jurisdictions will have to fall in the night.
And so there's this basically because it's gold and goose, lean golden eggs on the table at that, and components will try to destroy, but it only takes one of them to pick it up and go, actually, I'm going to, I'm going to, I'm going to start using this for myself and make mine myself and everybody else will have to fall in line. And the question is, what is the conventional damage going to be until that happens? Our job is to make sure that both ourselves, the network and our networks, users and builders stay out of it. We'll see how successful we are over the next five years. Completely agree, well said and well done.
As we maybe draw this to a close, I'm sort of interested in a lot of things about the Aztec journey, but one of the things that intrigues me the most is how long you guys have been doing this. So this has been really an endurance race. And I think we're in a world right now in crypto that feels somewhat jaded by short termists. Like it's kind of like where have all the cypher punks gone, right? I thought this thing was about rebuilding something new. In fact, you are an ex-particle physicist, I believe, Joe. You were a primarily a material scientist, right? So you got into crypto, I think, from other fields for a reason.
You've been working on this project for seven to eight years on Aztec. And we haven't gotten into all the commuters of the tech stack, but there's so much here that is net new and huge advances in the area of cryptography and ZK in particular that I know you guys have built yourselves. But this has been almost a decade's long journey already. And we're just getting to the starting line now with the Aztec ignition chain. I guess my question to both of you is like, what's kept you going? And like what keeps you here now? Maybe Zach, you first. The thing is, honestly, what else is there? What else is there?
Like if I left the space to pivot into some random piece of junk that I didn't believe in, then it's like, what's it all for? This product is, I drive a lot of meaning of purpose for this project because I can see, I can see a world that could exist that needs to be pulled into reality. And I feel like we're so close and we've been so close for years. And why would I give up? Is it to do what? Like what else would I do? This is the opportunity of a lifetime. I wouldn't trade it for anything. Yeah. So I see it's door-dye. Door-dye. Yeah. I think about it similarly, but it's definitely as well.
I mean, I kind of viewed as like the promise of this technology, like bringing the world on chain without strong privacy is something that terrifies me. And I think we have a real chance at preventing that future, like this dystopia where, you know, an MEV bot or some kind of AI agent knows what you're about to do before you've done it because they've seen all your future previous transactions and they can just predict every move. Like if we're going to try and like, meaningfully try and onboard like all of the unbanked people in the world to use crypto rails and we're going to take away something we enjoy in the Western world, which is basic privacy, like I can't see your bank account, like when I go to a shop and pay for something, they can't see how much money I have or like what I did last week, I think if we're going to, if we're going to do that and that's the world we're trying to kind of kind of put into existence here and we do it without privacy, like what are we doing?
And I feel like compelled to protect that and try and kind of protect the people who are ultimately going to be users of those chains who may not know the difference in the short term, but we'll have their data kind of extracted in mind if something like Aztec doesn't exist. So I think it's more kind of this, there's a lot of scope to have a lot of impact with this project, but also I think I feel compelled to kind of try and do something about that because too many projects just put their users data on chain and we'll see in 5, 10 years when it's all over it up, what the effects of that are.
And I think that's just not a world I really want to see exist, so that's what keeps me going. So privacy is actually a scary proposition and we certainly wish you well. There are many ways to get involved with this project. One of the ways right now is there's, I believe, a token sale going on if people want to actually participate in that, I get involved in the network. They can also use those tokens to become sequencers. As we draw this to a close, can you talk about how that works effectively? So let's say I want to learn a bit more about this. Maybe I want to participate in the token sale.
Maybe I want to, I don't run some infrastructure, become a sequencer. What do I do, Joe? Yeah, so we looked at the ways to kind of bootstruck this network and not many of them kind of were shipped for purpose. So we ended up partnering with Uniswap on a new kind of distribution auction model. It's called a continuous clearing auction and it's designed to kind of prioritize fair access to kind of token sales. Like historically with token sales, they can be sniped by whales or the price discovery doesn't really exist. So Uniswap and us have built this new type of auction that prioritizes fair access and it will, at the end of the auction, kind of find a fair price for the asset token.
It creates a Uniswap V4 pool at that fair price and everything's on chain, fully transparent. Funnatherian tokens. The tokens are an Ethereum layer one, okay. Yeah, it's a YC20 on Ethereum. The mainnet, the allocations, everything happens in smart contracts on the Ethereum mainnet. So you just have to head to our website to take part. You can either do ZK Passport, proof to prove you're not on a sanctions list or traditional kind of KYC. And then you can send your eth to a smart contract and place a bid as a result. Once the auction's over, you'll go to claim your tokens out out of those smart contracts and you can then stake them.
You'll need 200,000 tokens to stake. If you don't receive that many, you can still participate in governance on the network and kind of vote for changes. But yeah, you need 200,000 tokens to stake. You can either do that yourself on kind of a home-staking machine, the Harbour requirements are fairly easy on consumer hardware or you can delegate to some of the existing kind of lists of stakers. We have about 200 genesis kind of entities who accept kind of deposits from other individuals and so you can stake that way as well, much like Ethereum staking works. You can either do it yourself or you can kind of delegate to a third party.
And so yeah, it's all running on a Ethereum mainnet and the goal is to really distribute ownership of the network and governance to the community. And as a result, kind of, yeah, we're doing this token cell. And one of the other interesting things to note is that the liquidity for the token cell is put into a universal view for pool and the community actually gets to decide when TGE occurs. So the core team, everyone, has a lock up with the community tokens that are purchased in the cell. We'll be the only tokens that are 100% unlocked at TGE and the community gets to vote on that. And so it's kind of doing things the right way, decentralized governance, on a Ethereum mainnet.
So it's been a lot of work, but it's been really cool to partner with one of the original DeFi protocols you need to opt to make a new way of doing token distributions because we don't think the whole adrop meta was fit for launching a decentralized network, especially when people need skin in the game to state and run notes. And Joe, I can run these notes from home. I can run a Aztec sequencer from home. Yeah, you've got a dat mode. They're kind of, as a package on the dat mode app store, you can run it alongside your Ethereum Validator, which is kind of a great way to do it. So, I got to tell you guys, you know what?
And just when I was getting jaded and crypto again, this is the most crypto native project I've seen probably in years. You guys are doing this bottom to top, and I give you a lot of credit for this, like new territory, new frontiers, just about every particular area, layer two, privacy, even the ICO and distribution. This is really a unique project. So I'm hoping the best for it and very excited about the launch and then getting finally to, I guess. So this is sort of a beacon chain type of mainnet. And then what are you calling the main ignition mainnet? Is that actual mainnet? It's going to go to Alpha and then once we've run that with the kind of security and uptime requirements, Zach was talking about earlier, so hopefully three months in.
We'll call it up later. A bit like Cal. And that was still in beta. Okay. Well done. Thanks a lot for spending the time with us today. This has been absolutely fantastic, Zach and Joe, we're looking for big things. Thank you very much. Thanks for having us on, it's been a pleasure. Yeah. Thanks again. We'll see you in five years. Yeah. Oh my God. Hopefully next year, I heard a promise earlier, Joe, gotta let you know, bankless listeners, of course, none of this has been financial advice. You know, crypto is risky, so it's a frontier of privacy. You could lose what you put in, but we are headed 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.