Dates

  • Submission Period: July 16, 2021 (8:00 am Eastern Time) – July 30, 2021 (5:00 pm Eastern Time) (“Submission Period”).
  • Judging Period: August 2, 2021 (8:00 am Eastern Time) – August 13, 2021 (5:00 pm Eastern Time) (“Submission Period”).
  • Winners Announced: On or around August 17, 2021 (12:00 pm Eastern Time).

 

Who can participate?

  • Individual participants from all backgrounds, races, ethnicities, genders, and non-excluded geophraphies (see below) are welcome. There is an age restriction to participate in the hackathon. Participants must be 18 years or older
  • The hackathon is limited to individual participants who are residents of non-U.S. embargoed countries and territories as designated by the U.S. Treasury's Office of Foreign Assets Control ("OFAC").  The hackathon is void wherever it would be restricted by registration requirements or is otherwise prohibited by law.
  • No purchase of any kind is necessary.
  • Submission of an entry to the Hackathon constitutes an agreement with these Rules and Code of Conduct and represents a contract between the participant, the Hackathon sponsors and Devpost.

 

Sponsors

  • The primary sponsor of Blinkathon is BlinkSky, 12600 Deerfield Pkwy Suite 100, Alpharetta, GA 30004.
  • Additional sponsors may or may not be listed on Devpost and the Hackathon’s microsite (www.blinkathon.com).

 

Registration Rules

  • Each participant must register for the Hackathon at Devpost.
  • Participants must be a part of a team and submit their project as a team.  Team must have at least two participants and not more than eight.
  • The Hackathon is not open to individuals who are residents of or domiciled in a country, state, province or territory where United States law or local law prohibits participating in or receiving a prize from the Hackathon.  Excluded countries/locales include Brazil, Quebec, Cuba, Iran, North Korea, Syria and any other country designated by the United States Treasury's Office of Foreign Assets Control (“OFAC”).  
  • Employees, representatives and family members of the sponsor companies are not allowed to participate in the Hackathon.

 

How to Register

Entrants will go to https://blinkathon.devpost.com and complete registration for the Hackathon by clicking on the “Join Hackathon” button.  Note, entrants will need to either have a Devpost account or will need to create one.

 

Team Formation

  • Hackathon participants must participate in a team.  Teams must consist of at least two team members to a maximum of eight members. 
  • Changes to team members are not permitted after Saturday, July 17, 2021, at 12:00 Noon. Exceptions can be made on a case-by-case basis as decided by the rules committee.

 

Project Development

  • No development may start before the actual date and time of the event. Any teams that violate this rule will be automatically disqualified. The first line of code should be written on or after Thursday, January 16, 2021, at 8 pm after the team has registered. However, we encourage you to brainstorm ideas and create wireframes/mockups.
  • Any software development tools, IDE, and/or programming language can be used for the event. If a team member uses a purchased tool licensed to him or her and the license is not transferable to other members, the member’s team must choose one available to all developer teams.
  • To ensure a level field for all contestants, all code must be created only during the hackathon. You are permitted to use publicly developed and openly licensed API’s and SDKs for your project.
  • You will only be able to use a pre-public release of a product in developing your project if you bring at least one extra version that can be used by other teams in the Hackathon and provide any user support needed to teams using the device.
  • Project design/assets can be created prior to the start date of the hackathon. All assets should conform to the Creative Commons License agreement standard or are freely available and you have permission or license to use them. Proof of permission must be given upon request.
  • Assets, SDKs, APIs or other tools or components available under a trial license may be used.
  • A team can submit only one entry for the hackathon. Participation at the hackathon is subjected on a “per-team” basis meaning you are not allowed to be on more than one team at the event.
  • Any intellectual property developed during and within the scope of the hackathon must be open source and licensed under one of the licenses referenced in https://opensource.org/licenses.
  • The license selected by the team must be clearly listed in code (page per page) or a generic page announcing the license the application adheres to. The public code used inside your application should also list the licenses the code is subjected to.
  • A team can use multiple licenses in the application. For example, the public code used could be licensed under the Apache license agreement whereas the code written by the team for the application licensed under the MIT license agreement.
  • A team may not code applications that violate the code of conduct. For example, racially insensitive ideas for an application will automatically be disqualified.

 

Project Requirements

  • Participants must use BlinkSky APIs to build software applications that involve digital payments.  The Hackathon team will supply entrants sandbox accounts to BlinkSky’s API.
  • Applications should be either web or mobile based.
  • Participants must be able to allow the Hackathon judges to use and test their team applications and provide instructions on how to use the application.
  • All applications and descriptions of the applications must be in English.
  • Each Hackathon team should designate a team lead or representative who enters the submission for the team.

 

Attendee Code of Conduct

By participating in the Hackathon, you agree to abide by the following code of conduct.

  • Please treat all other hackers with the utmost respect.  We ask that you act kindly, behave professionally, and do not insult or put down other attendees.  Remember that harassment and racist, sexist, or exclusionary jokes are not appropriate for this event. If at any point you see a fellow hacker being harassed, please talk to the nearest hackathon organizer.
  • Please treat our sponsors, organizers, and judges with the utmost respect. Without them, nothing would be possible.  They're here for you! Show them you appreciate it.

Failure to comply with the above-stated Rules and Code of Conduct may result in the offending team's disqualification.

 

Photo Release Waiver

By attending Blinkathon, you hereby grant Blinkathon and its affiliates permission to use your likeness in a photograph, video, or other digital media (“photo”) in any and all of its publications, including web-based and social media publications, without payment or other consideration.  You understand and agree that all photos will become the property of Blinkathon or its affiliates and will not be returned. 

You irrevocably authorize Blinkathon and its affiliates to edit, alter, copy, exhibit, publish, or distribute these photos for any lawful purpose. In addition, you waive any right to inspect or approve the finished product wherein my likeness appears. Additionally, you waive any right to royalties or other compensation arising or related to the use of the photo. 

You hereby hold harmless, release, and forever discharge Blinkathon and its affiliates from all claims, demands, and causes of action which you, your heirs, representatives, executors, administrators, or any other persons acting on your behalf or on behalf of your estate have or may have by reason of this authorization. 

 

Intellectual Property

  • All eligible Submissions remain the intellectual property of the individuals that submitted them.  By entering the Hackathon, the entrants agree that the sponsors will have a perpetual, non-exclusive, fully paid license to use the entry for judging the entry.  
  • Entrants agree that the Sponsors will have full rights to promote Submissions and use the name, likeness and images of all teams and associated individuals contributing to Submissions.  
  • Entrants agree that Submissions and their content are not copyrighted or bound by other 3rd party agreements, intellectual property rights or any other rights unless those rights are held by the entrants.
  • Entrants agree that intellectual property rights of the Sponsors remain with the Sponsors