DeBots are a game changing paradigm in blockchain development which will introduce End-to-End Decentralization concept to users. However, there are a few developers capable of implementing DeBots. This contest will motivate developers to learn the tech behind DeBots and dive into the world of Free TON.
Contest duration: 7 days
Voting duration: 14 days
Start date: Feb, 22st, 2021, end of day UTC
End date: Feb, 28th, 2021, end of day UTC
Write and publish any DeBot
Description of use cases (scenarios) as well as actions available in DeBot.
Open-source code published under free license.
Your repo should include README with introduction and usage manual (reference) and deploy instructions (reference).
Each of the Free TON Smart Contract Jury Group can vote on a submission. Jurors whose team(s) intend to participate in this contest by providing submissions must abstain from voting in this contest.
Each juror will vote by rating each submission on a scale of 0 to 10 or can choose to reject it if it does not meet requirements, or they can choose to abstain from voting if they feel unqualified to judge (this should not be the case in this contest).
Jurors should provide feedback on each submission they vote for or reject.
Jury and Org Rewards
Jury rewards consist of 10% of prize pool. Organizational activity for contest initiation and holding rewarded as 5% of prize pool.
Jury for this contest consists of Smart Contract Jury Group and any other members which do like to participate in judging and have enough competences (have real experience in smart-contracts and can prove it on-chain). All those “other” members should contact organizers below before the start of this contest.
prize pool is relatively small.
this is not about rocket science , and really don’t need additional resources to put into organization and regulatioon .
task is clear : “build any debot”
requirements basically indicate our expectations that good participant has skills to document and describe code, and the code should work.
it’s also said that automated deployment procedure is great thing to include in codebase.
and of course it’s great to demonstrate some useful piece not a simple todo app.
it is great for participants to follow simple industry best practices as first priority, secondly - propose usecases and show the ability to apply the technology in real life.
small additional thing is to share feedback on their dev experience with debot engine , which will be of real value for tonlabs in further development of dengine and interfaces.
i agree that the paragraph with “additional criteria” is not really well formulated. these are not criteria really. just an optional task with a star
it is proposed to perform some code review , and any other smart contract submissions analysis including this contest simissions as well.
it is said “make separate submission with arbitrary feedback on what you have seen in codebases of others”
there are no criteria for judging this part of contest, but this activity is proposed to get more from devs who feel comfortable and want to try themselves as reviewers. obviously it will teach us all and give some clues on what to expect from Qualified SC Jury. and hopefully it will raise some interesting tech talks here and there.
i don’t want to reward “review and elaborate” parts because there are no real expectations, but the possible outcome is really interesting and everyone has full freedom to build some beautiful and share thoughts. isn’t that great?
I see this more like hakathon rules. So there are no strict functional requirements of tasks!
Of course the opinions will be non-formal for such criterias as Real use-case implmentation in case a couple of debots have such implementation. But, you know, we have several voters not a one machine!