There weren't really any, there was really nothing out there in terms of smart contract chains aside from Ethereum, we didn't know exactly how we would do it on a cerium, that we understood that the cost of storing data on the Ethereum Blockchain was very high, and the transaction fees were quite high as a result. I think we were also still, very early in our journey, we don't, we didn't know what we know. Now, of course, we didn't know how some of the architecture decisions would work out. So a lot has changed since those days. So first of all, the network grew to this enormous size. Which, you know, even for me being the most optimistic about Helium has been a surprise. We've learned a ton about the different kinds of problems and the different sort of modes of problems that arise from the different architectures that we've had, you know, so all the way back to hotspots being full nodes that did all the consensus and, you know, swapped around every now and then to validators to light Hotspot, you know, I think we've gotten a pretty good handle on what the difficult parts to scale are, and what the, you know, which parts are relatively straightforward. You know, then you've got, as I mentioned, sort of, at the start, you've got the availability of other stuff, right, so there's now Solana and polka dot and avalanche and Cardano, and JIRA. And as you know, there's like a million of these things out there now that are all perfectly capable, beyond capable of doing most of what of what Helium needs, if not all of it. And the other part, you know, that I think we've learned is, what really is important to people like that, I think that for at least for me, it was fairly unclear at the start of this journey. But for, you know, token oriented folks, consistency and reliability of proof of coverage, I think, has been a real pain point. Like the the rates of PoC goes up and down. Receipts vanish, no one knows why, you know, this, it's, it's a complicated system that's very, very difficult to debug. And then for users of the network, data reliability is critical. So we built a system called State channels, I think a bunch of you know, that is responsible for packet metering, and making sure that packets get delivered to the other side, and accounted for and that system also quite complicated, quite very novel, very clever way to solve the problem, but very, very complicated. And makes it again, difficult to debug where a packet is failing, you know, is it failing? Because there's RF interference? Is there a problem with the Hotspot? Is there a problem with the packet forwarder on the Hotspot, the problem with the sensor, you know, there's like so many places already that the that the packet could like, not show up from it, adding this little these layers of complexity makes it even harder to debug when something goes wrong. So that's sort of where we, where we sort of came at the problem from is that we've learned a lot, we understand what the problems are, and we understand what people need. So, you know, regardless, I'm just gonna ignore the sort of L1 Swap part for a second, because I know that that seems to get the most attention. The desire was, was really to try and simplify the architecture such that proof of coverage and Data Credit transfers were extremely reliable, right? So there was no ambiguity, for example, how often your Hotspot was supposed to be good, right? We just do that very consistently, like on an hourly time, or something like that. And so, so that reduces another sort of unknown point of the system, which is that you have this very complicated, challenging system today. So we wanted to simplify it all the way down as far as we could. We think the best way to do that, at least for now is to have a single article, that is sort of air quotes of the server that is responsible for