Polkadot Hackathon Global Series: North America Edition (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

Registration Period: May 18, 2022 at 9:00 am Pacific Time – May 30, 2022 at 5:00 pm Pacific Time (“Registration Period”).

Submission Period: May 30, 2022 at 9:00 am Pacific Time – July 11, 2022 at 12:00 am Pacific Time (“Submission Period”).

Judging Period: July 12, 2022 at 9:00 am Pacific Time – July 17, 2022 at 5:00 pm Pacific Time (“Judging Period”).

Winners Announced: On or around July 18, 2022 at 9:00 am Pacific Time.

2. Sponsor and Administrator

Angelhack Pte Ltd - 79 Robinson Road, #07-01, Singapore 068897, Singapore

3. Eligibility

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

B. 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 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 polkadot-na.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 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.
• Complete and enter all 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 create a project built on one of the following ecosystems/technologies: Polkadot, Kusama, or Substrate and indicate which track you are submitting to: (each a “Project”). All valid submissions will automatically be considered for the Community Choice prize.

• Interfaces & Experiences: Build a UX/UI interface or experience using Polkadot, Kusama, or Substrate
• DAO & Governance: Build a DAO, DAO tool, new governance mechanism, governance pallet or other solution advancing DAOs and governance for the Polkadot, Kusama or Substrate ecosystem
• DeFi: Build a DeFi related solution using Polkadot, Kusama, or Substrate
• NFT: Build a project to create a new NFT use case
• Web3 & Tooling: Build a tool or application that expands on Polkadot, Kusama, or Substrate’s web technology.
• Sponsor Challenges: Projects being submitted for Sponsor Prizes, must also follow the specific requirements listed in the corresponding section 

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

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

iv. Projects must be newly created by the Entrant after the start of 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. 

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. Project must include testing instructions for judging.  

For Projects running on widely available smartphones, tablets, or desktop computers, Entrants may make their Project 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 Project in the “Testing Instructions” field on the Enter a Submission form.

b. iOS Applications: 

• If your Project is available on the iTunes App Store provide a link on your submission form. If you charge a fee for downloading your Project, you must provide a promo code.
• If your Project is not yet publicly available on the iTunes App Store, you must send a test build to testing@devpost.com before the end of the Hackathon Submission Period iTunes TestFlight: https://developer.apple.com/testflight/ TestFlight / iTunes Connect: Enter the Administrator’s email address to share a build for testing. The Administrator’s TestFlight account email is: testing@devpost.com. 

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

d. Public Distribution: The Entrant may make the Project available to the public via a website or online store but is not required to do so. 

Submission Requirements. Submissions to the Hackathon must meet the following requirements:

1. Include a Project built with the required developer tools and meets the above Project Requirements.

2. Project Description
a. This is a detailed description of your team's project which should be a minimum of 150 words and contain the following:

i. Name and summary of the project
ii. Names/pseudonyms of team members and contact information (e.g. GitHub handle, email address, etc)
iii. The track you are submitting to and an overview of what problem is being addressed
iv. How the project uses Substrate, Kusama, Polkadot

3. Video Demo (note: different requirements for individuals and teams of individuals vs organizations; see below)
a. Demo Video
i. Create a video that includes footage that clearly explains your submission’s features and functionality through a comprehensive demonstration. (required)
ii. Maximum length 5 minutes

4. GitHub Repo Link
a. Each team to appoint 1 (one) person to create the team's GitHub repo and share the access with the team to collaborate on. During submission, the team needs to submit the link to this GitHub Repo which can be accessible to the judges.
b. Access must be provided to an Entrant’s working Project for judging and testing by: 
i. Providing a link to a repo hosting the application’s code and any other deployment files and testing instructions.
ii. Must have an open source license (GPL, MIT, Apache, and Unlicense are accepted, others may be considered on a case by case basis)

5. List of Tech Stack Used 
a. This is a list of tech stack used by the team to build your project

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

7. Access must be provided to an Entrant’s working Project for judging and testing by: 
a. Providing a link to a repo hosting the application’s code and any other deployment files and testing instructions.
b. Must have an open source license (GPL, MIT, Apache, and Unlicense are accepted, others may be considered on a case by case basis)

8. Entrants may not submit more than one submission.

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

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

B. 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 weighted criteria, and according to the sole and absolute discretion of the judges:

• Ecosystem Impact and Usefulness: How impactful and useful is the submission in the Polkadot/Kusama/Substrate ecosystem? 
• Web3 Contribution and Advancement: How does the submission contribute to and advance Web 3.0 as a whole? 
• Originality, Creativity and Innovation: How new and novel the submission is versus existing technologies? 
• Technical Difficulty: What is the level of skill or knowledge required to build the submission?
• Mass Usability: How feasible is the idea? How adaptable is it across other integrations? How sound is the business model?
• Specific sponsor prizes will have the following judging criteria: 
  • Acala:
    • Contribution to the Acala and aUSD Ecosystem (25%): Includes how useful the DApp is in the Acala and Karura ecosystem as a whole.
    • Originality, Creativity, and DeFi Innovation (25%): Includes how novel and creative the submission is versus existing technologies.
    • Technical Difficulty (25%): Includes the level of skill or knowledge required to build the DApp.
    • User Experience (25%): Includes how intuitive and understandable the project is for potential users or developers.
  • Astar Network
    • Contribution to the Astar ecosystem (25%)
    • Originality, Creativity, and Innovation (25%)
    • Technical Difficulty (25%)
    • User Experience (25%)
  • Crust Network:
    • Involved with IPFS
    • Involved with Crust cross-chain storage on Polkadot or directly with Crust blockchain
  • Equilibrium: 
    • A chain is launched with 2 validators (Alice, Bob) and N clients for balance distributors in each of the tokens. Then, every 3 blocks, 10 accounts are alternately added to the distributor and then 10 accounts are withdrawn from the distributor. If the data on the chain after several runs is correct and the block time of the chain has not exceeded 6 sec, N increases. The solution that works at the maximum N wins.
  • ICE Network:
    • Impact: How will the project impact the ICE ecosystem?
    • Quality of work: How well was the project developed?
    • User Experience: How well is the user experience and ease of use?
    • Novelty of idea: What unique idea/s does the project present and how creative was the idea?
    • Viability of a business: How viable is it to turn the project into a real business?"
  • Interlay:
    • Contribution to the Interlay/Kintsugi (iBTC/kBTC) Ecosystem (25%): Includes how useful the project is in the Interlay and Kintsugi ecosystem as a whole.
    • Originality, Creativity, and Innovation (25%): Includes how novel and creative the submission is versus existing technologies.
    • Technical Difficulty (25%): Includes the level of skill or knowledge required to build the project.
    • User Experience (25%): Includes how intuitive and understandable the submission is for potential Vaults
  • Phala Network:
    • For Advanced Challenge, a qualified submission should be useful to solve some real-world problems or bring fun to people. It should also address the unique features of Phala (privacy-preserving, CPU extensive, or with HTTP requests).
  • Robonomics Network:
    •  
    • Video with the demonstration of the use case. 
    • A link to github repository with source code provided. 
    • A short explanation of what you've done during the hackathon
  • RMRK:
    • The end result should be open source and locally runnable (decentralized) - not relying on some server that cannot also be run by the person running the UI.
    • Fewer SPOFs are better. Building UIs for RMRK on Pallets and EVM carries more weight than building UIs for RMRK on Kusama (consult the docs for implementations differences).
  • Subsocial:
    • Idea
    • Clean code
    • Working dapp 
    • Usage of Subsocial SDK or blockchain 
    • Startup potential, and future plans.
  • Subsquid:
    
    • Functionality (25%)
    • Performance (25%)
    • Understandability (25%)
    • Ease of use (25%)
  • Combined challenge by SubQuery, Moonbeam, Acala and HydraDX:
    • Understandability: How easy it is to understand and use for the average user (most important aspect)
  • SubQuery challenges:
    
    • Substrate Wasm Contract Support (with Gear):
      
      • How similar your implementation is to the existing Substrate EVM data processor implementation for consistency
      • How well you implement different handlers that make sense for wasm
      • Does your solution work with minimal configuration for other wasm implementations (like Astar)?
      • How much documentation you provide
    • aUSD/kUSD Liquidation Tools (with Acala):
      
      • How easy to use and intuitive the application is
      • How easy you make it for participants to participate in these events
      • Can you get notifications of events (e.g. via email or telegram bot) when they occur so you can participate
    • Cross Chain Indexing (SubQuery Project Composability):
      
      • Does this allow a user to index two seperate SubQuery projects into one data set
      • How well does your solution handle when the two projects are synced to different heights
      • When indexing two parachains, does your project account for the differences between blockheights on the different parachains (due to different lease starts)
      • Does your solution enable the following possible use cases
      • Polkadot XCM cases like cross-chain token transfer.
      • Isomeric chain bridge-like wormhole
    • RMRK Time-based NFT Explorer (with RMRK):
      • Entries will only be accepted if use SubQuery to index RMRK NFTs
      • You will be assessed on features first, and usability second
      • How well you manage to build a user experience around "time slider" aspect of this challenge
  • Unique Network:
    • Best concept (idea) 
    • Best method of implementation
    • Adherence to use of chain-native tools
    • Best presentation
  • Zeitgeist:
    
    • Quality
    • Creativity
    • Level of technical prowess

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.

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.

** If submitting a Substrate project, winners will receive an expedited session for the Substrate Builders Program

IMPORTANT NOTES ON MULTIPLE PRIZE ELIGIBILITY:

Entrants are eligible to win up to one track prize and one sponsor prize.

SPONSOR PRIZE REQUIREMENTS

• By making a Submission in the Sponsor Prize Category, Entrants acknowledge, and agree, that the Sponsor is fully responsible and in charge of, including but not limited to, the judging process, the winner selection, and the payout of the Sponsor Prize. In doing so, the Entrant discharges the Administrator from any liability or responsibility regarding the Sponsor Prize Category.
• Entrants must build a functional software application using the sponsor’s technology. Entrants must indicate which prize they are submitting for when they submit their project. Requirements of main tracks must be followed. 

Further sponsor prize requirements are the following:

• Acala Bounties: 
  • Must be deployed on Acala's Mandala testnet or your own testnet
• Astar Network Bounties:
  • You can submit your solution by opening a PR on GitHub.
  • Contact information (Telegram handle or email)
  •   Name of bounty you participated in
• Crust Network:
  • At least using Crust cross-chain storage or crust blockchain storage
  • Open sourced
• Equilibrium:
  • Code should be committed to their dedicated repository.
• ICE Network:
  • A working hosted and usable dApp.
  • Github or Gitlab link of the project built with its source code in its entirety.
• Interlay Bounties:
  • Name of bounty
• Phala Network: 
  • For Beginner Challenge, refer to this page.
  • For Advanced Challenge, refer to this page.
• Robonomics Network
  • Preferably github repository with python or JS implementation of the solution.
• RMRK:
  • Must be open source
  • Runs in local env. 
• Subsocial:
  • Public GitHub repository; 
  • comprehensive Readme file on how to use a dapp; 
  • the dapp should be deployed so that judges can try it; 
  • demo video of the dapp; 
  • GPL-3.0 license is preferred.
• Subsquid Bounties:
  • Reach out to Subsquid team via GitHub (Telegram or Discord are OK as well) before starting to work.
  • Submission should be a Pull Request to Squid's main repository, whereas DIA integration should be a PR to a repository that will be created specifically for the hackathon.
• Combined challenge by SubQuery, Moonbeam, Acala and HydraDX:
  • The final submission must include at least Moonriver, Karura, and Basalisk, and must use SubQuery to index the XCM events
• SubQuery:
  • please consult the challenge descriptions on this page
• Zeitgeist:
  
  • Code must be open-source.
  • No plagiarism.

Language requirements: All Submission materials must be in English or, if not in English, the team must provide an English translation of any demonstration videos, text descriptions, and testing instructions as well as all other materials submitted.

NOTE: 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, and as to the income and other tax consequences to them of such acquisition, holding and disposition.

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

B. 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 submitter 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.

C. 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. A monetary Prize will 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, only after receipt of the completed winner affidavit and other required forms (collectively the “Required Forms”), if applicable. 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 or the Entrant, or forfeiture of a Prize. Prizes will be delivered within 60 days of the Sponsor or Devpost’s receipt of the completed Required Forms.

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

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

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

(ii) 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.

(iii) 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. 

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

(i) 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; 

(ii) 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;

(iii) unauthorized human intervention in any part of the entry process or the Hackathon; 

(iv) technical or human error which may occur in the administration of the Hackathon or the processing of Submissions; or 

(v) 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. 

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

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

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

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

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

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

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

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

A. 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 jurisdiction of the Courts of Singapore;
2. the Singapore International Arbitration Centre 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.

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

C. 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 Singapore. 

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.