> For the complete documentation index, see [llms.txt](https://hyperpnl.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hyperpnl.gitbook.io/docs/architecture/smart-contracts/data-recorder.md).

# Data Recorder

The Data Recorder is the on-chain contract responsible for verifying, finalizing, and immutably recording challenge outcomes.

While trading execution and monitoring happen off-chain, final outcomes are anchored on-chain through the Data Recorder. This ensures that results cannot be altered, delayed, or overridden after completion.

#### What Gets Recorded

The Data Recorder stores cryptographic records representing the official state of a challenge.

This includes:

* Challenge progress checkpoints
* User-verified commitments
* The final challenge outcome

These records collectively determine whether a payout is authorized.

#### User-Verified Commitments

At defined points during a challenge, the system presents the user with a clear and complete summary of the relevant challenge state.

This summary includes all critical information required to evaluate the outcome, such as performance metrics, rule compliance, and final status.

The user can review this information in full before proceeding.

By signing the commitment, the user explicitly confirms that:

* All displayed information is accurate
* The recorded state correctly reflects their trading activity
* The outcome may be finalized based on this data

The signature serves as explicit user confirmation and is recorded on-chain by the Data Recorder.

This ensures that outcomes are not only system-generated, but also user-reviewed, acknowledged, and verified.

#### Final Outcome and Authorization

Once a challenge is completed, the final outcome is recorded on-chain and becomes immutable.

This on-chain record is the single source of truth used to authorize payouts.\
If the recorded outcome authorizes a payout, the Payout Treasury can execute it.\
If it does not, funds cannot be released.

There is no manual approval process.

#### Immutability and Corrections

The Data Recorder does not allow:

* Editing existing records
* Deleting outcomes
* Retroactive changes

If a correction is ever required, it must be recorded as a new on-chain entry.\
All previous records remain visible and verifiable.
