> For the complete documentation index, see [llms.txt](https://docs.hit.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hit.one/1000x/price-feeds-and-orderbooks.md).

# Price Feeds & Orderbooks

Hit One displays prices and executes trades using on-chain data.

This page explains where that data comes from, how it is used, and how to verify it independently.

### Price feeds

Hit One sources prices from RedStone, an on-chain oracle network.

It reads prices in real time from RedStone's high-speed feed adapter on MegaETH: `MegaEthFastMultiFeedAdapterV1`.

The same feeds drive every part of the product:

* Live PnL in the trading panel
* Stop loss and liquidation triggers
* Realized PnL on close
* Public price endpoints and WebSocket broadcasts

There is no separate display feed.

The price you see is the price the engine uses.

### Live markets

| Market | Status      |
| ------ | ----------- |
| `BTC`  | Live        |
| `ETH`  | Live        |
| `SOL`  | Live        |
| `HYPE` | Coming soon |

### Staleness protection

Hit One monitors the freshness of every price feed.

If a feed stops updating or fails sanity checks, that market is marked unhealthy and trading pauses automatically until the feed recovers.

This prevents positions from opening or closing against a stale price.

### The exchange and orderbook

Trades execute on World Capital Markets, a perpetual futures DEX on MegaETH.

Sizing, spread checks, and execution use WCM's live `PerpOrderBook` contract.

That is the same orderbook every other WCM trader sees.

The bid and ask spread shown in the trading panel is the live WCM spread, sampled in real time.

Hit One does not maintain a separate internal orderbook.

### Verifying the data

You can read the same data Hit One uses directly from MegaETH.

| Contract              | Address                                      |
| --------------------- | -------------------------------------------- |
| RedStone main adapter | `0x897A33A0AF45b3ba097Bd6045187D622252e6AcD` |
| WCM `PerpOrderBook`   | Per-market addresses will be added here      |

You can also use RedStone's public dashboards and feed explorers at [redstone.finance](https://redstone.finance).

### What's next

* [How it works](/1000x/how-it-works.md)
* [Stop Losses and Liquidation](/1000x/stop-losses-and-liquidation.md)
* [FAQ](/1000x/faq.md)


---

# 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.hit.one/1000x/price-feeds-and-orderbooks.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.