# "Developer Advocacy as Cypherpunk Infrastructure" by Francesco Andreoli // Cypherpunk Congress 2

- Channel: [Ethereum Cypherpunk Congress](https://streameth.org/ethereum-cypherpunk-congress)
- Date: 2026-01-09
- Duration: 14:08
- Topics: web3, privacy, now, crypto, cryptography, blockchain, data, security, human right, rights, tech, technology, internet, open source, free, freedom, ethereum, hackers, ethics, cypherpunk, dev, developer, dapp, decentralization, bitcoin, computer, surveillance, cyber, peer2peer, p2p, love, solidity, zk, zero knowledge, education, academy, w3pn, congress, ethereum cypherpunk, buenos aires, argentina, vitalik buterin, privacidad, filecoin, foundation
- Watch: https://streameth.org/watch/yt-nTL9vhaVZ9g
- YouTube: https://www.youtube.com/watch?v=nTL9vhaVZ9g

## Description

Ethereum Cypherpunk Congress by Web3Privacy Now is the world's largest cypherpunk and human rights event.
4500 people gathering in Buenos Aires to celebrate privacy with internet freedom leaders like Richard Stallman, Vitalik Buterin, Roger Dingledine, and Eva Galperin. 

Join us in building a free internet for all.

Website: https://web3privacy.info/
Congress site: https://congress.web3privacy.info/

## Transcript

Awesome. [applause] Awesome. Awesome. Appreciate it. So, this is a test, guys. So, I don't know if you know me. Uh, I'm doing developer relation for a long time. Oh, yeah. That was working. Um, and I I try to think about different kind of like, you know, talking co topics, right? And then in light of this specific you know uh conference the fact that we are all cyber punk at core I try to kind of like you know slash out some of the content that I think devil should go where is going now and where is now I don't know how many of you are doing kind of like developer advocacy today or at least how many of you know what a devil does h some some people okay kind of kind of kind of yeah yeah but basically like my talk is all about develop cyber punk infrastructure So that said um you know I've been around for I mean for around like 12 12 years organized bunch of hackathons uh shield different products known shield different products um build different kind of like programs for for developers to grow to get exposure uh participate in different like activation um lately I've been running one activation in in metam masking consensus called builder nights I don't know if you heard about builder nights but basically like the idea at the beginning was I don't want to shield anymore. I want to actually build a movement uh basically a developer event that speak about specific topics. We started around 437. We started about uh layer 2 infrastructure but we never kind of like had the idea to actually speak one single uh uh company or SDK stack right even if I'm in in a company. And then kind of like the things started to pick up my brain a bit um that you know devil is not really a marketing function right like devil is about uh um you know advocating for a space uh top of the funnel but most important trying to get developer excited what they want to build so it's giving the instrument of what um what to do so there were four main points that I kind of like tried to trigger here so de is not marketing is the infra privies and digitalization require builders on users. So we want to actually think about who are actually building for and the end user is the end goal obviously. So um and how we're doing that we want to conserve uh privacy. We want to defend the open system and be kind of like you know advocate for full decentralization and there are different things we want to maintain the ethos. I don't know if many of you guys know this kind of like cyberpunk ethos. I I put it out here. I don't know if you see it but um code speech right? So we want to able to actually verify everything proving everything especially in light of like A004 X42 that are coming around the gantic economies privacy as human rights and infrastructure might resist corporate and social capture. What does it mean this we want to make sure that we track things but we track it on an ethical way. So um this is a part I think it's a bit ced but um this is a part where I kind of like go on the other side right so today how we're building ecosystem is on silo I don't know if you're building on different stack but today you can on board obviously with hard foundry on on on solidity you can on board on other ras specific ecosystem but I don't know about you are you feeling a bit stuck in a specific ecosystem like this kind of like crosschain interrop development journey is kind of broken right so it's very centralized there are different bottleneck there are different green light a lot of those activation are feeling very very um centralized in terms you get green light I don't know if you add access to grants but also grants are always like divided in different parts and a lot of time those are kind of like singlehanded green lighted by by humans right grow hacked is all about ROI right here AI there and how we can actually like build an activation that return more monetary money and I'm always been very kind of like you know uh it's it's very tricky right because you want to provide a right in the same time to the company but in the same time you want to build something that is truly um honest and and has value in in everything and obviously you don't want to gatekeep right it's it's very important you need to have fully digitalization at his core and I think right now what we're doing is uh um cannibalizing trust that developer give us in the ecosystem especially newcomers if you've been like building software in web 2 for multiple years you need to go actually in a specific direction in web 3 and I think like decision making and chilling on the face of developers sometime is canalizing the trust and the the access of of this ecosystem the entire goal at the end is not siloing things specifically so trust cannot be shield into existent I think you around developer relations. We we build stack right from like docs, tutorials, events, content and one things that we need to think about is how we're building actually this infrastructure that is fully kind of like no shield that really embrace developer in the ecosystem. So from a doc specific to kind of like a culture um a cultural infrastructure and permission system. I think this is really really key because part of the journey that a developer is coming into web three is all about learning how to build a dab from scratch. It's about kind of like trying to use some tooling before even getting into the space and thinking about what to build. And I think sometimes we're skipping a lot this phase of this kind of like you know uh valuedriven on boarding versus kind of like the uh very kind of like product conversion on boarding and I don't know if you relate on that but uh that's also like the reason why I'm here and kind of like giving this talk and I want to also like make sure that if you guys have question or remarks or if you think about this is the case I want everyone to kind of like speak up and give some opinion. I I don't want to take all the 20 minutes. So, so what I'm kind of like thinking as NFAB is that how we can actually build uh the the professional devil as kind of like a strategic infrastructure, right? How we create this kind of like knowledge uh rails that are open and permission for everyone. And I think that's super important, right? Because if you empower the community, you're not just empowering feedbacks, but also like you're empowering new knowledge coming and training new developer coming into the space. And that's all about kind of like building this kind of like decentralized momentum. So uh privacy is every problem. I think like one part that I kind of like started to discover is that obviously you want to have privacy at your core. you want to have I mean we are tracking different telemetry status around our SDK and one thing is important that you don't want to capture all all data but you want to give the opportunity also developer sharing their their journey and having specific kind of telemetry on on that and I think tools also must support fully anominity by design right foundry and especially now with LM based learnings I don't know but we are training on centralized containers and things are is something that I'm quite scared he cared about. So I'm definitely recommend people to you know test out like you know decentralized inference protocol train your own uh models but most important if you want to change your your LLM also like you know you you don't basically start from scratch so here is something I kind of like put together around like a cyberpunk uh toolkit uh zero knowledge examples. So this is basically like if I would start a full no shield devil infra uh these are kind of like the main things that I will uh would care to kind of like advocate for right you have ak examples and templates you have security defaults by tutorials you have specifically so um um ID option and obviously unit test for for privacy rejection uh regressions so again devil has a cyber fun force right so we want to write code. We want to explicit advocate for writing code on a very open- source way. Uh but most important we want to defend uh privacy of not just our user but our developer building right and telemetry of our SDK for example is playing a big role. So and I put here together function as culture infrastructure defending um decentralization is something that we need to care about every time that we're building something and we are advocate and I think like deell right now is between engineering and the developer community is playing a huge role uh and and the reason why we kind of like want to resist this kind of like um way to put numbers on every um kind of like centralized on boarding. So when we speak about you know like shielding our developer tooling to developer without them even understanding why and what they want to build is something that we care about. Corporate incentives to collect user data is obviously one one big part. Private gatekeep your own knowledge I think is very is very important also to consider and there is a lot of like different you know um platform today you know it doesn't require you to start from from scratch. You have a decentralized docs. You have a decentralized interference training your LMS. You have even like you can speak with specific like uh events organizer and they're really good specific events that are actually done and preserving your own privacy when you're building things. So we all must kind of like resist this kind of like way of centralization. So principles are punk de I put together these five kind of principles you can kind of like take home. open by default, privacy by design, permission contribution, decentralized governance I think is one one one of the biggest uh pillar here and obviously zero resilience on user data and I'm excited to see also you know this presentation with with Nikico and the demo with Niko on the wallet privacy SDK I think is a big step into kind of like user collection and uh it's just exciting to see uh this coming and this finally coming people start to care about privacy by design and also like inheriting this to a developer tooling tool. So developer advocacy is a cyber punk infrastructure devil today are committing advocacy between both users and uh um and and developers in the community and I think like if this profession doesn't really like defend privacy in a no shield way nobody nobody will really will. So um for all the devils here in the room and people that advocate for technology to use user big shout out to you. Thanks for always like you know caring about this. Just the fact that you guys start in this conference is great. So big round of applause to to you guys and I think that's it. I wanted to keep it short. You know, if you guys think about also like the some of the topics that I spoke about, you kind of like also either agree or you want to add some points, no need for ask questions. You can you can uh give your your feedback or you can say, "Hey, this is all wrong what Francesca you're saying right now. Please speak up. I think this is an open conference. I'm excited that share those thought with me." Awesome. So um you were speaking about um that like if defas don't care about privacy and decentralization nobody will like what's like one of the best tips you can give to new defils to um make sure they implement this in the best possible way if they have like no real experience with cyber infrastructure like where can they find the best information about this etc. First I will definitely check out the web3 privacy ecosystem map. I think like it's is great to see is a great common start right and then I was trying to embed uh these kind of like pillars in every activation that you're doing example when you're doing workshops don't start with your you know your SDK star uh stack shielding on the dabs start with actually like a landscape of tooling that you can use and this is why we're going and deep diving this tool so having this kind of like I divided I build a framework work on uh you know uh how to actually like approach an advocacy experience and the first part is all about valuedriven on boarding understanding why you're doing this use case and how you're doing and I think it's this valuedriven on boarding this kind of like no shield way to actually like driving advocacy is very powerful and if people are on board with building uh this specific way then you can proceed on a product conversion you can actually like go further and uh and and and actually like show how to build these specific things. But I think the first part I think 98% of company today are actually not doing that's why for example stuff like builder nights um has been happening so naturally and speaking about those topics you know we don't want to speak about specific account structure stack we want to speak about how 437 is shaping specific journey so technical debates and not product debates are super important thanks everyone Thank you. [applause]