Free TON

Contest: TON OS Startup Edition installation scripts [Part 2 | Integration with TONDEV CLI]

Contest: TON OS Startup Edition installation scripts [Part 2 | Integration with TONDEV CLI]

Short description

Integrate solutions from the previous TON OS SE contest into TONDEV utility.

Contest dates

July 12, 2021 — August 9, 2021, 23:59 UTC

Voting cycle

14 days


TONDEV is a Node.js package with CLI interface that allows users to easily download and install all the core TON.DEV components in a background and use them from a single interface. Currently it supports TON OS SE installation by Docker engine, which adds additional requirements and complexity for end-users. This contest aims to extend the TONDEV utility to support non-docker TON OS SE installers developed in previous contest.


The task of this contest is to create a Github pull request with integration of previous contest results into TONDEV. TONDEV can be extended using a controller for your TON SE Installer. Details: tondev/ at main · tonlabs/tondev · GitHub. Participants can take any multi platform submission from the previous contest to integrate.


  • TONDEV must support Docker installation together with non-Docker one
  • non-Docker installation MUST have the same functionality as Docker one
  • need to add a non-docker option(flag) while running TON SE using tondev. Like this: “tondev se some-flag command”, meaning that some-flag should reflect that User uses non-docker installation
  • TONDEV must have the following commands to interact with non-Docker installation (again all MUST be the same as in Docker one with a difference only in “nd flag”):
    • start network
    • stop network
    • reset (restart the local blockchain from scratch)
    • configure port where it runs
    • expose arangoDB web interface to some port
    • and other possible/required or desired configuration options
    • upgrade TON SE
    • show current version
  • TONDEV VS Code extension should be able to work with non-Docker TON SE installation
  • using Docker and non-Docker installation simultaniasly should not be allowed or not affect user experience
  • TONDEV 0.7.4 must be used as a code version to integrate with (Merge pull request #40 from tonlabs/0.7.4-rc · tonlabs/tondev@9247423 · GitHub)

Submission format

Submissions must be uploaded to blockchain as a PDF with a link to Github pull request into GitHub - tonlabs/tondev: TON Development Environment - install all the core TON.DEV components in one click and access them from a single interface. repository.

Reject criteria

Submission is rejected if any of these criterias are present.

  • Lack of documentation
  • TONDEV doesn’t work as expected
  • TON OS SE cannot be fully managed only using TONDEV interface

Evaluation criteria

Considering the following criteria set, the submission score increases:

  • Non-Docker installation doesn’t add any complexity to TONDEV
  • User experience
  • Readable source code
  • Detailed documentation


  • The juror must have a solid understanding of the described technology to provide a score and feedback. If not, the juror should choose to “Abstain”.
  • Feedback should be provided as a comment to his vote and as a comment to pull request in Github
  • Each jury should clone changes from pull request branches and verify functionality on Windows, OS X and Linux systems


  • The juror must have a solid understanding of the described technology to provide a score and feedback. If not, the juror should choose to “Abstain”.
  • Jurors or whose team(s) intend to participate in this contest by providing submissions lose their right to vote in this contest.
  • Each juror will vote by rating each submission on a scale of 1 to 10 or can choose to reject it if it does not meet requirements or vote “Abstain” if they feel unqualified to judge.
  • Jurors must provide feedback on submissions or lose their reward.
  • The Jury will reject duplicate, sub-par, incomplete, or inappropriate submissions.

Contest Rewards

  1. :gem: 30’000
  2. :gem: 20’000
  3. :gem: 10’000

Reward Distribution

All rewards are distributed after the end of contest voting.

Jury Rewards:

An amount equal to 10% of the total sum of all total tokens awarded to contest winners will be distributed among jurors who vote and provide feedback. This percentage will be awarded on the following basis:

  • The percentage of tokens awarded to the jury will be distributed based on the number of votes each juror casts. For example, if one juror votes 50 times and another juror votes 5 times, the juror who votes 50 times will get 10 times more tokens than the juror who votes 5 times.
  • Feedback is mandatory to collect any rewards.

Org Rewards:

An amount equal to 5% of the total sum of all total tokens awarded to contest winners will be distributed among org members who helped to organize and promote the contest, and organize rewards distribution in equal proportion.

0:06c812287e994efba0640753a4f4bb5ef43e3caba6254cb0ae820ad7663ef815 - Sam
0:acad9bed05bbf1223de0c9c7865d5f34d488487e941f76e888b19640ced190cf - Ekaterina

Procedural requirements:

Accessibility. All submissions must be accessible for the jury to open and view, so please double-check your submission. If the submission is inaccessible or does not fit the criteria described, jurors may reject the submission.

Timing. Contestants must submit their work before the closing of the filing of applications. If not submitted on time, the submission will not count.

Contact. Each submission must have an identifiable contact that can be matched with your description. If you have not provided a forum description for discussion, then your application should contain links to your online persona, for example, a Telegram ID (preferred) or other direct contact information that can confirm that the submitted work is yours. In the absence of confirmation by the contestant of the authorship of the submitted work, the submission may be rejected.

Multiple submissions.

  • Each contestant has the right to provide several submissions if they are all different from one another. If they are too similar, or in any way appear to be partially the same work done twice, or if they appear to be one whole body of work divided into parts to create the illusion of several submissions, jurors have the right to reject such submissions.
  • If the contestant wants to make an additional submission to replace a previously published submission, the contestant must inform the jury about this fact and indicate which submission is the one to be judged. In this case, only the indicated work will count. If the contestant fails to indicate which submission to judge, only the first submission that is uploaded by timestamp will count. The Jury will reject all others.
1 Like

It is not clear who and how will determine the list of those “org members who helped to organize and promote the contest”. And who and how will keep track of “the time spent”.
I believe this should be clarified.

1 Like

Added. See updated version above