DAO-Fi Fusion (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. DATE & TIMING

Submission Period

Tuesday, March 14, 2023 (09:00 AM CET) – Sunday, May 14, 2023 (12:00 PM CEST)

Technical Review Period

Monday, May 15, 2023 (06:00 PM CEST) – Friday, May 19, 2023 (06:00 PM CEST)

Judging Period

Monday, May 22, 2023 (09:00 AM CEST) – Wednesday, May 24, 2023 (04:00 PM CEST)

Community Live Event & Winner Announcement

Thursday, May 25, 2023 (04:00 PM CEST)

Community Award Voting

Thursday, May 25, 2023 (05:00 PM CEST) – Friday, May 26, 2023 (05:00 PM CEST)

Community Award: Winner announcement

Friday, May 26, 2023

2. SPONSOR AND ADMINISTRATOR

Aeternity Establishment, Dr. Grass Str. 12, FL-9490 Vaduz, Liechtenstein

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 collective, “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, Afghanistan, Barbados, Burkina Faso, Cambodia, Cayman Islands, Haiti, Iran Islamic Republic of, Iraq, Jamaica, Jordan, Mali, Morocco, Myanmar, Nicaragua, Pakistan, Panama, Philippines, Russia, Senegal, Syrian Arab Republic, Uganda, Yemen, Zimbabwe 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 affiliates *** of any organization described above

• Any other individual or organization whose participation in the Hackathon would create, at 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 https://dao-fi-fusion-code-challenge.devpost.com (“Hackathon Website”) and the following the 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 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.

• Provide access to your code repository for judging and testing by making your code public on GitHub.

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

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

Project Requirements

(i) What to Create: Entrants must build an application that allows users to create and manage DAOs (powered by Sophia Smart Contracts) with their Superhero Wallet at least on æternity testnet (preferrably also mainnet) via an user interface. (each a “Project”)

(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) New & Existing: Projects must be either newly created by the Entrant or, if the Project existed prior to the Hackathon Submission Period, must have integrated the æternity blockchain after the start of the Hackathon Submission Period.

(iv) Third-Party Integrations: If a Project integrates any third-party SDK, APIs, and/or data, Entrant must be authorized by the third party to use them.

(v) Testing: The Entrant must publicly host the Project and make it available free of charge and without any restriction, for testing, evaluation, and use by the Sponsor, Administrator, and Judges until the Judging Period ends.

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 URL to your code repository for judging and testing by making your code public.

• 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 less than three (3) minutes

  • should include footage that shows the Project functioning on the platform 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, copyrighted music, or other material unless the Entrant has permission to use such material.

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

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

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

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, or your Organization with no other person or entity having any right or interest in it; and (c) not violate the intellectual property rights or other rights including but not limited to the 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 the 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 permit.

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.

The judging is split into different stages:

• Stage One: The sponsor will determine whether the submissions meet a baseline level of viability that applies to the submission requirements of the hackathon.
• State Two: All submissions that pass Stage One will be evaluated by technical reviewers from the community and Judges.

Technical reviewers will score the projects on the following equally weighted criteria:

• General

  • Quality of the README / Documentation

  • Completeness and functionality?

• Code Quality

  • Is the code well-organized and easy to read?

  • Does the code follow best practices and coding standards?

  • Are the variable names descriptive and meaningful?

• Functionality

  • Does the project work as expected?

  • Are there any bugs or errors?

  • How good is the test coverage? (specifically important for Smart Contracts)

  • Is the user interface intuitive and easy to use?

• Security

  • Are there any potential exploits or weaknesses that could be exploited by attackers?

  • How significant is the impact of potential exploits?

• æternity / blockchain

  • Is there a meaningful usage of specific protocol features?

  • Does the project require æternity / a blockchain at all?

  • Is the implementation compliant with established token standards? (e.g. AEX-9, AEX-141)

The technical reviewers will provide a score (0 low quality - 10 outstanding) as well as feedback for each criterion. The technical review will be published and visible to the community.

Note: The top 5 submissions according to the score in the technical review will receive a prize of $1,000 each (paid in Æ) - independent of the decision of the Judges!

Judges will score the projects on the following weighted criteria:

• Technical Implementation (40%)

  • Experienced æternity contributors will perform a technical review on each project. These reviews will be published and considered by judges to pick the winning team.

  • Smart Contracts are a MUST and a high test coverage of these is desired.

• Impact & Usefulness (30%)

  • Does the project make a significant impact on the æternity ecosystem?

  • How big is the overall market potential of the project?

• User Experience (20%)

  • How useable is your project? Does it look nice? Does it accomplish what it's set out to do in an easy-to-use and approachable way?

• Presentation & Communication (10%)

  • The quality of the project presentation and how well the team communicates the idea. The presentation should be clear, concise, and engaging.

  • Show the community who you are and why your project should win!

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.

Community Award Voting

At the end of the "Community Event" and the announcement of the official winners, the sponsor will create a poll in the official æternity Forum (https://forum.aeternity.com) where the community can vote on all eligible submissions. The submission that receives the most votes within 24 hours will be the winner of the "Community Award".

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 royalty-free, non-exclusive license to use the 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 the 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 the 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

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. The 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 the organization’s participating members, as the representative deems appropriate. The prize will be sent to the winning entrant’s æternity address (if an individual) or the representative’s æternity address (if a team or organization), 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 additional 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 sponsor or Devpost’s receipt of the completed required forms.

Notes:

• The sponsor will use the exchange rates on the date of payout which means that the amount of AE the entrant receives depends on the price USD/AE exchange rate on this day and cannot be determined prior to the payout.
• A Project can win multiple (max. 3) prizes.

D. Fees & Taxes: Winners (and in the case of the 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 the 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 member) 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 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 an 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, the 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 the 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 the 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 court proceedings held at the courts in Vaduz, Liechtenstein;

2. the Liechtenstein laws shall govern the interpretation, enforcement, and all proceedings.

B. Under no circumstances will the entrant be permitted to obtain awards for, and the 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 Liechtenstein.

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

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