Milestones for The Γ-Grant Program
The Γ-Grant Program is designed to support Challenge Owners and Challenge Designers in the development of computational challenges that helps building the TIG ecosystem.
This page outlines the high-level requirements and expectations for successfully achieving the technical milestones of The Γ-Grant Program.
Milestones for Challenge Owners
Evidence of a Well-Defined Challenge
To achieve this milestone, you will be required to:
- Define: Formally state and define the challenge along with pseudo-code. Outline its objective, constraints, and scope.
- Structure: Define the structure of the challenge along with pseudo-code. Clarify whether the target algorithms solve the full challenge or a subcomponent.
- Random Instance Generation: Describe how to generate unlimited, scalable, real-world-like benchmarks.
- Verification: Describe how to efficiently verify a solution along with pseudo-code. This may include introducing a baseline algorithm.
- Asymmetry: Demonstrate that finding a solution is substantially harder than verifying one.
- Difficulty Parameters: Define which parameters will scale the hardness of an instance, e.g., size (number of nodes) or quality (better than baseline metric).
Evidence of Real-World Alignment
To achieve this milestone, you will be required to engage with an expert who will:
- Review: Evaluate the challenge proposal for alignment with existing literature, potential impact, and real-world relevance.
- Design Guidance: Provide expert input on the problem definition, benchmark creation, and evaluation metrics, ensuring strong alignment with literature.
- Importance: Clearly articulate why the selected problem variant is optimal and likely to yield practical, real-world solutions.
- Expert Approval: Confirm that the final challenge design is robust, could attract state-of-the-art algorithms, and is positioned to deliver valuable outcomes.
Delivery of Implementation
To achieve this milestone, you will be required to deliver a functional, mainnet-ready implementation of your Challenge:
This means that you will need to have a working implementation/algorithm for your challenge that can be deployed on the TIG mainnet.
-
Clone the
tig-monorepoand switch to theblank_slatebranch to get started.git clone https://github.com/tig-foundation/tig-monorepo.git cd tig-monorepo git checkout blank_slateThis branch provides a template for implementing new challenges, including the necessary structure.
-
You can implement your challenge in the
tig-challengecrate, which is designed to support both Rust and CUDA implementations.If you are implementing a challenge in Rust, you can create a new file in the
tig-challenge/srcdirectory with the name<challenge>.rs. If you are implementing a CUDA challenge, you can create a file<challenge>.cuin the same directory. Also make sure to include a corresponding Markdown file<challenge>.mdthat describes the challenge, its objectives, constraints, and any other relevant information. -
You can now implement a simple working algorithm in the
tig-algorithmcrate. Read more about code submissions. -
Also make sure to update
tig-binary,tig-runtime, andtig-verifierto import your challenge. -
Once you have implemented your challenge, you will need to coordinate with the TIG Foundation to deploy your challenge to the testnet. This will involve working with the Foundation team to ensure that your challenge is properly integrated and tested.
This would also involve iterating on the implementation to address any issues that arise during testing and deployment.
TIG requires runtime_signature and fuel tracking which is natively supported by tig-binary and tig-runtime if your code is written in Rust and/or CUDA.
Use of other languages (e.g., Python, C++) must be discussed in advance and may require additional integration work.
Rust and/or CUDA are strongly recommended unless a specific framework is essential (e.g., quantum challenges using PennyLane).
Challenge Owner Infrastructure
To achieve this milestone, you are required to establish essential community and promotional infrastructure for the new Challenge, including:
- An official X (Twitter) account.
- A dedicated Discord channel on the TIG server.
- A detailed TIG forum post.
- A focused challenge website.
- Evidence of innovator outreach.