Scale like Skyweaver, Rarible, and MCH by Catering to Both Web3 & Web2 Users Yong Zhen Yu

hey guys how's everybody doing i know it's been a long day at denver and a lot of people have just flown in hope you guys are feeling comfortable though um is my presentation up yup so okay so i'm zen i'm one of the co-founders of web3 off and i'm here to share a little bit more about what applications like wearable sky weaver or my crypto heroes are doing to get like millions of monthly active users on their platforms today and some of that tooling to help out with so helping like hoping that some of you guys leave off with uh ideas about what to include or not to include inside the application today and hopefully web through off is one of them as well now there's this thing in marketing the hardest thing to get as an application is actually the users themselves and how do you get a viral application now there's this concept in uh marketing called decay factor uh and it's about the users it's about your user's journey into actually using your application it starts from when your user hears about application to when the user onboards into your app to like engaging with your application and then eventually sharing your application itself now if you're k factor if your time's up all these things and if your k factor is above one that means that every new user that joins your application actually results in a new new user which it's a definition of virality if it's below one you have to make effort and get into getting that first user and then you know make effort into getting the next subsequent users so now a is more of like a marketing problem uh c and d is more specific to your application and whether or not you can resonate with your user whether or not you're providing them something good whether or not you're providing those like social sharing capabilities what dev tooling in the web 3 space can often help you out with is actually b and let's expand and break that down a little bit more so a user's onboarding can be tricky in dapps today a user first has to connect a key or wallet they have to basically download two applications if you're a mobile app uh the second thing is um they then have to interact with your backend or like uh the the chain that you're on be it like a one of the l2's arbitrary polygon or l1 uh that you're on and then before your user needs to often interact with your application they need to go through the fiat to crypto process which requires kyc which requires like it could could make them go through an exchange and all that so how do you cut that all down such that the user can actually start interacting with your application the first step is connecting with your key or wallet now if your application is maybe like a d5 application uh something where that somebody is like trying to invest into uh metamask could work really well right um metamask is i mean like the defacto sign today and definitely should be integrated into your application but if your use case is a little bit lower in terms of like you know the per interaction use case if you're building a game or an nft your users often won't want to spend that 10 to 15 minute like onboarding process to start using your application they probably stop once you ask them to download something else so what can we do to make sure that this user onboards into your app now that's web3 3 off and web through off basically provides that login box on the left it provides these it provides an alternative for user to use a password list or social login to log in and access your application now the first question that we get often when we see this is how is this implemented how is this non-custodial is this non-custodial in the first place right so how web3 off works is we basically work like an off-chain multi-sig i'm not sure if some of you are familiar with threshold cryptography npc or anything like that but we basically split a user's key up into multiple different factors these factors are kept on different access points that a user owns the first factor being kept on the user's social login of choice be it passwordless be it google and the second factor being kept on the device and that's how the the setup works so it's non-custodial google login or non-custodial social logins that you can embed into application directly now um these are some of the other toolings that you could be using other wallets which you could be recommending for experiences arjun is one of them which is a smart contract wallet ledges rainbow is a fantastic option for the mobile experience when you're looking for an nft viewer as well for the mainstream user experience we're the best alternative out there and i think you guys should use us portus is another one that you could potentially be looking into um you could be also choosing to integrate a wallet aggregator uh via like web tree model or block native that helps you like integrate all of the wallets in one web through off does that as well a wall aggregator that is and you guys are that that's also an alternative there so um yeah now the second step is allowing a user to building the infrastructure to allow a user to interact with your uh with your backend services as well as the node setup that you're on i think most of you probably will be familiar with the node setups like infera alchemy as well as the other ones out there those are what you can do uh in terms of authenticating into your backend infrastructure uh to prevent dos or to prevent spam on your backend services or to even just create a user account often what people do is they use a personal sign um either on ethers or web3js and you can build that yourself but there's also a lot of libraries out there that you can use to kind of like help you with that authentication some of them include that first one there it includes like sequences jwt token authentication includes sign in for therm as well that's being built by spruce id so these are some great alternatives to be exploring as well now last but not least you're going to need to be interacting uh you're going to need to let users purchase a little bit of that crypto uh be it like ethmatic or whatever l2 that you're on um to allow them to start really interacting with your chain or your application now um there are there is uh there are ways to circumvent this you can pay for the user's gas fees and that's called meta transactions uh there's some providers out there there's bi-economy there's open gas station network there are people that have implemented themselves as well so you can use the build versus buy decision um and uh if you don't want to pay gas fees for your users then you would probably want them to use a credit card to like purchase and make that uh and and and get some of that crypto before interacting with your application now uh there are quite a few providers in the fiat the crypto uh atmosphere and environment i would say moonpay is probably one of the best out there with moonpay one of the big things is with the nfts they allow you to because nfts could be considered as goods and services they allow you to actually skip the whole kyc process with their nft solution uh this is on polygon or ethereum l1 i think soon to be on the other chains as well other other providers include transact include ramp network include wire uh simplex often they do still require kyc at this point we're still evolving when it comes to regulation in crypto and hopefully we could narrow that down to just skipping kyc in the future but that's what we have today and that's kind of like where we are so there we go uh head on to web3 off that io if your application in particular requires a social aspect would like to leverage on users social accounts web through off is a fantastic non-custodial way to get started and plug that social authentication into your application so you can leverage on that moving forward