Klever Global Hackathon Q2

:: The hackathon takes place every Quarter in 2022. For the first edition, registrations must take place until June 1st. Teams are welcome to submit projects anytime in advance of the July 1st deadline at 11:59 PM UTC.

Free Participation +

30,000,000 KLV

Estimated Total prize pool for the 3 Hackathons that will still take place in 2022 (Q2, Q3, Q4).​

Klever will host a series of hackathons in 2022 to promote and provide KleverChain solutions to users. During the Hackathon, teams will be able to interact with our development team to ask questions and learn how easy it is to create KleverChain applications.

Our team of judges evaluates the team's results at the end of every quarter, and the best projects will be awarded. Hackathons are remote, asynchronous, and global. Invite your developer friends to participate!

Dev Competition

Choose your category, register, and participate for free

Explorer
[THE CHALLENGE] Develop new solutions for the KleverChain Explorer.
ICO/Market Place
[THE CHALLENGE] Build a revolutionary Marketplace for KleverChain.
Game / NFT
[THE CHALLENGE] Build your own Game / NFT on KleverChain. (proof of concept)
Innovation
[THE CHALLENGE] Be creative and use KleverChain to create solutions.

Dev WINNERS

Klever Hackathon winners have been listed below

ICO/Marketplace

[WINNER]
Sky Gallery

Game/NFT

[WINNER]
DexBet.win

Innovation

[WINNER]
Sena Analytics
[2ND PLACE]
Crypto Registry
[3RD PLACE]
K1 Nodes Red Nodes

Important: Klever is not affiliated with any of these projects, use at own risk.

No Competition Categories

*Players will be paid by the application if they follow Klever rules. Entries will be accepted soon.​

Content Creators
[THE CHALLENGE] Produce content like articles, videos, images, posts, and stories for the Klever community.
Bugs and Security Bounty

[THE CHALLENGE] Report bugs and security issues

Hackathon Timeline

Applications open

May 11 – Jun 1st, 2022

Competition runs

May 16 – Jul 1st, 2022

Project submission

Jul 1st, 2022

Klever Judges & Considerations

Jul 1st – Jul 14, 2022

Awards

Jul 15, 2022

Hackathon Judging Criteria

Is the code well-written, efficient, and/or technically innovative?

Is this project useful to real-world problems? Can people use it?

Is this project likely to have a meaningful impact on the world?

Is this project a complete working product for end-users?

Is your content, considered, well-written, in-depth, and insightful?

HOW TO PARTICIPATE

Terms and rules

Check the rules for each category and guarantee your participation.

  • Dev Competition
  • Bugs and Security Bounty
  • Content Creators
  • Code of Conduct
Dev Competition
  1. Team threshold. (min 1 and max 4)
  2. Categories:
    1. Explorer

      New solutions to the KleverChain explorer, like (https://testnet.kleverscan.org/)

    2. ICO/Market Place

      Create a revolutionary Market Place for KleverChain 

    3. Game / NFT

      Create your own game (Proof of Concept) using NFT on KleverChain

    4. Innovation

      Be free, and use your imagination to create solutions with Kleverchain

  3. Prizes:
    1. Per category, as follow:
      1. 25K USD 1st (in KLV)
      2. 10K USD 2nd (in KLV)
      3. 5K USD 3rd (in KLV)
  4. Criteria to evaluate the projects:
    1. Originality & Innovation
    2. Quality of code
    3. Documentation coverage
    4. Usability
  5. Judgment:
    1. The jury will be formed by Klever guys and some other selected community people.
  6. Communication:
    1. Each participant will be invited to join a hackathon channel on Discord;
      1. Make sure you're using the correct Discord user in the registration form.
    2. It must be the only official channel of communication to solve questions and doubts;
    3. All communication is in an async way. Take it easy, your question will be answered;
    4. Do not leave the channel before the end of this campaign.
  7. Registration process:
    1. Once applied you will receive a confirmation email with technical information (link to kApp demo page, git repositories with examples of use, KleverChain SDK and documentation link)
      1. Only this email validates your and your team's registration
      2. Make sure that you're using a valid email
      3. A confirmation email will be sent from 05/13
    2. Applying for more than one category is allowed:
      1. Individually or as a team;
  8. Submit project process:
    1. Until 07/01 11:59 PM UTC you'll have got to submit your project to hackathon@klever.io, containing:
      1. Team name
      2. Project name
      3. Klever(TRC20) Wallet Address
      4. Link to pitch deck
      5. Link to your project running
      6. Link to GitHub repository
      7. Description of how to deploy and execute your project using docker container
    2. Please check your wallet address before submitting, this cannot be changed.
    3. Solutions copied or reproduced, in full or part, from other sources and/or competitions will not be accepted. The identification of a copy, total or partial, will be punished with the disqualification of the respective team.
  9. Winners award:
    1. On 07/15, a winner's list will be published in a winners section on the Kleverchain Hackathon landing page.
    2. On the same date, the prizes will be paid
  10. Any project with improper information or bad player behavior will be disqualified without notice (pay attention of our Code of Conduct)
  11. When the competition ends, you will have 7 days for any questions/complaints
  12. If you are disqualified for any reason, you will NOT receive any rewards
  13. All rights are reserved by Klever Finance, which can make any changes to rules or terms and conditions, if applicable.
Bugs and Security Bounty
Coming soon...
Content Creators
Coming soon...
Code of Conduct

This code of conduct applies before, during and after our events.

  1. Our expectations
    1. By participating in our meetings and events, we expect participants to abide by this Code of Conduct and accept the procedure by which any Code of Conduct incidents are resolved.
    2. Please treat everyone with respect. We expect all event participants and speakers to help ensure a safe and positive experience for everyone.
    3. Provide your true identity, affiliation, and, where appropriate, contact information, at registration and during attendance and participatory sessions, as required.
  2. Behaviours we encourage
    1. Use of welcoming and inclusive language
    2. Showing respect for different viewpoints and experience
    3. Graceful acceptance of constructive criticism
    4. Make space for others to speak and ask questions
    5. Appreciate that people will have different skills, levels of knowledge and expertise – be patient
  3. Unacceptable behavior
    1. Intimidating, harassing, abusive, discriminatory, derogatory or demeaning speech/actions.
    2. Harmful or prejudicial verbal or written comments or visual images related to age, background, belief, disability, ethnicity, race, religion, gender, identity, national origin, sexual orientation or other personal characteristics, including those protected by law.
    3. Inappropriate use of sexual language or imagery.
    4. Real or implied threat of professional or financial damage or harm.
    5. Inappropriate disruption of meetings or events.
    6. Photographing, video or audio recording of slides, oral or poster presentations without presenter/author’s permission.
    7. Violating the rules and regulations of the online platform (e.g. Discord).
  4. Reporting incidents
    1. If you believe someone is violating the code of conduct, please report this to the event organizer straight away, if you can, by emailing at support-hackathon@klever.io. The report will be reviewed by Klever and any action to address and/or resolve the issue will be communicated within one week.
  5. Resolution of incidents
    1. Incidents will be reviewed and if the code of conduct has been violated, the actions we take could include:
      1. Educating the person as to the consequences of their actions.
      2. Disqualification and removal from the event.
      3. Restrictions from future events.