There was no problem of administration. There was no giving you rights to sell the car. There was just the easy hand off of an asset as a barer instrument. And the el cap model is fundamentally almost everything is a bearer instrument, and that just means that patterns of change of who's allowed to do what, patterns of exchange, all of those just emerge out of yeah. I give you my cash, you give me my goods. We're done, right? And so they're very intuitive and very, very natural, especially to program, especially to people who have program in object frameworks like react or view or any of these things. Yeah, thanks for thanks for a little bit on the hood here. Maybe we can talk about this. So if you think of that now, you know, as JavaScript as this place to run smart contracts, I mean, today, even though you have so many different blockchains, it doesn't actually seem there's like that many models for doing smart contacts that have gotten traction. You basically have to EVM that has obviously the most traction. And then you have the EVM that's like running on many different chains, you know, Ethereum, avalanche, finance, small chain, et cetera, et cetera, and that dozens of little polygon, like many of them. And then you have I think Solana that has subtraction. Yeah, it's a good traction. You have this magnet, smart contracts. In RAS, you also have them. I think that has quite a bit of usage. Maybe there's not much. So I'm curious how do you see this play out? Do you think they're going JavaScript smart contract model? Will those be relevant for different use cases different areas where we have converge on fewer smart contract standards or will there be an explosion more in the future? So I actually think that there will be, you know, the number we have that we have including JavaScript is about right. If you think about now the programming world of web two, it's 13.9 million JavaScript developers. A bunch of rust developers, a bunch of sea developers and you know, sort of a list of languages, but the models are pretty similar in some cases. So let me pop out of that. The so I think there will be multiple models. The key thing for us is we're primarily focused on bridging to new developers. And new development, these are developers often FinTech developers, they know what's up with money. They heard there's an opportunity they come over and look, they look at salinity and go, that's a weird language, right? And your development environment sucks, and you have no testing tools and I have to use a different tools and I'm gonna go work for my buddy's hedge fund because I can make this much and yeah, whatever. Yeah, yeah. You talk about frothy returns and maybe, you know, but I understand volatility and you know, you can get in the returns you think you're getting some time, right? So you know, these are experts that they come and look and they go, you know, come back to me when you're grown up, right? Because it's just the bar is so low in terms of programmability. And programmability scaling the programmers is the hardest thing to scale. And so our focus is on programmability. Now, when I used the analogy of react a bunch, when react came out, experts were already doing pretty amazing stuff in JavaScript in browsers. And partly due to people that are here at a gore, driving sound software engineering into the JavaScript language, sort of in retrospect with strict mode and promises and proxies and stuff like that. But 6 months after react came out, beginners, new programmers could do more interesting, more responsive, more interactive, easier to internationalize mobile friendly applications better than experts could a year before because they had components and a framework to plug them together. And that literally gives you exponential growth in the effectiveness of programmers because every month there's a month more worth of components that they could slap together. I could grab a slideshow in a payment component and put it together and launch a site. Next month, I can grab a slideshow and interesting alerting compartment that shows me the status of my paintings and a payment component and update my site. Then I can do a vain and component that can handle ACH as well as, you know, I mean, all these kinds of things where I'm just gradually growing. Oh, one better now? Well, now there's a new nav component that does slick cool infinite scrolling for you, you know? I mean, whatever it is, right? And you can plug those together, even if you could not build them yourselves. And that leverage get gave real growth to the expressiveness that less senior programmers that were steeped in the ancient arts of async updating of your screen when models changed. And now suddenly, millions of programmers could do pretty awesome stuff pretty easily. And those experts can focus on really high value components that other people could use. And that's what we're bringing. So it's not just JavaScript, which would make a difference because now you can tap into 10 million plus developers for.