Rise to the Challenge: Klever Hackathon Winners' Roadmap! šŸš€

This is impossible to reach. Whole Klever ecosystem had 10k transactions in last 24h and a bit more than 1500 DAU.

How can each of us get 6x more DAU than the whole Kleverchain? Whole Fantom chain has 24k DAU, PancakeSwap has 60k+ DAU.

The milestones should be based on development of participants, community engagement, etc. We will develop further anyway, but knowing that we wont reach any of upcoming milestones burns a lot.

Cant get over the fact that Project of the month participants received more ā€œrewardsā€ doing airdrops than us. Literally feel like 1000s of hours were finally gona pay off, but got rekt.

4 Likes

Hello everyone,

First and foremost, I want to express my deep appreciation for all of you and apologize for the time it took to return here with an official update. We have been committed to finding the best solutions that align with Kleverā€™s core values of trust, transparency, collaboration, challenge, and continuous evolution.

Leading a company in the crypto world from scratch is both extremely challenging and incredibly motivating. Watching a community grow around our products, thrive, and prosper together is hard work, but itā€™s immensely gratifying. We understand that we will have successes and failures along the way, but please rest assured that all our actions are aimed at achieving the best possible outcomes for our users and our community.

To get straight to the point, we have addressed your main concern regarding the DAU indicator and have decided to readjust the milestones to focus on the number of transactions that your projects, directly or indirectly, generate on the KleverChain. After all, itā€™s about more projects and more transactions. The new milestones are as follows:

  • Milestone 3: 200K transactions on KleverChain over 90 days (from 06/01 to 08/30)*
  • Milestone 4: 250K transactions on KleverChain over 90 days (from 09/01 to 11/30)* along with the deployment of a Smart Contract on the KVM mainnet related to the project by 11/30

Notes:

1. Since we are changing the rules mid-month, we believe it is fairer to start counting transactions for the next milestone from the first day of the following month, giving projects more time to organize their actions.

2. The number of transactions will be measured by the projectā€™s token(s), which must be specified and get the ownership verified on KleverScan, and also transactions in any KDA that can be proven to originate from the project.

Although I havenā€™t met you all personally, I consider you friends and want you to know that you can count on me and the Klever team to build increasingly robust solutions in a technological and social environment that is ever more conducive to the emergence and growth of your ideas.

In life, we experience moments of joy, anger, frustration, and achievement, and these moments make us stronger, more united, and victorious. For those who have decided to leave the hackathon, I kindly ask you to reconsider if you wish, as the doors of Klever are and will always be open for you and for everyone who wants to embark on this journey with us. We will only win togetherā€”when one falls, the other lends a hand; when one wins, we all win.

Thank you for your continued support.

DK

6 Likes

Hello Duka, first of all I would like to thank you for your answer and the adjustments to the goals for the next milestones!
Even though this could certainly have been done earlier.

But as you wrote yourself, we are all still in the building phase and mistakes can happen.
The new targets are feasible, at least from our point of view, even if it will be a challenge!
But thatā€™s how it should be!

I have another question regarding the measurement of transactions.
To 2.
Is the measurement based on the project token (in our case PMD) and the integrated KDA?
In addition to PMD, we have integrated numerous other KDAs that can be used by our games.
Is it sufficient to communicate the corresponding game wallets (currently approx. 10) and the Project Token?

1 Like

Yo, Iā€™m glad to see you here again with us :raised_hands:

Yes, you only need to prove that these transactions originated from your project (your wallets are a good way), no matter what KDA is.

4 Likes

It looks like weā€™re back.

I am very pleased that there has been a correction.

Together, we can target and realise significantly higher transaction figures.

For my part, I am busy every day helping the new and old community projects to process transactions and developing separate applications for them.

Thank you @Duka for your commitment. :muscle:

4 Likes

So glad to hear that! Theese are a lot more realistic and also challenging goals!

Like Andreas said, if we prove transactions of project related wallets, they also count?

We have 7 swap pairs, 2 FT tokens and 1 NFT token. We are also distributing rewards in form of KLV to our NFT holders (they originate from our wallet), so theese will be also counted?

1 Like

Hey @Duka quick question regarding the evaluation.
You said it would be a possibility to share the game wallets with you to be able to analyze the transactions.
Should we send them to you privately or here?
Greetings
Andreas

1 Like

Hey bro, Iā€™ll request to all competitors to send me the report at the end of the milestoneā€™s timeframe. :facepunch:

All transactions you can prove that were originated by your product (hackathonā€™s winner), count.

1 Like

ok, great!
I assume incoming ones count too!?

sorry for the stupid questions, but I would have liked to clarify the requirements as far as possible :sweat_smile:

1 Like

There arenā€™t stupid questions, feel free to ask :wink:. Itā€™s new for allā€¦ Weā€™re building this together. :rocket: And yes, I think to consider the incomings ones fair enough.

However is important to know, yā€™all need to a convincing proof that these transactions are made by or for your product (hackathonā€™s winner) :face_with_monocle:

1 Like

Thatā€™s great to hear! Iā€™m known for my stupid questions :rofl:
But fun aside!

All our game wallets are public and both user transactions (incoming) and winnings (outgoing) are tagged in the metadata!

But in my opinion this is not the safest way to prevent fraud, as anyone can add metadata to a transaction!
So as far as the evidence is concerned, how did you imagine!

2 Likes

Maybe @Marco_Jaeger will create a live evaluation in Klever Radar like for the other eventsā€¦ That would be great! :raised_hands:

1 Like

Is it possible for us to label our transactions or transactions made by users with our products using metadata for proof? @Duka

1 Like

Iā€™m thinking about this my friend. I will return soon

2 Likes

I propose we explore the use of metadata to verify transactions conducted through the App participating in the hackathon. This approach offers an efficient method to confirm transactions that might otherwise be difficult or costly to verify due to the unique nature of Špps.

Metadata can act as a key identifier, linking transactions to specific projects even if thereā€™s no inherent connection. By attributing transactions to the projects that drive user engagement and experience, we can effectively demonstrate a projectā€™s value in stimulating network activity. This virtuous cycle of user engagement and transaction volume serves as a strong indicator of a projectā€™s positive impact on the KleverChain ecosystem.

Furthermore, using metadata eliminates the need for mandatory token usage or transactions directed to specific project addresses. This approach prioritizes fairness by recognizing projectsā€™ ability to attract users and generate activity on the KleverChain network.

I believe this solution offers a solid foundation for efficient and transparent transaction verification within the hackathon.

Colleagues, please consider supporting our proposal. We believe this approach will benefit the KleverChain ecosystem as a whole.

@Duka

4 Likes

I give a + to this offer! :+1:

2 Likes

Due to the different apps and applications, I think everyone should find their own way to verify the transactions.

For example, we track all our game wallets by reading out the incoming and outgoing transactions over the given period.
In addition, almost all of our transactions are marked with metadata as you described, which gives conclusions about us.

By the way, congratulations to @Marco_Jaeger who will probably crack the 200k transactions today or tomorrow with his project :raised_hands:

7 Likes

After the challenge is before the challenge.
We were able to complete Milestone III with 290521 transactions!

I hope that the other projects were also successful :raised_hands:

*Now we are looking forward to the next era and are very confident that we will master it together with our users :muscle:

8 Likes

Hackathon Milestone 3
Results: Beyond Expectations!

Required Transactions: 200,000
Completed Transactions: 372,089

Not only did we smash our target, but we did so by counting only Airdropsā€”no individual transactions included!

Klever Desktop Studio
Klever Radar
Klever Tip
KFI Dist and more ā€¦

Weā€™ve not just met the challenge; weā€™ve obliterated it! :muscle:

Many thanks to all those who use and have used my tools, who have suggested improvements and also reported errors.

Congratulations also to @Andreas_Hennersdorf . Clean result. I expected nothing less from you. :star_struck:

10 Likes