> For the complete documentation index, see [llms.txt](https://docs.gpu-fi.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpu-fi.uk/transparency/how-to-verify.md).

# How to Verify

Explains how to independently verify onchain information.

Do not take an onchain claim on trust. Verify the underlying data.

The following paths apply to deployed or reference information. Roadmap statements require a different standard because their underlying infrastructure may not exist yet.

### Verify the Pons V2 factory

Reference address:

```
0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
```

This is the Pons V2 factory address specified by the project. Check it on Robinhood Chain using an appropriate block explorer or RPC tooling.

### Verify the NVDA stock token

Reference address:

```
0xd0601CE157Db5bdC3162BbaC2a2C8aF5320D9EEC
```

The source identifies this as the NVDA stock token reference. The address can be checked independently onchain.

### Verify graduation data

The project references onchain graduation data when analyzing launch behavior.

{% stepper %}
{% step %}

#### Identify the relevant launch data

Locate the launch data relevant to the claim being reviewed.
{% endstep %}

{% step %}

#### Inspect associated onchain records

Review the associated transactions and contracts.
{% endstep %}

{% step %}

#### Confirm graduation

Confirm whether graduation occurred.
{% endstep %}

{% step %}

#### Compare the result

Compare the observed result with the project's stated data.
{% endstep %}
{% endstepper %}

### Verify tax configuration

Tax configuration can be checked onchain. Inspect the creator tax configuration, relevant contract configuration, and actual deployed parameters where applicable.

### Verify project scripts

The project references `scripts/` for research and verification. Review those scripts when assessing the related onchain claims.

No script filenames or command syntax are specified here.

### What cannot yet be verified onchain

Future roadmap items cannot be treated as deployed infrastructure until they actually exist.

{% hint style="warning" %}
The following cannot currently be verified as live: Phase 2 GPU purchases, unpublished GPU serial numbers, future GPU hosting, future GPU rental revenue, future external operators, the future inference API, and future admin renouncement.
{% endhint %}

Roadmap statements describe intended future actions. They become independently verifiable only when the underlying deployment, hardware, or transaction exists.

### Whitepaper versioning

Current version: `0.1`\
Date: September 2026

Updates are tracked publicly. No silent edits are intended. Material changes are intended to be explained publicly.

Verify what can be verified. Treat future milestones as future milestones.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gpu-fi.uk/transparency/how-to-verify.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.