 Mi je Miloš and this is my friend Kuki. We are both part of 327, that's an R&D collective. And our goal is to stay up to date with WebTree technologies. So today we're gonna talk about that. And today we can start with the challenges that we ran into during the last couple of years while researching and building in WebTree. Many times we would go deep into specific ecosystems so that we would miss all the innovations that would happen in the other ecosystems. Secondly, even though when we would like to enter new ecosystems we didn't know where to start. We didn't know what is the current state of the tech or there or where to watch, where to find useful information. And finally, somewhat different situation is when we would go deep into specific technology we would research it, trying to build something with it and then we would realize it's too early for it. It's too early for its adoption. And we would move to something else. However, in the meantime the initial technology would experience some changes and it would become somewhat revolutionary. But we weren't watching it anymore and we would miss the opportunity to innovate and to utilize the fact that we were over there before it was popular. It happened to us many times with AMMs, with DK, et cetera, et cetera. So, to prevent these kinds of situations from happening or at least to decrease its number we decided to create WebTree Tech Reader. That's a tool. And what we actually did is that we mapped as much as possible of WebTree technologies for this first version. We mapped technologies, tools, languages, frameworks, et cetera, et cetera. We divided them into the ecosystem and we visualized and arranged them using the Reader metaphor. But let's see how it really looks in practice. The first thing you're greeted with is a fine choice of different ecosystems. I know we're all huge fans of EVM-based systems but if you want to fool around, I won't tell anyone. So, inside each ecosystem we give some general information about it. This guides us to figure out if that ecosystem is the right fit for the WebTree product that we want to build. We have some basic information here but there is also the full report where we dive deeper into specific of each ecosystems. And then, of course, the highlight for each ecosystem is its technology radar. Like Miloš mentioned, we take all of the technologies we find for a specific ecosystem, we put them into these tiny little blips, and inside of each blip, like, let's say, for solidity we have a brief description of it, a link where you can find more if you're interested, and now our opinion, of course. And so, this is what we end up with. And we wanted to have a better understanding of what's happening. So, like Miloš mentioned, we have different quadrants. So we have platforms, tools, techniques and protocols and languages and frameworks. But, on the other hand, we also have rings. Those tell us how close to mass adoption a certain technology is in the WebTree space. So the highlighted ring that you see, that's for all those new and exciting things that have been popping up on Twitter, but that really haven't been fleshed out. On the other hand, adopt ring is for those things that are indispensable for any WebTree project. And on the border, far away is the hold ring. That's for those things that you probably want to be careful with, or that you should just totally ditch. For example, proof of work. Yay, give it up for the merge. So, of course, some of you may know, this is like inspired by the great folks over at ThoughtWorks. And with this, we at 3327 have a better feel of what's happening in a specific ecosystem. We know what new things are popping up, what things are getting fleshed out and what things are maybe getting deprecated. So we use that to stay in touch, keep up to date without having to scroll on Twitter all day. And it also helps us decide which technologies we might want to use for our next WebTree project. So we'll keep working on it because we use it all the time. But we also want to make it like a community effort, to make it a project that's by the community for the community. If you want to help us, please reach out to us. You can reach us on Twitter and also on the link below. This is something that we want to make a space for having a sense of this crazy and dynamic WebTree world that we're all building together. Just add one more thing that you can go on the link, on the Twitter. You can check over there the current alpha version. And in two weeks we're gonna come up with a new one. What can you plan to update? Is it a quarterly release? Yes, because we want to be thorough with each one. We want to really assess each technology. We want to do it quarterly. That's the general idea. After building here, Dapper, I'm curious how do you... how do you measure what is valuable and how do you measure that value and what gets closer to the center of the circle? So we measure how well-adopted it is. If you think about stuff, we have a huge team of developers inside our team. So we see their experience. It's our subjective opinion, but that's why we want the community to come in and challenge those opinions and to see really, if we all band together, let's really see what is good there and what's something that we might want to skip.