Les Amis d’Ethereum France #15 — Entreprendre en crypto, w/ Starknet & Mangrove

[Music] Glad to see another packed room and lots of people waiting outside who missed the last door closing, so sorry, I'm G, I'm the president of the France association and I'm stepping in at the last minute for Nathan who's having some minor health issues. So I'm going to introduce France a little bit for those who don't know it. Are there any of you who have already come to P France? Who hasn't come? Is this your first time?

Wow! And among those who have come, are you already members? Damn, I don't have much to do, frankly, sales. Okay, so our mission with ETM France... we've existed for almost nothing, practically since 2015.

In fact, in 2015 we were already organizing Meetups to understand how ETM worked with a small crypto community that was just starting out in France at that time. And from 2016 onwards, we structured ourselves with a 1901 association, and all that... originally the association was called ADS OTH, that's why when... If you want to donate to the association, send it to AS Point because we have the corresponding email address. We also manage the Etherum France website, which has actually become the name of the association because it's a stronger brand.

As you can see, our mission at Etherum France is to popularize blockchain in general, and Ethereum in particular, throughout the French-speaking world. It's an association that unites a fairly dynamic ecosystem. Since we're practically at the beginning of the mainnet, we've seen a lot of blockchains come and go. We have YouTube channels where you can find all this content that has existed for years, and especially the content from the Meetups we organize, notably the EthCC Meetups. EthCC is an event organized by Ether in France, an association founded in 1920.

So we try to create these kinds of gatherings and also try to bring people together around them, allowing our members to organize events, to think about Ethereum, and to publish articles to help it grow. Our ecosystem, but particularly in France, within the Francophonie, and especially in the Francophone world, because next year, as you know, we're organizing it in Brussels, Belgium. So, same date, roughly the same date, but not in Paris this time, but in Belgium. We have values ​​that are quite widely shared, I imagine you'll find in the blockchain ecosystem in general, which are sharing knowledge, having a certain open-mindedness, financial disinterest, and independence. It's primarily about cooperation.

Independence means that Therium France doesn't actually have any company members, only individual members. And historically, we've always remained independent, including from the French Foundation. We're financed solely by the SCC events we organize, but also by member contributions. That's why, if you want to join us, you can go to the Enfance website. There's a little something there: " Join us."

It's a non-profit organization (under the 1900 law), so you take out a subscription, or rather, a membership. This year, it gives you the right to an awesome NFT that you can tile for your friends to say, "I have the NFT France!" It also gives you access to a Discord server with several channels dedicated to members, and also to events we do remotely with our members on Discord. So, there are often French-speaking members who come to chat on our Discord servers. There are lots of events organized there, and you can also get a little closer to the organization of the CC (Community Content) that takes place every year.

Well, that's all I had to say. I hope you have an excellent Meetup. We have quality speakers today, as always, for France. If you want to see these presentations again, you can find them on the corresponding YouTube channels. And a big thank you again to Def France for helping us with this organization, and to...

we're in the Morpo logos here, no, no, Mangrov, in the Mangrov logos. So, thank you again to Mangrov for hosting us! For this event, well, hello everyone! So now we're going to talk very briefly about Defy France. I 'm Arthur, one of the three founders of Defy France.

We created Defy France in 2019 with Briss and Mounir from Paraswap. It's an initiative that follows in the footsteps of Ethereum France. We'll mainly be talking about Defy. At the end, I'll show you there's a QR code to join the association. There's a Discord server with many members; today there are about 2,000 members, of which 500 are active.

So if you have any questions, whether about joining this Defy movement or more technical questions about protocols, I invite you to join Defy France. Today's topic was a little bit about how to find your way in Web 3.0, and I'm going to explain a little bit about all the types of opportunities available to you if you want to go further. So we'll start with the most So, whether you're very knowledgeable about DeFi or blockchain, or you just want to discover a little bit about what it's all about, quests are a good way to start getting into it. What's interesting is seeing platforms like Galaxy Dwork, Zili, or you also have Layer 3 platforms, for example.

These are platforms where protocols, blockchains, or other entities can post quests. The principle is this: I'm a protocol, I want to attract users to my protocol, and potentially, I want to encourage people to contribute to the protocol. So, I'll create a whole set of quests. It could be depositing liquidity into a protocol, it can even go as far as, for example, Atlantis, a French company, which was running quests. If you knew someone with an institutional client who could be a borrower on the Atlantis B platform, if you gave them a connection, they could earn up to $1,000.

So, which is good The thing is, these quests generally have a fairly precise scope. They'll tell you very precisely what action you need to perform. It's rarely about earning money, but it can be winning an NFT or small goodies. So, it does require an initial commitment from you; you have to complete the quest to earn this reward. And so, it's up to you to put in the effort.

The good thing is that these quests can also allow you to close airdrops sometimes. So, if you just want to learn without risking too much by doing very complicated things, it's a good way to learn about new protocols, new chains, and to test things out a bit when you're not quite sure what to do. Then we have ban teas. Ban teas are often for people who are a bit more advanced in terms of crypto knowledge. Ban teas are generally for finding vulnerabilities or bugs.

And so, for example, this was a ranking of prizes. For the bans on Immunify, so it's each company that will say, " For the critical level, I'll give x amount," the minimum level, and so on, x amount again. Often these are fairly precise scopes where, since they don't know exactly which vulnerability to target, they 'll tell you, "We'll determine how critical the vulnerability is or not," and based on that, they'll tell you the amount of the bonus you can receive. So yes, we know about Google's bans and so on, but there are some protocols, notably Defy, particularly on Aken, or big chains that offer bonuses of up to a few million euros. So there you go.

After that, it's super hard to hunt down these bans, but it's a good way to get in, and sometimes there are small bugs, so it can be quite interesting. Then there's everything related to Akaton. There's a big one that 's quite well-known called IS Global, which is an Akaton that's generally online. So there are people here who participate in this kind of Haton, and what What's nice is that there are rewards generally offered by protocols, so Akaton doesn't necessarily have specific themes. If you're developing on a technology that's sponsored, like Polygon or Scroll, etc.

, you have a chance to receive one of the rewards allocated to the different projects. So globally, there are generally more than 100 reward categories at each Akaton. And so the protocols or sponsors rotate regularly. What's nice is that there are lots of categories; you can do DNFT, Defy, and again, whether it's quests, Akaton and so on isn't just for developers. Even if you do design or a little bit of product management, these things are accessible.

And what's nice about Akaton is that you can either create a team from scratch with your friends or join a team if you don't have anyone to team up with by going to Akaton. And so there are also... In- person acathons are generally found when there are Ethereum events or large chain events. Then there are all the grants, which are essentially subsidies awarded to encourage members of a community to build on the protocol in question or do things that could help the ecosystem of that protocol. So there are different types of tools.

You can also use grants when you have a protocol and want to outsource development. This can be for very core parts of the protocol, but it can also be for very peripheral things like dashboards, analytics tools, libraries, all sorts of things like that. What's also cool is that there are rewards. Now, you also have to know that sometimes there can be several people working in parallel on the same grant, so that's something to be careful about. And often you have to start with small grants to get known, let's say.

Foundations so that they can then more easily give you slightly more substantial grants. So here we're mentioning Ethereum Foundation, Gitcoin, AVs, and so on, which give quite a few grants. And if you want to find them, there will be links at the end with a whole bunch of foundations that offer grants. Then there are the job channels. There's one, I know, on Ethereum France, and there's one on Deffy France.

Here, I see at least three or four people who have landed jobs through these channels. So don't hesitate to post offers for the projects you're working on through these channels. And typically, I think four people from the company come from there. I just gave you an example of Pablo de Angel who says he's looking for positions at Angel. And the same thing on the management side, where we are today, well, we can talk about incubators.

So there are some American incubators that work very well, so all that Consensis Smesh, or rather, we were talking about Gitcoin before, but Gitcoin was incubated at Consensis Smesh. What's interesting about these incubators is that if you already have an idea, there are even incubators where you can come without an idea, just with skills. But generally, you come with an idea and you'll get mentoring. You'll be able to do workshops. Depending on where the funders have their strengths, there are usually other weaknesses that aren't covered.

So potentially, incubators can help you with that, whether it's financing, managing the company's finances, trying to determine which person in the team is best for which role, and then everything related to structuring fundraising, etc. So you should also know that incubators generally take money; it's not free. They'll take a share of the company. There's no pre- defined percentage; it depends on many factors, but we can say it's between 2 and 10%. So I've told you...

To give a few examples, there's Alliance, which is very well-known, and there's the Club Outler Ventures website, which is also a very good incubator. Now, there's another pretty cool topic: ongoing rewards. The principle is that, in fact, today we tend to do bonuses or give money for a given piece of work, and then we give money once. There are foundations that repeat this every year, and we can ask for money again for a service we've provided. But ongoing rewards are a bit more interesting in the sense that if you bring value to a protocol, if you develop something that generates money, well, some protocols have mechanisms for monetizing streaming, so you're rewarded according to what you've contributed to the protocol.

And all of this is streamed, so it's live. That's why there isn't necessarily a specific cap on the amount, and you have the possibility to... Creating businesses that are fairly independent by potentially generating revenue in this way—I think we'll talk about that more later— but here's a pretty interesting project called Drips, which allows you to create what they call " Drip Lists." So, what is a Drip List? It's simply...

I'll go look at it. For example, I have a GitHub repository with dependencies on other projects, and simply because I don't want these dependencies to stop working, I'd like to compensate those dependencies. So, let's imagine—this is just an example—that you use a particular library in your project, and you could reward them by creating a list like this. The steps are quite simple; in fact, anyone can do it. And what's great is that they can stream any ERC20 library on any wallet, and it works the other way around: you can receive funding through Drips.

Well, depending on what you've done, and so the principle of Drip is mainly to fund all open- source projects, so it's pretty cool. That was just an introduction. Next, we'll have Mangrov and Starknet, I think. If you have any questions, you can scan the QR code; it will have all the links to the foundations for the major ones, etc., with PR.

So, my name is Henri Lutau, and I work for the Starknet Foundation, which is relatively new. It's relatively new too, because, as you can see, I'm still wearing a Starare t-shirt because I haven't received my official Foundation t-shirts yet. I've been at the Foundation for about a month, a month and a half, and I'm in charge of developer relations at the Starknet Foundation. Okay, today what I'm going to talk to you about is the... the...

the... the... the... the pipeline, let's say, that most developers go through when they enter our ecosystem, the different opportunities available to them, and how we... From, "Oh, well, I'm new to the ecosystem," to "I founded a company on Starknet and I'm so happy," okay, uh, you have to understand that these things happen little by little, and overall, it's a bit like what Arthur was saying earlier.

In the current state of the ecosystem, it's not all these processes I'm describing; they're not set in stone. They're not fixed things where you'll find a page and be able to send a request. These are organic, emergent processes, and the core of what I'm going to describe here works with co-optation. That is to say, we're not yet at a stage where you can just read a page and say, "Oh, well, I'd like to do this," and then bam, you'll get a response. The core of what you'll be able to do in the Starknet ecosystem will revolve around the connections you make, the people you meet, and your willingness to collaborate with them.

It's not perfect, it's not for everyone, but that's how it works today, and if you have any ideas to improve it, we're happy to hear them. So, I'm going to talk to you about the different opportunities we offer people today. To be very clear, we have a big budget, you know. You can sit down on the... you're all standing there.

If you want to sit there, go ahead, no worries. I'd rather have you sit down now than in the middle of the press. So, we have a big budget for developers. It's not something we 're completely satisfied with. To build good products, you don't just need developers; you also need a lot of other skills.

But today, in fact, that's the state of our ecosystem. If you have skills that aren't development skills and you say, " Oh, but I could do that in the Starknet ecosystem," come see us. We'd be happy to discuss it. We want to know how we can do better, so it's really something we're open to. The discussion is about how we can improve.

Okay, so generally the first step people take when they arrive on Starknet is a Meetup of some kind. It could be a Meetup like the one we're doing today, which is in partnership with another Meetup group, or it could be a specific Starknet Meetup. Generally, people see something online and say, "Oh, I'll take a look." They hear a little about the ecosystem. Meetups are also a very easy way to get involved in the ecosystem, to contribute, and to take the first step towards getting involved.

For that, we have a relatively simple program where... oh, no, there isn't the text. Okay, so today the Meetup program is done, it 's launched, essentially maintained by Starknet. Soon the Foundation will have ours too. The deal will be pretty much the same; it's quite simple.

If you want to organize a MUP in your city, we'll give you a grant of $1000, which will allow you to pay for a meeting place, food, and maybe, I don't know, stickers. What you want with the idea of ​​getting together is why? Because there's a reason you're here tonight. It's really cool to see things on the internet, it's really cool to read technical documentation, it's super important, but ultimately, blockchain networks are human networks, and humans like to meet up. We have a bias towards that; we really like real-life events, and so we try to do our best to make it easy for people to meet up, exchange ideas about their respective projects, share a beer, present their projects, and find people to create new projects with.

We actually already had a Meetup here a while ago; it was pretty cool. Okay, so that's generally the first step; it's where people arrive for the first time, and it's also one of the simplest things you can do to get involved in the community. The second thing where people will start to get involved... The second step is a project we call... well, you see, I also put a link for the Meetups we do in Paris.

So this is the Starknet Paris Meetup group. We do them roughly every month, and at the last one, Tari was there and presented something. And there are a bunch of people in the room who come regularly, so don't hesitate to ask them; they'll tell you it's cool, at least I hope so. The second thing people will generally go through is where they'll start to think, "The developers have started saying, 'I want to improve my Starknet skills, how do I do that?'" Because, as you may know, Starknet isn't an EVM chain.

Starknet is a slightly different ecosystem. It's a slightly different stack from a high-level perspective. It works the same way; it's a blockchain. There are contracts. There are accounts, there are blocks, there are transactions—it's the same thing, but the way the network is structured is a little different from Ethereum.

The programming language of Smart Contracts is different from Solidity, so there's a slight learning curve that's different from Ethereum. At that point, people will be wondering, "Okay, how do I get skilled?" There are plenty of online programs that allow you to get skilled. I'm going to recommend two today. I didn't make a slide about them, but I'll mention them now.

There's an online tutorial called Stark Lings, which is very good. It's spelled Stark Lings, like Rust Lings, but with Stark at the beginning. It's very good for learning how to take your first steps in Kao. Secondly, there's a site called Node Guardians. I don't know if anyone knows Node Guardians.

Some people have already done quests on Node Guardians. Oh yes, that's right. Well, if you know Node Guardians, go ahead. Take a look, it's a great site. There are some great resources for improving your skills.

I would say that, generally speaking, our Guardian is good for when you have a slightly advanced level because the challenges are really in-depth, and once you finish them, the people who complete our Guardian program today clearly demonstrate a certain level of skill. It's a very good way prove you know what you're doing. Our Guardian program has courses in Cairo; don't hesitate to take them. They're good, and they also have a cool community. The third thing I mentioned is a program we launched a while ago, a little over a year ago, called Base Camp.

Base Camp is something my team and I do. It's a program of six 2-hour sessions, which we generally hold once a week for 2 hours. We also give you additional homework. It explains to people coming from Web 2 or another Web 3 ecosystem how to take their first steps in the ecosystem, deploy their first contract, and create a professional development environment so that by the end of these six weeks you're fully prepared and can start working on professional projects. The goal is really to take you from level 0 to level 1 and guide you through your first steps in the Starknet ecosystem.

It's something we do today. I can't tell you when the next one will be; we finished the last session we ran last week. It's completely free and online. Today, we offer it on a fee basis based on time zones in the United States and Europe, so it's quite convenient for you. We might not necessarily do it this way in future sessions, but this is how we operate today.

So, C is a good way to get started. Starknet and to really understand, we explain everything from how we code to how the network works. At one point, we used to do sessions on math, and we realized that most people don't care about math, or rather, they're not interested. It's a real question, actually, when you work on technologies like this: how deep do you have to go? Because the deeper you go, the less interested people become, and that's normal, there's no problem with that.

So we cover less math now. But if it's the math behind zero-knowledge proofs that interests you, we can guide you in that direction too. And as I was saying, it's something we do in a time zone, which is Europe and the United States. It's something we do in English. Is it satisfactory?

Well, not really, because there are a lot of developers who don't speak English. There's a There are tons of developers sleeping while we're not sleeping here, so we can't talk to everyone. BaseC is a completely free program with entirely open-source content, and we encourage people in the community who are interested in learning, taking from others, and sharing their knowledge. We encourage them to do their own BaseCamp sessions. So, I've noted all these groups because in each of these countries, we have people who came to us saying, "I'd like to...

I don't know, I'd really like to do a Meetup or a workshop where I can teach people to code." In Cairo, there are people who told us, "I'd really like to... I know all these developers, they're really good, they want to learn Web 3.0, I'd like to talk to them about Starknet." We provide them with the content, we potentially fund the tutors who will teach the courses, and we give them support in terms of visibility so they can reach as many people as possible.

People enroll and finish the course. The goal with this is really to make it easy to learn. Our goal with Basec isn't to create a paid course with thousands of students. The goal is to create a course that's as easy to consume and teach as possible. So we really encourage people to translate it into their own language, to teach it in their own way.

They can take all six sessions, they can decide to do three if they want, or twelve. They do their own thing; they decide how they teach it. And we also give them support in terms of... well, organizing a course isn't just about making a call, showing up, and learning things. There are a lot of really tedious things that go into it, like sending emails, scheduling appointments in calendars, managing people's registrations.

We give them all these tools so they can do it easily, and so the only thing they have to worry about is... What we do is explain things to people and spend quality time with them, okay? So that's another program we run, and it's another program too. Well, there are members of the ecosystem who, once they've finished B Camp, say, "Oh, well, I don't really know what to do, but I'd be interested in contributing." And so, well, they'll receive a large grant to do that.

It will allow them to continue to be involved in the ecosystem and improve their skills on Kiro Starknet because the more you explain, the more you learn. You never know a subject as well as when you explain it to someone else. It's also a way for them to improve their skills. Okay, another thing we do is we give builders large grants. We give large grants to builders who are joining the ecosystem.

Now, these aren't grants that will allow you to quit your job and join the ecosystem in general. It's more something that works well with people who are freelancers or people who have a job. There are several people in the room who have already received a grant. You can raise your hand to see. If you have any questions about the program, ask them; they'll explain how it works.

Generally, we give grants to people who have been recommended to us or to people we see on social media, on Discord, on Twitter. We see that they ask questions, that they know what they're talking about, that they've already coded and that they want to do a little more. The grant we're giving today is a standard size: $2500. We're not asking you to... we're just asking you to have an idea and say, "Well, I'd like to allocate this much time to this idea.

I'd like to try to do this with this thing." And we're not going to chase you to find out if you've delivered on this. For us, these grants are the goal; the objective is to give you the time. The space and peace of mind to explore what you can do on Starknet, try launching a project and see where it leads, and also, very clearly, it's an opportunity for us to give you the chance to build your portfolio because at some point, if you want to work 100 % on Starknet, you'll have to collaborate with people. Either you 'll create a company (I'll come back to that later), or you'll have to look for a job.

When you look for a job, you'll generally be asked what you can do. Our goal is that with that, you can create something really cool, and when you show it to people, they'll say, "Wow, that's awesome! I see you know what you're talking about!" Okay. And that's the same thing; it's not a process that's public.

We don't put anything in writing because it's not something we want to be flooded with by people who are just looking for freebies. So, we're not very selective, but we're not completely open either. No, don't hesitate to come and talk to me about it if you have any questions. The third thing we generally redirect people to, after the big ones, is sources of contributions to Open Source. Arthur mentioned it a little earlier: there are systems that allow you to make open source contributions and distribute money and allocate funds to your open source project.

We work a lot with a platform called Only Dust Only Do. It's a platform that allows open source projects to list their projects and say, "Here we are open to contributions, and we pay our contributors who make quality contributions." It's not a project where there's a bounty where you just see, "Oh, there's something to do here, and I 'll do it." No, it's a project that aims to have people who are really involved in the projects and who are there in a real relationship to become a contributor to the project, but who compensate them. Okay, and We redirect a lot of builders who know how to code in Cairo, who are familiar with the Starknet infrastructure, and who are particularly skilled in Rust.

There are people here who know Rust, okay? There are also JavaScript projects, and if you don't know REST, it's also a great way to improve your REST skills. In fact, there are a bunch of projects that will say, "Hey, I need help with these things," and for you, it'll be an opportunity to develop your skills, to meet people who build on Starknet, to exchange ideas, and to contribute to GitHub. You'll be able to say, "Aha, I actually did this, and I know what I'm doing." And there's also a benefit that isn't often talked about: you'll be working on cutting-edge open-source projects.

You'll be among the first to develop these tools, and you'll be the first to know how they work and to be able to... You can use them later when you start a business, or when a business is looking to use them. You'll be able to say, "Oh, I know how to use this thing," and look, "I've committed here, here, and here." So it's a really good way for you to get started because you'll be able to pay part of your rent with these things. You'll meet people, and it's a really good way to enter the ecosystem.

I strongly encourage you to go check one out. They have projects not just on Starknet, but in a bunch of other pretty cool ecosystems too. And another thing we launched not too long ago—this is more of a pilot—is a mentoring program. We've realized that what keeps people in the ecosystem isn't necessarily the money, even though money obviously helps. Money is a means, not an end, and most People who come into the ecosystem, what makes them stay, are the relationships they build and the projects they work on.

We decided we needed to encourage connections within the ecosystem as much as possible. So today, people who say, " I know how to do Kairo and I need help," or "I know how to do things on Starknet and I need help taking my project to the next stage," we connect them with people in the ecosystem who are building things that can guide them, both technically and personally. They might say, "Hey, you should talk to so-and-so; they did this," and so on. Okay, it's still a pilot project; what we're doing is really very hands-on, but if you want to try it, don't hesitate. It's definitely worth it.

And the last thing I wanted to mention is creating businesses, because ultimately, that's what most developers do. Today, people say, "Oh, I'd really like to find a job," and that's obviously very important. But today, in our ecosystem, we realize that there's also a need for people who are capable of creating jobs, of finding people who are capable of building businesses. And these aren't skills that just anyone can acquire. Well, I think that, like many things, anyone can learn them, but there are people who aren't necessarily developers but who know how to build businesses.

There are people who are developers and are n't at all interested in building businesses. Today, we realize that we can offer a lot to people who want to build businesses, and we want to help them with that, whether they already have experience in doing business or people who want to start. So, for people who are on this path, we have a mentoring program with entrepreneurs from the ecosystem— not with developers, but with entrepreneurs. We're going to connect them with people who have the same problems as them. We'll also give them advice on how to structure their fundraising if they want to do one.

Once their fundraising is well-structured, we'll connect them with VCs. Starkare is fortunate to have some very good VCs, and we can introduce them to all of them so they can raise funds and move their business to where it needs to go. We also work with several incubators and regularly make connections for entrepreneurs who want to know how to take their business to the next level. This is something that's quite new and relatively emerging, so if it's something that resonates with you, come see me and let's talk about it. If you're thinking, " Oh yeah, but actually, on SarkNet it's a hassle because it doesn't have this, that, and that," tell me, like, tell us we can do better because ultimately, what we want is for the ecosystem to be as strong as possible.

The most welcoming and interesting thing possible for the people who come, and for it to grow and be a cool thing, and the last thing I'm going to mention is obviously that we do events, so I don't know if any of you will be at Dev Connect in Istanbul, there will be a few, okay, some have already done something, I don't really know, but we'll be there anyway, and we'll have three big conferences, we'll be at St n CC which we're organizing, an ecosystem conference on Monday, November 13th, we'll be at the conference on obstruction on Tuesday, November 14th, and there will be a Starknet track for IF Global which is Haton which will be in Istanbul, I don't know if we can participate remotely in this one, but if you're there in person, participate in person, and if not, if we can't participate remotely, I know there's a remote one not long after and there you can participate, and where there are prizes to be won, obviously, well This is your chance to test what you can do with Starknet. If that's something that interests you, I strongly advise you to practice, or rather, take your first steps. Play Starklings, and ideally, play Not Guardians beforehand. That way, you'll arrive ready to go and you'll crush everything. Okay, and that's all for me.

It's a slide I had saved; I like it, so I included it. Honestly, I find the atmosphere in the crypto ecosystem right now ambivalent. What's interesting is that I have a lot of discussions with people who have been around for a long time. Everyone is asking themselves questions, like, "Damn, guys, we've been here for 10, 15 years, are we really doing anything meaningful? Does it work?"

What we do, or is there something going on or not? These are questions that I find really interesting because, firstly, they're important questions, and secondly, they're quite typical of this market phase we generally experience. A bear market isn't when things are going down, it's when things are flat and we're bored, and that's happening now. But that doesn't mean there's nothing to build. There are plenty of interesting things, plenty of opportunities out there.

Where do you allocate your time today, and what interesting things do you pursue? What interests you? That's what's really worth exploring. So, there you have it. I hope I'll have some feedback.

There are things I've mentioned that will interest you. Don't hesitate to come talk to me. See you soon. Good evening everyone. I'm Philippe from Mangrve, and tonight I'm going to talk to you about business development possibilities, specifically new projects in a protocol environment.

Mangrov is a platform where we have a specific approach, but I think the approach we propose is likely to be adopted, expanded, and adapted on many platforms. From what I've heard, obviously, from the overview presented by Arthur, and from what Henri showed, there are really a lot of things that resonate. So I'm going to show you our approach, and the initiative includes what are called pods within Mangrov, or on the Mangrov protocol. I'm going to be a little critical of large-scale projects. It's not that I dislike large-scale projects, it's that I think if we see the development of an ecosystem based solely on large-scale projects, we're missing something.

So I'm going to explain why we're talking about large-scale projects here. We'll go over these three points: first, we'll talk about the problems and limitations of large-scale projects, how they are a good thing, but also how they are a problem; and how we can draw inspiration from a Playbook, which is that of web platforms, to go further with the instruments and tools we give to developers who want to... Developers or builders—I use the term "builders"—develop things, products, initiatives on a Web 3 protocol. And we'll take our pod program within M as a specific example. So, first, the problem with large platforms is that things can get a bit out of hand.

There's something very striking in the Web 3 environment, and when working with DAOs, that large platforms have become the main instrument for soliciting and fostering initiatives within an ecosystem. There are even DAOs built specifically to distribute large platforms, for example, Gitcoin, etc. And often, when we try to see what these platforms are used for, there are two cases. There's one case where we act as a GR (Global Resource Group) because we don't want to hire people, and we use the large platforms to have work done by freelancers. Arthur was talking about this earlier; he warned us, "Be careful, what you do in a large platform might be taken by someone else."

Having another provider develop the same thing at the same time is a little strange. Either you give a job to one provider and then don't give it to the other because they'll be working for nothing, or you actually want to use the big players in a different way. The sentence shown here is taken from the landing page of a large-scale program. If the goal is something else entirely, if it's to motivate many people to work on building things within an ecosystem to develop products using a protocol, then it's different. It's not a service provider relationship; it's a real relationship within SEM management.

We're giving people the means to start doing things, and the question we're entitled to ask is: is relying on large players the best way to develop an ecosystem? I'm getting to this slide; you might know this famous sentence. From Charlie Munger, show me the initiations. Depending on what we have, we'll have different downstream behaviors. And what are the incentives when we give large rewards, and what are the outliers to expect?

There are two outliers that are very common. The first thing is that what we attract are bounty hunters, and that might sound pejorative, but it isn't necessarily. The general idea is that when we offer $1,000, $10,000, or $20,000 for a large reward, we're going to attract people who actually want to collect $2,000, $5,000, or $20,000. That's not necessarily the objective in the context of building an ecosystem where we want to have people who are motivated to develop a business or long-term projects and not to seek the reward. So it can have a priming role, like the program Henry was talking about earlier, where it's a small entry point that then leads to something else, but often when We saw the levels of funding provided by certain projects, as Arthur mentioned, where it goes up to 50,000, 100,000, 200,000.

We really wonder what we're looking for. Another problem this creates, and another well-known outcome, is that to ensure these funds are allocated professionally and ethically, we need to verify that the people actually provide them and that there are no conflicts of interest, that we're not giving to friends. So, we have to create a whole bureaucracy of processes, sometimes even decentralized committee systems, to ensure this level of oversight. This creates a lot of red tape. We can ask ourselves if this is really the best way to build a vibrant ecosystem with lots of projects, rather than building a centralized bureaucracy that distributes subsidies like a socialist state.

I don't want to go there. So, instead, I propose we consider other points of view, two other points of view: the point of view of the A builder who truly wants to create something—whether entrepreneur, developer, strategist, or designer, it doesn't matter— who wants to build something ambitious, something that will have a significant impact, will choose an ecosystem because they find that it has the potential to create a long-lasting business, a long-term enterprise. From the perspective of the ecosystem operator, or a protocol like M Gru, the idea is precisely that instead of subsidizing people who chase rewards and then stop working, who will chase the next reward as soon as they finish their job, we're looking for the opposite: people who have a vested interest in staying and developing their own businesses. We want to give them the means to succeed, and that's why I suggest we take a moment to consider what was happening before, or what is still happening in the real world— not the Web 3.0 world—around web platforms.

Web platforms, for the most part... They are organized in a bifacial, or double-sided marketplace, model, with producers on one side and consumers on the other, and a platform operator in the middle. This is a model that has been mapped dozens of times; it's very classic and you see it everywhere. As soon as you look into a platform, you see this system appear. Here's an example, and you can see why I'm introducing it here because it's the same in Web 2.

0 and Web 3.0. So when we think of YouTube, on one side we have people who consume videos, others who create videos or use them to develop an influencer activity, for example. When we think of Uber, well, on one side we have people who have a business driving people in their cars, and on the other side, people who are driven, and so on. All platforms generally operate on a system like this: double-sided, and sometimes multifaceted, with different types of actors.

But Web 3 protocols, whether they are deceptive protocols, Infrastructure protocols are generally in this same relationship with their users. For example, with Filecon, on one side you have people who provide storage space and others who use that space to store data. Similarly, with swap space, on one side you have liquidity providers and on the other you have traders. So we find this difference, this double game. And so how do Web 2.

0 platforms develop their ecosystem? How do they bring together actors from each side? This is important for them because if you don't quickly bring together actors from each side, the platform does n't work. If you try to be a user of Uber and there are no drivers, it doesn't work. But if you are a driver and there are no people who want to be driven, it doesn't work either.

So the platform often thinks about all the efforts it makes to attract consumers, but it also makes just as much effort to attract producers. Here you have some examples with Uber, Airbnb, and Amazon, and each time you see that they play on two types of incentives: on one hand, they facilitate the work. So that these people, the producers, can earn money, not by giving them money, but by enabling them to build their businesses, we'll facilitate customer acquisition with mobile apps, we'll facilitate payment processing, and we'll facilitate marketing and communication with, for example, the recommendation engine on Amazon. And on the other hand, what these platforms do is minimize friction to make starting a business as simple and inexpensive as possible. For example, Uber has implemented programs to make it easier for self -employed individuals to acquire or rent a car and have an all- inclusive package with maintenance and insurance.

It's the same for Airbnb, and the same for Amazon, where the entire logistics system is in place not just to push Amazon products and distribute them globally, but also to distribute the products of small shops or local artisans worldwide. So they provide tools that These tools and platforms allow us to create businesses that were completely impossible before we had these resources. So, we'll see how we can adopt this within the context of a protocol, specifically within a program called "pods," which we're launching with Mangrov. This program is also currently in its pilot stage, to use Henry's term, meaning it's still in the experimental phase. We have a first experimenter here, so I'll pause for a word to say a few words about Mangrov and why we can discuss this producer-consumer distinction in the case of Mangrov.

Mangrov is an Ind Dex, which is based on an order book. Its unique feature is that it's programmable. This means we can develop and deploy strategies in the form of code associated with offers placed on the order book. This opens up a completely new design space, allowing us to create persistent strategies on an order book and thus create new projects and new products. The analogy I like to use is to think of Ethereum versus Bitcoin.

In both cases, we have a data structure, which is a blockchain, but in the case of Ethereum, we have a Touring machine, and we can create anything on top of the blockchain. In the case of MangGrov, relatively speaking, it's the same paradigm shift. That is to say, we have the same data structure, an order book, but in one case, we can only make transactions, and in the other, we can create whatever we want from this order book and create strategies that have no limits in terms of inventiveness and creativity. So, for us, the producers will be developers and strategists, strategy designers who will be able to create not only market-making strategies, which are very close to the way an order book works, but also other very different strategies, for example, to cover a collateral ratio on a landing market. So, we need developers in the ecosystem who will do this because we at Mangrov's mission is to create the engine; we don't aim to replace an ecosystem and develop all these products.

For that, we'll also work on the two pillars I mentioned for Web 2.0. On the one hand, we'll make it easy to generate revenue, or at least as easy as possible for pods to generate revenue. One logical thing we can do is that, for any Dexterity (DEX), this is an advantage we have compared to other protocols. It's commonly accepted that when you make a transaction on an index, the user pays for " fills."

This means we can use these "fills" to redirect them to the strategies that triggered them. Therefore, strategy developers will be able to recover a portion of the "fills" generated during the deployment or execution of their code. Obviously, they can also have an on-top-off business model, independent of the Market Engine and the DEX itself. We can have... we currently have...

A project is being created where there's a subscription model in addition to using Mangr, so it's not necessarily limited to transaction fees, but there's this first layer: transaction fees can be sent to the developers. The second aspect is reducing friction. How can we do that? Okay, I understand that most people here are developers and designers. After the survey, the little survey, the idea is that as developers or designers, we don't necessarily have all the skills or the desire to mobilize or acquire them to develop a company.

However, we might want to have an activity, to develop an initiative to its completion by acquiring the necessary skills by partnering with third parties who will provide this additional support. Generally, there are two ways to do this. The first, classic way is to raise money and then hire people who complement the developers' profiles, but this is very cumbersome and not necessarily suitable for a relatively simple product that will find a market relatively quickly. The other possibility is to Organizing ourselves into a network of pods, a network of teams that will provide the missing skills, is why we're building a tool here called the value sharing agreement. This is inspired by other innovations in traditional business.

The idea is that transaction flows, monetary flows, and value flows coming from the Market Engine will be made available in a smart contract and automatically redistributed not only to the team that produced and led the initiative, but also to other teams that contributed their work and brought skills that were lacking in the development or strategy team that launched the product—for example, research, marketing, business development, and so on. So, we're trying to launch this system today with this model, which isn't yet implemented as a smart contract but is currently done manually. We're using support pods, meaning teams that provide these missing skills and are currently sourced from within... The Mangrove team, but with the aim of becoming independent, so that's the system we're proposing today. And the last point I'll end on is that it's extremely important that if you create a project that depends on an infrastructure—what we call platform risk—you make sure your project has autonomy; it's not vulnerable to the platform itself.

And we know very well that in the world of traditional web platforms, this is a constant risk. We saw Twitter close its APIs and kill all its clients overnight. We recently saw Reddit do the same thing. It's a tendency for traditional platforms to do this. Obviously, Amazon, whether it's Amazon Web Services or Amazon.

com, which competes with its sellers, is a fundamental problem for platforms. Here, what we're introducing is a governance model where one- third of the votes in Mangrove's overall governance are allocated to the people who build on Mangrove. There's no possibility of a short circuit that would leave people who have invested time, energy, and creativity in Mang grve unable to run their businesses. That's all I'll say, and I'd be very happy to talk more specifically about examples of the products we're working on and the possibilities of creating a new pod with those interested. [Applause] [Music] Thank you.