Prolongation of the RTDB: Analyze Hypercore internals contest
Short description
Analyze Hypercore internal structure, execution flows and algorithms.
This is the same contest “# 5 RTDB: Analyze Hypercore internals”, which was announced on 26 October, 2020 and is completely its continuation. All requirements and conditions remain the same.
Type
Contest
Dates
Starts: 21 November, 2020 at 01:00 PM UTC, Ends: 29 November, 2020 at 24:00 PM UTC
Motivation
The reason for the contest prolongation is lack of submissions.
FreeTON RTDB implementation is a complicated task, so we split it into parts. At this stage, it is necessary to investigate possible solutions. Hypercore seems like a promising base, but before we start, we should get a deep understanding on how it works inside.
Our goal is to understand in detail what hypercore/hypertrie is and how it works internally. This will help us find ways to integrate.
General requirements
Submission should give as clear as possible explanation of hypercore, hypertrie (and possible other suitable hypercore-based solutions like hyperdrive) architecture, modules, code relations, execution flow, data structures, internal messages and used algorithms.
This explanation should help us answer a question, how hypercore can be integrated with FreeTON.
Participants should provide:
- Description of the general architecture and main modules.
- Description of data structures used.
- Internal messaging and execution flow.
- Build a code diagram.
- Flow charts, who interacts with what and how.
- Other helpful information will be a plus.
Technical recommendations
- Reports should be clear and easy to read.
- Try to provide a sufficiently in-depth analysis, but without unnecessary, obvious detail.
Evaluation criteria and winning conditions
Proposals will be judged strictly on the merit of their accuracy in addressing all requirements.
Only qualified proposals that meet all the required criteria will be considered.
Rewards
1 place………………….……….
75’000
2 place………………….………. 60’000
3 place………….………………. 50’000
4-5 place………………………. 5’000
6-10 place……………………… 1’000
Voting
- Jurors 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 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.
- Jurors will provide feedback on your submissions.
- Duplicate, sub-par, incomplete, or inappropriate submissions will be rejected.
Jury rewards
An amount equal to 5% of the sum total of all total tokens actually awarded to winners of this contest will be divided equally between all jurors who vote and provide feedback. Both voting and feedback are mandatory in order to collect this reward.
Procedural reminders to all contestants
- 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, the submission may be rejected by jurors.
- Contestants must submit their work before the closing of the filing of applications. If not submitted on time, the submission will not count.
- All submissions must contain the contestant’s contact information, preferably a Telegram username by which jurors can verify that the submission belongs to the individual who submitted it. If not, your submission may be rejected.
- The content published in the forum and in the provided PDF file should not differ, except for formatting, otherwise, the submission may be rejected by jurors.
- If your submission has links to the work performed, the content of those links must have the contestant’s contact details, preferably a Telegram username so jurors can match it and verify who the work belongs to. If not, your submission may be rejected.
- The work must be uploaded to the PDF and any links can only be used as support for the submission, but that only the work in the PDF will be judged.
Disclaimer
Anyone can participate, but Free TON cannot distribute Tons to US citizens or US entities.
