HackaTRON® Season 6 (the “Hackathon”) Official Rules

NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR WIN. A PURCHASE OR PAYMENT WILL NOT INCREASE YOUR CHANCES OF WINNING. 

SUBMISSION OF ANY ENTRY CONSTITUTES AGREEMENT TO THESE OFFICIAL RULES AS A CONTRACT BETWEEN ENTRANT (AND EACH INDIVIDUAL MEMBER OF ENTRANT), THE HACKATHON SPONSOR, AND DEVPOST.

1. Dates and Timing

Submission Period: Tuesday, February 20, 2024 (10:30 am Pacific Time) – May 7, 2024 (5:00 pm Pacific Time) (“Submission Period”).

TRON DAO Forum Community Voting Period: Wednesday, May 22, 2024 (9:00 am Pacific Time) – Wednesday, May 29, 2024 (5:00 pm Pacific Time) (“Community Voting”).

Judging: Wednesday, May 22, 2024 (9:00 am Pacific Time) – Wednesday, May 29, 2024 (5:00 pm Pacific Time) (“Judging Period”).

Milestone 1 Winners Announced on Devpost: On or around Tuesday, June 11, 2024 (12:00 pm Pacific Time). 

TRON Demo Week: Monday, June 17, 2024 – Saturday, June 22, 2024 

Milestone 2 Completion - Notified by TRON: On or around Friday, June 28, 2024 (12:00 pm Pacific Time).

2. Sponsor and Administrator

Sponsor: TRON Network Limited, BVI

Administrator: Devpost, Inc. (“Devpost”), 222 Broadway, Floor 19, New York, NY 10038

3. Eligibility

• The Hackathon IS open to: 

• Individuals who are at least the age of majority where they reside as of the time of entry (“Eligible Individuals”);

• Teams of Eligible Individuals (“Teams”); and

• 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, “Entrants”)

An Eligible Individual may join more than one Team or Organization and an Eligible Individual who is part of a Team or Organization may also enter the Hackathon on an individual basis. If a Team or Organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. By entering a Submission on behalf of a Team or Organization you represent and warrant that you are the Representative authorized to act on behalf of your Team or Organization.

• The Hackathon IS NOT open to: 

• Individuals who are residents of, or Organizations domiciled in, a country, state, province or territory where the laws of the United States or local law prohibits participating or receiving a prize in the Hackathon (including, but not limited to, Brazil, Quebec, Russia, Crimea, Cuba, Iran, North Korea, Syria, Nigeria and any other country designated by the United States Treasury's Office of Foreign Assets Control) 

• Organizations involved with the design, production, paid promotion, execution, or distribution of the Hackathon, including the Sponsor and Administrator (“Promotion Entities”).

• Employees, representatives and agents** of such Promotion Entities, and all members of their immediate family or household*

• Any other individual involved with the design, production, promotion, execution, or distribution of the Hackathon, and each member of their immediate family or household*

• Any Judge (defined below), or company or individual that employs a Judge

• Any parent company, subsidiary, or other affiliate*** of any organization described above

• Any other individual or organization whose participation in the Hackathon would create, in the sole discretion of the Sponsor and/or Administrator, a real or apparent conflict of interest 

*The members of an individual’s immediate family include the individual’s spouse, children and stepchildren, parents and stepparents, and siblings and stepsiblings. The members of an individual’s household include any other person that shares the same residence as the individual for at least three (3) months out of the year. 

**Agents include individuals or organizations that in creating a Submission to the Hackathon, are acting on behalf of, and at the direction of, a Promotion Entity through a contractual or similar relationship.

***An affiliate is: (a) an organization that is under common control, sharing a common majority or controlling owner, or common management; or (b) an organization that has a substantial ownership in, or is substantially owned by the other organization.

4. How To Enter

Entrants may enter by visiting trons6.devpost.com (“Hackathon Website”) and following the below steps:

• Register for the Hackathon on the Hackathon Website 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 complete a Project described below in Project Requirements. Use of any 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.

• Entrants must create (or significantly update) a working software application/dApp/website that integrates with the TRON or BitTorrent blockchain and fits into one of the Hackathon tracks.

• Entrants must register not only on Devpost but also register on the TRON DAO Forum and create a post for the TRON Community under the Season 6 categories for TRON community voting. 

• Create a video that explains Entrant’s track and includes footage that explains your project’s features and functionality through a comprehensive demonstration.

• All Entrants are required to complete a TRON DAO Forum Submission during the Submission Period and follow the TRON DAO Forum Submission Requirements below to be eligible for TRON DAO Forum prizes.

• 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.

Projects entered on trons6.devpost.com but have not completed a TRON DAO Forum Submission by May 7th will be disqualified.

Project Requirements

• What to Create: Entrants must create (or significantly update) a working software application/dApp/website that integrates with the TRON or BitTorrent (BTTC) blockchain and fits into one of the hackathon tracks (each a “Project”).
  
  

• Hackathon Tracks:
  
  

• Web3: The Web3 track explores the decentralized future of the Internet. Participants are encouraged to create innovative projects in areas such as Artificial Intelligence, Decentralized Identity, Web3 Social Platforms, DeFi Solutions, Transparent Supply Chains, DAOs, and more! The focus is leveraging blockchain technology to empower users, enhance privacy, and redefine digital experiences.
  
  

• Artistry: Step into a dynamic realm where entertainment converges with blockchain technology. Delve into the future of gaming, crafting groundbreaking game ideas that redefine the industry. Simultaneously, embrace the creator economy and the limitless possibilities of NFT applications.
  
  

• DeFi: DeFi continues to be a crucial movement for the crypto space as it enables finance to operate in an open, accessible, and transparent digital form. Looking for the next innovative DeFI solution that could provide accessible financial resources to billions of people.
  
  

• Builder: A track for returning projects or Integration Track projects that continued development on TRON/BTTC and have created a significant update for their project.
  
  

• Integration: The Integration Track challenges participants to integrate cutting-edge protocols and tools into the TRON ecosystem. This track encourages the exploration of cross-protocol interoperability, scalability solutions, decentralized storage integration, oracle utilization for smart contracts, and privacy-preserving technologies.
  
  

• **Sponsor and Administrator reserve the right to reassign a Project from one category to another if deemed more appropriate based on the content.
  
  

• Functionality: The Project 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.

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

• New & Existing: 

• Projects submitted into the following Tracks: Web3, Artistry, DeFi, and Integration must be newly created by the Entrant.  

• Projects submitted into the following Tracks: Builder, the Entrant’s existing Project prior to the Hackathon Submission Period, must have been significantly updated after the start of the Hackathon Submission Period.

• Third Party Integrations: If a Project integrates any third-party SDK, APIs and/or data, Entrant must be authorized to use them in accordance with any terms and conditions or licensing requirements of the tool.

Devpost 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.

• Include a link to the required TRON DAO Forum project post for the Project.

• Select the Track you are submitting your Project into and complete any additional fields related to the Track.

• Include a text description that should explain the features and functionality of your Project.

• Include a demonstration video of your Project. The video portion of the Submission:

• should be around three (3) minutes (judges are not required to view content beyond the first 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.

• Include the Smart Contracts deployment links on TRON/BTTC (Mainnet / Testnet).

• Include a detailed description of how your Project integrates TRON/BTTC.

• If the Project has been submitted in any form to another hackathon, include which Hackathons.

• Include a valid personal contact - will be used to obtain energy prize.

• Include links to your code repository, website, and socials to help judges review your submission. 

• If Entrant’s website is private, Entrant must include login credentials in its testing instructions.

TRON DAO Forum Submissions Requirements 

• Register for the Hackathon via Devpost.

• Sign up on the TRON DAO Forum.

• Request access to https://forum.trondao.org/g/Hackathon group and wait for the approval. If you have already been accepted to the forum hackathon group in a previous season you can skip this step.

• Approval to the Hackathon group will give you permission to create a project post on the TRON Hackathon > Hackathon Season 6 category on the forum.

• Post your project in the TRON Hackathon > Hackathon Season 6 category on the TRON DAO Forum and tag it with one of the relevant tags: Web3, DeFi, Artistry, Builder, or Integration.

• Follow the hackathon project post format given to create a new topic for your hackathon project.

• Update your project post actively as you make progress throughout the hackathon period.

• Actively answer community questions in your own project post as the community will be the ones that choose the Forum Hackathon winners.

IMPORTANT: Entrants must be eligible to participate according to these official rules. Projects that have been entered on the TRON DAO Forum but have not submitted their projects to Devpost, or vice versa, by May 7th will be disqualified.

Multiple Submissions 

An Entrant may submit more than one Submission, however, each Submission must be unique and substantially different from each of the Entrant’s other Submissions, as determined by the Sponsor and Devpost in their sole discretion.

Submission ownership 

By making the Submission, the Entrant represents and warrants that the Submission is the original work of the Entrant, is  solely owned by the Entrant or Entrant’s Team, and does not violate the IP rights of any other person or entity.

Testing 

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. 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. Judges are not required to test the Project and may choose to judge based solely on the text description, images, and video provided in the Submission.

Access can be provided to the Sponsor and Administrator by sharing with support.hackathon@trondao.org and admin.hackathon@trondao.org. 

If the Project includes software that runs on proprietary or third party hardware that is not widely available to the public, including software running on devices or wearable technology other than smartphones, tablets, or desktop computers, the Sponsor and/or Administrator reserve the right, at their sole discretion, to require the Entrant to provide physical access to the Project hardware upon request.  

Language Requirements

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

Team Representation

If a team or organization is entering the Hackathon, they must appoint and authorize one individual (the “Representative”) to represent, act, and enter a Submission, on their behalf. The Representative must meet the eligibility requirements above. By entering a Submission on the Hackathon Website on behalf of a team or organization you represent and warrant that you are the Representative authorized to act on behalf of your team or organization.

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 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. An Entrant may contract with a third party for technical assistance to create the Submission provided the Submission components are solely the Entrant’s work product and the result of the Entrant’s ideas and creativity, and the Entrant owns all rights to them. An Entrant may submit a Submission that includes the use of open source software or hardware, provided the Entrant 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.

Financial or Preferential Support 

A Project must not have been developed, or derived from a Project developed, with financial or preferential support from the Sponsor or Administrator. Projects developed as part of the Builder or Integration tracks are exempt from this restriction. Such Projects 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 Sponsor or Administrator any time prior to the end of Hackathon Submission Period. The Sponsor, at their sole discretion, may disqualify a Project, if awarding a prize to the Project would create a real or apparent conflict of interest.

5. Submission Modifications

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 Hackathon 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.

Modifications 

After the Submission Period. The Sponsor and Devpost may permit you to modify part of your Submission after the Submission Period for the purpose of adding, removing or replacing 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 Sponsor and Devpost permits. 

6. 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:

1. Originality
   How novel and innovative is the idea? Does it set out to do something unique or at least improve existing models?

2. Technicality
   What is tech like? Is it user-friendly and does it have comprehensive and efficient features? Is it designed to scale?

3. Business Model
   What is the value proposition and how does it set out to differentiate itself? How will it capture the market and/or generate revenue?

4. Usability
   What is the user experience like? Is it clean and intuitive such that users not familiar with blockchain can easily interact with the program?

5. Practicality
   Is this something the community would actually use and want? Will the idea have an impact on the crypto community?

6. Contribution to the Crypto Ecosystem
   How does your idea increase crypto adoption, value for its users, and innovation in the field of blockchain? Does it welcome new users and help existing users?

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.

Stage Three) All Submissions that pass Stage Two will be required to demo at TRON’s Demo Week and required to complete Milestone 2 to receive the full prize amount. The TRON team will check the qualified Milestone 1 winners to ensure Milestone 2 completion by June 28, 2024.

• Milestone 2 completion means that a Milestone 1 winner’s Project is successfully on Mainnet. 

• Track Prize Winners (Devpost) will be awarded 30% of the prize total after the Milestone 1 winners are announced on Devpost. The remaining 70% will be awarded after Milestone 2 Completion on June 28, 2024. 

• Track winners who complete Milestone 2 will be eligible for the TRON Energy Prizes.

• Community Prize Winners (TRON DAO Forum) will be awarded 100% of the prize total after the Milestone 1 winners are announced on Devpost. 

• All Bonus Community Prizes (TRON DAO Forum) will need to meet Milestone 2 completion to receive the full prize amount. These projects will not be given any prize amount during Milestone 1 announcement. 

• Please note that Stage Three may happen after and outside of the Hackathon.

TRON DAO Forum Prize Judging:

The TRON DAO Forum prizes as seen in Section 8 will be awarded based on community votes on the TRON Forum projects. https://forum.trondao.org/ Projects posted on the forum are required to select one of the Track tags at entry: Web3, Artistry, DeFi, Builder, Integration. Potential winners of these prizes must be eligible to participate according to these official rules. The sponsor reserves the right to break ties for this prize by determining a winner.

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.

7. Intellectual Property Rights

All Submissions remain the intellectual property of the individuals or organizations that developed them. By submitting an entry, entrants agree that the Sponsor will have a fully paid, non-exclusive license to use such entry for judging the entry. Entrants agree that the Sponsor and Devpost shall have the right to promote the Submission and use the name, likeness, voice and image of all individuals contributing to a Submission, in any materials promoting or publicizing the Hackathon and its results, during the Hackathon Period and for three years thereafter.  Some Submission components may be displayed to the public. Other Submission materials may be viewed by the sponsor, Devpost, and judges for screening and evaluation. By submitting an entry or accepting any prize, entrants represent and warrant that (a) submitted content is not copyrighted, protected by trade secret or otherwise subject to third party intellectual property rights or other proprietary rights, including privacy and publicity rights, unless entrant is the owner of such rights or has permission from their rightful owner to post the content; and (b) the content submitted does not contain any viruses, Trojan horses, worms, spyware or other disabling devices or harmful or malicious code.

8. Prizes

Important: See section 6 of the rules for requirements to earn the Milestone 2 Prizes.

Initial Allocation | Energy Program

TRON Energy Prize Rules:

• After the initial allocation month, projects will be reviewed by TRON DAO at the beginning of each month for a total of 6 months to check their energy usage. Those needing more energy will be allocated on a case-by-case basis from our $150,000 USDT energy reward pool. 

• Only judge-selected winners will be eligible for energy rewards.

• Energy reload can only be used on Entrants own smart contracts or deployment that you have supplied during the application. Failure to notify of other smart contracts or usage will result in discontinuation. 

• Projects that use more than 50% of awarded energy can claim more energy for next month. This is reviewed monthly on a case-by-case basis. 

• The initial allocation will be $500 USDT worth of energy rental for 1 month for all judge-selected winners. 

• Projects with less than 50% of energy usage will be reviewed to either stay at current energy level rewards or be discontinued from future energy rewards.

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

• A project can win a maximum of one (1) Track (Devpost Projects) AND one (1) Community Prize (TRON DAO Forum Only Projects).

• A project that did not win any Track or Community Prizes may win one (1) Bonus Community Prize (TRON DAO Forum Only Projects).

• Only Track (Devpost Projects) winners will be eligible for the TRON Energy Prizes if the Project meets Milestone 2 completion.

• If there are no eligible submissions or participants for a prize, that prize will not be awarded.

• Entrants that have received prizes in TRON Grand Hackathon Seasons 2-5 are eligible to participate and win with entirely NEW projects OR they can enter the Builder Track, provided they make significant updates or improvements to their existing, non-winning project. 

• Projects that have received prizes in past hackathons are ineligible. 

• Entrants who won may participate with a new project or a previously existing, but updated project that has not won before.

NOTE: There is an additional $25,000 USDT mentioned in the introduction video that TRON will potentially allocate to non Devpost participants based on engagement in the community and possible onsite events.

NOTE: Conversion prices from USD to USDT or TRX will be calculated on the closing market price according to CoinGecko on the Winner Announcement date. Cryptocurrency is subject to a high degree of risk, volatility and illiquidity. Participants should make their own investigations and evaluations of any cryptocurrency that will be delivered pursuant thereto. Participants should inform themselves as to the legal requirements applicable to them in respect of the acquisition, holding and disposition of cryptocurrency and upon delivery, as to the income and other tax consequences to them of such acquisition, holding and disposition. Entrants who are United States Persons (any United States citizen or alien admitted for permanent residence in the United States, and any corporation, partnership, or other organization organized under the laws of the United States) are not eligible to receive a prize in TRX. Winners in the United States are eligible to receive prizes in USDT, subject to providing proof of ownership of a KYC compliant, eligible wallet address issued by an exchange operating in the United States. Winners who are non- United States Persons are eligible to receive prizes in the form of TRX.

1. Substitutions & Changes: Prizes are non-transferable by the winner. Sponsor in its sole discretion has the right to make a prize substitution of equivalent or greater value. Sponsor will not award a prize if there are no eligible Submissions entered in the Hackathon, or if there are no eligible Entrants or Submissions for a specific prize.

2. Verification Requirement: THE AWARD OF A PRIZE TO A POTENTIAL WINNER IS SUBJECT TO VERIFICATION OF THE IDENTITY, QUALIFICATIONS AND ROLE OF THE POTENTIAL WINNER IN THE CREATION OF THE SUBMISSION. No Submission or Entrant shall be deemed a winning Submission or winner until their post-competition prize affidavits have been completed and verified, even if prospective winners have been announced verbally or on the competition website. The final decision to designate a winner shall be made by the Sponsor and/or Administrator. Deadline for Returning Required Forms: ten (10) business days after the Required Forms are sent. Failure to fully complete or return the required forms on time may result in disqualification. Failure of the winner to return the completed paperwork in more than three months will result in forfeiture of the prize.

3. Prize Delivery: Prizes will be payable to the Entrant, if an individual; to the Entrant’s Representative, if a Team; or to the Organization, if the Entrant is an Organization. It will be the responsibility of the winning Entrant’s Representative to allocate the Prize among their Team or Organization’s participating members, as the Representative deems appropriate. At the discretion of the Sponsor, a monetary Prize may be mailed to the winning Entrant’s address (if an individual) or the Representative’s address (if a Team or Organization), or sent electronically to the Entrant, Entrant’s Representative, or Organization’s bank account or wallet address, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. The deadline for returning the Required Forms to the Administrator is ten (10) business days after the Required Forms are sent. Failure to provide correct information on the Required Forms, or other correct information required for the delivery of a Prize, may result in delayed Prize delivery, disqualification of the Entrant, or forfeiture of a Prize. Prizes will be delivered within 60 days of the Milestone 1 and Milestone 2 completion. 

4. Fees & Taxes: Winners (and in the case of Team or Organization, all participating members) are responsible for any fees associated with receiving or using a prize, including but not limited to, wiring fees or currency exchange fees. 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 may be required to provide certain information to facilitate receipt of the award, including completing and submitting any tax or other forms necessary for compliance with applicable withholding and reporting requirements. United States residents may be required to provide a completed form W-9 and residents of other countries may be required to provide a completed W-8BEN form. 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. The Sponsor, Devpost, and/or Prize provider reserves the right to withhold a portion of the prize amount to comply with the tax laws of the United States or other Sponsor jurisdiction, or those of a winner’s jurisdiction.

9. Entry Conditions and Release

1. By entering the Hackathon, you (and, if you are entering on behalf of a Team, Organization each participating members) agree(s) to the following:

1. The relationship between you, the Entrant, and the Sponsor and Administrator, is not a confidential, fiduciary, or other special relationship.

2. You will be bound by and comply with these Official Rules and the decisions of the Sponsor, Administrator, and/or the Hackathon Judges which are binding and final in all matters relating to the Hackathon.

3. You release, indemnify, defend and hold harmless the Promotion Entities, and their respective parent, subsidiary, and affiliated companies, the Prize suppliers and any other organizations responsible for sponsoring, fulfilling, administering, advertising or promoting the Hackathon, and all of their respective past and present officers, directors, employees, agents and representatives (hereafter the “Released Parties”) from and against any and all claims, expenses, and liabilities (including reasonable attorneys’ fees), including but not limited to negligence and damages of any kind to persons and property, defamation, slander, libel, violation of right of publicity, infringement of trademark, copyright or other intellectual property rights, property damage, or death or personal injury arising out of or relating to a Entrant’s entry, creation of Submission or entry of a Submission, participation in the Hackathon, acceptance or use or misuse of the Prize (including any travel or activity related thereto) and/or the broadcast, transmission, performance, exploitation or use of the Submission as authorized or licensed by these Official Rules. 

2. Without limiting the foregoing, the Released Parties shall have no liability in connection with: 

1. Any incorrect or inaccurate information, whether caused by the Sponsor or Administrator’s electronic or printing error, or by any of the equipment or programming associated with or utilized in the Hackathon; 

2. Technical failures of any kind, including, but not limited to malfunctions, interruptions, or disconnections in phone lines, internet connectivity or electronic transmission errors, or network hardware or software or failure of the Hackathon Website;

3. Unauthorized human intervention in any part of the entry process or the Hackathon;

4. Technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or 

5. Any injury or damage to persons or property which may be caused, directly or indirectly, in whole or in part, from the Entrant’s participation in the Hackathon or receipt or use or misuse of any Prize.

The Released Parties are not responsible for incomplete, late, misdirected, damaged, lost, illegible, or incomprehensible Submissions or for address or email address changes of the Entrants. Proof of sending or submitting the aforementioned will not be deemed to be proof of receipt by the Sponsor or Administrator. If for any reason any Entrant’s Submission is determined to have not been received or been erroneously deleted, lost, or otherwise destroyed or corrupted, the Entrant’s sole remedy is to request the opportunity to resubmit its Submission. Such a request must be made promptly after the Entrant knows or should have known there was a problem and will be determined at the sole discretion of the Sponsor.

10. Publicity

By participating in the Hackathon, Entrant consents to the promotion and display of the Entrant’s Submission, and to the use of personal information about themselves for promotional purposes, by the Sponsor, 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 but is not limited to advertising and promotional purposes. 

11. General Conditions 

1. Sponsor and Administrator reserve the right, in their sole discretion, to cancel, suspend and/or modify the Hackathon, or any part of it, in the event of a technical failure, fraud, or any other factor or event that was not anticipated or is not within their control.

2. Sponsor and Administrator reserve the right in their sole discretion to disqualify any individual or Entrant if it finds to be actually or presenting the appearance of tampering with the entry process or the operation of the Hackathon or to be acting in violation of these Official Rules or in a manner that is inappropriate, unsportsmanlike, not in the best interests of this Hackathon, or a violation of any applicable law or regulation.

3. Any attempt by any person to undermine the proper conduct of the Hackathon may be a violation of criminal and civil law. Should the Sponsor or Administrator suspect that such an attempt has been made or is threatened, they reserve the right to take appropriate action including but not limited to requiring an Entrant to cooperate with an investigation and referral to criminal and civil law enforcement authorities.

4. If there is any discrepancy or inconsistency between the terms and conditions of the Official Rules and disclosures or other statements contained in any Hackathon materials, including but not limited to the Hackathon Submission form, Hackathon Website, or advertising, the terms and conditions of the Official Rules shall prevail.

5. The terms and conditions of the Official Rules are subject to change at any time, including the rights or obligations of the Entrant, the Sponsor and Administrator. The Sponsor and Administrator will post the terms and conditions of the amended Official Rules on the Hackathon Website. To the fullest extent permitted by law, any amendment will become effective at the time specified in the posting of the amended Official Rules or, if no time is specified, the time of posting.

6. If at any time prior to the deadline, an Entrant or prospective Entrant believes that any term in the Official Rules is or may be ambiguous, they must submit a written request for clarification. 

7. The Sponsor or Administrator’s failure to enforce any term of these Official Rules shall not constitute a waiver of that provision. Should any provision of these Official Rules be or become illegal or unenforceable in any jurisdiction whose laws or regulations may apply to an Entrant, such illegality or unenforceability shall leave the remainder of these Official Rules, including the Rule affected, to the fullest extent permitted by law, unaffected and valid. The illegal or unenforceable provision shall be replaced by a valid and enforceable provision that comes closest and best reflects the Sponsor’s intention in a legal and enforceable manner with respect to the invalid or unenforceable provision.

8. Excluding Submissions, all intellectual property related to this Hackathon, including but not limited to copyrighted material, trademarks, trade-names, logos, designs, promotional materials, web pages, source codes, drawings, illustrations, slogans and representations are owned or used under license by the Sponsor and/or Administrator. All rights are reserved. Unauthorized copying or use of any copyrighted material or intellectual property without the express written consent of its owners is strictly prohibited. Any use in a Submission of Sponsor or Administrator’s intellectual property shall be solely to the extent provided for in these Official Rules.

12. Limitations of Liability

By entering, all Entrants (including, in the case of a Team or Organization, all participating members) agree to release the Released Parties from any and all liability in connection with the Prizes or Entrant’s participation in the Hackathon. Provided, however, that any liability limitation regarding gross negligence or intentional acts, or events of death or body injury shall not be applicable in jurisdictions where such limitation is not legal.

13. Disputes

1. Except where prohibited by law, as a condition of participating in this Hackathon, Entrant agrees that:

1. Any and all disputes and causes of action arising out of or connected with this Hackathon, or any Prizes awarded, shall be resolved individually, without resort to any form of class action lawsuit, and exclusively by final and binding arbitration under the rules of the American Arbitration Association and held at the AAA regional office nearest the contestant;

2. The Federal Arbitration Act shall govern the interpretation, enforcement and all proceedings at such arbitration; and

3. Judgment upon such arbitration award may be entered in any court having jurisdiction.

2. Under no circumstances will Entrant be permitted to obtain awards for, and Entrant hereby waives all rights to claim, punitive, incidental or consequential damages, or any other damages, including attorneys’ fees, other than contestant’s actual out-of-pocket expenses (i.e., costs associated with entering this Hackathon), and Entrant further waives all rights to have damages multiplied or increased.

3. All issues and questions concerning the construction, validity, interpretation and enforceability of these Official Rules, or the rights and obligations of the Entrant and Sponsor in connection with this Hackathon, shall be governed by, and construed in accordance with, the substantive laws of the State of New York, USA without regard to New York choice of law rules.

SOME JURISDICTIONS DO NOT ALLOW THE LIMITATIONS OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OF LIABILITY MAY NOT APPLY TO YOU.

14. Additional Terms

Please review the Devpost Terms of Service at https://info.devpost.com/terms for additional rules that apply to your participation in the Hackathon and more generally your use of the Hackathon Website. Such Terms of Service are incorporated by reference into these Official Rules, including that the term "Poster" in the Terms of Service shall mean the same as "Sponsor" in these Official Rules." If there is a conflict between the Terms of Service and these Official Rules, these Official Rules shall control with respect to this Hackathon only.

15. Entrant’s Personal Information

Information collected from Entrants is subject to the Devpost’s Privacy Policy, which is available at https://info.devpost.com/privacy.

For questions, send an email to support@devpost.com.