Web3 Native Messaging with Push Protocol

GM, GM, everybody. Welcome to what's going to be another great DevNTell. So if you didn't know, DevNTell is a 30-minute podcast held by the Developer DAO for people to come on to showcase their projects. It could be a new company you've started up, a weekend hack. Essentially, if you've got a passion for something or built something really cool, DevNTell is the place for you to showcase that. And today, I am excited to welcome Siddesh, who is a Developer Relations Engineer at Push Protocol. If you didn't know, Push Protocol is a Web3 native communication protocol that enables cross-chain notifications and messaging, group chat, video, and more for dApps, wallets, and services. So if you stick around for today's show, you'll learn all about Push Protocol and how you can add native messaging and notification support to your dApp. But before we get into the show, just a brief word from our sponsors.

Today's episode of DevNTell is brought to you by Consensus 2024 by CoinDesk. Consensus is the largest and most established global hub for all things crypto, blockchain, and Web3. Get your $299 developer pass today to connect with the industry's largest concentration of blockchain builders. Learn directly from top chains and protocols, as well as join the IRL Easy A Hackathon. Use the link in the description below to grab your ticket today. And for the first 30 people to register, you can save 20% with the code DEVDAO. That's D-E-V-D-A-O. Now, to today's episode.

Hey, hey, GM, GM. Welcome to the show, Siddesh. Happy to have you on, man.

GM, GM, Narb. Happy to be here. I'm super excited for this workshop, yeah.

Yeah, likewise, man. Yeah, I mean, Web3 messaging, it's a big thing. I don't think a lot of people realize how fundamental it is going to be going forward in the future, especially for mass adoption and the eventual user-facing apps that people are going to be able to build and have built now. But before we get into that, would you like to give a brief introduction about yourself, just in case people aren't familiar?

Sure, sure, sure. Myself Siddesh, I work as a Developer Relations Engineer at Push Protocol. Been in the space for over 3.5 years. I'm basically a serial hacker, you know, experimenting on a bunch of stuff, doing a lot of hackathons and stuff. And I also have to credit that I've been a great fan of Developer DAO, people from Developer DAO, and everyone, you know, awesome devs that I've been like, you know, look up to sometimes. These devs are amazing. So it's a great honor for me to be here today, a part of DevNTell podcast. Super excited. Thanks for having me here, Narb.

My pleasure, Siddesh. Yeah, and it's a pleasure to have you on. And I share the same sentiment. A lot of the greats in Web3 have made their way through Developer DAO at one point or another. So I feel you on that. I guess what brought you to Push Protocol?

Yeah, that's kind of an exciting point for me. I kind of started as a community contributor, not in terms of tech, but as a lot of community contribution in terms of content and a lot of other stuff in the Web3 space for the last two, two and a half years, even before that. And that's how I started contributing to Push as a community contributor. I'd be doing a lot of hackathons, I'd be writing some example projects and stuff like that. At one point, I met the founders in ETHIndia, which is a big ETHGlobal hackathon for India. And I kind of expressed my will to join the company and contribute even more, not just being a community member and just contributing to a broader vision of the Push Protocol's team. That's how I got into Push and everything has been a great run from that point. And we've been building really good products and too many things are coming up from Push Protocol's team side as well. But yeah, this is my quick intro how I got into Push Protocol.

That's awesome, man. Yeah, it seems your story is shared among many other folks who have begun their journeys into Web3. Just began with an interest in a given product or protocol, doing some write-ups and examples, and then meeting the founders at a conference and taking it from there. That's awesome to hear, man. Well, that's great to hear. I'm really excited to learn more about Push Protocol here. So if you don't mind, let's get going with the content.

Awesome, awesome. Let me quickly share my screen. Awesome. So for those people that haven't come across Push Protocol before, Push Protocol is basically the communications middleware of Web3. We basically build communication tools that are 100% or most importantly required by dApp builders and other projects that are in the Web3 space. I'll tell you why and why these things are very important, what are lacking and what we are trying to solve here. But today I'm going to talk about powering Web3 with native Push notifications and communication suite. We offer four power products, which is notifications, chat, and video calls, as well as spaces. I'll dive deep into each one of them as I proceed, but yeah.

So I'll quickly start with Push notifications. And if you have been in crypto for maybe like three or four years back, and you might have noticed when you start using an app for the first time, you'll be like, okay, I'm kind of going to make a swap in Uniswap, or maybe let's say I'm now a good Web3 user, I'm going to just go take some loans from Aave, or maybe let's say I'm going to deposit some money into Aave, or maybe buy an ENS name. Now you will know that none of these applications have interconnectivity or maybe there's no way of letting the users know that something has happened in the product that might be important for the user. So that's like a very big thing, right? For example, today you might be getting a hundred notifications and the first thing that you do when you wake up would be like checking your phone and then seeing, okay, I got this notification, I got this email, it might be something important. And that's how you basically start, that's how I start my day. But in Web3 that is a big missing piece, which is not taken into account in most cases. People don't give enough weightage, but it's like, say your ENS name is expiring someday in the next month, but you don't know because you bought it two years back and you don't know exactly when it's expiring. Once it expires, there's a bunch of complications for you to go ahead and register it again. What if someone goes and registers it before yourself? These are some important problems, right?

I think like in terms of finance, in terms of other use cases, even for example there's Lens Protocol and you want to be notified when there's something is happening to your Lens profile, maybe someone has tagged you or something is going on. These things are some things that are not accounted for. Most applications now have notifications, Push powers some of them. But usually like two, three years back there was no app that had this on their launch or on their application for users to use. So that made Web3 very isolated in the sense like I have to go visit my Aave profile or Aave's dashboard every day to see what's my loan health factor or something. That's kind of a not good UX for a user because I have to visit every day and make sure my loan is good or I have my ENS ready and it's not expiring anytime soon. So those are the very compelling problems. That's when Push team started. We started as a hackathon in 2020. So we started building Push notifications, which is a decentralized protocol. What it basically does is it lets any developer, any project in the blockchain space, right now in EVM, they can simply plug onto Push Protocol's notification system and they can send notifications directly to the wallet addresses.

So what that means is let's say you have a bunch of loans on Aave and Aave can easily send notifications to your wallet address saying your loan factor is this much and you have to put in more collateral or something like that. And this is pretty much fully customizable and that what that means is no one has to stick to few types of notifications or maybe like go through a bunch of applications to get started. Push is completely open, meaning you can even hop onto the Push website today and start using the tools available via the SDK or even if you want to do things from a smart contract level, which is also possible. So it's not like you have to have a Web2 way of doing it. For example, let's say if you don't have Push notifications from Push, you will probably need to set up your own server or something like that to listen to events in your smart contract and manually do some kind of an email or something to your user. But again, since we know that in Web3 we don't collect emails and stuff like that, we just know the wallet addresses.

That's where Push Protocol comes into play. You can simply send any notification to a particular user or your users. You can do it via a bunch of ways. Few of them I'll be giving you the information as we proceed. But again, the notifications that you send via Push Protocol are gasless. There are gasless ways of doing it. And it's multi-chain, meaning that right now we are in eight EVM chains, means you can directly trigger a notification from your smart contract in that particular chain itself or you can also you're also free to just set up your React or NodeJS server to trigger out those notifications based on some logic. Maybe it's like someone in Farcaster did something, you want to send notifications to someone, a wallet address, that is also possible. So I think that's how this product will be useful for dApp developers. And there has been many protocols that is using right now Push notifications in terms of Uniswap and some big names in the market, they use Push Protocol's notification service.

I'll probably define how you can use and what are the intricacies in using it. Also like few things we took into account while developing Push notifications is that to make sure that there's some control for spam. And there is some way that the user can control what they receive and what they see in their notification feed instead of just randomly some products send them a bunch of notifications. That is also again like a UX problem because what if you receive thousands of spam notifications? Some protocols don't have spam protection. So what if I receive thousands of spam notifications or something? That's going to be a headache. So we also have spam control feature where the user chooses to receive what they want. So ideally the way how it works right now is every dApp or every project, they create a channel in the Push network. And once they have created their channel, they are free to set up the channel details. And now users can opt in to the channel to receive the notifications. And in terms of let's say Aave, right? So Aave I want I am interested in only receiving the notifications about my loan health factor. So what Aave channel has done is they have defined few things. For example, as you can see on my screen, there are like for Thank You Arb, you are seeing giveaway alerts and a bunch of settings here.

So this is what we call notification settings. So what you can as a user what you can do is you can select what notification you want from a particular channel. So that's like I don't want any marketing notifications, I'm not interested in any such things, I just want notifications regarding my loan's health factor. You can pretty much enable that and the channel will only be sending you will be only receiving the notifications that's in that particular category and you will receive your notifications directly to your wallet. And from that point it's your choice to do whatever with it and you can visit that app or do anything. So this is a very good feature that we implemented recently based on the feedback that we got from our partners which were using our notification system. Which is a great start. And now I'll tell you there are from a user perspective, there are few ways how you can receive notifications. One being MetaMask Snaps. You can just simply download our MetaMask Snap. I'll quickly show you how it's done. Yeah, let's see that side by side itself.

So if you visit app.push.org/snap, and from this page you can pretty much click this button and you'll be prompted to click a approval message in your MetaMask and this Snap will be added to your MetaMask. And from that point you will directly get all the notifications about a particular address in your MetaMask itself. Meaning you don't have to go to anywhere to receive your notifications. You'll get all your notifications there and you can pretty much interact with whatever apps that's sending you notifications. And that being there, you can also visit our website, our dApp, to see all your notifications. Once you connect your wallet you will be able to see all the notifications. And you can also go here and explore all the channels that are available in the Push Protocol's network right now. And as you can see like Lens Protocol has a channel. If you subscribe to this you will probably get notifications regarding your account's likes and stuff like that. You can also choose what you want to receive from here. You can also do for the some channels. Some channels have set up their settings. And yeah, that's how you receive a notification. And you'll also see your notifications here if you haven't installed your MetaMask Snap. You can also see your notifications directly here itself. For sending notification you have to create a channel as I mentioned earlier. And once you create a channel you will be able to send notifications directly from this dashboard itself or you can use the developer tools to do it in terms of SDKs and if you want to trigger a notification directly from a smart contract that is also possible.

And Push docs, this is the best page to get started. And as you can see sending a notification is very simple if you want to do it from a JS server or something. You just copy-paste this and you are good to go send a notification to your users. And notifications being fully customizable, meaning that you can send a broadcast to every subscriber of your channel, or you can also specifically do a subset of people to send the notification to. And this can be very useful if maybe you have a community where you want to send notifications only to a subset of people who have bought your NFT or something. That's also possible. So that's there. And I would suggest like just go visit this particular link, which is push.org/docs and if you visit notifications, you have a very clear documentation. I would suggest you just visit this quick start which gives you a very quick way to get started. And yeah, you can integrate into your application. And as I was also mentioning you can do a bunch of things from your smart contract, that is also possible. If you just navigate to tutorials under the docs of notifications you will find a bunch of tutorials where you can send a notification from your subgraph. Just click here you will be having a full definition of how to do it via your subgraph. So these being some ways, there are a bunch of other ways as well to integrate notifications. I'll probably leave this link as well in the chat. Feel free to look into it. These will be very helpful if you want to integrate Push Protocol's notification into your smart contract, into your React application, or your NodeJS server.

And we also have few other developer tools like which has everything defined. You just have to add your JS logic and it works very good. And I would suggest to take a look at it. Yeah, so that's there. And also if you don't want to spend more time building your UI parts, we also have UI components. This applies to all of the products from Push. Push Chat has UI components which you can simply plug and play and your app will now have Push Chat and your app will now have Push notifications integrated seamlessly. So these will be some things that you would explore if you want to implement UI components. Now back to the presentation. I was here, right? So I think that's pretty much about notifications. And there are some few more things that I might explain but I think we might be running out of time. But feel free to take a look at push.org/docs and under notification you will find all the information that you might require. And now let's talk about chat. So chat is one of the interesting and exciting feature I personally love it in terms of what it has opened up as a dev whatever you can it has opened up a lot of opportunities and I've also built a bunch of things you know that are like for fun but it's really powerful and you can do bunch of stuff.

I'll talk about what we offer with Push Chat. Push Chat is a decentralized chat solution. It's a system where you can enable wallet-to-wallet chat between your users in your app. So let's say you have a social media application or any application, you want to enable a wallet-to-wallet chat and Push Protocol chat system would be the right fit for you. You can integrate Push Chat in less than five minutes with our SDK and your app has now wallet-native Web3 way of texting and yeah your users can just directly text with ENS names, wallet addresses and yeah that's the starting version. And the most exciting part that literally excites me is the group chat. And in group chat, you can have up to a hundred thousand members in a particular public group which none other solutions have right now in any even in Web2 solutions. Only like I think Telegram has it and mostly even WhatsApp has a limit of 1024 members in a group and no other products have 100,000 members in a public group. Which means in Web3 it's it might be a common thing to have 50k people or 60k people in a community because DAO might have many people like that, right? So you can simply now onboard all your people into one place. And now you can chat and you have all the Web3 native features like token-gated or custom-gated rules where you can specify that and since like Developer DAO has a NFT that lets access to Developer DAO Discord, you can define such rules in Push Protocol's chat group chats where you can define one or two or any number of rules being it holding a 10 NFTs or being it you have to hold some amount of tokens.

You can define those rules and then you can put it together. Then the user can only join if they satisfy their rules. That's there which is a very very interesting thing. Now you can probably say like just subscribe to my newsletter, you'll be able to access such chat specific exclusive chat with me. Those are some interesting use cases and now you can say you can build something like a pay-to-text app where I'm an influencer say say I'm an influencer, you can say just pay five dollars to text me or five USDC to text me. That's pretty much possible and it will take you very less amount in terms of integration. So that's a very interesting feature. And apart from that groups can be public as well as private. Private groups are encrypted, meaning that only the people that are involved in the conversation might be able to see it. So those things we took care in terms of security. Everything we have taken account in that as well. And we also have some integrations which use Push group chats and chats. I'll talk about it.

So yeah, those are some Web3 native native use cases. I really loved when when Push Chat launched and I kind of like build some really crazy things, which are like simple but really really fun useful for Web3 degens. So the use cases is very much very high. You can build anything. You can ask us if you need a specific feature, we look into it. So yeah.

Before you move on, just a quick question on the chat. Does it cost money for a user to post a message?

Yeah, so I should have mentioned this. At this point, even Push notifications is free of charge for users. Only the channel owners will be staking some amount of PUSH tokens to create their channel. And for Push Chat it's completely free. It doesn't charge you or cost you anything to get started or use no matter like who you are, you can integrate our Push chat systems and it's free to use. Very good question.

Gotcha, gotcha. Cool.

Yeah, so yeah this was something that I mentioned. You can define these rules. Then your users can only join this group only if they satisfy these these particular conditions. And you you you can also mention some rules like Guild, the platform for communities, right? You can also mention those rules where you have to be some you have to have that particular role in Guild. Then only you can join this group. That's pretty much possible. So yeah these are there. These are very powerful and I personally this is my favorite favorite feature in Push Chat. So yeah.

And one of the important partners, I think the image is not loading here. Yeah, it's here. So recently Unstoppable integrated Push group chats into their messaging product where now any any user in their in their particular product can create groups, maybe like a domain gated groups. For example, let's say .x holders or .pudgy holders. And they have been experimenting. I I believe they have almost now like 15,000 groups. I might be wrong in terms of the number but they I think last time when I saw it was like some 15,000 groups from Unstoppable side. You know a bunch of NFT degens, a lot of people. So that's a great great example of how you can use Push Protocol's powerful chat systems.

So moving on, this is the most favorite feature of mine: Push video. This is the decentralized version. So when I when I spoke about Push being the the communication middleware and this is where what I was meaning. You have chat, which is the basic basic requirement, you know, for people to communicate within your apps. And now you also have video solutions where you can enable wallet-to-wallet calls. Let's say I can call a let's say vitalik.eth. So you can pretty much call any Web3 EVM address. And nothing else is required. Everything is like, you know, purely Web3 standards. You just call that's how it works. And this is a very interesting feature because I kind of like went rogue into building stuff like, you know, building some Omegle some phone app where you just like have a app on your mobile and you type in a ENS name and you just make a call and then they receive it and you talk about it. It's just like having a normal call apps but you can it's fully Web3. And you just don't have to input your mobile numbers or give up some private data. Now it's just like directly calling your wallet. So that was very very interesting for me. And you can today integrate Push video. I'll be showing how, it's very easy. Trust me when I say this, it hardly takes you five minutes to plug in plug in the SDK and you'd be good to go.

The last we also have Push spaces, which I have not mentioned here. But you can still integrate Push spaces, which is the audio spaces equivalent to Twitter Spaces where you can let people join with their wallet addresses. Again, why is it powerful? It's powerful because you all have access to Web3 native features like, you know, NFT gating, token gating, Guild gating. You have access to all these stuff. So now you can say who can join my space. It can be an exclusive space like that. So that that that's a very important feature as well. So you can also build using Push spaces right now. I'll be dropping the links as well.

So yeah, that's about the product right now. These are the products available out. People know about it. And this is something that we are about to launch in the Q3 of this year, which is the Push network launch. It would be a proof-of-stake network where Push nodes can be run by community and they contribute to the community and they have will have some incentive mechanism going there to make sure that their work is, you know, incentivized. And basically now this part will be where Push organization will be decentralizing its efforts. Right now the nodes are run by the Push Foundation but moving forward into Push PoS launch, it will become like a way where the community will be able to take, you know, take this up and they can run their nodes and they will be validating all the notifications, their chats, and everything that comes to the network and they'll be a core part of the Push Protocol ecosystem of projects using Push notifications, chat, and video. And I'm not going diving deep into this particular product but this is something that's exciting, launching very soon. I think we also have some Alpha Access NFT which lets you, you know, get access to these nodes as soon as they are launched. But yeah, feel free to take a look at our Twitter where we are updating all those details.

Yeah, as I mentioned previously, these are some of the numbers since we launched: 80 million notifications, 227,000 subscribers, and a bunch of integrations including top protocols like Uniswap and, you know, some other Aave and some of these protocols use Push Protocol today. Yeah. So I think yeah that's about it, that's that's what I exactly wanted to talk about before doing a really really run on how to implement and how you can get started today. I'll just quickly show you how you can get started with Push Protocol.

So right now when you visit the app you can see inbox where you will receive notification as I previously mentioned. You also have access to spam box which is like the notification that you are receiving even without opting in. So these will land up here so you don't have to, you know, just be reading all those unnecessary notifications in your inbox. That's there and channel we spoke about it. And chat is, you know, you can chat with any Web3 wallet. You just connect your wallet and then you should be good to go. You can text any Web3 domain, Unstoppable domains, ENS names, anything you can do. You can pretty much chat with anyone. And this is just a just for the user's point of view I'm talking about and yeah it's oh, Alpha Alpha Alpha. Okay. So Push Chat also supports Frames that you had built with Farcasters. Now live, I think we never announced this but I think this will be where we launch this. Exciting.

Alpha on DevNTell, there you go.

Yeah, yeah. For example, being able to send funds directly from your chat, yes I'll take it any day. You can now you can put put this link your payment link on your group chat, let people pay you. I'll take it. So yeah those are the things that are really really exciting. I think we'll be launching this very very soon. As again spam is a very important feature that we have, it will land up in your requests tab you have to approve it, only then you can use you'll be able to text with them. So those are the primary things that we have. And as far with Snaps, I mentioned you have to go here and then you can just install your snap from here. So this is the user's perspective. If you're a dev, I will show you how you can get started.

This is the best place, push.org/docs is the best place to get started with Push. And I should mention we also have a grants running, I think it started it runs from last year. And we have a allocation of up to $1 million in terms of offering to people, to projects. Right now there are few projects that are working with us in terms of integrating and using Push Protocol's products: chats, video, notifications. And if you are someone that's building a dApp, feel free to check it out. I think every app needs will need notification, chat systems at any point of time. So feel free to check it out. I'll be happy to, you know, maybe help you even more if you can text me or DM me. I'll be happy to help you and, you know, get you going. So yeah.

Siddesh, we have a question around how spam is detected. Could you perhaps briefly touch on that before we move on? Yeah.

Right, yeah. So in terms of spam in notifications, the way how you detect is like, you know, the user has to subscribe to a channel. And every notification that comes from that channel is put in the inbox and we don't consider them as spams. But since your wallet address is public, anyone can send you notification, right? So that ultimately lands up in spam. That's how you can you can still go to spam tab and then just, you know, see those notifications. If you think those are something that you want to receive, you can accept it. That's how spam works in notifications aspect. And in chat, the spam control the way how it's done is like every chat will land up in your request tab only. And the only chat that you want to text will land up in once you accept it. If you have seen here, I have accepted all my chats, all my requests that have landed. So all of them are here but tomorrow let's say some guy is texting me right directly to my wallet address. But you know even you can text me directly from this just copy-pasting this wallet address and I'll be receiving it as a request. Then you can you'll be given a way to accept it or decline it. Once you decline they won't be able to send you messages anymore. That's how it works. They've kept it like very simple so that we don't have to, we don't want to complicate stuff. So that's how spam detection works right now. All the accepted chats land up in this particular tab.

Great question, great question. Yes.

Very good question. Awesome. So we were talking about the docs. Yeah, so the best part about the the docs is like, you know, it gives you a way to just get started in less than two minutes. And even if you want to start with integrating your chat into your application, it hardly takes it's it's going to take you very less amount of time to get started. We took a look at notifications, you can see chat, video, and there are some example apps as well and some hacker guides, a lot of other stuff that you should take a look at. So I'm going to go to Push chat. You can see in the quick start section, you you can see what all the libraries that you need and you can simply copy-paste these codes. So the most important thing is like we we use something called Push profiles and that's how we decrypt, encrypt stuff and you know do a bunch of things in the backend, abstracting everything from the user. You just have to initialize the user and the user will be asked to sign a message. That's how they get access to their particular account. And from that point they can text and they can receive all the chats directly. And you can see pretty much these are code snippets. I don't have to even explain, these are like pretty much self, you know, you can just go ahead and then do it.

And the important thing that I want to talk about is, so the idea about Push chat being is like you can pretty much do every almost almost everything that you would do in a normal Web2 chat. For example like sending texts, images, files, media embed, reactions. And also you can also pass in some custom messages. For example if your app requires some some kind of a custom way to do a bunch of things. For example let's say you have a dApp and every time someone sends a message using your app you want to have some extra metadata. You can also add that thing those things into your app. So you can read it when you receive it. Those things are there. And we have ready-made UI components. I think this is the best part to you just can go visit here and you can just you can try it from here itself. We have a live playground. Let's visit this part. Yeah, okay there is some problem over here but but ideally it should work. So the way how it works is you can this is the code that you need to get started with a chat support bot. If you want to integrate a Push chat, this is the code that you would need, just few lines of code. That's it. Like as I mentioned like you know it's hardly takes you like seven to eight lines to have a fully functioning Web3 chat in your particular application. Yeah that's powerful enough to you know get started. And you you will be seeing some kind of an UI like this where if it if it's a group chat, the user will be prompted to verify their access and then you know get started in texting and those things that we saw here as well, right? These are pretty simple.

This is how it would look like. You can text here once you have access to that particular group. If it's a private group you have to verify access and those things are also handled there. So just like just copy-paste this code and your app now has fully functioning Web3 native chat solution. And there's a bunch of things that you can do, you know you can see all these components. Feel free to take a look, I'm not going to go into it. But but yeah, you have access to all these components. And if you just want to have Frames into your chat app, you just need to just implement ChatViewBubble and your app has a fully functioning Frames into your chat app. Everything is simplified here, you don't have to do it anything from scratch. So yeah, that's there. And yeah I think pretty much that's that's about it. That that that's something that I would suggest. And if you want to get start try chat and video before using it, this is the way. Just go to this link and I'll show you. It's not here.

So this this demo app lets you do a everything that you can do with the SDK. And I would suggest you go here once and try out few things before you you get started so you get a idea about what's there and what are the methods available and everything. As a developer this can be very helpful. And the link is react... maybe I can drop it drop it somewhere. Let me just drop it in the comments I guess.

Yeah, yeah for sure. And then we'll have that also available in the YouTube description as well. So folks can play around. Yeah, great question, great question. Yes. Awesome, awesome. Yeah, and unfortunately that brings us to time here, but really really appreciate you taking the time, Siddesh. This was very informative, very interesting. There's some things in here that I didn't even realize Push was able to do, like the the video and the group chats, which is really cool. And looking forward to people in DD playing around with that and coming up with some cool projects, either in their next hack or weekend project. Let's see those Web3 Zoom apps, folks. But yeah, that's excellent. And like I mentioned before, all those resources that Siddesh has shared will be available for you to browse around if you click in the YouTube description as well as I've dropped them in the comments as well. But before everybody leaves, I'd like to share the QR code for those of you that stuck around till the end for you to claim your DevNTell attendee NFT for being in attendance today on DevNTell.

So what you'll want to do is scan this QR code and fill out the form, and you'll be airdropped a NFT for being an attendee on DevNTell today on the Base network within a couple of days. So you'll have about an hour and a half from now to be able to claim the NFT before the form closes, so definitely get on that. And I just want to wish everybody a very happy Friday, happy weekend. Thank you again, Siddesh. Really appreciate you taking the time. And that will catch all of you back here next week for another episode of DevNTell.

Thank you guys, and thank you Narb. It's been a wonderful wonderful event. And have a great weekend guys. Bye-bye.

Yeah, likewise. Right on. Have a good one. Bye.