1. ENTRY SEGMENTS

Developer

Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”) (*NOTE: The age of majority is the threshold of adulthood as recognized or declared by law. Most countries set the age of majority at 18 including the US, UK, Germany https://en.wikipedia.org/wiki/Age_of_majority).
Teams of Eligible Individuals (“Teams”)
Organizations (including corporations, not-for-profit corporations and other nonprofit organizations, limited liability companies, partnerships, and other legal entities) that exist and have been organized or incorporated at the time of entry

Student

Eligible individual: University / College students globally. Students must register the hackathon with their student emails to be eligible for participating in the Student segment
Teams of Eligible Individuals (“Teams”)

2. SUBMISSION GUIDE

Makers must do the following to participate in the Hackathon:

a. FOR STUDENT

Register for the Hackathon with your student email address on the Hackathon Website by clicking the “Register for this Hackathon” button. To complete registration, sign up to create a Devpost account, or log in with an existing Devpost account. There is no charge for creating a Devpost account. This will enable you to receive important updates and access the “Enter a Submission” page.
Access the APIs at http://www.icondev.io.
Submissions from students do not have to be a fully functioning software. Students do not have to build SCORE smart contracts (develop in Python or Java), rather they can utilize available ICON SDKs to develop backend services which can communicate with existing SCOREs.
Include a link to the functional software application if available.
Include a link to your solution code on GitHub or any other code repository sharing method. Your code repository may be public or private. If your repository is private, access must be shared with [email protected] and stated in the testing instructions provided with your submission. Code will be used only for solution review and testing.
Create a video that includes footage that clearly explains your application’s features and functionality through a comprehensive demonstration. Clearly state your entry segment at the beginning of your video.
Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Hackathon Submission Period, and follow the requirements below.

A. Language Requirements

All Submission materials must be in English or, if not in English, the Maker must provide an English translation of the demonstration video, text description, and testing instructions as well as all other materials submitted.

B. Application Requirements

(i) What to Create: Student makers can build functioning end to end software utilizing ICON Smart Contracts (SCORE) or utilize available ICON SDKs to develop backend services which can communicate with existing SCOREs, related to at least one of the below categories (each an “Application”).

Categories	Example solutions
1. Social media	Blockchain Social Media are decentralized networking platforms built using blockchain protocols/platforms that allow the development of applications and smart contracts. Examples may include: In-platform transactions Rewarding users Crowdfunding
2. Metaverse	Metaverse refers to shared virtual worlds where land, buildings, avatars and even names can be bought and sold, often using cryptocurrency. Examples may include: Virtual office / conference platforms Virtual land ownership
3. DeFi	Decentralized finance (De-Fi) category refers to financial applications that are being developed on the ICON protocol. Examples may include: Creating monetary banking services Providing peer-to-peer or pooled lending and borrowing platforms Enabling financial instruments such as DEX, tokenization platforms, derivatives and predictions markets
4. NFT	NFT and/or gaming refers to NFT applications that deploy ICON’s NFT Standard or non-NFT based games that utilize the ICON protocol. Note: Gambling/Casino games will NOT be accepted. Examples may include: NFT Card Game NFT RPG Game NFT Marketplace Non-NFT based Blockchain Gaming
5. Utility	Utility category refers to useful ICON applications for non-technical or technical users. They can be applications used daily by the average consumer or technical developer tools that enhance ICON’s developer ecosystem. Examples may include: Useful Dapps for everyday use Developer tools On-Chain analysis

(ii) Functionality: The Application must be capable of being successfully installed and running consistently on the platform for which it is intended, and must function as depicted in the video and/or expressed in the text description.

(iii) Platforms: A submitted Application must run on at least one of the following:

A smartphone or tablet (iOS or Android)
A web browser (mobile or desktop)

(iv) New & Existing: Applications must be either newly created by the Maker or, if the Application existed prior to the Hackathon Submission Period, must have been significantly updated after the start of the Hackathon Submission Period.

(v) Testing: The Maker must make the Application available free of charge and without any restriction, for testing, evaluation and use by the Poster, Administrator and judges during the Hackathon and until the Judging Period ends. Makers must make their Application available for testing by:

Include a link to your solution code on GitHub or using another code repository sharing method. Your code repository may be public or private. If your repository is private, access must be given to [email protected] and testing instructions provided with your submission. Code will be used only for solution review and testing.
Including all deployment files and testing instructions needed for testing the Application.

For Applications running on widely available smartphones, tablets, or desktop computers, Makers may make their Application available using one of the following methods:

a. Android Applications: Upload an .apk file on the Enter a Submission form or provide a link for downloading the Application in the “Testing Instructions” field on the Enter a Submission form.

b. iOS Applications:

If your Application is available on the iTunes App Store provide a link in the “Website URL” field on “Enter a Submission” form. If you charge a fee for downloading your Application, you must provide a promo code.
If your Application is not yet publicly available on the iTunes App Store, you must send a test build to the Administrator before the end of the Hackathon Submission Period using iTunes Connect. Enter the Administrator’s email address to share a build for testing. The Administrator’s iTunes account email is: [email protected]

Administrator UDID:

iOS UDID: e0abfb3b517a10522de16dbd0b72f92cd4a9335f

c. Web/Mobile Web: Provide a link for accessing your Application on the “Testing Instructions” field on the Enter a Submission form.

(vi) Public Distribution: The Maker may make the Application available to the public via a website or online store, but is not required to do so.

(vii) Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Maker’s other Submissions, as determined by the Poster and/or the Administrator.

(viii) SDKs, APIs, & Data: Applications may integrate SDKs, APIs and data, provided the Maker is authorized to use them.

(ix) Intellectual Property: Your Submission must: (a) be your (or your Team or Organization’s) original work product; (b) be solely owned by you, your Team, or your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, and/or privacy rights, of any other person or entity. A Maker may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Maker’s work product and the result of the Maker’s ideas and creativity, and the Maker owns all rights to them. A Maker may submit a Submission that includes the use of open source software or hardware, provided the Maker complies with applicable open source licenses and, as part of the Submission, creates software that enhances and builds upon the features and functionality included in the underlying open source product. By entering the Hackathon you represent, warrant, and agree that your Submission meets these requirements.

(x) Financial or Preferential Support: An Application must not have been developed, or derived from an Application developed, with financial or preferential support from the Poster or Administrator. Such Applications include, but are not limited to, those that received funding or investment for their development, were developed under contract, or received a commercial license, from the Poster or Administrator any time prior to the end of Hackathon Submission Period. The Poster, at their sole discretion, may disqualify an Application, if awarding a prize to the Application would create a real or apparent conflict of interest.

C. Text Description, Image, and Video Requirements

(i) Text Description: The text description should explain the features and functionality of your Application.

(ii) Images: The image(s) should be photographs or screenshots of your working Application.

(iii) Video: The required video portion of the Submission:

should be less than three (3) minutes;
must include footage that clearly explains the Application’s features and functionality through a comprehensive demo of the software;
must be uploaded to 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 Maker has permission to use such material.

D. Submission Modifications

i. Draft Submissions: Prior to the end of the Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Competition for evaluation. Once the Submission Period has ended, you may not make any changes or alterations to your Submission, but you may continue to update the project in your Devpost portfolio.

ii. Modifications after the Submission Period. The Poster may permit you to modify part of your Submission after the Submission Period for the purpose of removing material that potentially infringes a third party mark or right, discloses personally identifiable information, or is otherwise inappropriate. The modified Submission must remain substantively the same as the original Submission with the only modification being what the Poster permits. The administrator may add the Competition hashtag to the demonstration video on behalf of the submitter.

b. FOR DEVELOPER

Register for the Hackathon on the Hackathon Website by clicking the “Register for this Hackathon” button. To complete registration, sign up to create a Devpost account, or log in with an existing Devpost account. There is no charge for creating a Devpost account. This will enable you to receive important updates and access the “Enter a Submission” page.
Access the APIs at http://www.icondev.io.
Build functioning end to end software utilizing ICON Smart Contract (SCORE) and/or interfacing with the ICON protocol in the hackathon categories: Social media, Metaverse, Decentralized Finance, NFT. The software can be a standalone app (front end + back end), SDK to be used with the ICON protocol, or web integration of the ICON protocol.
Testing and development of SCORE (ICON's smart contract) must be done on the ICON Sejong: https://www.icondev.io/introduction/the-icon-network/testnet. This must be followed by a SCORE audit. ICON has launched a new SCORE (smart contract) audit system which you must go through to deploy your projects on the ICON testnet.
Include a link to the functional software application.
Include a link to your solution code on GitHub or any other code repository sharing method. Your code repository may be public or private. If your repository is private, access must be shared with [email protected] and stated in the testing instructions provided with your submission. Code will be used only for solution review and testing.
Create a video that includes footage that clearly explains your application’s features and functionality through a comprehensive demonstration. Clealy state your entry segment at the beginning of your video.
Complete and enter all of the required fields on the “Enter a Submission” page of the Hackathon Website (each a “Submission”) during the Hackathon Submission Period, and follow the requirements below.