> 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/market-data-and-providers/hyperliquid-metadata.md).

# Hyperliquid metadata drift

## Observe

Load the public catalog first, then inspect aggregate health:

```powershell
Invoke-RestMethod http://127.0.0.1:3000/api/market?venue=hyperliquid
Invoke-RestMethod http://127.0.0.1:3000/api/health
```

Healthy metadata reports `hyperliquidMetadataState=healthy`, `hyperliquidMetadataSchemaDrift=false`, positive DEX/asset counts and a recent `hyperliquidMetadataLastSuccessAtMs`. `degraded` with `HYPERLIQUID_METADATA_SCHEMA_DRIFT` means the normalized public catalog passed all required invariants but Hyperliquid added an unreviewed field. `unavailable` means parsing, cardinality, identity or one of the complete DEX reads failed. Configured-account reconciliation separately requires `allPerpMetas` to preserve the same sparse DEX slots and provide one exact collateral token per active DEX.

## Contain

* Keep Hyperliquid execution disabled. Execution review already rejects schema drift and invalid metadata.
* Do not delete a failing DEX, fabricate an index, loosen tuple/cardinality checks or treat the last cache as current discovery.
* Preserve only the fixed health reason and aggregate counts in incident material. Do not copy account responses, credentials or raw provider payloads into logs or tickets.

## Review

Compare the change against the official [perpetual metadata](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint/perpetuals), [spot metadata](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint/spot), [asset ID](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/asset-ids), and [precision](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/tick-and-lot-size) documentation. Verify `perpDexs`, `allPerpMetas` and `metaAndAssetCtxs` cardinality together; review any `collateralToken`, spot token identity or reserve-oracle change before accepting it. Add a field to the known set only after its type and capital-moving meaning are understood. Unknown enum values or changed required-field semantics remain fatal.

Run the focused and complete gates after a reviewed update:

```powershell
pnpm --filter @terminal/venues test
pnpm --filter @terminal/web test
pnpm handoff:verify
pnpm local:restart
pnpm local:health
```

Confirm the terminal shows current primary and HIP-3 markets, exact market IDs/precision remain stable, `/api/health` returns to `healthy`, and execution is still disabled unless its independent external gates have been deliberately satisfied.


---

# 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/market-data-and-providers/hyperliquid-metadata.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.