MetaMask Snaps and permissionless innovation strategies - Francesco Andreoli | MetaMask

so welcome everybody and uh yeah great to see some faces that are here in the morning so well done well done for you guys to not party too much or sleep too uh uh yeah sleep too less anyway um let's get it started so like as as she mentioned a bit we will start speaking a little bit about snaps what are snaps why we are actually like create this kind of permissionless innovation environment and also like then I will drive a little bit into some like Deval Frameworks how many of you guys are developers so okay how many of you guys are de deel maybe okay okay oh yeah so probably like this framework at the end will be uh quite useful for you guys okay so um my name is yeah as you mentioned Francesco I'm part of the Deval team at consensus mostly like uh concentrating around like snaps lately I started as a protocol uh devel and I'm just helping out developers building uh cool stuff with uh with our products so consensus is the big company right and then you have like stuff like you guys used like in fura uh you can deploy stuff on like uh our ZK evm colinia and obviously then all the metamask developer uh tooling right and right now the main verticals are the DAP API metamask SDK for Native integration and snaps that's uh that's something that we will uh speak speak a little bit later um yeah I'm learning a little bit chess and uh I'm quite surfing so for you guys that want to play uh and win chess play with me awesome cool so um I don't want to bore you guys with uh there were a bunch of like different like slide before but uh I just cut a little bit through the chase you know why you know Web Two we're becoming all the product we are just signing uh specific transaction and data uh to like be corporate we are kind of like becoming uh kind of like our own product without even getting monetized so like I push here like five principle for trying to understand you know how we want to build the web three products in the in the future that has much more like a cons ual web from users to developers to uh company so first big part is the user uh owned account right you want to give uh uh people like fully control of their identity and in terms of like identity is not just about user exchange but also like anything like the request related I don't know how many of you guys are using like extension on like different browsers but a lot of time you have even no idea what you're actually like if the if the extension is uh uh manipulating specific data if they're accessing specific uh um uh specific like web apps and uh and you have no idea how to revoke all of those accesses second big principle is that we need to obviously like uh build for uh an accessible interface for uh users out there for developers to uh onboard more and easier like uh tooling and also like every of those requests need to be fully transparent so we we kind of like call like consensus uh uh you know uh the consent is King meaning like you really want to understand and give users a possibility to uh Drive their decision based on like data and based of like kind of like very instructural decision uh third part is like you want to have also like transparency request uh setups and this is probably the most priority part whenever you're building like web three uh products so anything need to be kind of like transparent right uh and one part I really like for like this kind of like fourth principle is every re need to be uh kind of like very transparent like users can be also entitled to revoke those accxes any time uh whenever they are right cool and then the last part is all about kind of like this permissionless Innovation concept that you want to share uh progressively meaning like you want to basically add modularity to every product that you're building and meaning like uh could be from starting from a specific like uh uh product setup and then you know the users can gradually like and progressively um use uh the product but it's also like a trust trust mechanism right cool so just a little bit to resume uh we want to also like Thrive uh and build for uh activating much more like uh the developer community and uh having different ecosystem fully kind of like interoperable uh build for utility uh and uh I really like the last point on extensibility as I mentioned before and also something that we're working on on on trust and Attis station obviously like we are in a path to decentralize our product you saw that right you saw with INF fura the din decentralized not infrastructure you saw with uh even like you know customer support with Village Dow uh you saw on different like uh uh products like you know with with linear Z KVM obviously like we are on the path to uh sequencer decentralization if you guys follow the last two three days it's it's quite interesting concept um and obviously like with metamask and the wallet and mobile uh the the idea is also like share progressively The Innovation with the uh with the community and you will see a little bit how so what is the future wallet looks like so I have no idea how the future wallet will look like I will tell you how doesn't H how does I uh think that it doesn't look like right so obviously like player versus player I don't think I I don't think we will have like this kind of like setup um anymore I don't think we will have customized Journey every every single users has different needs you will always see people that are more I don't know defi heavy you will see more people there are more around uh uh I don't know nft specific use case uh and and there is no kind of extension that fit everybody so I think like in the future we will get much more costumized Journey right and also like I'm quite excited you know to see much more custumized uh uh wallets in the future or like preet up wallets for specific use case uh one entity knows best I I don't know so I started uh maybe for uh was that four years ago and I remember like back back in the days the the the repo the metamask repo had something like 7,000 open issues of people that want to integrate people that want to like you know get feuture feedbacks and most important like people that want to extend the functionality of what the extension was doing at the time and basically that's kind of like how how things started right uh and uh I repeat a little bit like those those five principle repeating like if you want to kind of like move to a much more like consensual web we will need to also like push the users to be kind of like a very user Centric uh uh narrative so that everything that we're building is uh uh very transparent for like users to adapt and uh and give permissions trusting is the other the other big part so it's a consequence like trust that you want to have people to uh to kind of like uh trusting the mechanism but not trusting the people behind but actually like thanks to all these transparencies uh is part of the game um and uh obviously like decentralization why we're also doing this is also to empower the communities so you want to give community's instrument to push uh your product further but in a way that is fully owned by the community right there is this concept like power back to the community right and I think uh it's very strong because right now especially like in web 2 right we are getting like feedbacks from Community just you know on roadmap feedback on like open some opening some issues but you never find like really like active Community instrument for furthering develop your product further right extensibility modularity all these concept are are are quite big right this is why we're super bullish on this like permiss Innovation concept so we want to try to give instrument and build like a framework and kind of like a like um a language that you can start modularizing like specific like features and products and now we're coming to snaps so get some some air now but how many of you guys use snaps as a users until now okay how many of you guys before snaps will launch on prod you build a snap on flask okay cool a couple of people maybe you want some hackaton that's cool but uh but yeah so for anybody doesn't know snaps there are nothing else uh we kind of like defining as add-ons so they're basically like a functionality extension on top of what um the wallet does today right so there are different like use case right from uh from extending uh uh and leveraging your own API stack and I will tell you like why also like Snaps are kind of like Silo and why they are so kind of powerful to interact also with like external API but most important like on on different like use case basis right and I mention a little bit like if if we met a little bit in the aaton or during the conference uh I'm excited about different verticals right now there are 50 plus snap in out list but um uh super interesting like I don't know if you ever use like the BTC snap the Solana snap all these kind of non evm compatible snap uh are quite uh uh used uh today in the in the ecosystem and basically they're furthering extending the functionality of the W the wallet the cool thing is that you know like both the community the organization the individual contributors are building those nap right so they're they're fully owned by by the community um inability snaps those are the non evm compatible snap then you different things in the security section you have transaction inside snap I really like like a snap called from from the guys from block fense for example they are uh actively like tracking a a specific like um a malicious account and basically every time they are signing transaction they're giving you hints saying okay uh this address interacting previously with a malicious count so a lot of like kind of like red flxs alerting that's quite interesting uh on the a side you will see much more like NPC and TFA uh uh snap social snap is quite quite interesting I also like interesting to see much more like notification snap so everything that is happening with like you know game deps developer or game users that are getting notified on prod that's that's also like quite uh quite interesting so just to uh uh further a bit like the discussion so the most uh question I get is around security and around you know how snaps can interact with not just extension but also like external uh API suits right and and uh around security so we just need to understand something Snaps are nothing else is like an mpm package hosted right and they're fully isolated what does it mean this every time that the snap is speaking or interacting with the with the extension that will always like notified and get the users to approve uh everything right it's a fully siloed environment so basically they don't have access uh to any private key until you're giving actually like permission to do so so there is a fully transparence on what uh the snap is asking to the extension and what kind of accesses are being uh approved or not right so uh and and and this is why it's super important to understand this part because you get a lot of questions like oh like what will happen you know when when people are hacking this snap what what you know there are different like kind of like interesting like scenarios but uh long story short not only you will see uh both the source codes in in mpm the the the permissions being requested uh but also like you will see like also the DD the DD side uh and we're also working on a fully open source attestation service with Karma three laabs I don't know if you about these guys but basically like uh also like due diling snaps from the community will be much easier in the future because also like community members they have a strong uh uh you know snap uh let's say snaps development skills can start due diligence in in a first or a second like uh uh level uh the the snap going to the allow list this is just an example how you will see like um uh the uh like like the transparence process when you're installing a snap even when uh the snap is accessing like the internet or even like when when when there is some dialog Windows being showed you always like uh uh need to approve it right and that's kind of like it's it's really cool because you know I wish to have this for example when I'm dealing with extensions uh in my I don't know Chrome or bra browsers right and you know on the other hand also like you can revoke accesses anytime right you will have uh your snap in your setting on your extension metamask extension and you can actually revoke put in standby and do different things with the snap if you don't use it anymore like an example A lot of people are just using the Solana snap to get air drop from the Solana ecosystem because obviously like you have uh you have different uh uh non evm let's say uh ecos system like play that you can uh you can do that and on the unnown evm I forgot to say also like the the Stark net snap for example so Layer Two nonm compatible also is quite an interesting use case and um uh and yeah so just to resume s say cials they're leaving your wallet and basically like whatever you install you will see in your setting and you can revoke accesses and permission any time that you want right so you have this kind of like fully transparence as a users um so this is a quick QR code for uh the snaps allow list uh and that's for kind of like the users here they want to test it out um I will say like you know start with like whatever interest you the most maybe they just do some kind of like non evm uh transaction directly on your extension or maybe like you know uh if you're a gamer try the notification snap there is also a chat to chat snap super interesting from uh uh from uh from the guys like it's it's uh it's super interesting then you have you can also like move to a little bit more more on the security snaps that uh is giving you like is a giving you more data points to uh to uh sign specific transaction and understanding you know who are you really interacting with so different like uh categories right right now you will see like there is a full uh inability security coms and account management category and you can basically like filter and test it out uh for anybody that you know want to build a snap there are a bunch of like you know monor repo and example snaps you can take fork and uh and build on top of it and uh also like in this snaps Builder program basically it's nothing else as a a support basically system for like snaps developer or people that just want to start building some uh uh some uh some snaps and uh you also see a list in the GitHub discussion like of wish list snaps so if you guys you know have uh I don't know I will say no time to hack or something but in in the future that we will have also like some some bounties is acone that's also like a good inspiration of snaps that uh that are kind of like missing although like right now people are getting like crazy and building and building some specific use case so I think like my my theory is that we will see a lot of snaps kind of like competing with each other and seeing uh a very similar use case in the same time cool so um and this is kind of like the last part when I was asking like you guys like who is really doing a developer relations and how you guys are onboarding developers because naps is most important like a big use case and I just want to say that because I went through like uh all the kind of like the uh this like the snaps development phase from like from scratch being only like on on flask to kind of like production and even now that we are adding new and new categories and new uh type of snaps so I just want to mention that you know like building a cool technology is not enough what we want is also like building cool uh specific like building framework so that you know between not just Deval but activation any product out there that is Building Products need to activate their developer community and a lot of time like you want to have kind of you want to speak the same language right because a lot of time when we're giving like two uh talks or even like conference we're speaking about different metrics and uh it's always like tricky to uh to compare different activation because you are in different time of the developer in different time uh of the developer funnel in uh kind of like a on on different levels and different Target Persona developers and uh and uh and yeah and a lot of time like a lot of company don't know where you stand in this kind of like Builder Builder hierarchy of needs right and I want to show you a little bit these two Frameworks that I've been working for the past like year and a half to just standardize a little bit the industry around developer activation and why for example we are adopting this within uh within this zap uh snap framework right so I don't know if you remember these guys here like I studied that 10 years ago was called the mow hierarchy of needs basically like specific like needs for specific like type type of like level in the pyramid and basically I transform this to be a kind of like a hierarchy of builder needs and I was calling it like franisco hierarchy of builder needs but basically this is nothing else as kind of like the uh Builder hierarchy of needs uh levels right a lot of time we're speaking about different activation a lot of time we saying hey let's go to Virtual AC and then you're checking out the docks of this product that are super they're not really like on top notch right so basically I ask myself what are the uh main things that you want to have before even going on top right and I will just show you the first two right so Flagship event access to resources and basic education um for example this is like the most basic things that you want to push uh when uh when uh when adopting like those uh developer uh engagement strategy you want to have your your docks they really not on top of things but also like having specific tutorials even running like stuff like cons academy uh so you can actually like have this top of the funnel like fully um fully embraced for SNAP specifically right we did maybe six hackaton every hackaton with a two months lag we came back home and we revamp all the docks uh and every time that we were going to an acon with a different bounties we were testing out some specific feature that we were launching right and uh was a very interesting like process but the most important part is is that until those last part is satisfied you cannot move to kind of like the next one and the second part that we'll talk a little bit about in the final later is uh this kind of like safety level and this kind of like what I'm calling like building the safe space around developers people are not interesting to get shield on on on their face how to build your first nap now right they're interesting on use case and verticals right when you start to speak about okay notification snaps uh or like notification vertical extension for wallets are very useful for I don't know like Gamers then people are getting interested and they want to understand okay how I'm doing that right so building this safe space that is actually product agnostic uh is uh oh nice I can use the red one it's very it's very uh powerful right and those are not product specific so you will basically have expectation of like running like ecosystem Community calls like developer meetups on specific vertical and uh we started one maybe like almost two years ago doing this Builder nights Builder nights are known chill like uh meetups that are focused on specific topics we started doing on 437 we started doing on uh kind of like layer two and you know design uh uh narratives we're doing also like a builder KN this will be on 7702 uh for the peopleit in a construction uh here they will be in the uh tenderly office uh in uh uh tomorrow night I think and uh that's basically it right so going back second and uh that's it right so with this kind of framework basically you can understand and compare activations you can also like give kind of instruments to whoever is approving your budget or whoever like is driving those activation more more data points so I I wrote this paper that I presented in Denver uh there is bunch of like other stuff here and can share also like the slides about about it so we now went through like okay this is the hierarchy we are standardizing the framework and uh I also showed you like you know how kind of snaps came together and all this like principle around like uh consensual uh web three that we want a drive for building uh really like web through we three products one things that we are missing right now is um there are different type of builder needs and also like there are different type of uh levels in the funnel right and that's basically a coming in in my last uh in my last uh uh framework that is basically like trying to understand uh what znaps can do for which developer type because snaps is also like it's not super easy to pick it up right it's not something like oh let's go in crypto zombies and do some like solidity um uh tutorials you need to somehow also like have some some kind of like uh level and also like that's why it's super important to understand where in the funnel you are kind of like playing right and uh that's why like uh um I want to show you this these second things and I can stay hours to speak about this but basically like uh speaking about I don't know maybe 95% of company today in web 3 uh the majority of activations is done h on this part like the product specific conversion right so you will basically like direct developers to build on top of their technology directly without actually giving like a Why without actually giving okay why is that important and why you should build the vertical first before actually engaging in very product specific uh activation right and just to give an example for example like you know this could run like a snaps Community call this could be run like a you don't know like a snaps Workshop right and basically the cool thing is about like all this kind of like highest part is missing and this highest part is nothing else kind of like a this value driven on boarding and is not has nothing to do with direct product uh topics and I think this is like why is extremely powerful and I was showing you like kind of a lesson to learn that you should get today is that whenever like you're building your your DB you want whenever you want to like shield on like you know in in the industry like important part is like trying to build this kind of like first first funnel part and excite developers because you're an authentic kind of like you know an authentic like um uh not person but driving the product adoption through vertical and examples right like people as I mentioned before people are not interesting about you know like build a uh wallet to wallet chat uh snap right people are interesting to understand okay how we can make communication uh much more efficient between two wallets right and not kind of uh uh going through like a centralized provider and I think if you're tackling the conversation much more on uh on on verticalized and topic Focus narrative uh you're always winning uh this kind of like safe safe space part and then you can still run everything whenever you have your kind of like trusted like developer ecosystem then you can go further and saying okay now let's learn really about snap let's build our first snap together uh in in a workshop right but people understand also like why they are here and why uh they are kind of embarking this like uh development Journey so that's uh that's a little bit it right so just a recap because I think we're almost on time so we spoke about uh permission Innovation you know why we want to build with those five principle we spoke about you know why uh building a um solid product is not enough if you want to have a driving community that actually extend the functionality of what the wallet is today creating engagement and uh uh continue to improve is also like part of like uh part of the game uh why also we're doing this is nothing else because you know active feedbacks from the community are good but they're not enough people want to engage with your product road map people want to uh build actively new features on top of the product that's why like all this extensibility and modularity is key in order on in order like to get a better like let's say web 3 but more in in globed web three with everybody in the in the community uh and then we spoke about those kind of two Frameworks uh like this kind of like Builder hierarchy of needs meaning uh what a builder really wants and what you need to satisfy in order to really engage with the community um and then yeah and uh remember always like why we are all here we want to also like extend and modular modularize like uh uh like the like much more like those developer tooling but also we are here to engage much more with uh with uh users uh in in web 3 on a more transparent uh way and really like giving at the end of the day like more data points to make uh uh make really like solid decisions right so yeah that's uh that's a little bit it so thanks everybody and uh thanks to the guys awesome if you guys have a question let me know does anyone have any questions I can throw the mic no we have to anyone well I guess everything was very clear thank you once again uh thank you very much this is for you