5 |
6 | This is an open source template for organizing your own Blockathon.
7 |
8 | We wanted to provide a single README file with as much support material as possible. This will help you understand what is required so you can start planning your very own awesome Blockathon!
9 |
10 | # Table of Contents
11 |
12 | Before the Event
13 | - [What is a Blockathon](https://github.com/bitfwdcommunity/Blockathon#what-is-a-blockathon-1)
14 | - [Organising Team](https://github.com/bitfwdcommunity/Blockathon#organising-team)
15 | - [Theme](https://github.com/bitfwdcommunity/Blockathon#theme)
16 | - [Title](https://github.com/bitfwdcommunity/Blockathon#title-and-description)
17 | - [Format](https://github.com/bitfwdcommunity/Blockathon#format)
18 | - [Date and Time](https://github.com/bitfwdcommunity/Blockathon#date-and-time)
19 | - [Venue](https://github.com/bitfwdcommunity/Blockathon#venue)
20 | - [Budgetting](https://github.com/bitfwdcommunity/Blockathon#budgetting)
21 | - [Sponsorship](https://github.com/bitfwdcommunity/Blockathon#sponsorship)
22 | - [Pitch Format](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#pitch-format)
23 | - [Speakers / Judges / Mentors](https://github.com/bitfwdcommunity/Blockathon#speakers-and-judges)
24 | - [Prizes](https://github.com/bitfwdcommunity/Blockathon#prizes)
25 | - [Merchandise / Swag](https://github.com/bitfwdcommunity/Blockathon/blob/master/README.md#merchandise)
26 |
27 | Marketing
28 | - [Landing Page](https://github.com/bitfwdcommunity/Blockathon#landing-page)
29 | - [Registration](https://github.com/bitfwdcommunity/Blockathon#registration)
30 | - [Information pack](https://github.com/bitfwdcommunity/Blockathon#distribution-and-spreading-the-word)
31 | - [Distribution and Spreading the Word](https://github.com/bitfwdcommunity/Blockathon#distribution-and-spreading-the-word)
32 |
33 | During the Event
34 | - [Organising Team](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#organising-team-1)
35 | - [Morning Preparation](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#morning-preparation)
36 | - [Arrival](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#arival-of-attendees)
37 | - [Introduction + Keynote Speaker](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#introduction--keynote-speaker)
38 | - [Team Formation + Brainstorm activities](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#team-formation--brainstorm-exercises)
39 | - [Food](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#food)
40 | - [HACK !!!!!!](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#hack)
41 | - [Social Media](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#social-media)
42 | - [Code Freeze + Pitch Collection Period](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#code-freeze--pitch-collection-period)
43 | - [Pitch](https://github.com/bitfwdcommunity/Blockathon#the-pitch)
44 | - [End of the Pitches](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#announce-winners--prizes)
45 | - [Winner announcement + Thank everyone + Celebrate](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#thank-you-for-sponsors-judges-mentors-and-organising-team)
46 |
47 | After the Event
48 | - [Packing up](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#packing-up)
49 | - [Get some sleep](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#get-some-sleep)
50 | - [Follow up with your winners, judges, mentors and sponsors](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#follow-up-with-your-winners-judges-mentors-and-sponsors)
51 | - [Feedback form](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#feedback-form)
52 | - [Thank you + Keeping in touch with the attendees](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#thank-you--keeping-in-touch-with-the-teams)
53 | - [Follow up content](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#follow-up-content)
57 |
58 | ## What is a Blockathon?
59 | Blockathon = Blockchain + Hackathon.
60 |
61 | Blockchain encompassing the technology driving the new age of trust and decentralisation and hackathon being an event in which anyone from any field can come together and work on a project in a given timeframe. By combining the two, you get an event where people come together and work on meaningful projects for the Blockchain.
62 |
63 | Whether you are a Hacker (programmers), Hipster (Growth/User Interface/User Experience), Hustler (Business XX) + Academic, anyone is welcome to participate. Blockathons have been founded on the principles to further develop the Blockchain community, coming together with like-minded individuals and learning from one another.
64 |
65 |
66 | Blockathons typically last between a day to a week in length, depending on the event. The ideas that people work on can either be pre-planned or formed on the day of the event. Depending on the Blockathon, there may be a specific focus which can include the programming language used, the operating system, an application, an API, the subject and the demographic group of the programmers. In other cases, there is no restriction on the type of software being created. Today, this term is not related to "hacking", it is just a programming marathon.
69 | A lot of planning has to be done in order to get a Blockathon rolling, but that's what this guide is for. Key considerations include who will be organising most of the event, when and where will it be held, how much money will you have for the event and who will be judging at the end.
70 |
71 | ## Organising Team
72 | Your organising team is the most important foundation for running a successful blockathon. You will all be working together for XXX. There are several key roles that we have identified:
73 |
74 | * Logistics - This person will handle the venue organisation, catering for food/drinks and ensure the event runs smoothly
75 | * Finances - The person will liase with the respective stakeholders to finance the event.
76 | * Marketing/Social Media - This person will be in charge of marketing the event to the necessary audience through the most appropriate channels (Facebook, Twitter, Telegram etc.) - If your organization has its own Twitter or other social media accounts, you may want to consider giving this person temporary access so they can manage the social media tools for the event.
77 | * Other - Someone responsible for design of promotional material+ development for website if necessary
78 |
79 | These roles can be delegated or a sole person can handle all the activities.
80 |
81 | ## Theme
82 | The best themes are the ones that are most relevant to your audience and consideration of their expertise in the topic/industry. With the current state of Blockchain technology, there are so many problems that can be solved by leveraging it's protocols and infastructure so finding a theme should be no problem.
83 |
84 | Example themes include: Art, Civic, Data, Education, Games, Green Energy, Health, Journalism, Language, Mobile, Movies, Music, Photos, Politics, Robotics, Science, Sports and Water
85 |
86 | This theme will tie into what they will be solving and if there are specific APIs / plguisn that will be used ...
87 |
88 | Your hackathon attendees will appreciate you putting a lot of thought into your theme 🙂
89 |
90 | Below are a list of past Blockathons:
91 | * [MCIC Blockathon](https://mcichack.com/blockathon/)
92 | * [Akropolis.io Mini-Blockathon](https://www.meetup.com/BokkyPooBahs-Ethereum-Workshop/events/247793778/?eventId=247793778)
93 | * Add more to the list...🔴🔴
94 |
95 | ## Title and Description
96 | Give your event a catchy name that represents your theme and will stick in the minds of developers/participants.
97 |
98 | Provide a detailed, but concise description of your event. Generally 250-750 characters is sufficient to explain the theme and outcome of the blockathon.
99 |
100 | ## Format
101 | The formats for hackathons depend on the organisers. Usually they revolve around two formats:
102 | * Hack Day - 12 to 24 hour timeframe
103 | * Hack Weekend - 24 to 72 hour timeframe
104 |
105 | ### Hack Day Example ( 24 Hours)
106 |
107 | | Time | Agenda |
108 | | --- | --- |
109 | | 900-930AM | Set up of venue |
110 | | 930-1030AM | Breakfast + Registration + Welcome |
111 | | 1030-1100AM | Introduction + Team Building Exercise |
112 | | 1100-1130AM | Keynote Talk + Presentation of problem|
113 | | 1130-1200PM | Team Formation Exercise |
114 | | 1200-1230PM | Lunch |
115 | | 1230-430PM | Hack! |
116 | | 430-500PM | Code Freeze + Chillout |
117 | | 500-545PM | Pitches |
118 | | 545-600PM | Judges Discussion for winners |
119 | | 600-615PM | Presentation + Prizes |
120 | | 615-700PM+ | Afterparty drinks |
121 |
122 | ### Hack Weekend Example (48 Hours)
123 |
124 | | Time | Agenda |
125 | | --- | --- |
126 | | 900-930AM | Set up of venue |
127 | | 930-1030AM | Breakfast + Registration + Welcome |
128 | | 1030-1100AM | Introduction + Team Building Exercise |
129 | | 1100-1130AM | Keynote Talk + Presentation of problem|
130 | | 1130-1200PM | Team Formation Exercise |
131 | | 1200-1230PM | Lunch |
132 | | 1230-800PM | Hack!!! + Mentoring + Any guest speakers + Dinner! |
133 |
134 | | Time | Agenda |
135 | | --- | --- |
136 | | 900-930AM | Set up of venue |
137 | | 930-1030AM | Breakfast + Welcome |
138 | | 1030-1100AM | Review of the first 24 hours|
139 | | 1100-1230AM | Hack! + Mentoring + Any guest speakers + Dinner! |
140 | | 1230-100PM | Lunch |
141 | | 100-430PM | Hack!!! |
142 | | 430-500PM | Code Freeze + Chillout |
143 | | 500-545PM | Pitches |
144 | | 545-600PM | Judges Discussion for winners |
145 | | 600-615PM | Presentation + Prizes |
146 | | 615-700PM+ | Afterparty drinks + food|
147 |
148 | ### Hack Weekend Example with proper 2.5 days (60 Hours)
149 |
150 | | Day 1: Time | Agenda |
151 | | --- | --- |
152 | | 400-500PM | Set up of venue |
153 | | 500-530PM | Registration + Welcome |
154 | | 530-600PM | Introduction + Team Building Exercise |
155 | | 600-630PM | Pizza |
156 | | 630-900PM | Hack begins + Teams forming |
157 |
158 |
159 |
160 | |Day 2: Time | Agenda |
161 | | --- | --- |
162 | | 900-930AM | Set up of venue |
163 | | 930-1030AM | Breakfast + Welcome |
164 | | 1030AM-1200PM | Hack! |
165 | | 1200-1230PM | Lunch |
166 | | 1230-800PM | Hack!!! + Mentoring + Any guest speakers + Dinner! |
167 |
168 |
169 |
170 | |Day 3: Time | Agenda |
171 | | --- | --- |
172 | | 900-930AM | Set up of venue |
173 | | 930-1030AM | Breakfast + Welcome |
174 | | 1030-1100AM | Review of the first 24 hours|
175 | | 1100-1230AM | Hack! + Mentoring + Any guest speakers + Dinner! |
176 | | 1230-100PM | Lunch |
177 | | 100-430PM | Hack!!! |
178 | | 430-500PM | Code Freeze + Chillout |
179 | | 500-545PM | Pitches |
180 | | 545-600PM | Judges Discussion for winners |
181 | | 600-615PM | Presentation + Prizes |
182 | | 615-700PM+ | Afterparty drinks + food|
183 |
184 | This is a sample agenda and represents just a few approaches to formatting a hackathon. The best way to find out what works is attend other events, and find the characteristics you like best.
185 |
186 | ## Date and Time
187 | The date can have significant influence on how well it is attended and how much impact it has. Community blockathons are typically held on weekends when people are not working. So it is necessary to choose a date to allow yourself to promote and have the attendees clear their schedule. Also best to avoid any public weekends / holidays as people will be away on vacation during that time. Also make sure that the event does not clash with any other events within the Blockchain community and that it is promoted well in advance.
188 |
189 | For time, clear the schedule of your event to participants in advance. If you choose a 9am start time, expect 20% to show up at 10am. Having an itinerary published at event signup will help make sure you can get started earlier. Schedule reception type activities at the beginning of the day to allow for some late arrivals.
190 |
191 | ## Venue
192 | The venue is also crucial to the atmosphere of the event. Most blockathons are held in a co-working space or an Innovation Hub area which is easy to get to. The place should also represents the theme of the Blockchain culture of innovation and creating something new for the world!
193 |
194 | * Food area + bins
195 | * Bathrooms
196 | * Accessbility
197 | * Internet
198 | * Size of venue
199 | * Area to hack
200 | * Security
201 | * OHS
202 | * Wifi
203 | * Power sockets + safety
204 | * Audio + visual
205 | * Microphone
206 | * Projectors
207 | * Enough utensils
208 |
209 | Blockathons come in all sizes from as small as 5-10 people to 200 people. Bigger isn't always better, but conducting larger events without proper experience and resources can be a major disaster. Keep size in line with your over goal for throwing a blockathon.
210 |
211 | Asking for pre-registration will give you and your team an indication of the number of attendees for the event and how much catering you will have to provide. Using services such as Eventbite or Google Form can help you with this process.
212 |
213 | ## Budgetting
214 | Understanding your budget is crucial to the running of the event. Most of the budget will be for the food and drinks catering as it is important to keep your attendees full and let them focus on hacking. Spending an entire day or weekend together, solving problems and sharing breakfast, lunch, dinner and late night snacks has a way of bringing people together.
215 |
216 | Make the food at your hackathon a healthy, fulfilling experience for attendees. Sample Budgets (Priced in AUD) as below:
217 |
218 | 12 Hour Blockathon Day
219 | For 12 Hour Blockathon Day
220 | - One Lunch + One Dinner and Drinks + Snacks
221 | - Approx cost: $300 - 1000
222 |
223 | 24 Hour Blockathon Day
224 | - One Breakfast + One Lunch + One Dinner and drinks + Snacks
225 | - Approx cost: $500 - $2000
226 |
227 | 48 Hour Blockathon Day
228 | - Two Breakfasts + Two Lunches + Two Dinners and drinks + Snacks
229 | - Approx cost: $1000 - 10000+
230 |
231 | - Breakfast ideas: Waffles, Pancakes, Cereal, Toast
232 | - Lunch ideas: Sandwiches, Buritos, Falalel wraps, sushi,
233 | - Dinner ideas: Pizza, Pick a favourite restaurant nearby and do an Uber Eats order
234 | - Snacks: Chips, Dips, Lollies, Tea, Coffee
235 |
236 | For alcohol budgetting, it is usally best to estimate $10 per person.
237 |
238 | ## Sponsorship
239 | Unless you have a budget for Hackathons, you will want to find a sponsor for your event to cover your costs. Costs include those for a venue (if you are unable to find a free option), and food. Your sponsor may be able to provide you with a venue for your event.
240 |
241 | In addition to providing a good working space for your attendees, it’s a good idea to provide plenty of food. Not only will your attendees appreciate the gesture, but you want them to be able to focus on their projects without the distraction of leaving to get food and drinks. For a one-day event starting in the morning, be prepared to provide coffee and pastries in the morning, a nutritious lunch with beverages, and snacks, water and cold beverages through the day.
242 |
243 | When you talk to prospective sponsors about your event, they may have never heard of Blockathons. They will want to know what to expect, so be prepared to explain a bit about Hackathons as well as about your cause. Think about how they can benefit from your Hackathon so you can explain to them. Benefits may include:
244 |
245 | * Being associated with their brand name
246 | * Being able to meet and talk with the Blockathon attendees
247 | * Having attention paid to their particular business area
248 | * Exposure for their open data efforts
249 | * Having prototype apps created using their API/data
250 |
251 | Be sure to let them know that you’d like to thank them publicly for their support, both on your Hackathon web page and via your social media. Sometimes event sponsors are happy to help out but are not comfortable with the more public forms of gratitude such as Twitter and Facebook, so be sure you have their permission to mention them in social media. You want to show thanks in a way that works for them.
252 |
253 | Part of the benefit of using sponsors is of course covering the costs. Another benefit is to increase the exposure for your cause, or associate your cause and organization with other organizations. Remember the reputation of your cause and organization will be affected by the host and sponsor you associate with, and vice versa, so choose organizations that are well respected and easy to work with. Be respectful, gracious and professional in your interaction with them.
254 |
255 | ## Pitch Format
256 | The format of the pitches varies, but typically they follow this example format:
257 |
258 | - 5 minutes pitch time
259 | - Strict time guidelines are to be addressed by measuring with the Phone timer etc.
260 | - First warning bells / sign at 4 minutes and second warning ball and cutoff at 5 minutes.
261 | - Judging time will be between 3-5 minutes as well
262 | - Judges should have the judging criteria sheet + pen + extra paper to write notes
263 |
264 | [Here is a sample registration Google Form we created](https://docs.google.com/forms/d/16hM6Tmd3EBDclWubygj711fHMgoKWMx9GiW8Mz_rTX8/edit?usp=drive_web
265 |
266 |
267 | ## Speakers, Judges and Mentors
268 |
269 | Speakers, judges and mentors are in important piece of hackathons. Often times they are representing sponsors, but you should consider workshops and other talks that are more informative and help hackathon participants succeed.
270 |
271 | Have a structured approach to structuring your speaker line-up. Provide a framework for speakers to pariticpate in, providing title and abstracts for their talk within a set format and time line you dictate.
272 |
273 | Make sure your speaker line-up is logical and fits well with the theme and schedule of your hackathon.
274 |
275 | For Judges and Mentors, these are people who are well respected in the Blockchain community and can offer valuable feedback to the blockathon participants who are pitching. Judges should range from 3 to 5 individuals. Mentors are any number of individuals who are available to help out during the hacking and answer any expertise questions the attendees may have on the day.
276 |
277 | 
278 | Example: Blockathon Judges / Speakers
279 | 280 | ## Prizes 281 | Not every hack day needs prizes so make sure it's not all about the money/toys. Some people go to hack days to learn, or to play. However if you do choose to award them prizes,make sure it is divisible to encourage teamwork. Commonly in blockathons, it is some cryptocurrencies. 282 | 283 | An example prize that we found was really cool was giving away Trezor / Ledger Nanos or prizing some ETH. 284 | 285 | Remember, the hackathon is not about the winner or prizes. It's about the learning, experience and community :) 286 | 287 | ## Swag and Merchandise 288 | You may also want to consider getting special tshirts, stickers and other merchandie for your team + attendees if it is within budget. They will serve as a really nice memory for everyone! 289 | 290 | 291 |
292 |
293 | Now that you have planned all the pre-requisites of the Blockathon, now it's time to start marketing the event. The aim of marketing the event is to get as many people to come 'hack' and be a part of the Blockchain community. However, if there are particular groups you would like to have attend (developers or industry experts), you will want to think about where best to reach out to them to be sure they know about the event.
294 |
295 | ## Landing Page
296 |
297 | A landing page allows you to visually board and design all the necessary information for your Blockathon. It will list all the details you have organised before the event.
298 |
299 | This can be done by creating a github README.md file or a website / landing page. Websites and landing pages can easily be made through services such as Wordpress, Wix, SquareSpace, Unbounce or you can code it yourself 💻
300 |
301 | Below is a preview of our landing page:
302 |
303 | 
304 | 305 | [MCIC Blockathon](https://mcichack.com/blockathon/) 306 |
307 | 308 | 309 | ## Registration 310 | 311 | A formal registration process for the hackathon should setup to handle attendees from start to finish. The most commonly tools are Facebook Events, Eventbrite Google Forms. Some required field would be: 312 | 313 | * First Name 314 | * Last Name 315 | * Email 316 | * How did you find out about the event? 317 | * Any Dietary requirements? 318 | * Add any other questions / fields that are required for your Blockathon 319 | 320 | A registration process will give you the necessary tools to manage your attendees and understand the scope of your event--as well as give your participants the feeling of organization around the whole process. 321 | 322 | The bitfwd 'stack' that has worked well for us has been: 323 | * Creating a Facebook event with the description - This is for awareness 324 | * Creating an Eventbrite ticket or Google Form link for registration and detail collection 325 | * Send an information pack 1 week before the event to all the registrants 326 | 327 | For any other 'stacks', feel free to add below for the community :) 328 | * Insert stack 329 | * Insert stack 330 | * Insert stack 331 | 🔴🔴 332 | 333 | When you require your attendees to register, make it clear what information is required for signing up and what the deadline for the registration is. If there’s a maximum number of attendees the venue can handle, communicate how the selection process works and when/how people will be notified if they’ve been granted attendance or not. 334 | 335 | If there’s a waiting list for the event, make sure to explain how it works. 336 | 337 | ## Distribution and Spreading the Word 338 | The most important part is getting as many participants coming to your event! So distribution and utilising the various social media and messaging platforms will help you promote your event to the right audience. 339 | 340 | Email 341 | For those that have an email list, this will be a very strong source to send out an EDM to reach potential attendees. 342 | 343 | 344 | Telegram 345 | Telegram is a very common communication tool for people in the Blockchain / Crypto space so doing an announcement and including the event details + links will be awesome. Getting individuals to start talking about it in the respective groups will be great for your event as well. 346 | 347 | Facebook 348 | Twitter and Facebook are also another commonly used social media platform in the Blockchain / Crypto space. Posting there with an FB event / event details will help spread the word. 349 | 350 |
351 | Now for the fun part of how to run the Blockathon on the day! Initially the organising team should arrive 1 to 1.5 hours before the event starts. (I.e arrive 730-8am if the event starts at 9am)
352 |
353 |
354 | ## Organising Team
355 | On the day you will need to assign a few roles to make things run smoothly. It would also be ideal for other people/volunteers to help out with the event to help with the setting up on the venue and ssisiting the attendees for anything they need.
356 |
357 | * Logistics - This person will handle the venue organisation, catering for food/drinks and ensure the event runs smoothly
358 | * MC - The person will help host the introduction of the event and the end of Blockathon pitches
359 | * Marketing/Social Media - This person will be in charge of tweeting / posting live updates of the event. If your organization has its own Twitter or other social media accounts, you may want to consider giving this person temporary access so they can manage the social media tools for the event.
360 | * Other - People to help up with the distribution of food and setting up the venue.
361 |
362 | ## Morning Preparation
363 | This is highly dependant on the venue but there are certain task that need to be done before all the attendees arrive:
364 |
365 | - Chair / Space Setup - How would you like to set up the room and the 'hacking' tables.
366 | - Breakfast (if provided) - Have the plates, utensils, cups and drinks prepared
367 | - Powerpoints / plugs - Each 'hacking' table should have at least one power plug for participants to charge their laptops. Make sure the plugs are not a hazard to people's pathway
368 | - Snacks for the hackathon tables - Lollies, chips, nuts etc. for the partipants to snack on during the hack
369 | - Paper, stickies, permanent markers, whiteboards - For the teams to brainstorm on
370 | - Wifi + Telegram Group link- Would be best to print the details onto a piece of paper and leave on all the tables
371 | - List of expected attendees - To tick off during arrival
372 |
373 | ## Arrival of Attendees
374 | Your event particants will start coming in at the designated start time. Greet them in a friendly manner and make them feel welcome. Start chatting to them and get them to register the required details.
375 |
376 | A name tag also helps remembering names so having a Sharpie/permanent marker with some stick on name tags work great :)
377 |
378 | Also be mindful that the participants will most likely not be arriving exactly on the start time so allow for some leway time before the first agenda item commences.
379 |
380 | ## Introduction + Keynote Speaker
381 | Once a majority of the attendees have arrived, it's time to open the opening address with your MC and your keynote speaker. During this time, you would have the MC:
382 |
383 | - Thank all the attendees for coming to 'hack' at the blockathon
384 | - Thank the sponsors for making this event possible
385 | - Have the keynote speaker/MC talk about the problem that needs to be solved for the blockathon
386 | - Discuss the criteria for the outcomes/pitches (How long the pitch is, when is code freeze)
387 | - Address any other safety requirements and agenda items (Bathroom, after hours access etc.)
388 | - An overview of the day/days
389 |
390 | ## Team formation / brainstorm exercises
391 | After the initial introduction and the attendees are settled in nicely, it is nice to start team building and getting to know one another. From a lot of the hackathons/blockathons that we have seen, just putting people into groups is not the best solution.
392 |
393 | Individuals should form teams in the most natural ways (within the required time allocation) and then start forming about Blockchain ideas and solutions.
394 |
395 | A combination of exercises we have done include:
396 |
397 | Meet 10 people in 10 minutes
398 | 1. Turn to the person next to you, introduce yourself and talk about a specific topic (I.e. How did you get started with Blockchain)
399 | 2. After 1 minute, the bell rings and you talk to someone else new
400 | 3. This rotation is done 10 times and the participants would have met 10 new people.
401 |
402 | Present ideas in 1 minute
403 | 1. Whoever wants to present an idea is allocated 1 minute to talk to everyone in the audience
404 | 2. Everyone is given a chance to talk
405 | 3. At the end of all the pitches, everyone who presented stands at the front and in an orderly fashion, participants are free to talk to
406 |
407 | Brainstorming
408 | 1. Have an idea around Blockchain / Non Blockchain related
409 | 2. Get people to form groups of 4 -5, depending on the number of attendees. Give them 5-10 minutes to form a pitch around the idea (Blockchain + Energy)
410 | 3. Revise how this process works...
411 |
412 | 🔴🔴 (Robin to add pull request/ more info)
413 |
414 | Teams are usually formed over a certain time period, but it's also great to allow them to do it over a social setting such as lunch.
415 |
416 | ## Food
417 | A meal is what brings people together and allows them to discuss really cool ideas, so:
418 |
419 | - Make sure that the food and drinks arrives 10 minutes before your set time of allocation.
420 | - Organise enough plates, cutlery, napkins and cups
421 | - Organise the layout of the food and drinks so that attendees can walk around and talk to one another. (I.e. in the foyer or outside)
422 |
423 | ## Hack
424 | Once teams are sorted, Blockathon hacking can commence! 🎉
425 |
426 | The teams will sit around their designated tables and start bringing their ideas to life.
427 |
428 | As aforementioned in the [Morning Preparation](https://github.com/bitfwdcommunity/Blockathon/blob/readme_edit_1/README.md#morning-preparation) section, hopefully the teams have enough powerpoints, snacks and brainstorming tools to work together.
429 |
430 | The mentors for the Blockathon can go around during the day to help support the teams with any business or technical questions they may have.
431 |
432 | As per your agenda, let the participants know whenever there is a guest talk, lunch afternoon tea, dinner, lunch.
433 |
434 | The organising team should go around fromt iem to time to check if the blockathon participants need any assistance/anything that answer any questions.
435 |
436 | ## Social Media
437 | Creating content during these blockathons are also important to document the process for the future process. So utilising the various platforms (Facebook / Twitter / Telegram )
438 |
439 | Live streaming and having your own photographer / videographer would also be awesome.
440 |
441 | ## Code Freeze / Pitch Collection Period
442 | All good things must come to an end, including the hacking. 😌
443 |
444 | This is why the code freeze (as per [sample agenda](https://github.com/bitfwdcommunity/Blockathon#format)) is important and provides the strict deadline as to when the coding / pitches are finalised. The collection of pitches can then commence while the teams chillout and relax a bit.
445 |
446 | There are a few ways to collect the slides:
447 | - Send the Google Slides via the Telegram group
448 | - Put on slides on USB
449 | - Share to a common Google Drive + provide them with the URL
450 |
451 | If some of the teams are doing a demo, make sure that you ask them and see what requirements are needed for their AV inputs.
452 |
453 | - AV requirements
454 | - Video projector
455 | - (Apple Mac) Mini DisplayPort, VGA, DVI, and HDMI
456 | - Live stream (optional)
457 |
458 | ## The Pitch
459 | After all the teams have pitched and provided with their judging feedback, the MC will thank all the teams for the awesome projects they have hacked at the Blockathon. Then allow the judges to convene to another room to discuss who will be the winners as per criteria.
460 |
461 | Allow the rest of the audience and participants to start mingling, have some food and drinks.
462 |
463 | After the judges are back, the MC will gather everyone around again/get them to sit down.
464 |
465 | ## Announce Winners + Prizes
466 | The judges will then announce the winners with explanation as to why they won.
467 |
468 |
469 | ## Thank you for sponsors, judges, mentors and organising team
470 | Many thanks are in order for being able to run a successful event. So after the winners have been announced, make sure the MC thanks all the sponsors, judges mentors and the organising team for making the event possible.
471 |
472 | It is also nice to have a small gift (wine,chocolates etc.) to give to the mentors and judges for taking time out of their day to give back to the community.
473 |
474 | Then the MC will conclude the Blockathon event and invite everyone to stay for some more awesome food and drinks. 🎉🎉🎉
475 |
476 | 
477 | Even after your event is technically over, there are still a few things to tick off the checklist
478 |
479 | ## Packing up
480 | After the event has concluded and the Blockathon attendees head home, it's time to pack up the venue. All the dishes, chairs and rubbish are to be placed in their rightful place. Mopping up the floors (if necessary) and putting everything back to its original
481 |
482 | ## Get some sleep
483 | Self explanatory and well earned! 😴
484 |
485 | ## Follow up with your winners, judges, mentors and sponsors
486 | The next day, it would be advisable to do a quick thank you email to each individual judge, mentor and sponsor for their time.
487 |
488 | Also if there are any followups needed for the winners, it would be a great opportunity to do so / send them their prize (I.e. ETH etc.)
489 |
490 | ## Feedback Form
491 | While the Blockathon is still fresh in their minds, receiving feedback from your participants is also a great way to assess with the team what they did well and what they could improve on for the next Blockathon.
492 |
493 | This can be sent through a Google Form / Typeform via Telegram or email.
494 |
495 | ## Thank you + Keeping in touch with the teams
496 | A general thank you email blast or across the Telegram group is also a great gesture to thanking the Blockathon participants for coming along to the venue. Maintaining contact with all the teams is a great idea to see if they further develop their ideas.
497 |
498 | ## Follow up content
499 | For the marketing side, there is opportunity for you to showcase how awesome your Blockathon was as well as create follow up content (Interviews/Videos/Linkedin post / Medium post).
500 |
501 | This could be asking your attendees to create a followup video or writing a Medium article about their experience.
502 |
--------------------------------------------------------------------------------
/imagess/guide.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/bitfwdcommunity/Blockathon/daff74b78e4c7536f9ec05072fdbc28545faffc2/imagess/guide.png
--------------------------------------------------------------------------------