Urbit-native Blockchain

**A** (0:04): All right, thank you guys for coming. I'm going to be giving a talk today about imagining an Urbit native blockchain. And you know, when I talk about this, I mean like really urban native, really focused, you know, I think there's a lot of talks around like going on about like, you know, how do we bring knock to like more places and stuff. But like what we're talking about here is like really like something that's like Urbit native owned by the stakeholders of urbit, which is the current address space holders. How do we expand the utility of address space to do more? So yeah, my name is Sonny Agrawal. A little bit about me really quickly. I've been in crypto since about 2015. My claim to fame is I've helped build a blockchain stack called Cosmos and then particularly worked on it. I worked today on a decentralized exchange called Osmosis using that stack. But more generally I'm just a explorer of blockchains. You know, I think crypto tribalism is good because different cultures breed different types of experiments and you know, I like to be like the informational bridge between these different communities. I've given talks at Bitcoin conference and Bitcoin Cash conferences, Ethereum conferences, Theorem Classic conferences, Ripple conferences, Dogecoin conferences. Right. I think there's always good ideas to learn from everywhere and act as this informational bridge between them. So today I'm here to talk a little bit about URBIT and some ideas I think we can bring from other ecosystems into URBIT to improve what we're building here today. So I'm an Urbit enthusiast. I was good friends with Keaton Dunsford if anyone remembers him. He was pretty involved in the community early days so he went to Berkeley together. He tried to show me on urbit. I didn't get it until like 2020 I think. Yeah, I think I, at some point it just clicked. Everything just clicked to me and I think I somehow figured out how to explain I understood URBIT in context of blockchains and then you know, not to be too haughty, I think I'm one of the best explainers of URBIT to blockchain people you just have to put it in context of what Ethereum did to bitcoin. Urbit does to like past DAG based social networks like Secure Scuttlebutt and then it suddenly all clicks. But sorry. So speaking of like, you know, the relationship between URBIT and blockchains, you know, historically Urbit has been like very. My clicker is not working very well. Okay. So historically Urbit's been very like not very pro blockchain. Back in the day they were like, oh, you know, why do we need a blockchain? We're just going to store all this stuff on GitHub, right. And that GitHub file is going to be the source of truth. And, you know, eventually. Now I think Urbit's like a little bit more open to it right now. Okay. Azimuth now exists on Ethereum and but you know, it's still. Urbit's not a blockchain project. Right. It's using the blockchain to accomplish specific things. You know, I think the goal is that we need to move. Is there something I can do about the clicker? Okay. You know, I think we can move towards a world where, you know, I think a blockchain can be a core part of what URBIT really is. So why does Urbit need a blockchain? Thank you. Cool. So, you know, obviously there's the use case today, which is Azimuth. Right. You want a identity system and namespace needs some sort of global shared state. Right. And that's why we eventually moved Azimuth onto Ethereum and then eventually onto its own L2. Not really. But you know, there's other applications other than a namespace that need shared state. Right. Like imagine you had a poker game going with friends. If that poker game is hosted on one person's ship and that ship goes offline, now the entire poker game is like broken. You want places for shared state and communication to happen and that's persistent, not on any one person's state ship. So we actually ran into this issue right now where, you know, you also can use a blockchain as a global coordination and discovery layer. We have a version of Osmosis front end hosted on URBIT right now, but it's on AJ's ship right now, which is, I believe down. So you can't actually access it right now. Right. And you can't even like access this thing. And so having a global discovery layer and a shared state is very important. And then you want to be able to interact with the digital economy. You know, Urbit, we're building this like identity and social layer, but at the end of the day, you know, your social life is inextricably linked to your economic life. And you want a way for Urbit, your ship, to interact with the digital economy that is growing on the rest the wider blockchain ecosystem today. So to do that, you kind of want a way for your Urbit chips to interact natively with blockchains. So. But why does URBIT need its own own blockchain, right? What's wrong with using an existing blockchain today, like Ethereum or something like that? So one is you can use your URBIT identity at the base layer. You know, you go out to the guide on how to receive an URBIT planet. The first step is to go get an Ethereum address, right? That's like not, you know, you're baking your onboarding flow into someone else's identity system instead. With a custom blockchain, your Urbit IDs can be the base account system of the blockchain. You can use the NOC vm, right? Other people's. There's a lot of projects today now working on building NOC VMs as blockchain. So you want to be able to treat the blockchain itself as just another ship. The way your personal ship will talk to the blockchain. You could treat it like a comet, right? But it's a decentralized comet that you're just talking about. Your ship is talking to it. You can tap into the zeitgeist. You know, blockchain developers are growing and you know, obviously our goal here is we want to be increasing the number of developers building urban applications, learning who and you know, fact of the matter is that, you know, there's a lot of hype today around people getting interested in learning blockchains, blockchain development, especially for new ecosystems. By allowing Hoon development to not just happen for urban dapps, but also for blockchain dapps, we can increase the amount of people learning and using Hoon as a development environment and culture and sovereignty, right? This is something that's actually very important to us at Cosmos, where every blockchain today, you know, we like to think of blockchains as apolitical systems, but they are not, right? Every blockchain has its own community and culture associated with it and, and all of these cultures have different values, right? Like, you know, and Ethereum is not an apolitical thing. And I would go so far as to argue that like part of the reason I don't work on. I didn't. I chose not to work on Ethereum and chose to work on Cosmos instead was I thought I did not agree with the fundamental philosophies of Ethereum. I think Ethereum is a fundamentally globalist technology building a world computer, which is, I think, at odds with what we believe at Cosmos, which is an idea ideology of localism and sovereignty, and which I believe is much more attuned with the beliefs of urban as well. So I think making sure that the technology that you build upon reflects the cultural values of the community is important. And then finally, you don't want to leak your value. So culture has economic value. We see this through the NFT boom that happened where culture is economic value. And by putting your community's cultural imprints on someone else's blockchain, you're basically leaking all that value that is actually economic activity and value that could be captured in your own internal economy. And so by having your own blockchain, you can build ways of doing that. So if we want to build a blockchain, great, why don't we just go do it, right? It's not that hard. People are building blockchains all the time. URBIT has one unique challenge to it, which makes it different than other things. There's no URBIT token, right? And this is actually a little bit of a challenge, right? Because today almost all blockchain designs are extremely token centric for security. They assume that proof of stake, it's some sort of token system, right? You have some staking system or even if you're doing proof of work, the incentive models are built such that you use token inflation as the primary way of driving value. And then a big one is fees. Resource pricing uses this gas token model where you have to pay your fee. You pay for usage of the blockchain based off of paying in some fungible token. This all works great, but the problem is that doesn't work for Urbit, right? Because Urbit ownership is framed as NFTs, right? Are you going to pay a planet every time you want to make a transaction? That doesn't make any sense, right? That's not what the urban address space was designed for. So how do we solve this? Well, I mean, just because something's an nft, if you squint, maybe these all look kind of the same. Things can be NFTs can be functionally fungible. Your cache has a serial number. But like, for the purposes of paying each other, they can be fungible. You can have NFTs be like, hey, for the purposes of staking, we can treat all the NFTs as a fungible thing. So people are working on NFT staking protocols and stuff. There's a project in Cosmos called Stargaze. They're working on incorporating NFTs into staking. But the problem is URBIT is even more challenging because it doesn't only have NFTS it actually has three sets of NFTs. Right? There's three classes of NFTs in the urban system. They're called. Oops, that's the old name. They're called galaxies, stars and planets. Right? And the thing with these is there's no formal relationship between them. Right? Once a galaxy is given to the star, a star is issued or a planet is issued from a star, there's no formal relationship on what these things are supposed to do. And so now you get into this, like, who owns what power structures, where in a blockchain, where does economic value go? What is the value of all of these things? And there's almost this weird class conflict that ends up happening between these three systems, these three classes of owners in the urban system. Well, you know, what we have here is a classic mechanism, design problem that we need to solve. And we've been doing this for thousands of years. This is from one of my favorite Twitter threads. It's about how the medieval Europe basically solved the conflict between the clergy, the nobility, and the peasantry and what it did to solve that. So what would this look like in the urban system? Here's my proposal for what an economic system for an Urbit L1 could look like. So let's start with the planets, right? The. They're the quote, unquote, lowest class. They're the peasantry. Right? What they are is the base identity layer of the chain. And what's unique about this URBIT blockchain is that to make any transactions, to have an account at all, you need to own a planet. So now you have civil resistance built into the blockchain. And that is a valuable thing that almost no blockchain has today. And so a planet is just your access ticket to be a of part. A part of this community, be a part of this economic system. Okay. That's very simple. We understand that. Okay. Next one we can do is the galaxies, right? The galaxies is, you know, let's go all the way to the top of the stack. You know, they're the ultimate owners of the system, right? They are the ones who are supposed to govern this thing justly. And I propose that they are the ones who should provide the base infrastructure for the system. Right. In a BFT consensus protocol, you have this concept of validators. If every single galaxy ran a validator, you'd actually have one of the most decentralized blockchains in the world, probably, right? You look at the Nakamoto coefficient, which is the number of entities that control power in a blockchain in ethereum, it's about 14 validators. No, sorry. 21 validators control two thirds of the. Of the voting power in. Is it lower? Okay, Brian's telling me it's lower. So probably maybe like 14 or 15. Yeah. So, you know, if you can. But. Because in this system, we're going to say every galaxy gets an equal slot in the consensus system, you can actually build a far more decentralized Nakamoto coefficient than you see in most blockchains today. And they will get value from. From the MEV revenue. So, you know, you look at blockchains today, transaction fees are going to be negligible over time. Right. You want to build blockchains that are scalable enough that the transaction fees go down. The real value of the economic system is by, like. Of a blockchain is, like, by owning the transaction ordering rights, what we call MEV revenues. And the validator, the galaxies, will earn the economic value from doing this. Cool. So galaxies are great. They are the owners. They're the validators of this blockchain. But now you're stuck with the awkward middle child. Right? What do you do about stars? And this is, I think, something I've talked to people at the Urban foundation about a bunch like, how do we bring value to stars? What do we do with stars? And this is actually the whole problem that medieval society was trying to figure out. How do you do. How do you deal with these, like. How do you deal with these, like, marauding knights that are just, like, pillaging the land? Well, you build an economic system that's, like, designed to incorporate them. And instead of them, like, you know, pillaging the land, you give them the land and ask them to. You ask them to manage the land. Right. I think that the job, you know, having all the galaxy holders be the managers of the block space is not going to, you know, it's gonna be difficult. Let's give this responsibility to the stars owners. So what we're gonna build here is a land model of blockchain block space. And to do this, you know, I mentioned at the beginning, I think you can. You should look to many sources of blockchains as inspiration for how to design systems. And I'm going to lean on a very probably controversial one. But one of the most interesting blockchain systems is eos. Before you laugh, the EOS that was delivered was a pile of garbage. But if you actually go read their original white paper, they had some very interesting concepts there. Probably ahead of its time. We can scroll through the white paper A little bit, yeah. So you know, you come down here, you have like, you know, basically everything we talk about today in account abstractions. They had this kind of concept already sitting in the white paper. Where should I be pointing this? Like there. Oh, okay, I'll do that from now on. Okay. So you come down here, you have like they were talking about parallel execution of blockchains. This is what like aptos and SWE do today. But what we care about here, as you scroll even further down to their token model and resource usage section. So they had a lot of cool concepts about like splitting apart storage and compute and network bandwidth. But the part that I'm really focused on here is this one section down here which is this part. It says here, if an account holds 1% of the total tokens distributable pursuant to that blockchain, then that account has the potential to utilize 1% of, of the state storage capacity. This is very interesting because this is, that worked okay, the EOS token model, right? So you know what they. So if you own 1% of the EOS tokens, you get unrestricted access to 1% of the blockchain storage capacity. Okay. And so what's interesting here is you can use it yourself or you can let others use it, right? So couple ideas of if you're not going to use it yourself. One of the ideas that EOS was going for was they thought app developers would buy the EOS tokens and then let their users use their applications for free. Or you can rent it out, right? You can say, hey, I'm not using this block space, I'm going to rent, charge, charge other people to use my block space. For me this is very different than the gas token blockchain. The gas model of blockchains used today, this gas model is used by Bitcoin, Ethereum and basically almost everything that is live today. And it requires a base token to denominate fees in. And one of the problems here is the gas prices are only non negligible if blocks are full. And this leads to very perverse incentives because it incentivizes the owners of the blockchain, the eth holders, let's say in Ethereum's case to be anti scalability, right? Because if you let your blockchain scale, you're not actually going to capture, you know, the gas fees are not gonna be meaningful. The EIP 1559 burn is gonna go down and it's like the owners of the blockchain are misaligned incentives with the users of the Blockchain who want more scalability. There's also no way of hedging gas price spikes. Right. If you're trying to build an application on top of this thing, you want to provide a steady source of cost, but you have no way of dealing with the fact of, oh, some other NFT just suddenly came up and your gas prices just spiked. It's very difficult to hedge and have long term sustainable cost models for app developers. What we're doing here from a, you know, more economic perspective, like political economic perspective is effectively using a very georgist model of like, of block space here, right? We're effectively saying all block space is publicly is collectively owned by all ETH holders and is constantly up for auction based off of like whoever's paying the most for it. Right. This is a free market model. But the thing is, free markets are fundamentally like opposite of the concepts of private property. Right? Private property is basically saying you own this thing and you have unrestricted access to it. Right? No one else can just come take it from you because they value it more. And my belief is that urbit's philosophy is one of property rights. URBIT is land and land is valuable because you have property rights over it. And let's take this property rights system of URBIT and apply it to a blockchain context. So I'm going to call this star space. So star space basically means for every star you own, you get unrestricted access to 1 65,280th of the blockchain's capacity. Right? Resource capacity. Now we can go into technical details. Are we talking about storage? Are we talking about compute, Are we talking about bandwidth? Okay, for simplicity, we can just talk about storage. Right? Now I think that's actually the simplest. So you get, as the chain grows and the resource capacity of the chain increases, you get your ownership access of that portion of the block space. What's cool is as a start owner, you can do with the block space as you see fit. If you're not going to use it yourself, you can, you can let users of urban apps use it for free and use other forms of Sybil resistance and ddos prevention to deal with that. You could pass through ownership of that block space to your planets. So you might say, hey, I'm not actually going to use the block space of my star, but I'll just let my planets use it for free. That could increase the value of the planets that are under your star. That's one option, what you can do. Or you can charge rental fees, but the Thing is you can charge because it's not the chain that's charging rental fees and has to know how to denominate block. In one native token, I as a star holder might charge rent for my block space in Bitcoin while a different user might charge it in eth, while a different star holder might charge rent in Venmo payments or something like that, or some USD payment. So it leaves it up to the free market. And what's cool here is you know you have different models of let you know, you let the system decide. Oh, another thing you could do is you can also tokenize block space, right and resell them. So what's cool about this is you let this like more free market system evolve of how you like. You know, you let different star holders figure out what's the best economic systems to use for their block space and you let you know the free market will eventually, instead of expecting the EF to figure out the Ethereum foundation to figure out what is the right model for how to do block space, you let this ownership based system and whoever does the best system will end up providing a good political system. Some slightly more details of how this would work. All stars are worth the same amount of block space regardless of how many planets they issue. So if you have a naked star or a full star, they're still worth the same portion of block space. Galaxies are allowed to use the block space for their unissued stars. So if I have a full galaxy, I have access to all that block space. And star space rights exist as a on chain. They're denominated on the blockchain itself and thus they can be interacted with as smart contracts. These are assets, right? The block space, just like land is an asset, block space is an asset. And you can, you know, you could tokenize these on chain if you'd like. You know I have models for how to do that if anyone wants to talk about that. But like you can tokenize these and like resell them. Build financial products around the land rights themselves. Cool. So what we have here is we have this economic system with like three different actors. And what we've effectively built here is, is a properly economic system that actually has one proposal of how we solve the mechanism designed to make sure that this economic flywheel works for all the actors involved. So basically once again these are just high level ideas. There's probably lots of unknowns to uncover here, but if you're an enterprising blockchain mechanism designer, you should be on the edge of Your seat. Because I think this is like one of the most exciting experiments in blockchain innovation. This whole gas token model of block space is like, we've been using it for 13 years since Bitcoin and like, cool. We know it works for some cases, but like, let's like expand our mind and like, is there other stuff we can try? Right? And I think like this is, this is an exciting opportunity to do like a ground up, like rethinking of like what ground zero rethinking of like what blockchain mechanism design could look like. So this is really exciting. Two more things I want to talk about. One, this is just, you know, this stuff is a little bit more speculative, but like, how do you fund this? This is just like an idea of like, you know, we could go like, you know, we can go beg the Urbit foundation right now, like, hey guys, I think this is a great idea, they should do this. But I think there's like some interesting ideas of what you can do. This is actually an idea that was inspired from, by Trent from Holiam. But you can basically say like, hey, at the end of the day, it's galaxies that are benefiting the most from the system, as they're the ones who own and govern the entire system here. Right? So you can go basically raise capital in the form of stars from the galaxies, where you basically say each galaxy needs to buy membership into this blockchain by contributing that say four stars to a development fund. But by buying membership, that's what lets, that's what lets them have a validator slot, participate in the economic flywheel that this is going to create. And it lets their address space actually participate in the network. Right? If a galaxy does not buy membership, all the stars that they have issued don't get block space rights and all the planets underneath them as well don't get to use the chain. So it is in the, you know, in order to like join the system, the galaxies have to contribute to the development fund of the system. And they can do that by contributing a portion of stars. It doesn't have to necessarily be their own stars, it could be another galaxy's stars, but they just have to contribute stars. And you can also do something where you can algorithmically increase the buy in cost over time. So that way you can solve this like free rider problem where it's like, oh, as a galaxy holder, I'm going to wait till this whole thing is developed and then buy my membership. But if you do that, maybe it's going to cost 20 stars by then. So you want to incentivize Galaxy owners to contribute to the funding of this project early on. Lastly, I'm going to talk quickly about the Cosmos SDK, which is a tech stack that I work on and why I think it is actually very well suited to be the base system for how we build build this chain. So first off, what is Cosmos? What is it not? It is not a blockchain, it is not a token. What Cosmos is, is an open source stack, a network and a community. It is an open source stack that makes it very easy to build blockchains, custom blockchains and normally when I explain this, you know, what is Cosmos to like normal people, I usually tell them it's like, think of it like Linux, it's an open source stack, it's a networking system and it's a community. Well, here I think more people might be. It's very similar to urbit, right? It's an open source stack, it's a network and it's a community. But it's really focused. It is a open source stack community focused on building blockchains. It comes with a couple of key components. Comet, bft, Tendermint Consensus is the most battle tested consensus engine that probably exists today. The SDK is a framework that makes it very easy for you to build these custom blockchains and it's used by over 100 blockchains, some of the biggest blockchains in the space. DYDX is the biggest dex in all of crypto. Celestia just launched this week, or is launching this week, my project. I work on osmosis but you have some that we don't like to talk about, like Terra, but you have hundreds of blockchains that are built using this open source stack. Why do people choose to use this stack? Well, a couple things, you know, mainline version is written in Go, which is yes, I know Earth code. Yucky. But what's cool about the Cosmos SDK is everything is extremely modular. So you know, that's a big philosophy of ours is modularity. So you know, we already have people that are like, oh, we don't want to use the Cosmos SDK, we still want to use Tendermint. So we're going to rip out the Cosmos SDK and replace it with something else. Or Celestia is like, oh, we like the consensus and the Cosmos gate, but we don't like the networking stack, we're going to rip out the networking stack and replace it with something else. So the Cosmos framework gives you a stack to Build off of and then we can start to replace Earth code with Mars code as the system evolves. What's really starting with probably the pluggable VMs, right? So in the Cosmos SDK, we already have implementations. We have multiple VMs that run on top of the Cosmos SDK. So we have Cosmwasm, which is a Rust based smart contracting framework that was kind of developed within the Cosmos community. Then we also have the EVM as a framework, as a VM that can run on top of this stack. We have the Solana VM as a frame, as a VM that can run on top of the stack. It was developed by the Injective team and I think we can build a NOC VM as a VM that still runs on top of the stack. So the nice thing is by having a NOC vm, it can still interact with ships directly. The Cosmos SDK was designed to experiment. So you know a lot of block space market experimentation, right? That's the name of the game here. We already do a lot of really cool block space market experiments today. So one of them is fee abstraction. Fee abstraction is the idea that you can pay your transaction fees in any token, in every other blockchain. Today you have to pay fees and eth, and it's just like terrible ux, right? In Osmosis you can pay your transaction fees in Bitcoin, in eth, in Atom, in usdc. You can pay in anything you want, right? So we already do that today. That's a cool block space market experiment that runs in Cosmos. We have this idea of fee credits. We say like, hey, the more you stake on our blockchain, we can actually discount the amount of fees that you have to pay. We do things like top of the block auctions, where what we recognize is that there's really two spots in a blockchain that are valuable. There's either you want to be in a block or you want to be at the front of a block. If you ever go to the amusement park at the roller coaster, you know how there's a separate line to go in the first seat in the roller coaster and the people who really care about that, they can wait in the longer line. This is what we've done in the Cosmos SDK. We basically make it so if you want to be the first transaction in a block because you're trying to do some sort of arbitrage or liquidation or whatever it is you're trying to do, you can pay extra for that opportunity, but not drive up the Gap the cost for everyone else. One of the projects that we're working on is free transactions based off of Privacy Pass. So Privacy Pass is a W3C standard kind of driven a lot by Cloudflare that uses captcha but like authenticatable captcha. So we basically say, hey, if you solve this captcha, we're going to let you make your first five transactions on the osmosis blockchain for free. So that's like really valuable. One of the hiring tasks that we used to do was like tell people was oh, write a module for the Cosmos SDK that you can make free transactions by doing a little bit of proof of work. You can do stuff like that. So well if you want to innovate and experiment with ownership based fee systems, land based systems, the conscious SDK is the place to do block space experimentation. You also have validator sidecars. You can make your validators do more. We do things like make them run price oracles, mempool order books. That's something that DYDX does. You can have them run like VPNs, basically front end servers, bridge nodes off chain computation. So you can do stuff like say like hey, I think that eventually this chain should be where Azimuth is moved onto as well. But while it's still in the prototype stages, I think Azimuth can stay on Ethereum. But what you can have the validators do is run an oracle to Azimuth. And so that way any change that is made on Azimuth and is immediately reflected on this chain as well. And eventually once you're ready to migrate Azimuth, you can actually have the validators of this chain, the galaxies run an Azimuth bridge. Finally, next one is we have this idea of native account abstraction. Your URBIT ID can be your base identity on the chain. So no more hex addresses. You can actually, you know, urban identities will be able to support multiple cryptographic keys and you don't have to separate your Azimuth key from your Ethereum wallet key anymore. Your key for interacting with Azimuth can be your ship key itself. And then you'll be able to, by adding new custom cryptography, you'll be able to make transactions directly from your URBIT ship over Ames talking to the blockchain VM directly. The other thing that the Cosmos stack gives you is this protocol called ibc. It's basically what it is is it's a trustless end to end cryptographically authenticated communication protocol between blockchains to Urbit people. It's Basically aims for blockchains, right? It's like it's an authenticated way of two blockchains talking to each other. No bridges, nothing in between. It's two blockchains are cryptographically verifying each other, verifying each other's messages. And there are implementations for this in multiple blockchain frameworks already. So in the Cosmos SDK was the first one. But now we have IBC implementations for Ethereum for polkadot chain substrate chains, we have implementations for near and more and more blockchains over time. So yeah, back to what is Cosmos, Talk a little bit about the open source stack. As mentioned, it's also a network. It's a network of. This is a picture from I think over a year ago. So I think the number of blockchains in this IBC connected network has probably over doubled since then. But yeah, so by being built on this stack you have this easy interoperability with the rest of the blockchain ecosystem. And one of the ways you can really use this is this concept of interchain accounts. So this is a concept that our team developed years ago. It's basically the idea that an account on one blockchain can make transactions on another blockchain. So today in blockchain world, let's say I have a DAO or something on one blockchain, it can't make transactions on, it can't do a swap on a dex on a different blockchain. Using interchain accounts, it's a standard that we built on top of ibc, you can basically do this sort of like astral projection where your account on one chain is actually able to make transactions on a different chain, having this astrally projecting yourself. So if you have this urbit L1, you have your urbit ID as the base identity system of this chain. You can have that make transactions on Ethereum, you can do a swap on Uniswap directly from your URBIT account, right. Without needing to have a Metamask account or an Ethereum key in the middle here. You can also do the same with Cosmos apps like Osmosis. So this is how we'll have URBIT actually be the like step in to be an identity layer in the actual blockchain ecosystem, wider blockchain ecosystem. So yeah, finally, you know what I mentioned, it's a network and it's a community, right? And I think the community is often one of the most important parts. I think that the Cosmos is a number of different blockchains, right? And they actually all have different cultures, different philosophies. But I think one thing that ties a lot of the cosmos ecosystem together is like these core things as philosophies. A belief in bottom up systems, a belief in sovereignty, a belief in modularity, a belief in experimentation, and a belief in openness. And you know, personally, I feel that these are very in line with a lot of the URBIT philosophies as well, which is why you see such high overlap between cosmonauts and orbiters. Right. So yeah, I think there's a deep philosophical alignment here as well. So hopefully I see that one day this orbit L1 can be part of this larger IBC network as well. So thank you so much, everyone. All right.