HACKATHON RULES

Hackathon Name: UTON HACK (the “Hackathon”)

Hackathon Website: https://utonhack.com (the “Hackathon Website”)

You can learn more about LikeLib on GitHub

  • Hacks must fall into one of our tracks. Hacks which don't fall into any of our tracks will not be eligible for prizes. You can find the tracks on our website. 
  • Processes and Services source code must be uploaded to publically-available GitHub in repositories
  • Teams that make it to the final round will be given up to three minutes to present their finished project to a panel of judges.
  • At least one team member must be has opportunity present during CLOSING CEREMONY to show online the project to the judges during assigned presentation time.
  • The prizes will be awarded solely based on the decision of the judging panel.

 

DATES AND TIMING

UTONHACK Opening Ceremony: July 17, 2020 01:00 PM UTC Live Stream

Hackathon Submission Period: July 17, 2020 (01:00pm Coordinated Universal Time) – July 25, 2020 (08:00pm Coordinated Universal Time)

Judging Period: July 26, 2020 – August 2, 2020 

Winners Announced: On August 2, 2020  Live Stream

 

UTONHACK 2.0 WEBINARS

1. Sat, Jul 18, 2020

2. Sun, Jul 19, 2020

 

ELIGIBILITY

The Hackathon is open to:

  • Individuals (provided they are at least eighteen years old)
  • Teams of Eligible Individuals
  • 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.

(the above are collectively, “Makers”)

The Hackathon is not open to:

  • Individuals who are residents of, or Organizations domiciled in any country, state, province or territory where the laws prohibits participating or receiving a prize in the Hackathon
  • Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon
  • Any Judge or company that employs a Judge
  • Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Administrator, a real or apparent conflict of interest

 

PRIZES and Nominations:

We invite you to compete in two prize blocks, each of which contains three interesting nominations. Hackathon participants must create a working prototype of the blockchain project and submit their decision to the jury on July 25 (5pm Eastern Time).

1. LikeLib Ecosystem

Create your solution to expand application tools, functionality and usability of LikeLib. We’re looking for useful tools in the LikeLib ecosystem (e.g. wallets, explorers, process builders, debuggers), or new services and processes. 

  • BEST SOLUTION FOR LIKELIB - 9000 USDT
  • BEST FINTECH PROJECT - 4500 USDT
  • BEST SMART-CONTRACT - 4500 USDT

You can learn more about LikeLib on GitHub

2. Blockchain Ecosystem

Hackathon participants must create a working prototype with using any blockchain technology

  • BEST BLOCKCHAIN GAME - 4500 USDT
  • BLOCKCHAIN & IOT - 4500 USDT
  • HACK THE CRISIS - 4500 USDT

Prizes will be delivered within 30 days of the Sponsor’s receipt of declaring the Winner.

 

SUBMISSION REQUIREMENTS

1. How to Enter

Makers must do the following to participate in the Hackathon:

  • 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 receive important updates and access the “Enter a Submission” page.

2. Text Description and Video Requirements

Text Description: The text description should explain the features and functionality of your Application

Video (Optional): The video portion of the Submission:

a) should be less than five (5) minutes;

b) should include footage that clearly explains the Application’s features and functionality through a comprehensive demonstration;

c) should be uploaded to YouTube, Vimeo, or Youku, and a link to the video must be provided on the submission form on the Hackathon Website;

d) must not include third party trademarks, or copyrighted music or other material unless the Maker has permission to use such material.

Main requirement: Build at one of the following two options: 

  1. Tooling or improvements for the LikeLib ecosystem (e.g. wallets, explorers, process builders, debuggers, compilers, linters)

  2. An application based on the processes and / or services of any blockchain technology.

New and Existing: Applications must be either newly created or, if the Application existed prior to the Hackathon Submission Period, must have been updated after the start of the Hackathon Submission Period.

Testing: The Maker must make the Application available free of charge and without any restriction, for testing, evaluation and use by the judges during the Hackathon and until the Judging Period ends. The Maker must include a link to their application code on GitHub.

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

Multiple Submissions: A Maker may submit more than one Submission, however, each Submission must be unique

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, your or your Organization with no other person or entity having any right or interest in it;

(c) not violate the intellectual property rights or other rights including but not limited to copyright, trademark, patent, contract, licensing terms of use, 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.

Submit the following before 04:00pm EST July 25th, 2020:

  • Completed submission form with all required details. Late submissions won’t be accepted.
  • A link to your publically-accessible code repository on Github and access to your application.
  • A step-by-step demo video showcasing your application.

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.

Draft Submissions: Prior to the end of the Hackathon Submission Period, you may save draft versions of your Submission on Devpost to your portfolio before submitting the Submission materials to the Hackathon for evaluation.

 

JUDGING

Judges: Eligible Submissions will be evaluated by a panel of judges.

Criteria: The Judges will score eligible Submissions using the following equally weighted criteria (the “Judging Criteria”):

  • Application/Impact
  • Technical Complexity
  • Creativity/ Innovation
  • Functionality/Quality

Submission Review: Judges are not required to test the Application and may choose to judge Applications based solely on the text description and video provided in the Submission.

 

VERIFICATION OF POTENTIAL WINNERS

Verification Requirement: The award of a prize to potential winner is subject to verification of the identity, qualifications and role of the potential winner in creation of the submission. Potential winners will be notified using the email address associated with the Devpost account used to enter the Submission.

PRIZE DISTRIBUTION

Prize Delivery: Prizes will be payable to the Maker, if an individual, to the Maker’s Representative, if a Team or Organization, if the Maker is an Organization. It will be the responsibility of the winning Maker’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate.

Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for reporting and paying all applicable taxes in their jurisdiction of residence (federal, state/provincial/territorial and local). Winners are also responsible for complying with foreign exchange and banking regulations in their respective jurisdictions and reporting the receipt of the Prize to relevant government departments/agencies, if necessary.

 

PUBLICITY

By participating in the Hackathon you consent to the use of personal information about you, if you are a winner, by the Poster, Administrator, and third parties acting on their behalf. Such personal information includes, but is not limited to, your name, likeness, photograph, voice, opinions, comments and hometown and country of residence. It may be used in any existing or newly created media, worldwide without further payment or consideration or right of review, unless prohibited by law. Authorized use includes advertising and promotional purposes.

This consent applies, as applicable, to all members a Maker’s Team, or Organization that participated in the winning Submission.

 

CODE OF CONDUCT

  • As per Hack Code of Conduct, there is no discrimination on the basis of race, religion, national origin, color, sex, gender identity, sexual orientation, social class, economic status, veteran status or disability.
  • Please treat all other participants with the utmost respect. We ask that you act kindly, behave professionally, and do not insult or put down other attendees. If at any point you see a fellow hacker being harassed, please talk to the nearest hackathon organizer.
  • Please treat our sponsors, organizers, and judges with the utmost respect. Without them, nothing would be possible.
  • Failure to comply with the above-stated Rules and Code of Conduct may result in the offending team's disqualification.