 Thanks, everyone, for coming. Actually, who's from the EF here? Okay, not everyone. That's good. All right, my name is Thore, and I'm working for the Privacy and Scaling Explorations team at the Ethereum Foundation, and in these slides, I will talk about what we do in our team and how you can get involved. Before I start, I would like to get a sense for the room, so please raise your hand if you have used a ZK-powered application in the past. Nice, that's like 30%, that's good. And who has written code related to zero-knowledge proofs? One, two, three, and two are from our team, one is from our grantees. And who would be able to tell a relative about zero-knowledge proof and explain, like, high level what a ZKP does? Okay, 20%, great. Nice, so let's get started. The Privacy and Scaling Explorations team is one of the larger teams at the Ethereum Foundation, and what we do is we explore what can be done with zero-knowledge proofs, what type of applications can be built. So we are not building proof systems ourselves, we use the existing proof systems to build applications on top. And this space is really exciting and rapidly evolving right now, especially due to some recent advancements in, like, engineering and academic work such as PLONK and PLUKUP, much more complex use cases are possible just recently, and so it's a really good time if you already had an itch to get involved, to get involved now. So what we do in our team usually starts with a circuit. A circuit is a description for the ZKP system to tell it what it should be proving about. So we have a bunch of guys in our team that are deeply familiar with ZKPs and they understand what type of circuits could be useful, and we build these circuits. On top of these circuits we often build what we call gadgets or primitives, so these are tools or libraries that allow you as a non-ZK savvy developer to integrate the specific functionality that the circuit provides into an application. And sometimes we also build user-facing applications on top of these gadgets in order to showcase to the ecosystem how this can be used. On the side we also do some other things such as education, so we do like blog posts and workshops to help people get up to speed with ZKPs. One thing that we do quite a lot as well is grants, so we work a lot with the ecosystem support program, and that's the reason why I'm invited here today in the second part of this presentation. I will show you a little bit how you can get involved and get a grant with us. So this slide is sort of a black box explanation just to get everybody on the same page about what a ZKP is, so you might have heard that with a ZKP you can prove that you have done some computation correctly. You might have also heard about all these different proof systems like Snark, Starks, Plonk, Groth 16 and all of that. They all have in common that these proof systems need these circuits or something like that, so a description for the proof system that allows it to understand what the proof should be about. Once you have this circuit then you can set things up and you will have a prover algorithm and you have a verifier algorithm. If you satisfy the prover algorithm, so you give it the right witness, it will provide you with a short proof string. This is the actual proof. And that proof can then be fed to the verifier algorithm, and this checks basically, gives you assurance that this computation really has been performed correctly. So that way Ethereum is essentially able to learn whether something that happened off-chain, some computation that happened off-chain and that is potentially large, is correct or not. So it can learn something that it couldn't process itself. And it has sort of this scaling aspect to it. It also has, like with zero-knowledge proofs, it also gives you the optional ability to hide the inputs of this computation. So this is how zero-knowledge proofs got their name because of this property, but it's actually an optional thing. So with these two things together, you have the scalability aspect and you have this privacy aspect. And if you tag them together and you use them in the right way, you can give Ethereum back its privacy and its scalability. And this is why we are in our team excited about CKPs. So now I'm going to show you a couple of projects that are in our team, that we work on in our team. And these are just three projects. I counted we have 15 different projects at the moment, and you can see them all on our website. On the last slide I showcased, I have the link to that. So I give just these three examples. And I've included the people that have the right access to the repos here. That was the easiest way for me to determine who is willing to be publicly associated with the project. So the first project I want to talk about is CKEVM. That's our largest project and it's a really talented team, really interesting project. And what they work on, they build a set of circuits that allow you to prove that you have processed an Ethereum transaction correctly. And of course this can be useful for like roll-ups or so the roll-up can prove whatever state transitions happened in the roll-up are correct and Ethereum can verify this then. And maybe in the future it could also be useful for layer one so that light clients make use of this technology. This project is also called the Community Edition of CKEVM. So everything they build is open source. You can go on privacy scaling minus exploration CKEVM circuits and look at what's going on there. If you have the right skills then you're welcome to become a contributor. They're working quite closely with the scroll project as well. So please check that out. Vitalik has done a blog recently that shows like the differences between this various CKEVM projects. There are quite a number of them out there. And they all make like different trade-offs. This project goes for perfect compatibility with Ethereum at the expense of proven time. The project is written in the Halo 2 proof system and it's developed by CKEVM. They made some modifications to that but everybody's really excited about Halo 2. So this was our first project. The second project I want to show you here is SAMA4. The main contributor is CEDOR, he's sitting back there. And we have hired a PO, Andy, who's not on the slide, and actually Wager and Kobe, these two guys, they have left us a while ago but they have made some very important contributions. So what is SAMA4? SAMA4 is a protocol that allows you to prove that you are part of a group privately. So you can think of a group as basically a merkle tree and you create an identity, you stick it into this merkle tree and then you are able, using SAMA4 to prove that you are in this merkle tree. In practice it's a set of circuits, some contracts and some JavaScript libraries that make it easy for developers to integrate this functionality into their applications. And CEDOR has built some quick setup template. It's really straightforward. If you have an idea, some application in mind that could use that, then you can go ahead. We have recently started a SAMA4 grants round and I will talk about that in a future slide. If you want to see SAMA4 in action, you can go, I think on the first floor, there is the temporary anonymous zone and they will give you a card, you, on this card is a link, you join, this link allows you to join the DEF CON Bogota SAMA4 group and then you are also able to make use of that, interact with some applications there and it's a nice showcase. If you want to learn more about SAMA4, you can go on SAMA4.appliedckp.org. So this is the last project I want to show here. The name is Macy and it's an idea that Vitalik came up with. It's currently run or managed by an anonymous guy called Q. And there are also two important people that don't write code here. This is V and Feeney. They should also, they're not included in this slide. So Macy stands for minimal anti-collusion infrastructure and the idea is, the point of Macy is to prevent bribery in voting systems. So as an example, you could have, you could think of something like Gitcoin where there are voters that basically vote on allocation of funds and in this system someone could say, everybody who provably voted for me will get an airdrop later on. And so this would sort of distort these incentives of the quadratic funding system. And Macy can help you get around that using zero-knowledge proofs. How Macy works is that all the voters, they encrypt their votes, they put them on chain and then there is a coordinator who tallies all the votes and so he's able to decrypt the votes that are on chain. He tallies the votes. He publishes the result along with the zero-knowledge proof that shows that the telling has been performed correctly. So he only has two choices. Either he doesn't participate at all or he publishes the correct result. Another important feature of Macy is that it's always possible for voters to override their vote again. So if the briber looked over their shoulder while they were voting, they could always change their mind later on and override that vote. Yeah, so this is Macy, how it works. You can also see this in action here on DefCon. They are running together with the clear fund guys, clr.fund. They're running a quadratic funding round, DefCon, Bogota, quadratic funding round. They are supporting local communities here in Latin America, I think with 250K. The team is also running a project called QFI. This is an incubator that helps local communities to spin up their own quadratic funding round and basically provide them with the infrastructure for that. Yeah, so these were like a sample, a couple of projects we are working on. And I hope those got you excited because in the following slides I will talk about how you can get involved and how you can contribute to such projects. And in fact, these projects that I just showed you were in large part built by also grantees that made like big contributions. So the first thing that I want to talk about in regards to how to get involved is targeted grants rounds that we're doing. So occasionally, we just get out to the ecosystem and encourage them to submit applications on a specific topic. The first one I want to mention here is SAMR4. So this is a dedicated grants round for people that build an application on top of SAMR4 or that extend SAMR4 or that have like a completely different approach to solve the same problem as SAMR4. So we're interested in supporting all such kind of projects. Projects at all stages are welcome to apply here. You can follow this QR code here. It will lead you to the announcement blog post. And in this blog post you find your way to a submission form where you can type in the actual application. And there is also a wish list which can give you some inspiration on what type of projects could be interesting to build on SAMR4. So examples for that could be anonymous voting application, whistle-blowing application, anonymous chat applications, anonymous reputation systems. There's a huge amount of like untapped potential here. One of our guys had the idea to build like a private feedback, but in Discord that our team can use internally to like share feedback. So yeah, please, if that's interesting for you, follow this QR code and submit an application. An upcoming grants round that we are currently preparing is the L2 community grants round. It is with James from the Ethereum Foundation. This will start on October 24th. So there will also be a blog post about that with a submission form and a wish list. So examples of interesting things here would be like R&D stuff, like cross-rollup execution or compression for rollup, better compression for rollup data, L2 Lite clients, things like that. Educational efforts would be great to like inform the ecosystem about advantages of rollups and potentially the risks. Yeah, so yeah, please look forward to that. So these targeted grants rounds, we get quite a lot of grants from that. But that's not most of the grants that we're doing. Most of the grants are what I would call discretionary grants. So these are things where we find someone, someone tweeted a cool project that did on Twitter and we reach out to them and ask them, do you need support like we can give you advice or we can support you with funding? Or sometimes people also come up to us with ideas. In general, if you are thinking about getting a grant from the EF, your first thought should be the ecosystem support program. Like they have the right infrastructure and well-oiled machine to process your application and make it a nice experience. With us, it makes a lot of sense to talk directly to us, however, if you have a ZK focus and if you're an individual, we are not really working with like Corpse or DeFi project, DAOS or whatever. Like this is just too difficult for us to deal with in terms of like the due diligence. Yeah, so these type of discretionary grants are very often these are people that build something on top of our projects or that extend somehow the functionality of our existing systems. So people find out what we're doing and just want to get involved somehow here. Quite often people come also to us with ideas on their own that we don't really have in-house expertise on. So we have been doing a number of ZK machine learning grants for example lately and we support them as good as we can with like what we know and with funding. Finally, we always have like some ideas of what we would be excited about. If you have no idea at all about what you would like to do but you do definitely have the right skills to do something, then please talk to us. We have like these are normally the more difficult grants or more complex projects like we would be really interested in supporting the Halo 2 ecosystem more like building a DSL for that, make it as easy to ride a circuit in a circum. I see the battleships guys are excited about it. Make it as easy to build a circuit in Halo 2 as it is for circum or have more circuits, make recursion easier and things like that. Or if you're into breaking things, we want to see people that try to break these snark-friendly hash functions for example. Yeah, so if any of that is up your alley, please get in touch with us directly. We are also hiring. I have in the last slide, I have a link to our jobs page. You can check those open positions out but it also always makes sense to just talk to us. If you're good at rust, if you have experience building circuits or if you are just really excited about building applications about that use CKPs in some way and you don't really have a lot of deep experience in CK, it still makes sense to talk to us directly. We might just be able to find something for you. And of course, if you don't want money, everything is open source. Everybody's welcome to contribute to what we're doing. So this is the last slide, how to get involved. Our website still has our old name. It was called AppliedCKP, so it's AppliedCKP.org. The GitHub is privacy minus scaling minus explorations. This left QR code here is for our job site and the right QR code is for our Discord. We have a very friendly and open Discord channel. So please get in touch there. We would be welcoming you. Yeah, this was my presentation. Thank you so much. You can talk to me later. And you can reach out to me on Telegram at ck.discord.ch.