[REDACTED] Hackathon |

Go Back

[REDACTED] Hackathon

Big corporations and governments aren’t just going to put blockchain and AI technologies in users’ hands—to serve users’ interests and not their own.

The user-owned future isn’t going to just happen.

We’re going to have to hack it open.

[REDACTED] is a global convergence to shape the future of User-Owned AI and Chain Abstraction—a future where technology belongs to the people, not corporations.

The [REDACTED] hackathon is a call to developers, creators, and visionaries to take on the biggest challenges in Chain Abstraction and at the intersection of AI and Web3.

Guided by expert mentors and using the best developer tools, you'll have the opportunity to build game-changing products alongside peers, unleash your creativity, and push the limits of AI x Web3.

And oh yeah, take a shot at over $500k in prize money.

Here’s how it goes:

Right now: Register here to qualify.

September 5: The [REDACTED] hackathon begins. An eight-week virtual immersion with other builders with specific themes, workshops, tutorials, and experts to provide interactive builder support.
November 9-11: The hackathon culminates live in Bangkok, Thailand, at the [REDACTED] IRL movement. Hackers get the chance to join a gathering of 1,500+ like-minded devs, founders, creatives, and leaders, upskilling and connecting to build the user-owned future. (And because we really want you to be there IRL, we’re making travel scholarships available to qualifying hackathon participants.)

It’s time to reclaim your sovereignty. Are you in?

When Remote: Sept 5 - October 25, 2024
When IRL: Nov 9-11, 2024
Where: Bangkok, Thailand

Requirements

Register for the Hackathon by clicking the “Join Hackathon” button. To complete registration, sign up to create a free Devpost account, or log in with an existing Devpost account. This will enable you to receive important updates and to create your Submission.
Entrants will obtain access to the required developer tools and complete a Project described below in Project Requirements. Use of the developer tools will be subject to the license agreement related thereto. Entry in the Hackathon constitutes consent for the Sponsor and Devpost to collect and maintain an entrant’s personal information for the purpose of operating and publicizing the Hackathon.
Build a Project that meets the requirements of one of the below descriptions (each a “Track”), to be eligible for the relevant Prize (each a “Track Prize”).
- Native track – New and substantially modified existing projects built using NEAR and/or NEAR adjacent technology
- Chain agnostic track – New and substantially modified existing projects built using blockchain and/or AI technology.

Create a video that includes footage that explains your project’s features and functionality through a comprehensive demonstration.
Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Submission Period and follow the requirements below.

Project Requirements

(i) What to Create: Entrants must build an app using NEAR technology, NEAR adjacent technology or third party technology provided by one of the Hackathon sponsors (each a “Project”) and submit it for one of the Tracks:

Native track – New and substantially modified existing projects built using NEAR and/or NEAR adjacent technology
Chain agnostic track – New and substantially modified existing projects built using blockchain and/or AI technology.

(ii) Functionality: The Project must be capable and running consistently on NEAR Testnet or Mainnet. This will include Projects built with adjacent projects such as Aurora and Mintbase, and Projects built with third party technology provided by one of the Hackathon sponsors.

(iii) Platforms: A submitted Project must run on the platform for which it is intended and which is specified in the Submission Requirements.

(iv) New & Existing: Projects must be newly created or substantially modified by the Entrant during the hackathon submission period.

(v) Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them.

(vi) Testing: The Entrant must make the Project available free of charge and without any restriction, for testing, evaluation and use by the Sponsor, Administrator and Judges until the Judging Period ends.

Entrants must make their Project available in the following method:

Provide a URL to your open source code repository for judging and testing. Your code must have an open source license like one of the below:
-  MIT - https://opensource.org/licenses/MIT ;
- Apache 2.0 - https://opensource.org/licenses/Apache-2.0 ;
- 3-Clause BSD - https://opensource.org/licenses/BSD-3-Clause

Submission Requirements

Submissions to the Hackathon must meet the following requirements:

Include a Project built with the required developer tools and meets the above Project Requirements.
Provide a URL to your open source Project code repository for judging and testing. Your code must have an open source license similar to one of the below:
-  MIT - https://opensource.org/licenses/MIT ;
- Apache 2.0 - https://opensource.org/licenses/Apache-2.0 ;
- 3-Clause BSD - https://opensource.org/licenses/BSD-3-Clause
Include a text description that should explain the features, functionality, and Track for your Project. If the Project is being submitted for a Sponsor Prize (defined below), the description must include how the Project fulfills the specific Sponsor Requirements listed in section 8. Prizes.
Include a demonstration video of your Project.
The video portion of the submission:

should not exceed three (3) minutes
should include footage that shows the Project functioning on the device for which it was built
must be uploaded to and made publicly visible on YouTube, Vimeo, Facebook Video, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website; and
must not include third party trademarks, or copyrighted music or other material unless the Entrant has permission to use such material.

Select the Track the Project is being submitted into.
Be the original work of the submitter, be solely owned by the submitter, and not violate the IP rights of any other person or entity.
Access must be provided to an Entrant’s working Project for judging and testing by providing a link to a website, functioning demo, or a test build. If Entrant’s website is private, Entrant must include login credentials in its testing instructions.
Multiple Submissions: An Entrant may not submit more than one Submission

Judges & Criteria

Eligible submissions will be evaluated by a panel of judges selected by the Sponsor (the “Judges”). Judges may be employees of the sponsor or third parties, may or may not be listed individually on the Hackathon Website, and may change before or during the Judging Period. Judging may take place in one or more rounds with one or more panels of Judges, at the discretion of the sponsor.

Stage One) The first stage will determine via pass/fail whether the ideas meet a baseline level of viability, in that the project reasonably fits the theme and reasonably applies the required APIs/SDKs featured in the Hackathon.

Stage Two) All submissions that pass Stage One will be evaluated in Stage Two based on the following equally weighted criteria (the “Judging Criteria”):

Entries will be judged on the following equally weighted criteria, and according to the sole and absolute discretion of the judges:
- Technological Implementation (Does the interaction with NEAR demonstrate quality software development?)
- Design (Is the user experience and design of the project well thought out?)
- Potential Impact (Is the Project Open Source and how big of an impact could the project have on the NEAR ecosystem?)
- Quality of the Idea (How creative and unique is the project?)
- Project Sustainability (Is the plan for the Project thought out and realistic?)
The scores from the Judges will determine the potential winners of the applicable Prizes. The Entrant(s) that are eligible for a Prize, and whose Submissions earn the highest overall scores based on the applicable Judging Criteria, will become potential winners of that Prize.

Tie Breaking. For each Prize listed below, if two or more submissions are tied, the tied submission with the highest score in the first applicable criterion listed above will be considered the higher scoring submission. In the event any ties remain, this process will be repeated, as needed, by comparing the tied Submissions’ scores on the next applicable criterion. If two or more submissions are tied on all applicable criteria, the panel of Judges will vote on the tied submissions.

See Rules for more on requirements.

Hackathon Sponsors