Beginner's Workshop: What to Expect at ETHGlobal Mumbai 2026

Transcript

Just going to give this another minute or two. Just need a few final setup steps and remove a bunch of the note-taking eyes that will be uh spamming our channel otherwise. This is going to get super annoying. Just bear with me for a second. Just make sure that nobody sneaks in here. Perfect. Almost ready to go. There we go.

Let's try this again. Good morning, good afternoon, good evening, everybody. My name is Pascal. I'm head of success with ETH Global and I would like to welcome you to this workshop, What to Expect at ETH Global Mumbai. This is our final in-person hackathon of the year and it's going to be one of the larger ones. So, we are very, very excited about this and this workshop is primarily to get you up and ready for the event. We're going to go over a bunch of things like the overall hacker dashboard, the venue, about what Pragma is, when this is happening, the schedule, the prizes, how you can set up, join a team, how the whole team work in general works, and how you can actually submit your project. I'm going

to walk you through this entire process. Just as a note, this workshop is getting recorded and live-streamed to YouTube so you can always rewatch it if you have any questions. In addition to that, if there's anything that's unclear, if you have any questions, please um just post them into the chat and I will go over them like one by one throughout the workshop or at the end. And at the end of the workshop, so this is roughly going to be like 50 to 60 minutes, going to have like 5 to 10 minutes just to go over a bunch of questions um that you might be having. Fantastic.

Okay, sweet. So, uh everybody here in this call is fully confirmed, otherwise you would not be joining. So, even if this is your first time, your second time, your 10th time at an ETH Global Hackathon, welcome. We're happy to have you. We're really excited. This is the uh main page that you have all seen. It lists a bit of information about ETH Global, about what we've done in the past, what we're doing, about the specific tracks, about the amazing prizes and partners that we're having, about the rest of the event week. As you all know, this is happening uh at the end of and partially during Devcon. A note, we're not the Ethereum Foundation and we do not run Devcon, so this is completely separate. We just run the Hackathon and the Pragma.

So, on the schedule, you can um pretty much see everything that's happening before and during the event. So, we already had a team formation session uh 2 days ago. We have another one tomorrow and we're going to have one in person as well on the Thursday of the Hackathon. So, the overall schedule, if you hacked with us before, we usually run our events Friday to Sunday. Due to uh the festivals on the weekend, we moved this for 1 day, so we have the Thursday, Friday, and Saturday instead. So, everything that's usually Friday is Thursday and everything that we usually do on the Sunday is on the Saturday.

Please keep this in mind, especially when it comes to the submissions. So, we open up the event registration at 1:00 p.m. on the Thursday. Really, really important, you cannot enter the space before 1:00 p.m. So, even if you're traveling from somewhere else and arrive earlier, we cannot let you in before 1:00 p.m. So, the registration / check-in happens starting 1:00 p.m. and we open it up until 10:00 p.m. So, you have to check in between 1:00 p.m. and 10:00 p.m. on the Thursday. Starting 3:30, we have a bunch of workshops happening with our amazing partners in several workshop rooms. You can check

all that stuff out here. Then we have dinner as like the first main meal that we have at the weekend. Just as a note, if you never attended our events before, uh we have 24/7 snacks and beverages and we have several major meals like brunch, dinner, lunch, and breakfast depending on the day. You can check all that out on the schedule, so you always see when what is happening. Then the opening ceremony starts at 8:00 p.m. and at 9:00 p.m. is where hacking starts. Really important, hackathon or the actual hacking time is 36 hours. So, from 9:00 p.m. on the Thursday to 9:00 a.m. on the Saturday.

So, you have 36 hours to build your project. You should not start earlier. Like all the work for the hackathon, regardless if it's starting from scratch or continuity, I'll explain something about that later as well, has to be done during those times. So, between 9:00 p.m. and 9:00 a.m. Then we have another one of those lovely team formation sessions in person. So, if you're hacking and you want to get more people into your team or you're currently solo and you want to join with other people, you can meet me at workshop room number one at 9:30 p.m. and we can help you form teams and brainstorm some ideas to get you going because personally, I think hacking is more fun together with people. You're in a room with thousands of some of these

smartest people in the space and it's really great to hack with you people, to get to know them, to build something fantastic. Much more fun than just hacking solo. You'll learn much, much more. Trust me on this. Then registration, as I mentioned, closes at 10:00 p.m. Important, registration can be misleading. So, everybody that's going to come to the event has to be confirmed before. We cannot register any new people like on that day. So, you would have to come in with your QR code on your ticket and a piece of ID that you can bring to the event that we can verify this is you. You get your badge and wristband that you wear with you the entirety of the duration of the hackathon to get access to the event.

Sweet. And then we have a midnight snack or late night snack at uh 11:59 or pretty much at midnight. On Friday, there's going to be brunch, dinner, and a late-night snack. And again, we have overall snacks and beverages 24/7, so you always have something to snack on. Really, really important, you can stay at the venue the entire time, but you can also leave and re-enter as long as you have your wristband and your badge with you. And then on Saturday, we have breakfast at 8:00 a.m. and the project submissions are due at 9:00 a.m. Really, really important, the only requirement for you to receive your stake back is to submit a project. It doesn't matter which state that project is in. It has to be submitted by 9:00 a.m. There's no

exception, so make sure you at least submit your project once by 9:00 a.m. I'm going to show you how all that works. And then judging starts around 9:30, lasts around 3 hours for partner prizes as well for the main finalist judging. Going to talk about that in a bit as well. We have lunch at 12:30. We try to find to notify all the potential finalists around 3:15. Closing ceremonies and then the uh closing, like after the closing ceremony ends, the hackathon officially ends and everybody gets escorted out in like a lovely and nice way.

Um a list of all of our partners. We have 12 and this is the location. We're also [clears throat] going to be having a venue map on this page in the next couple of days as well. So, this is going to be at the Geo World Convention Center, which is the same location as Def Con. So, if you're attending Def Con, you're already already know where to go. We're just in a separate uh hall, but it's the same venue, it's the same building. We have a list of FAQs that I would highly recommend everybody to check out. Sweet.

Now, I would go to the Well, not the one I wanted to show, but either way, going to show this one later. So, um the main thing or like your main place of navigation, your main hub, your main home for the uh duration of the hackathon is going to be your hacker dashboard. The hacker dashboard has everything that you need to know and everything that you need for your project submission. So, it you can select which mode you're hacking on. One would be from scratch, meaning you come in with absolutely nothing at the hackathon. You start at 9:00 p.m. on the Thursday and you submit your project by 9:00 a.m. and the stuff that's being built at the event completely fresh gets submitted as new project. Then we also

have the continuity, which we started doing this year. This means if you already built a project at a previous hackathon or it's your startup that you're launching and you want to add a new feature to the event to this project, you can do this. Like the only requirement is the feature has to be completely open source and only built during the hackathon and you have to completely show what was built at the hackathon and what was built before. So, for example, let's say you built a project at ETHOnline or even you built a project in Tokyo a couple of weeks ago, you want to continue, want to add a new feature because you want to integrate, let's say, World, you want to integrate Uniswap, you can do that at the event.

And we have separate prize listed for from scratch or continuity, which I'm going to show you in a bit as well. Really important about this, you can only qualify for the prizes within your tracks specifically. And as for finalists, there's going to be finalists in the categories of continuity as well as building from scratch. Okay. So, the dashboard has also a bunch of packs, which I'm going to explain later. We can create our project, which we're going to be doing in a couple of minutes. You can connect your Discord account directly here, which I would highly recommend. You will automatically get added to our Discord server and if you are fully confirmed and you sync your account on Discord and ETHGlobal, you automatically get access to all of the event channels,

which look like this. So, you have a Mumbai chat, you have all the partner channels, which is great because you have an overview of all the prizes and you can chat with the DevRels there directly as well. I always recommend just to reach out to them and talk to them in person, but sometimes people are there, sometimes stuff can be handled async, so you can just drop your questions in here. One thing I always recommend is do not ask to ask questions. Just ask the question. Don't try to hide certain things unless it has to be like 100% confidential. Okay, sure, but most cases it's just a question that you have. Maybe other people have that question as well. Just ask it openly so other people can jump in and help you out.

Um we're going to have a new networking app at the event. So you can scan everybody's and get connected with them. It's double opt-in, so you can just like randomly scan people. They also have to accept and you can share your socials, share connections. You can connect with DevRels, connect with mentors that directly and you can have like a list of all the people that you interacted with at the event. If you require a visa letter, you can request this here. This is just a form that will open up. Check and show you. Um you enter your full name, your date of birth, and your passport, and this will generate a visa invitation letter if you need one >> entering um India.

>> Sweet. Um overall you have an overview of what to do. So what to do next? The thing that we're going to be doing now is creating a project. This is something that you can do already before the hackathon as long as you don't actually start building the project. This is completely fine. So this is what I'm going to be doing now and what everybody has to do in general. Really important, if you work in at a team, only one person has to do this, but everybody can uh update that form as well. So a few things to put in here. For the sake of time, I'm going to copy-paste a bunch of stuff. Please do not do this.

Actually take time and think about something useful here. Um for the project as well, I'm going to select uh which um category this belongs to. I'm say this is data analytics and for um emojis that I want to select, let's assume, yeah, tooth works fantastic for my project. So here's an acknowledgement and overall. So please read through those things because been doing this for like over 2 years now and I get the exact same questions and complaints every single time because people do not properly read. So, make sure to read all the requirements. So, you have to start your submission early. Do not wait until the last second because you think you can push this entire thing through in

like 5 minutes. This is not going to be the case. Um if you want to opt in for the live judging for the finalists, you're going to have to have a video. This is not optional. So, for the finest track, you have to have a video. So, make sure it's recorded properly and it fulfills all those requirements. So, videos have to be between 2 and 4 minutes long, not shorter than 2 minutes, not longer than 4 minutes. Has to be 720p at least. This also means the resolution, not just the quality. And it has to include audio of you speaking and not music. Really, really important. And as well, commit frequently to a public repository, meaning do not just commit uh submit the project with one giant

commit. We want to see how this project's being being built out throughout the hackathon. After we accept all this, we create our project. We have a few extra pieces of information here. Since we started from from scratch, the project should start from scratch. Use version control, open source, and the video. Again, if we only opt in for top 10, we need it. We generally recommend for you to record a video because it's nice as a fallback and for people to watch it to understand your project a little bit better. But yeah, just make sure to read all these things properly. It's not that much text, so everybody should be able to understand that. I'll just feed it to your agent.

Okay, cool. Um as we said, start submitting early as soon as we open it up, usually on the second day in the morning. We cannot submit this yet because project submissions aren't open. So, for demonstration link, really, really important, the demonstration link should be a link to your actual project. So, your project being deployed somewhere. This should not be a YouTube video. This should not be the GitHub repository. This should be the live demo. So, if you put something, doesn't have to be on a domain, can be on Vercel Railway Render whatever but the domain should be here or like the URL should be here so people can look at it and check it out. And really important, if you want to qualify for the finalist teams, it has to have a live deployment.

Then we enter a short description. Again, I'm just copy-pasting a bunch of stuff, but this is all going to be showing on the showcase, so make sure it actually describes on what your project does. A longer description, and also worth noting, this is what your project is going to be judged by by the partners. So this is what they're going to be seeing on their end, so make sure to fill this out. Like how it's made, the description, be as detailed as possible. I would recommend not to just hand this over to AI because you're going to get a super long text with not a lot of information in there, and people are not going to be reading it. So take your time, write this out properly. This is something you can do way ahead. You It doesn't have to be like in the last

couple of minutes of the hackathon. Um if you attended our events before, um and have complained about this not auto-saving, this now auto-saves. So which is kind of nice, so even if you accidentally leave the site, something crashes, you have all your information here. Then we will have to connect a uh GitHub account to um to ETH Global or like a uh Oop. To connect our repositories. Just going to do this in the background real quick here. Just give me a sec. This is important so we can verify that you actually own the repository. So this has to be uh done or can be done by only one person in the team. Um the person has to have permission of that

repository or has to be in the organization that owns that repository. So I have my test account here. Now I can select up to five repositories to add. Why up to five? So you can put everything in a mono repo, but if you have it like split up, let's say you have different front end, contracts, and back end, or whatever you want to use, you can select all that stuff here. So you can technically add multiple repositories. It doesn't necessarily have to be just one. Just going to add a bunch to show you what this looks like, and then you can select which one is which, but one has to be the primary one. You can always remove those or switch in between others as well. So, again, it doesn't have to be just one.

It can be one. Perfect. Then the other thing that we need is images. We need a logo, and everything needs a cover image. Those are the requirements. I'll just say like the ideal ratio, so it looks nice. Um the reason why we're doing this, I'm going to show you here, is because every single project that is getting submitted at an ETH Global Hackathon is going to be showing in the showcase page. This is the cover image. This is the name. This is the short description, and the Hackathon where everything is built. And if you would just go into one of those projects, you see the video, you see the screenshots, and you see the logo. So, this is why you fill all of this stuff

out. Let's see. Yep. So, I'm just going to be uploading a bunch of images here. Bunch of screenshots. Again, these are just placeholder images. You can keep them as placeholders, but just make sure that when you're actually submitting, you're submitting them properly. Fantastic. Can I hit continue? It's going to see if all of this stuff works.

It's really important. We're going to have to have at least three screenshots. It can be up to six. Have to be at least four. Uh then we have to fill out the tech stack. So, what we used to build out the project. So, um which developer tools did we use? Let's just see. Uh say we used 1 inch, we used Alchemy. Um which blockchain we used? Um let's say Arbitrum, Arc, Zero G, and Base. Programming languages, obviously using Assembly, cuz it's the best. Let's say we're using uh Fast API as a web framework, database we use Couchbase and design and say we built everything on Figma. If it's not there, it doesn't have to be in here. This is just for

overall to see what people are using, what people are building, but just make sure to fill this out. If anything is missing, you can let us know, we can add it afterwards. And if there's anything that's not on the list and you want to keep added at this here. Cool. Something they if applicable I think at this point is kind of useless because everybody uses AI tools, which is completely fine. You can use AI kind of say it's encouraged to build the tools. I would highly recommend not to use AI for ideation because the results are going to be really really bad.

You're not going to have a good time, not going to get any bounties from the judges and you're probably not going to get finalists because all the AI generated ideas that we've seen in the past were really really really bad and it's the same over and over again. For coding assistance, for development, sure you can use it, but just make sure to actually disclose on what you built this for. This is not going to be you're not going to get penalized for being honest. So if you say I built this entire thing out using AI, sure, but just describe on how you actually used it. That's all we're asking.

Then comes the fun part. So as you as you saw earlier, we have over $150,000 in prizes available and we have two modes. I'm going to spend a little bit more time to explain those two. Again, if you have any questions, feel free to just put them in the chat. So you can select here which ones you're going for. So building a completely fresh project, that will be building from scratch. If it's continuity, you have something existing, something that was built before and you're adding a new feature, not something that you started like a day before the hackathon, but an actual existing project that you're building closed or open source and you build a new feature on top of that open source, you select continuity.

Important, all the team members have to be on the same track. So for the submission types, we have two as well. One would be top 10 finalists as well as the partner prizes, and one would be partner prizes only. If you opt in for the top 10, meaning you would go to a separate round of judging to be eligible for the finalist prizes, to be eligible to present your project live on stage at the closing ceremony, and be crowned amongst the top eight to 10 teams depending on the quality of the projects, a video and a live deployment are required.

That means the video has to be between two and four minutes. It has to be 720p at least and audio but without music. This has to be done, otherwise your submission will fail. You'll not be able to qualify for finalist judging. So, make sure that you have a live deployment, not just a video, a live deployment plus the video. And the video has to be uploaded to our site. I'm going to show you how this looks like as well. It cannot be like a YouTube link or something similar. It has to be uploaded to our site, and this can take a little bit, so please do not wait until the end. And also, recording a four-minute video takes longer than four minutes.

And also, you're more than welcome to edit and cut your video. It does not have to be a one-shot. So, if you have like waiting times, like something that has to be cut out, um you can just do that. That's not a problem. Okay. Um which partner prizes are you applying for? As you can see here, you apply to a maximum of three partners, not three bounties but three partners. Meaning that depending on what you build, it is possible that you can qualify for multiple bounties within one partner, but you can only apply for a maximum of three. So, let's say you're building a project, and you build something that's like on a bounty for the Ethereum Foundation, for ENS, and for Chainlink. Those are the three that you can use. Anything else will cause an

error. So, those are three are the maximum that you could use. You can technically implement every single thing, but you can only qualify for bounties for up to three. We implemented this rule because most of the times when people were just adding a bunch of integrations, the applica- the projects got way, way worse, they got way, way less money, and nobody was happy. So, make sure to properly think about what you implement, and use fewer integrations, but make those integrations count, and make them really, really well, and execute them super well within the project. So, there's a maximum of three that you can select. You can go with one, completely fine.

Important here, write a few sentences, minimum of 20, uh like uh uh 20 characters, or like how you integrated them, or like um why you should be eligible for that prize. So, um let's say for the Ethereum Foundation and their bounty, you just read what they want, and you filled all that stuff out. Then here you would, for example, link to the uh line of code, or to the block of code where this would be sent in. Here you can actually rate how the integration was for you. So, if it was like really hard, or really easy, or if you have any feedback, please provide that feedback with them, because this is going to help bring the ecosystem further, because every single thing that you can be reporting to the teams, saying like, "Hey, for example, let's

say on Arc, we found a bug, we found an issue, this was really terrible to integrate, the the documentation was bad." Just help them improve it, it makes it better, and the chance of you getting rewarded for fixing their stuff, or helping them improve it, is much, much higher. Fantastic, and then here, yeah, provide feedback as much as possible, be transparent, be honest about it, but also uh with every feedback, uh yes, uh be fair. So, don't tell anybody, like, don't say, "Oh, your stuff sucks, you're you're assholes." This would not be great. Be constructive, be honest, and uh you're going to be awarded for that. And again, if you have multiple um technologies that you integrated, but you're just not going to

be qualifying for, you can still mention them directly here as well. But really, really important, the only ones that you can qualify for are the ones you select here, and you can select a maximum of three. So, really important, you have to check those boxes and you fill out that information. Otherwise, you won't be able to qualify for those prizes. Fantastic. Just a quick thing. You write like some workshop. Okay, perfect. Cool. Then we have the video I was talking about so much. Again, I'm going to keep repeating this because people will still completely ignore this between 2 and 4 minutes, 720p, audio without music.

So, um let's see. I should have a video here that would meet those requirements. I do. Perfect. So, uh you have to upload the video again directly to our project. If you're getting annoyed by this, I'm sorry, not sorry, but I'm just going to have to repeat it because again people will ignore this. Um video upload can take a while, specifically um if hundreds of people try to upload their video at the same time. So, make sure to plan enough time for this.

Um there's going to be a few checks running to see if the video matches all the requirements. So, if it's between 2 and 4 minutes, if the minimum resolution is met, and if the video has audio but no music. And once the check passes, you'll see a check mark here. Um we can switch to uh There you go. We're done. We see the video displays. Perfect. We can continue and save. Then we can uh jump to next one. This is just a quick uh button asking us if we're interested in like any grants or accelerators or incubator pro- uh programs for the future. And then we would go ahead and submit. This again will not work because submission is not open. The really important thing here is, and I really really encourage that,

please read the information and read the notifications. So, for example, for this one it says not eligible for any prizes because I'm not checked in, which makes sense because the event has not started. I have not checked in. Also, the system is running some checks on the repositories to see if it matches the requirements. In 90% of the times, you will be able to submit the project. This is just a warning. It just provides you some information, so make sure to actually properly read this out, and it's also going to be showing everybody in your team.

This is the submission process. It is pretty straightforward, but it can take a little bit of time, especially if it's the first time you're filling this out. But, a lot of the stuff you can do relatively early. You don't have to do everything all at once, but for example, um like filling out the project details, you can do relatively early. If selecting the prizes, you can do it early as well. And none of this should actually uh be blocking. If something is blocking, you're going to see the information popped up in the top there. Cool. That was pretty much everything about the uh overall submission process. And again, hacking starts at 9:00 p.m., ends at 9:00 a.m. You have to submit at least once. What I mean by submitting at least once is you can edit your project after

the submission until the submission deadline. But, in order to receive a stake back, you have to submit your project at least once. Cool. Just going to quickly head over to team. So um everybody by default starts out hacking solo, but um you can hack up with a total of five people in your team. As I said before, I highly encourage you to hack with other people. It's way more fun. You learn a lot, and at the event usually everybody is super super friendly, and you can assume that half of people are smarter than you, which is great. So, you can learn a bunch and build some really really cool stuff.

So, um you can invite people to your team just by name and email. Really important that for the team invites, they have to be accepted at the event. You cannot just invite random people, and they can join you. Every single person in your team has to be fully confirmed, and everybody has to be checked in at the event. This is not a remote hackathon, means everybody that's confirmed has to show up at the event. If you're not showing up, you will also lose your stake. Um you have a team invite link that you can also send over. And if you are uncertain about your team, or you want to hack with somebody else, you can always leave a team and this is a invite a team invite code that you can paste in here. So, if somebody like your friend or let's say um somebody from my team

says like, "Hey, I would love for you to join. Send me the code over." I would input the code over here and I could join the team directly. And as you can see on the side, because I already filled out or like started creating my project, it checks this position this thing off. Next would be to submit and then present to judges. So, again, pretty straightforward. Really, really cool thing about all of this, pretty much about the entire workshop, this entire workshop is also available in text form in the info pages.

So, the info pages has a lovely guide on how to overall get started. This is a bunch of information even before the hackathon, but also during the hackathon. But, a thing that I would highly encourage everybody to do is go for the judging rules and submission, because it provides you with everything that you need. This one is the project submission deadline. So, as I said before, 9:00 a.m. on the Saturday, November 7th. Submission happening on the dashboard. Demo video between 2 and 4 minutes long. Um size-wise, I would say usually video between 50 and 150 megabytes is fine. If you upload a 1 gigabyte video, it's going to take a long time to actually upload that video and then to check. So,

just keep that in mind. Um but like a screen recording, even if it's 4 minutes with a bunch of audio on top of it, is usually not that large. Um yeah, partner prizes says this as well. Three partner prizes, all the important rules on the start from scratch versus continuity, usage of AI tooling, uh how you submit your projects, the difference between finalist and partner. So, again, everything is directly here. One thing that I will note, because I haven't talked about this yet. So, I talked about the two forms of uh judging. One would being the partner judging only, the other one would being finalist plus partner judging. So, for the partner judging, technically you do not have to demo in front of everybody.

You can submit your project, and you would be done. But, we highly encourage you to walk up to the partners. You can usually line up there because a lot of people want to present their project, um just to demo your project and get feedback. If you opt in for the top 10, so getting like the extra prizes potentially and being an ETH Global Finalist or being in that judging role, you will uh be lined up separately. This happens on Sunday, as well. You will be or like your group will be put into one of the judging rooms that we're going to be having, and you have 7 minutes in total. 4 minutes of that will be the demo, and 3 minutes will be a Q&A with the judges. Really important, those are not ETH Global judges, nobody from the ETH Global team, and it's not going to

be anybody from the uh partner companies. Those are independent people, usually like C-level or like really high-experience people in the Ethereum ecosystem that are going to be judging. They're going to be scoring you based on the technicality of the project, originality, the practicality, the usability, and the wow factor. So, that's like the rubric for the judging. And once that is all done, you get a I demo sticker. So, this would be like the two ways of judging. But again, if you opt in for finalist, the partner judging is automatically included. And some questions you can prepare for is like, "What inspired your project?

Like, why did you actually build this? What tools did you use? What challenges did you involve? And what problem is it actually solving?" One important thing about the judging or about overall your project, um don't spend too much time on slides. Um don't make it overly flashy. Like, we really want to focus on the actual project, the actual product that you built. So, if your demo is 3 minutes of slide and 1 minute of demo, there's really low chance that you're going to get further because we want to actually see what you built at the event and not why this is the greatest project ever. So, you can introduce your team, completely fine, but like showcase what you actually built, show the demo. If it's live, if people can interact with it, that is great. If you built like a tool and it's

online, you can say like, "Hey, you can just check out this link. You can interact with it directly." Perfect. Cool. Again, information about the partner judging and overall tips for a good demo video. I'm not going to go over this again because it's Yeah, I I talked about the demo video already way, way too much, but I can highly recommend just check out the judging rules and overall the info pages. Gives you some helpful resources as well and a way to get started at the event, too. So, then we have a list of all of our mentors. Those are ecosystem mentors that have been in the space for quite a while. Some have mentored us before, some for the first time, but have experience in like building products.

They're super, super technical. There's a mix of everything. You have their skills listed here. Um they're going to be walking around the venue with vests that say mentor on the back. We're always going to have a few mentors available 24/7, so you can always talk with them. You can get feedback on your project. They can help you get unstuck. There is also ways that you can connect with them directly on Discord or on Twitter, but again, they're going to be at the venue. Some uh familiar names are going to be there as well. Really, really cool people, really smart people, and they're going to help you uh build the best version of your project. One thing worth noting, they're not your extra team member. They're there to support you and help you out.

And on top of that, um these are the ecosystem mentors. We also have dev roles from all of the teams available at their booths. They're not going to be there 24/7, but throughout the main hacking hours throughout the day, so you can always directly walk up to them. Be respectful, obviously, of the time and of others as well. Don't like um try to cut in line. Um just respect everybody and you're going to get helped and you're going to get feedback and you can build a fantastic project as well. Sweet. Then uh we also have the FAQ section I um I told you about earlier. The schedule we talked about. Um let's see. Oh, yeah. Really important thing I didn't talk about yet. A lot of people are super excited about are the prizes

for the event. So, we have 12 amazing partners. We have World, 1inch, Zero GE, Uniswap Foundation Arc Kleros Archive White Chain, the Ethereum Foundation, ENS, Definity, and Chainlink. They're offering about like 150k in prizes. Eth Global is putting some prize money on top of that as well for finalists. I'm going to say something about that in a second as well. You can see all the required like all the prizes that they're putting out. So, for example, for the continuity track, meaning existing projects that build a new feature at the hackathon, if they're building on World, they can qualify for this one for a total of $2,500.

It lists the requirements, so make sure to read through all those properly. All those sites, which is fantastic, also have links to resources and documentation to get you started. And if you're stuck with something uncertain, you can either reach out to them on Discord, but I would highly encourage you just walk up to them directly. They can help you unblock and answer any questions that you might be having. So, for all the teams that we have there, you have their prize overview, so make sure to check all those out. And again, if there's no banner that says continuity, it's from scratch. So, if it says this one is for continuity, this is for existing projects. For anything new, doesn't have the banner, it's listed right here. So, you can see for 1inch,

they have two bounties in total, one being for the continuity and one being for the regular one. Again, depending on what you select, this is the only one that you can qualify for. You cannot mix and match in between. This will not work. So, if a partner, for example, does not offer a bounty for continuity, you cannot get that bounty if you're building on continuity. Pretty easy. Okay, sweet. So, recommend everybody to check this out and build your projects accordingly. Again, I'm just going to highlight this once more. Don't try to bounty farm. Um the good projects are the projects that make sense, that integrate a protocol well. Um if there's no real use case for, let's say, an

integration with um Arc, and you still integrate it, create more usage for Arc, but you're probably not going to win a bounty. If there's a functionality that you build for World that doesn't really help your project, then I would recommend don't use World. If you have something, you have an idea, and you say like, "Oh, World makes so much sense because it solves a problem." Fantastic, implement it. Then your chances of winning a bounty or actually winning more prizes is much, much higher versus just trying to Frankenstein a project together just for the sake of maximizing everything that you can get out of it. Um because I would say building something at the hackathon is great. Building a project just for the hackathon is fine. Learning

something is fantastic. Um but it's also a great opportunity to potentially start a new company, to potentially build a project that goes beyond the hackathon. So, try to focus on making that project, making those integrations as great as possible versus building like a shitty version of a project with as much money that you could potentially extract because usually you end up with less money, shittier projects, and nobody's happy about that. So, yeah, I would say only integrate what actually makes sense. Think about the parts that you want to implement, do that well, and you're going to have much higher chances of succeeding, and also the chances of becoming a finalist project is much higher as well.

Speaking of the um finalist projects, let's see. Let's just do this quickly. So, um all the teams that end up making ETH Global finalist for events, it's usually eight to 10 teams, will receive a finalist pack. The finalist pack is an on-chain NFT that you can show to people literally saying like qualified proof on chain that you were amongst the top teams at the ETH Global hackathon. All those teams can mint this as an example for the finalist pack for Lisbon this year.

And every single team member gets these as extra perks on top of the title. So, you get one free year of ETHGlobal Plus. If you don't know this, ETHGlobal Plus is our all-in-one ETHGlobal subscription. It gives you access to every single conference, every single single summit that we're doing. This also includes the ETHGlobal ticket pro pass, which at full price is over $1,000. So, you can if you make finalist at this event, um it's on us for you next year to come to ETHGlobal. Each team member gets uh up to $1,000 in USDC, uh $500 travel reimbursement, meaning if you attend any in-person event in 2027 because we don't have any more in 2026, you get $500 from us directly just for showing up and

hacking. Every team member gets a finalist hoodie, which is a hoodie like with a nice little ETHGlobal embroidered logo that only past finalists have. And you get uh $10,000 in AWS startup credits that you can use. So, this is what you would get if you would end up being amongst the uh top eight to 10 teams um at the hackathon if you go through the finalist judging and yeah, make it amongst those top teams. Um you can check all the stuff out at ethglobal.com/packs and the plus page would be just ethglobal.com/plus.

Um speaking of packs, we also have something that everybody here already has. We have community packs and the lowest tier one that we have is the hacker pack. The hacker pack, you automatically uh can mint. Well, you have to mint to access our Discord. So, this is currently claimed by over 14,000 people. Um it gives you a bunch of really, really cool perks. One perk being a discounted ETHGlobal ticket for next year. The more fun thing for a bunch of people is we can give you a reduced uh tickets for DEF CON and even free passes for DEF CON day three and four. So, you can claim this pass um if you have a uh if you have the hacker pack, which everybody here has. And also really important for this event, we're

going to have a Pragma, which is our one-day conference. It's happening on the Friday of the hackathon and every single hackathon participant in Mumbai can claim their free network pass. This doesn't include food, but you can attend, you can talk to all the partners, all the sponsors that are there, you can network with people, and you can watch all the talks live. So, you just go to um the hacker pack page, you can click on redeem, you can redeem your coupon, you get uh you go to the Pragma page, which I'm going to be showing you in a bit. And there you can just claim your ticket. Really important, this is for the network pass, not the hacker pass, network pass.

We also have a bunch of stuff like free Pi, which literally gives you free AI credits, free inference. We get uh extra testnet tokens for our faucet, which is accessible at ethglobal.com/faucet. So, you get free testnet tokens on um Ethereum testnet, on Base testnet, on a bunch of other chains. You get a free ENS domain after the project submission or after the event is done. This is on us. Either you get like one free renewal or one ENS domain for a year. And a bunch of other stuff, and these packs are constantly being updated as well.

And we have dish uh different tiers of those packs. So, the next one would be the builder pack, for example, which you can get if you attended one IRL and one async hackathon, won at least $100 in prizes, or were a finalist. Um it has a bunch more things like additional uh faucet token limits, uh get auto accepted to events. Exception, for example, was this time in Mumbai because of the amount of applications. So, a bunch of more stuff, 6 months of Notion Pro, developer credits for Circle, and the largest community pack that we have is the pioneer pack. You get additional discounts um on a bunch of stuff. You get $50 in Render credits, which is cool. So, if you already qualified for this, you can use this for the

hackathon. You can literally get 1 month of free uh for boat. It's like sandboxes for your AI agents, uh compute for uh Olive on-demand compute. So, a bunch of stuff that you can unlock depending on how well you did in past hackathons. And again, those are getting updated. Fresh perks are coming out shortly. I quickly touch Pragma. So, Pragma again is our one-day conference happening on the Friday of the hackathon. And again, for everybody here, we're going to have more speakers and the schedule. Um for everybody here, like if you claimed the perk and you got your coupon code, you would head over to purchase your net uh network pass, you would enter the discount code, and you

would get a 100% discount on the ticket. You get this for free access to the Pragma conference, which is also happening in the same venue. So, separated area, but you can just pretty much walk in there if you have your ticket. So, you would enter the discount code, 100% off, you get your ticket, boom, hackathon and Pragma attendee. So, as long as you're hacking at ETHGlobal Mumbai, and as long as you uh claim the ticket, you can directly get in there. Uh speaking of tickets, speaking of hacking, I briefly touched this at the beginning. Every attendee gets a wristband and a badge. Please keep those with you at all times. Do not take them off when you're at the venue. It's really important for two reasons.

Security, so we don't have any random people walking in. And also, the badge has a QR code and your name. Those QR codes will be scanned for uh the meals. So, if you want to get, for example, dinner, and you don't have your badge, you're not going to get any food. So, make sure to keep that. Do not toss it. Do not give this to somebody else. If you're impersonating like if somebody's impersonating you or uses your stuff, you can lose your stake, and you'll probably going to get banned from the event. So, everything is issued once. You get run one wristband. You can take a shower with that, no problem at all.

It will not get damaged. You get get uh you get one badge, so make sure to keep all of that, and don't take it off. Um why am I saying don't take this off? Because, for example, you do not have to be at the venue 24/7. You can be at the venue 24/7. What that means is if you have like a BNB, if you have a hotel, if you have a hostel, you can just go there to sleep. You can come back. If you want to grab some outside food, you can grab outside food and come back, but you're always going to have to have your wristband and your badge, cuz otherwise you're going to get denied entry, and inside you're not going to get any food.

Pretty simple. Just keep that with you for the duration of the hackathon. And again, you're more than welcome to stay at the hackathon from 1:00 p.m. on the Thursday till around 5:00 to 6:00 p.m. 6:00 p.m. on the Saturday when we close the event. Um these times are all default to like IST, but for example, if you're currently joining from somewhere else, this should default to where you are right now. So, for example, all those times in Eastern time would be here, not really relevant since we're going to be in this time zone. Make sure to really key times. We open up at 1:00 p.m. Hacking starts at 9:00 p.m. And the uh we'll close uh the project submission, sorry

about that, is at 9:00 a.m. on the Saturday. Okay fantastic. Um yeah, I think we talked about a lot of stuff. One thing I briefly touched was the team. Um we also have a nice feature, which is called the find team feature. I'm going to paste this link in the chat. Uh There we go. Going to paste this link in the chat. So um if you are opting in to be uh discoverable by this one, like if you want to share your Discord, um you can actually look for all the people that want to join a team or they're looking

for team members. You can filter by different interests, by different tools, and contact those people directly. On our Discord, we have a channel that is called find a team channel. So, I highly recommend to just drop an introduction here saying like, "Hey, this is me. This is my um This is my background. This is what I'm doing, or this is my idea on building. I'm looking for extra builders." So, you can just literally do this here and uh yeah, find people on Discord already to chat before, but also there's plenty of time at the hackathon.

So, um before the actual hacking starts, we initially we intentionally do this first of all because you can uh check out all the workshops. So, all the technical workshops by the partners, you can attend, watch, and see what you can actually build on top of that. You have plenty of time to talk and interact with people and network because again, finding people in person is super super fun. Um and whoops, didn't want to switch over there. Yeah. So, you can form teams before, you can form teams during the event, and even after hacking starts, you can still uh form teams and get new people into your team as well. Again, I'll run one of those sessions tomorrow online, and it's going to be an in-person one on the Thursday as well on the schedule. Let me just show this

again. Whoop. On the Thursday, 9:30 p.m. after the uh opening ceremonies. This is when everything starts. Okay. Uh curious why hacking starts at night? We want to have the hackathon for 36 hours. This is just really convenient, so you can do from 9:00 p.m. to 9:00 a.m. And it also gives people time to actually brainstorm and think about ideas up front, and we have plenty of time for the actual workshops. So, you can really dive deep into the tech, brainstorm with people, talk with people, come up with ideas, meet new friends, meet new teammates, and you don't have to jump in right away. And also, sometimes people just don't make

it directly at 1:00 uh 1:00 p.m. They might show up a little bit later because of other um uh because of other things that they have planned since the starting throughout the week. So, yeah. We just default to starting at 9:00 p.m. going to 9:00 a.m. to have the 36 hours. Fantastic. Okay, we covered the dashboard, we covered projects, we covered the team, the mentors, the schedule, the infos, um partners, the venue, da da da again, venue map is pending. Let's see. Should have everything.

Are there any questions? In the meantime, I'm just going to quickly go to Discord again to show a few more channels. So, we have the event schedule which literally pings everybody that's on the Discord if something is happening like food, like workshop, everything is there. You have an overall information channel. I would highly recommend to keep an eye out for this one. Because again it has all the information, links to your dashboard, the resources, the rules for judging, rules for continuity versus from scratch, how you can form a team, and we're also going to be putting information out there throughout the weekend. I'm also going to be super annoying and I'm going to be sending a lot of emails and a lot of Discord pings about project submission, about deadlines, and if people say they didn't

receive anything, I know that they're lying because I sent this out to thousands of people every single time. So, please make sure to at least sometimes look into this so you see when the deadlines and everything is happening. We do have an overall mentorship help channel. The all the mentors at the event and past mentors have this mentor tag so they're available. This links to all of the partner channels as well. And every single partner has a channel which shows all the prizes, information about them, and the dev rails from the teams should have an eye on this so they can answer async questions there as well. If you cannot really locate them, and again what I said before, try to not ask to ask a question, ask the question directly or say I have this specific

problem, provide information about that problem. You're going to get unblocked much much faster versus saying, "Oh, I have a question for the 0G team." And then maybe after a couple of hours the 0G team, "Yeah, what's your question?" Then maybe you're asleep and it just takes a lot of time. This is just much much quicker. Can you rank what the judging is based on an order of uniqueness, functionality? As as a loaded question, I would say everything can be counted equally. Um what I would say is try to build something that is incredibly useful or maybe something that you have not seen before. So, one thing that we now see with AI is people literally doing

the exact same thing over and over again because they just try to copy a project that was successful in the past. So, as I showed you earlier, we have a project showcase which has all like I think at this point 18,000 projects that were ever built at ETHGlobal event. You can filter by prize you can filter by prizes, you can filter if they were finalists or not, which um which hackathon that they were built at. Um and just rebuilding successful projects is not going to be successful for you. Um if you looked at the finalists of the last couple of events, what stood out amongst them was that it was something unique, something that was really useful, something that was maybe like new technology that wasn't seen before. Um I would just generally

recommend just build the best possible project that you can build. Um if it's built technically excellent, fantastic. If it was never built before, it's even greater. If it has a huge potential to make millions, that's fantastic. Um but I would say if it solves a problem, that is really really great. But if it's just the 17,000th prediction market, probably not going to win you a lot unless there's a really cool twist to it maybe. But yeah. And yeah, pretty much all the information is literally on that page. Um but I would say don't focus too much on oh, how can I maximize profits? Just build something that's useful, build something that's fun for you. It's a hackathon, it's 36 hours. Nobody expects

you to build the next unicorn. Um but if you leave the hackathon with some new friends, maybe some money, but like something new that you learned over the weekend. For example, if you never built with ZK, but you want to try ZK, do ZK. Super easy. Uh ba ba ba ba ba let's see. There we go. Um okay, cool. Yeah, I touched this earlier, but we have the faucet. So, if you need some testnet ETH on like ETH Sepolia, USDC on Sepolia, OP Sepolia, Arbitrum Zora Base Filecoin, Gnosis, like all the ones that we have here. Everybody by default can claim 0.05 ETH a day. If you have the

hacker pack, you automatically get bumped to 0.1 ETH. If you have the builder pack, it's 0.5 ETH a day. And if you have the pioneer pack or were finalists in the past, you already get one ETH a day on testnet. Yeah. Um oh, cool. Thanks, RB, for sharing. Yes, this workshop is streamed and recorded, so you can always go back. And really important about the demos, like all the information is in the uh is in the info pages, in the judging rules. This explains how the video is supposed to look like, what the judging criteria is, and how everything is built out as well.

Yeah, let's see. Have a few questions in the DM. Is there any kind of sleeping arrangement, resting area, or maybe somewhere to shower? Great question. So, we do have dedicated like chill spaces / nap areas. We have a unisex one and one for females only. You can rest there. There's going to be a few air mattresses and blankets. Really important, we don't have that many, so it's not going to accommodate all over 1,000 people that are going to be at the event. So, it's limited space, but you can definitely like take rest there, but it's first come, first serve, and it's not going to be a guaranteed spot for the entirety of the time. And

the mattresses stay in there, so you cannot take them out and just like hoard them for yourself. It's supposed to be for as many people as possible. Um and there are no showers at the venue. Okay, let's see if there's another question, another direct message. I answered that one before. Cool. Uh we have luggage keeping area somewhere at the venue. Yes, there is going to be a dedicated luggage storage. Important about that, it's not monitored. So, if you put something there, this is at your own risk. If something gets stolen, if something gets broken, if something gets lost, this is 100% on you, but there's a dedicated like separated storage area that you can

access, but again, it's not monitored. Uh when should we exit the venue? So, overall exit of the venue, you can enter and exit at every time like at any time as long as you have your badge and wristband. Um overall, you have to leave the venue by around like 6:00 p.m. on the Saturday when the event closes. So, you cannot stay longer. After the event ends, the event ends. Um wanted to ask about Pragma, when will the speakers be released? They should be released end of day today or tomorrow. So, just keep an eye out on the Pragma page, the speakers will show up there shortly as we're still finalizing some things.

Okay fantastic. Cool. Um overall, if you have any questions, if anything wasn't clear, or you just want to know something, um the easiest way to do so is just send an email to hello@eeglobal.com or go into the Discord, either ask in the Mumbai chat, or if it's something that is supposed to be private, um please open up a support ticket. For this one, you would just go to uh SOS support, create a new ticket, and somebody from the team will reach out to you. Please avoid DMing the team because if somebody from the team is not available, your request will get lost. I receive literally hundreds of DMs each day about certain things. I try to

answer all of them, but sometimes I'm not even the right person to contact. So, if you open up a support ticket or email hello@eeglobal.com, we can redirect this to the proper people in the team. So, specifically for the hackathon, please avoid DMing the team. And also, there's no need to re-ping the team for all all I read every single message. It just sometimes takes a while and I'm only human. I try to sleep sometimes as well. So, I usually get back to everybody within a reasonable uh amount of time. Uh bu bu bu It's my first Devcon. Any specific points to keep in mind? I know it's not uh related to EVE Global still.

I would say just have a good time. Be respectful to others. There's going to be people from a lot of different cultures and places. So, um some people might interact uh differently. But yeah, as Obie said, just meet people, be open, be nice, be a good person, treat others well, and just enjoy enjoy the environment, talk to as many people as possible, have great conversations, have stupid conversations, just have a good time, and don't take things too seriously, even at the hackathon. It's like oh, a hackathon is a competition. It kind of is, but it also is not. For me personally, hackathons are to meet people and to grow personally. And for that, you don't have to fight with 1,500 people. You can actually build something

great with more people together because that's the whole ethos of Ethereum. Everything is open. Most of the stuff is open. Most people are super smart and really open. So, yeah. Just enjoy and have a good time. And take in as much as possible. Get some rest in between. Don't overwork yourself. Yeah. Just Yeah, just just have a good one. It's going to be a lot of fun. Okay, fantastic. Um with that being said, we're pretty much almost at time. Again, if you need anything, just um support ticket hello@eveglobal.com. Um in person, the easiest way is just approach anybody from the team, especially me. I'm usually really easy to spot. The only guy on the team that doesn't have any hair and has big ass earlobes. So, just reach out, have a

chat with me. I'm usually pretty open unless I'm like super super tired, then I might look a little bit grumpy, but I'm usually pretty friendly. So, yeah. I think most of the people that uh have talked to me before can attest to that. That being said, um I want to thank everybody very much for uh spending your time here. Again, this workshop can be rewatched on YouTube. Looking forward to chatting with each and every single one of you in Mumbai. We're looking forward to our last in-person event of the year. I hope everybody has a blast and yeah, see you next week in Mumbai. Cheers. Goodbye, everybody.

Thank you.