The user asked whether we can see order-book volume for each side of the QTC pairs on NEAR Intents. There is no order book. Solvers quote privately, off-chain, per request, and intents.near records only the trades that settle. So there is nothing on-chain with price levels.
What is on-chain is each solver's inventory inside intents.near: its multi-token balances, which are what it fills from. Checked on 2026-10-03 against our own node: intents.near lives on the shard it tracks, so mt_balance_of / mt_batch_balance_of are answered locally in ~40 ms, with no public endpoint and no rate limit. At the time:
solver-priv-liq.near held 1,899,452.9 wNEAR
blockzen-1-main.near held 1,409 wNEAR, 57.67 ZEC, 18.57 USDt and 0 QTC
What
Who counts as a solver. Accounts seen filling trades, recorded by the scan from every executed outcome it already parses, not only QTC's. A solver is a leg with no referral on a named account (not an implicit hex or 0x… account), which matches the #30 survey: 589 such legs, all solver accounts. They go in a new intents_solver table (migration 0011) with first and last NEAR height and fill count, so the list survives restarts. Before QTC trades, the list is the solvers that fill other pairs. That is the useful part: when they start stocking QTC, the page shows it before the first trade.
Inventory: every 60 s, one mt_batch_balance_of per solver against our node (not the public view endpoint). The tokens asked for are the asset plus every counter token ever traded against it. The result is held in memory (refreshed, not historical) and served at GET /v1/chains/{chain}/intents/inventory.
Sides:
sell side is the asset held by solvers: what a buyer of QTC could be filled from.
buy side is each counter token held by solvers: what a seller of QTC could be paid in.
Each comes with a count of solvers holding a non-zero balance.
Page: an Inventory panel on /:chain/market/near-intents. It is a table, not a chart: token, side, held, solvers holding. It is labelled as inventory and never as depth or an order book.
Not this, and what the page must say
No price levels. It is capacity, not depth at a price.
Shared across pairs. The same USDT backs every pair a solver quotes, so buy-side figures overlap and must not be summed.
Not a ceiling. Solvers deposit just in time from elsewhere and route through other tokens. Zero means "none held right now", not "cannot be filled".
The solver list is ours. An account that fills only by a route this indexer does not read (cross-contract receipts, #27's known blind spot) is not in it.
1Click dry-quote depth probing is out. Quotes are offers, not trades (#27), and polling them loads other people's solvers. QTC quotes also fail today.
## Why
The user asked whether we can see order-book volume for each side of the QTC pairs on NEAR Intents. **There is no order book.** Solvers quote privately, off-chain, per request, and `intents.near` records only the trades that settle. So there is nothing on-chain with price levels.
What *is* on-chain is each solver's **inventory inside `intents.near`**: its multi-token balances, which are what it fills from. Checked on 2026-10-03 against our own node: `intents.near` lives on the shard it tracks, so `mt_balance_of` / `mt_batch_balance_of` are answered **locally in ~40 ms**, with no public endpoint and no rate limit. At the time:
- `solver-priv-liq.near` held 1,899,452.9 wNEAR
- `blockzen-1-main.near` held 1,409 wNEAR, 57.67 ZEC, 18.57 USDt and 0 QTC
## What
- **Who counts as a solver.** Accounts seen filling trades, recorded by the scan from every executed outcome it already parses, not only QTC's. A solver is a leg with no `referral` on a named account (not an implicit hex or `0x…` account), which matches the #30 survey: 589 such legs, all solver accounts. They go in a new `intents_solver` table (migration 0011) with first and last NEAR height and fill count, so the list survives restarts. Before QTC trades, the list is the solvers that fill other pairs. That is the useful part: when they start stocking QTC, the page shows it before the first trade.
- **Inventory:** every 60 s, one `mt_batch_balance_of` per solver against **our node** (not the public view endpoint). The tokens asked for are the asset plus every counter token ever traded against it. The result is held in memory (refreshed, not historical) and served at `GET /v1/chains/{chain}/intents/inventory`.
- **Sides:**
- **sell side** is the asset held by solvers: what a buyer of QTC could be filled from.
- **buy side** is each counter token held by solvers: what a seller of QTC could be paid in.
Each comes with a count of solvers holding a non-zero balance.
- **Page:** an **Inventory** panel on `/:chain/market/near-intents`. It is a table, not a chart: token, side, held, solvers holding. It is labelled as inventory and never as depth or an order book.
## Not this, and what the page must say
- **No price levels.** It is capacity, not depth at a price.
- **Shared across pairs.** The same USDT backs every pair a solver quotes, so buy-side figures overlap and must not be summed.
- **Not a ceiling.** Solvers deposit just in time from elsewhere and route through other tokens. Zero means "none held right now", not "cannot be filled".
- **The solver list is ours.** An account that fills only by a route this indexer does not read (cross-contract receipts, #27's known blind spot) is not in it.
- **1Click dry-quote depth probing is out.** Quotes are offers, not trades (#27), and polling them loads other people's solvers. QTC quotes also fail today.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
The user asked whether we can see order-book volume for each side of the QTC pairs on NEAR Intents. There is no order book. Solvers quote privately, off-chain, per request, and
intents.nearrecords only the trades that settle. So there is nothing on-chain with price levels.What is on-chain is each solver's inventory inside
intents.near: its multi-token balances, which are what it fills from. Checked on 2026-10-03 against our own node:intents.nearlives on the shard it tracks, somt_balance_of/mt_batch_balance_ofare answered locally in ~40 ms, with no public endpoint and no rate limit. At the time:solver-priv-liq.nearheld 1,899,452.9 wNEARblockzen-1-main.nearheld 1,409 wNEAR, 57.67 ZEC, 18.57 USDt and 0 QTCWhat
Who counts as a solver. Accounts seen filling trades, recorded by the scan from every executed outcome it already parses, not only QTC's. A solver is a leg with no
referralon a named account (not an implicit hex or0x…account), which matches the #30 survey: 589 such legs, all solver accounts. They go in a newintents_solvertable (migration 0011) with first and last NEAR height and fill count, so the list survives restarts. Before QTC trades, the list is the solvers that fill other pairs. That is the useful part: when they start stocking QTC, the page shows it before the first trade.Inventory: every 60 s, one
mt_batch_balance_ofper solver against our node (not the public view endpoint). The tokens asked for are the asset plus every counter token ever traded against it. The result is held in memory (refreshed, not historical) and served atGET /v1/chains/{chain}/intents/inventory.Sides:
Each comes with a count of solvers holding a non-zero balance.
Page: an Inventory panel on
/:chain/market/near-intents. It is a table, not a chart: token, side, held, solvers holding. It is labelled as inventory and never as depth or an order book.Not this, and what the page must say