Free TON

Contest: Analytics of partner requests

Contest: Analytics of partner requests

Short description

Creation and support of an analytical system about potential and current partners with all the key characteristics of each request.



Contest entry period:

June 21, 11:59 PM UTC - July 20, 23:59 PM UTC

Voting Cycle:

7 days


To date, more than 80 requests for partnerships have been submitted. Some requests have been approved, others are pending and will likely not be accepted.

The community has repeatedly raised the issue that summary information on all accepted and rejected partnerships is needed. There is no convenient toolkit for the community that can conveniently analyze previously submitted partnerships and form a holistic view of current and potential partners.


Creation of an analytical system that consolidates information on all requests from potential partners. It will be regularly updated (at least once a week) and will allow you to answer the following questions:

  • How many partnerships are submitted to the community each month?
  • Which of the applicants attracted more potential partners and which of these partners was accepted?
  • From what areas are partners more often accepted?
  • What are the requests of potential partners in the context of areas of activity? Does the request amount change as the project develops?
  • How many tokens have been allocated for each partner?
  • How did each accepted partner dispose of the received tokens?

The system should show the scale of the current affiliate network and make the process transparent for all participants. This will allow potential partners to make a more balanced proposal for new partnerships.

Evaluation criteria and winning conditions:

● Analytics should include all applications that exist at the time of the launch of this competition.

● Analytics should contain a description of each potential partner and their field of activity, KPI, information about AMA Session

● Analytics should have an automatic solution to update information on actual receipts and debits from the partner’s wallet.

● Information must be provided in English, but other languages are encouraged.


Only submissions that receives average score 6 and above will get a chance to get prizes for participation. And only submissions with score 7 and above could get into TOP-3.

1st prize…………………………………………… 50,000 Tons

2nd prize…………………………………………… 30,000 Tons

3rd prize…………………………………………… 20,000 Tons

Runners up from 4th to 10th place ……………… 3,000 Tons

Rewards will be paid over three months, at 33.3% of prize once a month. The winner undertakes to maintain his analytics until the end of the vesting period. Otherwise, the payment of the prize may be suspended.

Note: If the number of winning submissions is less than the number of rewards available, any remaining rewards are not subject to distribution and are considered void.


● The juror must have a solid understanding of the described subject in order 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.

● The number of days for jury voting is hereby set at 7 days

Jury rewards:

An amount equal to 15% of the sum total 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 20 times and another juror votes 5 times, the juror who votes 20 times will get 4 times more tokens than the juror who votes 5 times.

● Feedback is mandatory in order to collect any rewards.

Reward for contest creation:

An amount equal to 1% of the sum total of all total tokens awarded to contest winners will be distributed to the author of the contest:


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 reject the submission.

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

Content. The request should include screenshots of analytics showing the number of partnerships it contains, information about actual payments, and other significant elements of the report. If the report differs from the screenshots from the request, the work will be evaluated based on the data visible in the screenshots.

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 is 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 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 made will count. The Jury will reject all others.

Estimated budget:

121 000 + 0,15 * 121 000 + 0,01 * 121 000 = 140 360 TONs

1 Like

На мой взгляд, срок подачи заявок должен быть не меньше месяца. 20 дней - слишком маленький срок, что приведет к минимальной конкуренции и наспех сделанным дашбордам.

Кроме того, сейчас начата работа по KPI отчетам, если в разработанном аналитическом сервисе будет предусмотрена возможность добавления ссылок на KPI отчеты - это будет большой +.
В итоге получим единую полную базу по всем партнерам.

Данные аналитического сервиса должны обновляться постоянно, а не в течение 3 месяцев, пока будут осуществляться выплаты. Возможно внести пункт о дополнительных выплатах конкурсанту, занявшему первое место, чтобы обновления были на систематической основе, иначе вообще нет смысла в АС, который через 3 месяца будет неактуален.

The contest entry period must be at least one month. 20 days is too little time, which will lead to minimal competition and hastily made dashboards.
In addition, we have been preparing KPI reports. If the developed analytical service will provide the ability to add links to KPI reports - this will be a big +.
As a result, we will get a single complete database for all partners.

1 Like

разработка требует времени и большой предварительной работы. За такие бюджеты сообщество должно четко понимать что получит на выходе конкурса.

Need more time for creating quality product. Community should clearly understand what will be result of that contest.

Participants can come up with their team work

стоит плавнее сделать шкалу 4-5 места до 7000-6000 ТОН, поднять награду 6-10 места до 5к ТОН и поставить на контест трешхолд 5 например.

для участников это разработка кода и если будет много участников, то награда в 3к не покроет издержки. к тому же месяц конкурс идти будет.

1 Like