Year of the SporkWhale | Feb 23 - Mar 3, 2024 Denver, Colorado
#BUIDLATHON

Track Judging

At ETHDenver, there are two types of judging:
Community Track Judging and Sponsor Bounty Judging.

Saturday March 2nd, 2024

Community Track Judging

Judging Teams

Each Community Judge at ETHDenver will specialize in judging one #BUIDLathon track. Judges who apply will indicated their top three tracks and the specific roles they are experts in. These roles include:

Technical: Web3 Security
Technical: Back End Development + Front End Development
Technical: Smart Contracts + Solidity
UI + UX
Business Development
Professional roles in Legal, Compliance, and Regulatory
Technical Founder Investor: Someone who was/is a technical founder / technical co founder of a startup who had a successful exit / acquisition / raised Series A/B/C/D and now invests in startups.

Judges are required to justify their expertise in these areas, provide details of their past judging experiences, and, for those in technical roles, submit their GitHub profiles. They are vetted by #BUIDL Stewards and #BUIDL Council.

Judging teams are organized around a single track and divided into four expertises:

Technical
Business Development / Professional
UI + UX
Technical Investor

Sunday March 3rd, 2024

Top 15 + Alternates

For ETHDenver 2024, we are introducing a new group: "alternates." This addition caters to various scenarios that may arise during the event:

Acknowledging Team Availability: We understand that some teams might choose not to present on the main stage or may have scheduled to depart before the closing ceremony, not expecting to advance to Sunday.

Substituting for Absent Winners:If a team from the top three is unable to present at the closing ceremony, the first alternate will step in to take their place and claim the track prize. In the event that two of the top three teams are absent, both the first and second alternates will fill in and be awarded accordingly.

Requirement for Prize Eligibility: To be eligible for the track prize, it's mandatory for teams to be present on Sunday and to perform a demonstration on the main stage. This approach ensures that all deserving projects get their chance to shine and accommodates the dynamic nature of participant schedules and decisions.

First Round

Short Format Demo

The essential components of this initial presentation include:
> A clear explanation of the problem that the project is designed to solve.
> The technology stack utilized in the project & bounties incorporated.
> A demonstration of the working project

It's important to understand that this presentation is not a "business concept pitch" or a "pitch for funding." Instead, it's a concise, rapid demonstration focusing on the project's technical capabilities and innovation.

After all the presentations in a track are complete, the community judges will meet, go through notes, review the project code for their favorite projects, and will then select their top three projects and two alternates.

To be considered for the Top 15, it's important for teams to stay within the #BUIDLHub area until the results for their track are announced on the website. This methodical process is designed to ensure a fair and thorough evaluation of each project, based on its technical proficiency and the innovative application of technology.

Second Round

Long Format Demo

The essential parts of this long format demo presentation include:
> A clear explanation of the problem that the project is designed to solve.
> The technology stack utilized in the project & bounties incorporated.
> A demonstration of the working project

It is important to understand that this presentation is not a "business concept pitch" or a "pitch for funding". Instead, it's a technical demonstration focusing on the projects technical capabilities, UI/UX, and innovation.

The total duration of a second round long format demo with judging Q&A will be eight (8) to nine (9) minutes.
- Five minutes to demo the working project
- Three minutes for Q&A focused on Technical, UI/UX, + Product

Saturday March 2nd, 2024

First Round Schedule

Apply to judge WAITLIST
10:00 AM MST Project Submission Due

#BUIDLer Projects need to be submitted on Devfolio by 10:00 AM MST, Saturday, March 2nd, 2024. Unfortunately, if submissions are after 10:00:01 AM, we regret to inform you that exceptions cannot be made.

1:00 PM MST First Round Schedule Posted

ETHDenver's #BUIDLx team will post the #BUIDLathon Presentation Schedules on ETHDenver.com/buidl-judging. Teams will be notified of the schedule via email, and it is their responsibility to be present at the stage to pitch their project. Mentors and #BUIDL council members will review the projects to ensure they are technically operational. Projects that are found to be non-deployable will be noted in our system and may not be eligible for the Top 15.

2:00 PM MST Community Judging Starts

Community judges will be directed to one of three stages. #BUIDLers will wait in line for the opportunity to present.

Submarine Stage : Infrasturcture and Scalability (2pm)
Trident Stage: Identity, Privacy, and Security (2pm)
Neptune Stage: Defi-, NFTs, and Gaming (2pm)
Trident Stage: Impact + Public Goods (Approximately 4-5pm)
Neptune Stage: DAOs + Communities (Approximately 4-5pm)

2:00 PM MST #BUIDLHub Stage 1, Stage 2, Stage 3 #BUIDLathon Presentations

Around 25-34 teams per hour on each stage will present their #BUIDLathon projects to the community judges. The judging panels are organized by specific tracks. During these presentations, we encourage participants to either join the audience or be present on the floor.

5-6:00 PM MST #BUIDLHub Stage 2, Stage 3 #BUIDLathon Presentations

Around 25-34 teams per hour on each stage will present their #BUIDLathon projects to the community judges. The judging panels are organized by specific tracks. During these presentations, we encourage participants to either join the audience or be present on the floor.

8:00 PM MST Community Judging Ends

After all teams have completed their demos, the judging panel will collaborate to identify five potential winners: three winners and two alternates. Before making their final selection, the judges will ask these teams for a more in-depth demonstration of their technology. Additionally, they will have the option to review any notes and findings from the Mentors and #BUIDL Council members to inform their decision.

8:00 - 9:00 PM MST Posting Top 15 Winners on ETHDenver.com

Winners for each track will be progressively updated on the ETHDenver website, depending on the timing of your project presentation. The Top 15 Projects will also be featured on the website. Additionally, an announcement will be made over the intercom, listing the winners and alternates for each track.

A new group in 2024 introduces "alternates". This change acknowledges that some teams may opt not to present on the main stage, or might have arranged to leave before the closing ceremony, not anticipating their advancement to Sunday. If a winning team is unable to present, the first alternate will step in to replace them and claim the prize. If two teams are absent, both first and second alternates will take their places and receive the awards.To qualify for the track prize, teams must be present on Sunday and give a demonstration on the main stage.

11:59 PM MST Confirmation of Presenting

The Top 15 Teams announced as winners will need to confirm their participation in the Closing Ceremonies. Team that do no confirm their participation will be replaced by the alternates.

Sunday March 3rd, 2024

Community Track Judging

9:00 AM MST Top 15 Technical Pitch Practice

The Top 15 Teams will arrive at #BUIDLHub to work with mentors and #BUIDL council members on their "Long Form Presentations" that will be delivered during the closing ceremony.

9:00 AM MST Community Project Fair Setup

SporkDAO Member Project Teams that are participating in the Community Project Fair will begin to setup their table on the #BUIDL Floor.

10:00 AM MST SporkDAO Community Project Fair Starts

SporkDAO Community members arrive at #BUIDLHub to explore the hundreds of projects that submitted to the #BUIDLathon. SporkDAO Members will login to Devfolio to participate in a Quadratic Voting round, awarding 100 total points to their favorite projects.

12:30 PM MST Top 15 Projects Lunch
1:00 PM MST SporkDAO Community Project Fair Ends
2:00 PM MST #BUIDLathon Closing Ceremony

Join us for ETHDenver's 2024 #BUIDLathon Closing Ceremony as we celebrate the Top 15 Projects according to the Community Judges. The Top 15 teams will present their projects to a new panel of judges, providing longer period of time to showcase the new ideas.

4:45 PM MST #BUIDLathon Top 5 Announced

The Top 15 Judging Panel will identity the best projects for each track of the #BUIDLathon.

5:00 PM MST ETHDenver 2024 Ends.

That's a wrap for ETHDenver 2024. We will see you next year.

ETHDENVER TRACK

Judging Criteria

How you are judged as a BUIDLer for ETHDenver:

All projects submitted to ETHDenver track belong to one of the five Tracks. As in years past, we continue to promote high impact projects, but no matter what you choose to work on, you can stack up sweet bounty prizes with some sick engineering or user experience design. We designed the following criteria to reward strong team projects without favoring specific types (e.g. dApps vs. developer tools). The following criteria will judge all projects in one of the five Tracks:

Best for Blockchain

How much does this project improve the Blockchain ecosystem (e.g. giving developers better tools, driving adoption, improving the architecture, etc.)?

Best User Experience

How easy is it for experts and amateurs to use this product/service?

Best Engineering

How impressive is the technical implementation? How well is it engineered?

Highest "WOW" Factor

Did this project get you excited? Are you impressed?

Most Innovative

How original, creative, novel, and useful is this project?

Additional Judging Criteria for the Impact + Public Goods Track

The Impact + Public Goods Track will not only be judged by the Track criteria, requiring great engineering and user experience, but also on the following additional factors:

Most Impactful

How much of a difference does this project make in terms of the UN's Sustainable Development Goals?

Most Sustainable

Is it a practical solution? How easy is it to keep this initiative going? Is this a one-and-done or can it keep giving?

Best Use of Crypto/Blockchain Tech

Does crypto/blockchain tech add significant value to this solution over centralized alternatives?

Additional Judging Criteria for UIUX Team Member

If your team opts to incorporate an additional member dedicated exclusively to UI/UX design, it's important to note that the UI/UX Designer will not engage in coding tasks. These responsibilities will remain the sole domain of your backend/front end developer. During evaluation, the judges will expect the UI/UX designer to present their own submission, emphasizing UI/UX design aspects, with the following details included.

Submission of Research

ETHDenver expects you to demonstrate your research process leading to your design. This should encompass elements such as Empathy Maps, Customer Personas, Customer Scenarios, and Storyboards.

Submission of Ideation Map

ETHDenver judges want to see your Moodboards showcasing your color scheme, style guide, and the visual aesthetics of the project.

Submission of Prototype

ETHDenver will expect flowchart diagrams illustrating the sequential steps in a process, along with the digital prototype (Wireframe and Actual Design)

ETHDENVER TRACK

Project Submission

Submitting projects on Devfolio

In order to submit a project in the #BUIDLathon you need to be checked into ETHDenver and Devoflio by March 1, 2024 at 10:00 am.

Project submissions can be completed starting at 8:00 pm on March 1 and need to be submitted by 10:00 am on March 2.

Submitting your project can take up to 60 minutes if you are not familiar with the Devfolio platform https://ethdenver2024.devfolio.co please begin submitting your project at least two hours (8:00am) before the deal to ensure you have time to connect with the ETHDenver team in case you have any questions about the submission process.

Using you will only need to submit your project once. 

ETHDenver begins on February 23rd and not before. Submission criteria is below.

Team Name

Name of your team

Team Members

First name, last names, role in project, and Discord handles

Short Description

Describe your project in no more than four sentances

Technical Video Demo

Your public video should be at most 4.5 minutes in length. Please include hashtags: #ETHDenver2024 #BUIDLathon

Track

Write the track you are submitting your project to. You can only choose one.

Project Bounties

Have a header that says "project bounties" and include all the Sponsor Bounties in your project with links to the bounties.

Links to Resources

We want to see your source code on a public repo GitHub.

Presentation Slide Deck

We want to see a public link to your presentation

Document Daily Journey (Recommended, but optional)

We want to see some type of document in your Github and or a public Google Document that showcases your journey through ETHDenver. This is here to help you see all that youv'e overcome and show judges what you endured.

Additional Judging Criteria for UIUX Team Member (Team of 5)

If your team opts to incorporate an additional member dedicated exclusively to UI/UX design, it's important to note that the UI/UX Designer will not engage in coding tasks. These responsibilities will remain the sole domain of your backend/front end developer. During evaluation, the judges will expect the UI/UX designer to present their own submission, emphasizing UI/UX design aspects, with the following details included.

Name of UIUX Designer

Name of the focused UIUX Deisgner

Visual Presentation

A public link to see your digital work on a platform such as Figma or Adobe. We want to see you research, ideation, and prototypes,

Claim Period

Your project submissions on Devfolio need to be untouched and live until June 16, 2024, which is when Payment Period is complete.

If you are continuing your project in anothe way, you'll need to fork and or copy to another project.

#BUIDLATHON

Community JUDGE Application