Breakthrough Submissions
Breakthrough submissions involve the introduction of novel algorithms tailored to solve TIG’s proof-of-work challenges. A breakthrough submission will often yield such a significant performance enhancement that even unoptimised code of the new algorithm outpaces the most optimised code of an existing one.
All the breakthrough submissions lives under the tig-breakthrough
directory in the TIG monorepo.
Each submission is committed to their own branch in the format <challenge_name>/breakthrough/<method_name>
. The method name should be unique and descriptive of the algorithm.
Making a Submission
-
Read important docs for what is a Breakthrough and how it is rewarded:
-
Email the following to
[email protected]
with subject “Breakthrough Submission (<breakthrough_name>
)”:-
Evidence form: copy & fill in
evidence.md
. Of particular importance is Section 1 which describes your breakthrough -
Invention assignment: copy & replace invention_assignment.doc the highlighted parts. Inventor and witness must sign.
-
Address Signature: use etherscan to sign a message
I am signing this message to confirm my submission of breakthrough <breakthrough_name>
. Use your player_id that is making the submission. Send the verified etherscan link with message and signature. -
(Optional) Code implementation: attach code implementing your breakthrough. Do not submit this code to TIG separately. This will be done for you
-
Notes:
-
The time of submission will be taken as the timestamp of the auto-reply to your email attaching the required documents.
-
Iterations are permitted for errors highlighted by the Foundation. This will not change the timestamp of your submission
-
250 TIG will be deducted from your Available Fee Balance to make a breakthrough submission
-
An additional 10 TIG will be deducted from your Available Fee Balance to make an algorithm submission (if one is attached)
-
You can top up via the Benchmarker Dashboard
Submission Flow
-
The evidence form of the submission is added to a private branch with format
<challenge_name>/breakthrough/<method_name>
. -
The evidence form will be pushed to the public repository at the start of round
X + 2
(whereX
is the round the submission was made). A forum post will also be created for discussing the evidence -
During round
X + 3
, token holders can vote on whether they consider the method to be a breakthrough based off the evidence and discussion
Only deposits that remain locked at round X + 6
are eligible to vote
- At the start of round
X + 4
, votes are tallied. If the submission has at least 50% yes votes, it becomes active.
Active Breakthroughs
-
Every block, a method’s adoption is the sum of all algorithm adoption, where the algorithm is attributed to that method. Methods with at least 50% adoption earn rewards and a merge point.
-
At the end of a round, a method from each challenge with the most merge points, meeting the minimum threshold of 5040, gets merged to the
main
branch.Merged methods are considered breakthroughs, and receive rewards every block where their adoption is greater than 0%