> For the complete documentation index, see [llms.txt](https://nytshift.gitbook.io/nytshift-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nytshift.gitbook.io/nytshift-docs/hyperliquid/hyperliquid-builder-rewards.md).

# Builder reward state

## Inspect

1. Authenticate the local operator session and open terminal Safety settings.
2. In `COMMERCIAL CONTROL`, compare `LOCAL FILL LEDGER` with `VENUE BUILDER REWARDS`. They are independent evidence and are not expected to be identical.
3. Confirm the venue network and exact per-token reward rows. The browser response intentionally contains no builder, account or referrer identity.
4. Treat `UNCONFIGURED` as the safe default when `NIGHTSHIFT_HL_BUILDER_ADDRESS` is absent.

## State meanings

* `available`: the official referral response and every referenced spot-token identity passed strict normalization and token-zero root parity. Unreferenced catalog rows are outside this report's authority.
* `unconfigured`: no builder address is configured, so no venue request is made.
* `unavailable`: network/address configuration, provider access or response schema failed closed.
* `schema-unreviewed`: Hyperliquid has documented the builder archive location but not a normative CSV column contract; NIGHTSHIFT has not ingested it.

The displayed `builderRewards` field is per token. `unclaimedRewards` and `claimedRewards` are combined referral/affiliate/builder balances in the venue response and are not labeled builder-only revenue.

## Degraded response

1. Verify `HL_NETWORK` is exactly `testnet` or `mainnet` and the configured builder address is lowercase.
2. Confirm official `/info` access for both `referral` and `spotMeta` without logging the configured identity.
3. If token indices or response fields changed, keep the panel unavailable and review current official documentation before changing the contract.
4. Never fall back to floating-point conversion, scrape a frontend, accept browser-provided identity, or infer token identity from array position.
5. Do not claim rewards from this panel. Hyperliquid claims require a separately authorized main-wallet signature and the current statement is not claim-ledger reconciled.


---

# 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://nytshift.gitbook.io/nytshift-docs/hyperliquid/hyperliquid-builder-rewards.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.