# Infinite Build Welcome to **Infinite Build**, where we take the idea of a hackathon and mix it up with some Infinite Games philosophy. The goal? Keep playing, keep creating, and let the journey be the point. It's like a hackathon that never really ends. We're a small crew of people who just want to make fun stuff and help each other along the way. No competition, no pressure. I'm organising it because this is the community *I* want to be part of—a constant, joyful exploration. [Sign up to be notified when we start.](https://tally.so/r/wbr8pZ) ## Caravans We'll kick things off with a monthly hackathon, online, over the weekend-- called **Caravans**. But it’s not like the usual hackathons you know. Here’s how it goes down: 1. **Inclusive Gates**: No applications, no barriers. You'll just make a simple REST API call, and boom—you’re in. Whether you’re figuring out APIs for the first time or you're a seasoned builder, it’s all about [learning and leveling up together](https://wiki.infinite.build/start). 3. **Solo Builds**: Everyone works solo, so your vision stays *yours*. But if you want to jump in and help others, you can be a "free agent" and hop in wherever you're needed. It’s all about keeping the creativity flowing. 1. **Traffic Light Feedback**: We use a simple traffic light system to show how we're doing: 🟢 green means you’re in the zone, 🟡 yellow means you’re facing some annoying challenges, 🔴 red means your computer was thrown out the window. See a red or yellow light? Jump in and help. Hit green again? Time to celebrate! 🎉 1. **Peer Mentorship**: We don’t do hierarchies here. Everyone helps everyone. Maybe you’ve got coding skills, or maybe you’re a game designer, writer, or musician. Whatever you bring, someone else needs it. Even beginners can help OGs, just by asking questions to make them explain their thinking and find their own bugs. We mentor each other, not just with code, but with ideas, strategy, and emotional support. 1. **Hackers as Connectors**: You can find collaborators in our "Crossroads" chatrooms. It’s as simple as saying, “I’m just a [whatever] trying to [do this thing] in [this context].” People will jump in. Or you can @ someone when you see them struggling with a yellow or red light. 1. **Council Calls**: Twice a day, we have 80-minute feedback sessions. You get 20 minutes to talk about what you're working on and get feedback from 3 others. Then, you pay it forward by giving feedback to 3 more people. It’s like a quick reset to make sure you’re heading in the right direction. ## The Big Ideas 1. **Names, Not Titles**: We don’t care about titles or ranks. When you join us, you get a name. No points, badges or status. Your name is your path—who you are and what you're working on. 1. **Continuous Play**: We’re all about trying things out, pushing boundaries, and keeping it fun. 1. **Surprise & Genius**: Work on projects that really resonate with you, and look forward to what they teach you when they get into the real world. 1. **Response over Roles**: Roles are like scripts, and who wants to be scripted? We’re all about genuine reactions to each other. 1. **Pseudonymous-First**: Whether you're a journalist, activist, or just someone who values privacy, pseudonyms are encouraged. They help give everyone an equal shot, regardless of their background or situation. ### Keep Building, Keep Playing So what happens after the hackathon? More hacking, of course. We stay in transit, always moving, always exploring. Some once per month optional get-togethers. **Transit Tuesdays**: Screenshare where we’re at—what we’re working on, what we’ve discovered, what’s challenging us. No demos or pitches, just shop talk and helping each other. **Paper Parties**: Read and discuss whitepapers and systems we want to learn about. It’s low-key and super informative. Occasionally: **Hack and Tell**: Our version of Hack and Tell covers everything from open-source projects to games, music, art, and cryptography. **Guest Visits**: Chill, open sessions where engineers and creatives pop in for AMAs, office hours, and hands-on debugging. We brew tea, share screens, and dive into projects together. **Empirical Beauty**: We pick protocols, products, or communities and see how they behave—what patterns emerge from their designs, what behaviors they lead to. ### Join the Caravan - starting November We’re traveling in caravans, and the next one departs just after Devcon in November. There's something special about starting together. The energy and momentum from the event will carry forward, and we’ll keep building, supporting, and inspiring each other along the way. [Sign up to be notified when we start](https://tally.so/r/wbr8pZ) --- Let’s keeping building cool stuff, and keep the game going. \- [Voboda](https://voboda.com)