Benchmark Validation

After the Proof of Work phase of a benchmark is complete, a Benchmarker’s direct involvement ends. The benchmark is then part of the protocol and goes through a process of verification and rewards, which we call the validation part of the benchmark.

The TIG protocol implements a lifecycle mechanism that ensures proper verification while incentivizing prompt submissions. This process is summarized in the diagram below:

Validation Lifecycle Steps

The validation lifecycle of a benchmark consists of several key steps, each with specific conditions and transitions. Refer to the Validation Lifecycle diagram above for a visual representation of these steps:

Proof of Work Completion (1)

This refers to the completed Proof of Work phase of the benchmark.

Pending Status (2)

Once proofs are submitted, the benchmark automatically moves to pending status.

Transition to Verification (3)

At each block, benchmarks have a chance to move from pending to verifying. This transition occurs when the following condition is met:

When this condition is satisfied, the verifying solutions set is updated:

• ${verifying\_solutions}$: Solutions from the benchmarker already in the verification process.
• ${qualifiers}$: This is the set of solutions from the benchmarker that qualified for rewards in the last block.
• ${benchmark\_solutions}$: The set of solutions from the current benchmark.
• ${delay}$: Number of blocks between the referenced block and when the benchmark moves from pending to verifying.
• ${cutoff}$ is the benchmarkers cutoff for the challenge that this benchmark targets.

This mechanism prevents benchmarkers from overwhelming the verification system with solutions that won’t qualify for rewards due to cutoff limits.

Verification Process (4)

Solutions undergo a comprehensive verification process lasting $1.2 \times \text{delay}$ blocks. During this phase:

• Sampled nonces have their hashes checked.
• Solutions are verified for correctness.
• Methods are validated.

After verification completes, the benchmark become active.

For more details, check Probabilistic Verification.

Active Phase and Rewards (5)

Benchmarks have a total lifespan of 120 blocks from their referenced precommit block. They remain active for the remaining blocks after $(1 + 1.2) \times \text{delay}$ blocks have elapsed since the initial reference.

Once a benchmark is active, it can earn rewards based on the Pareto Frontier mechanism.