DAPP Network Hackathon

234 Registered Allowed team size: 2 - 5

Winners are announced.

hackathon
Online
starts on:
Nov 17, 2019, 06:00 AM
ends on:
Nov 24, 2019, 11:00 AM

Winners

Rules

  1. Registration & Teams

    1.1. The Hackathon DAPP Network Hackathon (the “Hackathon”) is a team competition. Enrolment in the Hackathon is only possible as a team of at least two (2) and a maximum of five (5) participants. Participants cannot be a member of more than one team or switch teams.

    1.2. Enrolment in the Hackathon is only possible through the HackerEarth Sprint Platform’s DAPP Network Hackathon page (the “Platform”, https://dappnetwork.hackerearth.com). Each team member must be registered to the Hackathon using the Platform prior to submitting a project.

    1.3. Each team may only take part in the development and submission of one project.

    1.4. Please note: Individual work is not allowed in the Hackathon, and projects that will be submitted by a single individual participant (which is not a Team Leader, as defined below) will not be accepted nor evaluated.

    1.5. Each team must nominate an individual that will act as the team representative (“Team Leader”), being the sole contact person regarding all matters relating to the Hackathon. The individual user who has been selected as the Team Leader, should invite all other team members to join his team on the Hackathon platform.

    1.6. Participants must be at least 18 years or older, or have reached the age of majority in the relevant jurisdiction, to be eligible to participate in the Hackathon.

    1.7. By enrolling in the Hackathon, participants shall be deemed to have accepted the Hackathon Rules and Terms and Conditions.


  2. Communications

    2.1. General information regarding the Hackathon, including the Rules of Participation and Terms and Conditions, can be found on the Platform.

    2.2. The Hackathon’s formal communication environment is the Hackathon’s designated Slack workspace (“Slack”, click to enter). Announcements, updates and other relevant information will be given on Slack and it is the participants’ sole responsibility to monitor it for any update or change.

    2.3. All the participants will be added to the following channels on Slack:
    ■ #announcements - formal announcements, updates, and messages that relate to all Hackathon participants will be published there. Only admins can post on this channel.
    ■ #find-team - a dedicated channel for participants to get in touch with each other, search for team members and form teams.
    ■ #general - a channel for all non-technical related discussions and general information.
    ■ #rules - for questions and clarifications regarding the Rules, Terms & Conditions, and grey areas. Please note: Only answers given by the LiquidApps team are to be considered official responses.
    ■ #guidance - for support and guidance with the product, the business aspects of your project, pitching it, and any non-technical issues.
    ■ #tech-support - Q&A Zone for technical support. Mentoring and technical guidance along the Hackathon will be given on this channel.
    ■ #dsp-support - for technical support regarding working with DSPs, accessing service packages and similar issues.
    ■ #random - a dedicated channel for conversations regarding non-Hackathon related matters.


    2.4. Participants are allowed to open private channels and one-on-one chats on Slack for internal communication regarding the Hackathon.

    2.5. Participants are required to be courteous to their fellow hackers, behave in a professional manner, and treat them with respect and dignity. Failing to meet this rule might result in expelling from Slack and/or the Hackathon.


  3. Hacking Rules

    3.1. The hacking period starts on Sunday, November 17th 2019, at 11:00 UTC.

    3.2. The deadline for submissions is Sunday, November 24th 2019, at 17:00 UTC (the “Submission Deadline”).

    3.3. Please note: The Hackathon deadlines are subject to change, and additional deadlines may be introduced during the Hackathon. Any additional or altered deadlines, not already described in these rules, will be updated on Slack’s #announcements channel and all participants will be bound by such changes. It is the participants’ sole responsibility to monitor Slack’s #announcements channel regularly to get information about new or updated deadlines.

    3.4. Fresh Code Enforced: The projects must be built from the ground. All teams can start coding at the same time and face the same submission deadline. Participants may utilize and include open-source repositories and libraries, as long as these are available to everyone and team members are not the main contributor to these repositories.

    3.5. Code Review: Winning teams may be subject to a code-review at some point in time following the Hackathon, or even immediately after submission or winning the competition. This is to ensure that all code used is in fact fresh.

    3.6. KEEP YOUR PERSONAL KEYS SAFE! - no member of the LiquidApps team or mentors will ever ask you about your personal keys. If you witness such an incident, please report to hackathon@liquidapps.io at once.


  4. Themes

    4.1. The Hackathon challenges include three independent themes: (1) Decentralized finance ("DeFi"); (2) Decentralized gaming ("Gaming"); (3) Extending the DAPP Network’s Functionality ("New Service").

    4.2. Each submitted project must fall within (at least) one of the above three themes.

    4.3. The instructions for creating a project that falls within the DeFi theme are as follows: Take part in making the financial system more transparent by building any DeFi-related dApp, product or service that harnesses at least two DAPP Network services.

    4.4. The instructions for creating a project that falls within the Gaming theme are as follows: Use at least two DAPP Network services to build any kind of game or game-related product, and play your part in the blockchain gaming revolution.

    4.5. The instructions for creating a project that falls within the New Service theme are as follows: Build your own service that DSPs can offer on a free-market basis, and help create new opportunities for developers building scalable dApps using the DAPP Network


  5. Guidelines for Submissions

    5.1. Each Team Leader shall submit his team’s project in the platform before meeting the Submission Deadline.

    5.2. Submissions after the Submission Deadline or contrary to the guidelines described under this section will be disqualified and will not be considered.

    5.3. Projects can be submitted at any time after the hacking period started. The last version that was uploaded to the Platform will count as the submission.

    5.4. LiquidApps is not responsible for any lost, delayed, misdirected, incomplete, damaged or undeliverable submissions.

    5.5. Each submission must include the following items (“Mandatory Items”):
    Project pitch: A link to a pre-recorded video pitch and/or demo of your project. The pitch should be up to a three (3) minute long and should demonstrate what your team has built. Any length of time over three (3) minutes will not be watched.
    Source code: A link to a private GitHub repository or a link to a downloadable compressed file, containing all of the project's source code.
    Please note: In case a private GitHub repository is being used, the link may be submitted any time before the deadline. When evaluating the codebase, only the last commit before the deadline will be considered.

    5.6. Running dApp: In addition to the Mandatory Items described in section 4.5 above, teams are encouraged to submit a link to a functional version of the decentralized application that they have built (“Running dApp”). Submitted Running dApps will be evaluated and could gain the submitting teams extra points. Running dApps must be submitted through the Platform.

    5.7. In case participant had utilized and included open-source repositories and libraries, as described in section 3.4 above, they must include a specific list of these repositories, libraries, etc. in their submission (links included).

    5.8. Technical specifications and requirements:
    ■ The submitted project will be deployed on Kylin Testnet, and/or on any other environment that will be accessible for an external review, and must include a smart contract.
    ■ Also, if the submitted project falls within DeFi and/or Gaming theme, it must explicitly utilize at least two (2) DAPP Network services and/or products that are already in Beta Release (i.e. LiquidAccounts, although it uses vRAM as part of its core functionality, counts as only one service). At the moment, these services include, among other: vRAM, LiquidOracles, LiquidAccounts, and LiquidScheduler.
    Please note: additional services might reach Best Stage towards or during the Hackathon, and will be counted as part of this section’s requirement. The updated stage for each service and/or product can be found on https://docs.liquidapps.io under “Services” section. It is the participants’ sole responsibility to make sure the services they choose to implement in their projects are qualifying for this section’s requirements.
    ■ If the submitted project falls within New Services theme and extends an existing service, the extension must be significant, enable new functionality, demonstrate a brand new opportunity or make something radically easier that was more difficult before. It will be the Judges and Examiners (as described below) sole discretion to determine whether a submitted project demonstrated such significant improvement or not.
    Please note: For this section, any service that appears in the LiquidApps documentation page (https://docs.liquidapps.io) will be considered as an existing service.
    ■ The following DAPP Service Providers (“DSPs”) are available on Kylin Testnet for the Hackathon participants to use: heliosselene and/or uuddlrlrbass. It is up to the participants to decide whether to use one of them or both (in case they would like to demonstrate redundancy which might be required for the specific service/s they decide to implement).
    ■ Teams may deploy and run their own DSP node/s as part of the Hackathon and using it in their projects. In that case, it is the team’s sole responsibility to make sure their DSP/s will function properly while their smart contracts might be tested and evaluated (such a test and evaluation might take place up until December 31st, 2019).
    ■ Participants are allowed to use the DAPP Kyling Testnet Faucet (https://kylin-dapp-faucet.liquidapps.io) to acquire DAPP tokens on Kylin.
    ■ Participants are allowed to use the Kylin Testnet Faucet to create new accounts (http://faucet.cryptokylin.io/create/new_account_name) and/or to acquire EOS tokens, that could be used to gain access to resources such as RAM, CPU, and Net (http://faucet.cryptokylin.io/get_token/your_account_name).

    5.9. Teams are allowed, but not obligated, to submit additional materials in which they think could contribute to their submission (e.g. snapshots, presentation, demo link, instructions, etc., “Additional Materials”). Any Additional Materials must be submitted through the Platform.

    5.10. In their project pitch, teams may present their submission in any way they see fit, but they are encouraged to explain and demonstrate how their project meets the Judging Criteria below.

    5.11. All submissions are deemed to confirm the following:
    ■ It does not breach the Hackathon Rules and Terms and Conditions.
    ■ It does not breach the terms and conditions of any embedded software or service used by your submission.
    ■ It does not violate any intellectual property rights.
    ■ It does not contain or refer to any crude, vulgar, obscene, sexually explicit, disparaging, discriminatory, offensive, illegal or otherwise unsuitable language, activity or other content (all as determined by LiquidApps in its sole discretion).
    ■ It does not contain any content that violates any law or any third party’s rights (including without limitation privacy, personality and intellectual property rights).
    ■ It does not contain viruses, worms, Trojan Horses, backdoors and all other types of disabling harmful or malicious code.

    5.12. LiquidApps may disqualify submissions, in its sole discretion, with or without warning, in case they do not apply with the Hackathon Rules and/or the Terms and Conditions, including but not limited to the criteria set under section 4.11 above.


  6. Evaluation and Judging of the Submitted Projects

    6.1. A panel of judges (the “Judges”) will select the winners (the “Final Round”). The judges consist of employees at LiquidApps, complemented by experts in the fields of Blockchain, software development, and/or other technology.

    6.2. A panel of LiquidApps employees and Hackathon mentors (the “Examiners”) will determine which of the submitted projects will be qualifying for the Final Round (the “Preliminary Round”). Only projects who will qualify the Preliminary Round will be evaluated by the Judges in the Final Round.

    6.3. The Judges and the Examiners will be using the same framework (the “Judging Criteria”) in order to evaluate the projects in both the Preliminary Round and the Final Round. The different Judging Criteria has the same weight of five (5) points each.

    6.4. The Judging Criteria are: (5 points each)
    ■ Utilization of LiquidApps Services:
      ● If the submitted project falls within DeFi and/or Gaming theme:
      ● A MINIMAL REQUIREMENT - were two (2) different LiquidApps services and/or products successfully and explicitly implemented in the project?
      ● How well suited is the project to LiquidApps technology?
      ● If the submitted project falls within New Service theme:
      ● How suitable is it for the DAPP Network? How well does the service fit in the DAPP Network ecosystem?
      ● If the submitted project extends an existing service, then - A MINIMAL REQUIREMENT - does the project demonstrate a significant improvement as described in section 5.8?
    ■ Technical Complexity:
     ● Is the project technically impressive and complex?
     ● How technically sophisticated, advanced and elegant was the solution?
    ■ Innovation and Creativity:
     ● How innovative, creative and unique is the idea and the solution for the challenge?
     ● Is it something that was seen before, or a brand new concept?
     ● Was there a novel approach applied to solve the problem?
    ■ Impact:
     ● Can it impact the ecosystem in a significant way?
     ● Is it feasible to implement and scale?
     ● How solid is the business model behind the project?

    6.5. Preliminary Round evaluation method:
    ■ Examiners will use the submitted pre-recorded project pitch and source code in order to evaluate the projects. In case a Running dApp was submitted in addition to the Mandatory Items, it will be used for the evaluation as well.
    ■ The decision to watch, use or take into consideration any Additional Materials is under the Examiners’ exclusive and complete discretion.
    ■ The projects will be independently evaluated under the Examiners’ exclusive and complete discretion. The selection of the qualifying teams will be at the sole discretion of the Examiners and is irrevocable and not open to objection or appeal.
    ■ The Examiners will be allowed to qualify any project they see fit for the Final Round, and they are not bound to a specific number of projects.

    6.6. Final Round evaluation method:
    ■ The projects that will qualify for the Final Round will be invited to present their projects in front of the Judges during the live-stream closing ceremony. Each team will have up to three (3) minutes to demonstrate its project to the judges, followed by up to two (2) minute question and answer session.
    Please note: It is the teams’ sole responsibility to connect to the live-stream closing ceremony during their pitch time-frame. If a team has failed to connect the live-stream closing ceremony, for any reason, its pre-recorded project pitch that was submitted and used in the Preliminary Round will be used to evaluate their project.
    ■ In case a Running dApp was submitted in addition to the Mandatory Items, it will be used for the evaluation as well.
    ■ The decision to watch, use or take into consideration any Additional Materials is under the Judges’ exclusive and complete discretion.
    ■ Each qualifying project will be independently scored by each one of the Judges with a score between zero (0) to twenty (20) points, with the final score being the total sum of the Judges’ scores.
    ■ The projects will be examined, evaluated and judged under the Judges’ exclusive and complete discretion.

    6.7. All decisions regarding the qualifying and winning projects, in both the Preliminary Round and the Final Round, are final and shall not be subjected to any further procedures or appeals.


  7. Evaluation and Judging of Additional Prizes

    7.1. Rather than the best-submitted projects, three additional competitions will take part during the Hackathon: Crowd Favorite Project, Best Social Media Post, and Best Mentor.

    7.2. Crowd Favorite Project:
    ■ The Crowd Favorite Project prize will be given to the submitted project who gets the most votes from the teams who submitted projects.
    ■ Teams that would like to vote for the Crowd Favorite project prize, should have their Team Leader send an email to hackathon@liquidapps.io with a subject line that includes “Vote” and the team you wish to vote for.
    ■ Teams can vote for one team which is not theirs and have until the last team finishes pitching in the closing ceremony to vote for their favorite project.
    ■ Participants must not incentivize voting or buy votes in the community vote and will be disqualified if they do so.

    7.3. Best Social Media Post:
    ■ The Best Social Media Post competition starts on November 4th 2019, 15:00 UTC, and ends at the same time of the Submission Deadline.
    ■ The eligible social media platform for this prize are Twitter, Instagram, Youtube, Telegram and Facebook.
    ■ The prize will be given to a single individual who owns the account and/or user on which the winning post will be posted.
    ■ In order to participate in the Best Social Media Post, participants are required to be registered to the Hackathon using the Platform, include the hashtag #DAPPHackathon in the post, and submit a link to hackathon@liquidapps.io prior to the Submission Deadline.
    ■ Individual participation in the Best Social Media Post competition is allowed. You do not required to be part of a team.
    ■ Submissions for this prize will be evaluated by LiquidApps team members, and the winner will be determined by their sole discretion.

    7.4. Best Mentor:
    ■ The Best Mentor prize will be given to the Hackathon mentor who gets the most votes from participants who submitted their projects.
    ■ Voting for the Best Mentor competition will be done as part of the submission process. Teams wishing to vote for the mentor who provided them with the best guidance and added value should write the mentor's name in the "Instructions to Run" field when submitting their project.
    ■ Each team can vote for one (1) mentor. If a team writes more than one (1) mentor in the "Instructions to Run" field, the first appearance will be counted as the team's vote.
    ■ Mentors must not incentivize voting or buy votes and will be disqualified if they do so.


  8. Prizes

    8.1. Prizes amounts:
    Grand Winner: USD 15,000 + DAPP 500,000
    1st Runner Up: USD 7,500 + DAPP 250,000
    2nd Runner Up: USD 5,000 + DAPP 125,000
    Crowd Favorite Project: USD 5,000
    Best Social Media Post: USD 3,000
    Best Mentor: USD 3,000

    8.2. Please note: Some of the prizes may be given in cryptocurrencies, and therefore the amounts are an approximation.

    8.3. Prizes shall be paid once to the winning team’s Team Leaders, which shall be responsible to split the prizes between their team members. LiquidApps has no responsibility for how prize money or other prizes are distributed between the members of a team or for any other disagreement between team members.

    8.4. Participants, either individuals or team, are exclusively liable and responsible for any applicable tax liability for participation in the Hackathon or receipt of a prize, or costs or expenses relating to participation in the Hackathon or the operation and ownership of the submitted project.


  9. Intellectual Property

    LiquidApps has no, and shall have no liability, responsibility or accountability regarding or in connection to Participants intellectual property rights, and any related claims thereto.
    Furthermore, Participants hereby agree and acknowledge that the Projects shall be published and made openly available to third parties (such as: Judges, Examiners, mentors, etc.), and hereby irrevocably and unconditionally represents it shall have no, and waives any claim or demand towards LiquidApps and any affiliate thereof in such regard.

    9.1. Each Participant, Team and/or individual Team members bears the exclusive responsibility to determine the applicable terms regarding ownership of intellectual property rights to their respective project (including between participating Teams, and within the Teams themselves). Participant represents and warrants that they have all intellectual property rights in all materials, information, data, know how, code and other forms of intellectual property used to create their projects, and all rights to agree and determine the terms of ownership, rights and use with any applicable party. This representation includes, without limitation, the fact that participants will not use any licensed intellectual property in the creation of the project.

    9.2. Despite any provision set forth herein to the contrary, each team hereby grants LiquidApps a limited, non-exclusive, non-transferable (except to affiliates), worldwide, royalty-free license to their project for purposes of operating and promoting the Hackathon and similar future events, as LiquidApps shall deem fit at its own discretion.

    9.3. Participant understands and agrees that LiquidApps may make promotional and marketing use of the submitted projects or any portion thereof, participant’s likeness and attendance at the Hackathon, and related matters or derivative works without any compensation to the participants.


  10. Use of Software by the Participants

    10.1. Participants are given access to LiquidApps software and technology, which may include, but not limited to, open-source code, software libraries and tools, published specifications, and documentation, as may be applicable on a case to case basis (the ‘Software’).

    10.2. The use of the Software is allowed only according to the LiquidApps License (https://github.com/liquidapps-io/dist/blob/master/LICENSE). The said LiquidApps License constitutes the only and exclusive terms governing the use of the Software, and will prevail over the Hackathon Rules and Terms and Conditions, or any other connected publication and documentation, in case of contradiction.

    10.3. Any and all intellectual property rights of the Software belongs to LiquidApps at all times. Nothing set forth herein, including access to and use of the Software during the Hackathon, shall not grant any Participant or third party with any intellectual property rights regarding the Software.

    10.4. Participants will inform LiquidApps, without any delay, of any loss or unauthorized use of the Software, including any breach of these Hackathon Rules and Terms and Conditions.

Terms and Conditions

1) When entering the Hackathon, you must consider it is possible that you may receive a lower reward than you’ve expected or no reward at all.

2) Participation in the Hackathon is on your own behalf and benefit, using your own assets, knowledge, tools, equipment, and personnel.

3) LiquidApps does not offer, and will not provide the Hackathon’s participants any information, knowledge, support, advice or explanation of any kind, other than what has explicitly provided herein and/or will be provided in Slack #tech-support channel. When participating in the Hackathon, Hackathon participants rely on their own knowledge, know-how, experience and understanding, including but not limited to, blockchain technology, DAPP Network, software and relevant code. LIQUIDAPPS DOES NOT PROVIDE ANY WARRANTY WHATSOEVER WITH RESPECT TO THE DAPP NETWORK, THE DAPP TOKEN, DSPs, AND THEIR RELATED TECHNOLOGIES, and it is the participants own responsibility to examine the relevant code and material available at (and subject to the ascribed terms and conditions): https://github.com/liquidapps-io.

4) LiquidApps reserves the right, under its exclusive and independent discretion, to: (1) end the Hackathon at anytime, with or without cause; (2) amend the terms herein; (3) change the Judges composition. LiquidApps will communicate and apply such changes by publishing notice on Slack’s #announcements channel. By participating in the Hackathon, or continuing to participate after any such changes occurred, you shall be deemed to have accepted the applicable terms and conditions.

5) Your project is under your complete responsibility and liability. LiquidApps and/or any of the Judges and/or Examiners will only examine, relate and evaluate functionality, usability and visualization. LiquidApps and/or any of the Judges and/or Examiners will not check, relate, consider, advise, examine or address in any other way any legal, regulatory, compliance or financial aspects of the project, nor shall they bear any responsibility or liability. As the developer of your project, you will have and retain full rights and ownership in the project developed by you, and with complete liability and responsibility with any and all aspects relating to your project or any other content created and published by you or on your behalf. Your responsibilities and liabilities include, but not limited to, the following (as may be applicable): registration, licensing, non-infringement of third parties rights, privacy, data protection, product and software warranty, terms of use and any applicable laws. LiquidApps and any of the Judges, Examiners and/or their affiliates will not assume any liability or responsibility of any sort or nature whatsoever regarding any project, including by accepting, judging and awarding project, which shall remain with the creators and owners of the project at all times.

6) The DAPP Network is open and is not controlled by LiquidApps, any of the Judges, Examiners and/or any of their affiliates. You remain at all times an independent party. Parties participating in the Hackathon and the submitted projects to the Hackathon, including those that will be awarded and win the Hackathon, will not form or claim to have any partnership, joint venture, cooperation, employment, collaboration and/or business relations with LiquidApps, any of the Judges, Examiners and/or any of their affiliates, or be affiliated with them in any way.

7) Any use of any of LiquidApps, the Judges, Examiners and/or any of their affiliates, names, brands, trademarks or trade signs is hereby forbidden, without prior written approval from the relevant party. The only use that shall be permitted is in reference to the Hackathon (provided that you shall not imply any endorsement by LiquidApps, the Judges, Examiners and/or any of their affiliates).

8) You agree not to make any other statements or publication, without the prior written consent of LiquidApps, implying any circumstances, terms or relations which are different from those stated herein.

9) You do not have any authority of any kind to bind LiquidApps, the Judges, Examiners and/or any of their affiliates in any respect whatsoever.

10) LiquidApps reserves the right to make all decisions relating to the Hackathon at its sole discretion, and such decisions are final and binding. Participants in the Hackathon agree that: (1) any and all disputes, claims, and/or causes of action arising out of or connected with this Hackathon, or any benefits received, or the administration of the Hackathon, shall be resolved individually, without resort to any form of class action, and exclusively by arbitration, under the Rules of Arbitration of the International Chamber of Commerce by one arbitrator appointed in accordance with the said Rules. The place of arbitration shall be Tel Aviv, Israel. The arbitration procedure shall be conducted in English. The Swiss federal court (Bundesgericht) will have exclusive jurisdiction over any appeals of an arbitration decision; (2) any and all claims, judgments and reliefs shall be limited to actual direct out of pocket costs incurred, including costs associated with participating in the Challenge and in no event shall participant be entitled to receive attorneys’ fees or other legal costs; (3) under no circumstances will a participant be permitted to obtain reliefs for and participants hereby waive all rights to claim punitive, incidental and consequential damages and any other damages, other than for actual out of pocket expenses; and (4) any and all disputes, claims, and causes of action arising out of or relating to the Challenge, or any grant awarded must be brought within one (1) year after the occurrence of the event giving rise to such claim (if such claim is not filed, then that claim is permanently barred). Except where prohibited, all issues and questions concerning the construction, validity, interpretation and enforceability of these terms and conditions, or the rights and obligations of participant(s) and LiquidApps in connection with the Hackathon, shall be governed by, and construed in accordance with, the laws of Israel, without regard for conflicts of law doctrine of any jurisdiction, and subject to resolution through arbitration only in Tel Aviv, Israel. LiquidApps’s failure to exercise or enforce any right or provision under these terms and conditions will not constitute a waiver of such right or provision and will not be deemed a waiver of any further rights hereunder.

11) NO WARRANTY. LIQUIDAPPS, ITS AFFILIATED COMPANIES AND ALL OF THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, REPRESENTATIVES AND AGENTS (COLLECTIVELY, THE “RELEASED PARTIES”) EXPRESSLY DISCLAIM ANY AND ALL WARRANTIES OR CONDITIONS OF ANY KIND (WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE), INCLUDING BUT NOT LIMITED TO, IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. UNDER NO CIRCUMSTANCES SHALL RELEASED PARTIES BE HELD RESPONSIBLE OR LIABLE FOR A PARTICIPANT’S USE OF ANY INFORMATION AND/OR PRODUCTS PUBLISHED AND/OR MADE AVAILABLE BY THE RELEASED PARTIES WITH OR WITHOUT CONNECTION TO THE HACKATHON OR FOR ERRORS OR ANOMALIES RESULTING IN THE UNINTENDED OR ERRONEOUS PARTICIPATION, AWARD OF HACKATHON PRIZES OR OTHER BENEFITS UNDER THE HACKATHON TO PARTICIPANTS. RELEASED PARTIES OFFER NO ASSURANCES, GUARANTEES OR WARRANTIES OR CONDITIONS THAT THE HACKATHON OR HACKATHON WEBSITES WILL BE UNINTERRUPTED OR ERROR FREE AND DOES NOT GUARANTEE THE ACCURACY OR RELIABILITY OF ANY INFORMATION OBTAINED THROUGH THE HACKATHON. RELEASED PARTIES ASSUME NO RESPONSIBILITY FOR ANY COMPUTER RELATED DAMAGES DUE TO DOWNLOADING MATERIALS. RELEASED PARTIES WILL NOT BE LIABLE, AND ARE NOT RESPONSIBLE, FOR DAMAGES OF ANY KIND RELATED TO A PARTICIPANT’S PARTICIPATION OR INABILITY TO PARTICIPATE IN THE HACKATHON, WHETHER THE DAMAGES ARE DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL. FURTHER, BY PARTICIPATING IN THE HACKATHON AND/OR ACCEPTING AN HACKATHON PRIZE, A PARTICIPANT AGREES THAT RELEASED PARTIES SHALL NOT BE LIABLE FOR, AND WILL BE HELD HARMLESS BY PARTICIPANT AGAINST, ANY LIABILITY FOR ANY DAMAGE, INJURY OR LOSS TO PERSON (INCLUDING DEATH) OR PROPERTY DUE IN WHOLE OR IN PART, DIRECTLY OR INDIRECTLY, TO ACCEPTANCE, POSSESSION, USE OR MISUSE OF A HACKATHON PRIZE, PARTICIPATION IN ANY HACKATHON RELATED ACTIVITY, RELEASED PARTIES’ USE OF ANY TENDERED ENTRY OR PARTICIPATION IN THIS HACKATHON.

12) Participants agree to release, defend, indemnify and hold harmless Released Parties from and against, and accept all responsibility of any kind, including but not limited to financial, for any liability, claims, losses, damages or proceedings, including but not limited for death, (including reasonable attorneys’ fees) relating to any actions taken by a Participant, including any submissions, or anyone else using a Participant’s email or team password or otherwise purporting to act on Participant’s behalf in regard to the Hackathon (whether or not such use occurred with or without your permission). Participant also agrees to release, defend, indemnify and hold harmless the Released Parties from any and all liability, claims, losses, damages or proceedings, including but not limited for death (including reasonable attorneys’ fees) relating to prizes and any other matter in connection with a participant’s participation in the Hackathon or LiquidApps’ or its designees or LiquidApps’ or its designees use of his/her submission. These rules, terms and conditions specified here comprise the Hackathon Official Terms and Conditions and, together with the LiquidApps’ Terms of Service (https://www.liquidapps.io/terms-of-service), Privacy Policy (https://www.liquidapps.io/privacy-policy) and official Hackathon communications or publications by LiquidApps, shall govern and apply to all participation and activity arising out of and relating to the Hackathon and use of LiquidApps’ site. These terms and conditions cannot be modified or superseded except by LiquidApps, at its sole discretion.

Notifications
View All Notifications

?