 Hello, everybody. So I'm here. I'm going to speak a little bit about developer communities and how Cowery is trying to drive further developer adoption for the Ethereum ecosystem and the projects within it. And talk about the EF grant that we received and how we've been using that. So current community landscape for crypto projects, as many of you are familiar, consist of developers, users, and thirdly token holders. With few exceptions, the most successful projects today have really strong core developer ecosystems building on top of them. And we can learn a lot from the lessons of Web 2 and apply that to Web 3. We don't need to reinvent the entire playbook. So there you have it. This is how many of us think of our communities. But in many cases, this is what makes a really healthy Web 3 community. And that user group, you want it to expand, to take over, and make all token holders users as well. But really what's important is that core kernel, the developers. So now we're just going to focus on that developer ecosystem and what to do there. And some of these lessons can be learned and applied to user groups in more technical ecosystems. But for now, I'm just going to focus on developers. So one key component is have a technical community manager for technical communities. It's really important that people can get into the code, answer questions, come up with creative demos, really inspire your users, your developers. A lot of times in this ecosystem, we see pre-product people investing in marketing and big pushes. It's way more effective if people can actually get into the code or play around with a test net or an SDK. And the best teams, so this is based off of 30-plus interviews with developer community managers and developer relations, both in Web 2 and Web 3, the best teams are focusing on key metrics and relentlessly iterating, keeping their eye on those key metrics and just making sure that they're getting the engagement and the adoption that they'd like to see. This is a framework which I really like for measuring the impact that you can have on a developer community. It's from Phil Legada of Nexmo. And he has taken the pirate metrics of startups, so R, and then taken it all the way through the product because there's a loop back and a cycle there. And it starts with awareness. So why should I use your platform? What is it? Just knowing that it's out there. Then second acquisition, it's not good enough just to know that it's out there. Like, I need a relationship with user developer. Either it's an NPM install, which is a little bit harder to track with metrics. But you can use email strategies, these types of things, having an engaged platform where people can ask questions, where people can interact with your content, get in touch with you. And what's really important is that this cycle flows all the way down into products. So if your community is not really involved in the decisions that you're making in products and potentially even contributing to the code base, you're missing a big opportunity there. So what does Cowery do? Cowery is really focused on the first couple of areas. So it's awareness for your project and acquisition. So people taking the first step, actually using your technology for the first time. And our main focus is the Ethereum ecosystem and the tools, libraries, and frameworks within the ecosystem. And within our community, there are three main types of users. So there are the readers who are coming to Cowery to learn about how to use this technology or just want to read an interesting article. Contributors, contributors are writers. They are a rare breed. They're hard to come by. But having a really good writer can make a huge difference for your project. And then communities. Communities keep content up to date. They interact with it. They engage with it. They point out gaps. And contributors and communities is an area which we're really focused on. And I'll share a bit more about this in a second. But before I jump into that, this is what Cowery looks like. So this is the homepage. This is for our first user group. This is for readers so that they come in. They know where to go. They can read about topics which are important in the Ethereum ecosystem, getting started, finance, scaling, privacy, these types of things. Then, essentially, an essential component is you need to be good at the single player game. We spend a lot of time catering towards writers so that they can write in, mark down, have content, have clear attribution. So this was written by Hader. He's a full stack dev, loves using Kotlin, and part of the Java community. And he wrote this article about using Web 3.j for user authentication. And then bringing that together is multiple contributors can now contribute to one community. And here, this is the Java Ethereum community. So there are representatives from Consensuses Pegasus team, which were a client in Java called Pantheon, which is now Hyperledger Bezu. The IO Builders team, a couple of Cary team members, because our back end is in Java, and a couple of individual contributors, and importantly, Connys Venson, who is the creator of the Web 3 library. But what's interesting about communities is many people can have the permissions to keep content up to date. And this is where we've been using a lot of the grant funding. So and the key to this is rewarding writers. So to get good content out there, where there are gaps within the ecosystem. So grants right now are coming from the Ethereum Foundation and Consensuses Grants. This has sponsored a lot of the Getting Started materials. Many of the tools, libraries, and frameworks have been written about. And then also working on keeping the Ethereum wiki up to date, Solidity Docs, various different docs. One area which Cary is also moving into, if you want to get in touch, is commission content. So if your project needs better tutorials, help your developer community understand how to use you, so that why, that top of the funnel, let us know. And then getting involved, the next communities which we're launching are Getting Started, which will come out this week. This has some really exciting content, including a couple of tutorials on how to use a new web ID, which means you don't need to set up your whole tool chain. And it's just some interesting templates to give developers which are new to the Ethereum ecosystem that first aha moment. And you'll hear more about that experience in other talks, or Albert's talk, IA's talk. The Super Blocks team has been doing some great work there. Web 3 onboarding is another one. ETH2, as the contract gets deployed and get closer to a robust beacon chain in the beginning of next year, will have materials on how do you actually connect with the network, how do you send funds to the stake and contract, that kind of stuff. And then L2 scaling, which is a really important topic. And there's been a ton of research over the past few years. But I think we're now moving from research into actual production use cases. So get in touch if you'd like to be involved. This is all about community making greater engagement with each of these projects and bringing more developers into the Ethereum ecosystem. So you can reach me at my email or our Twitter account is cowry underscore IA. Thank you very much.