# Nest (/providers-market-data/nest)



The CLI reads Nest pools from Furge's catalog. HyperEVM markets use `999:<pool-address>`. Elysium markets use `99901:<hook>:<pool-id>`. Both preserve token addresses, pool type, and quote units.

```bash
mlab markets --exchange nest --refresh
```

## Python live data [#python-live-data]

```python
script = {"name": "watch-nest", "version": "2", "lookback": 1}
SOURCE = "UBTC/USDC@trades@nest"


def on_data(ctx, history):
    trade = history.source(SOURCE, 0)
    if trade is not None:
        print(trade)
```

Use a unique pool pair or the exact market key. See [Nest Scripts](/scripting-v2/nest#declare-the-pool) for selector forms. Python trade records expose `price` in the pool's quote asset and `size` in base tokens. The triggering event time is available as `ctx.timestamp_ms`.

The Nest feed supports live trades, trade-derived candles and volume delta, and indexed volume profiles. Registered pools have candle and aggregate-volume history within stored coverage. Raw trades are live-only.

## Yield metadata [#yield-metadata]

Furge's pool catalog can include the following normalized fields from Nest's public API on HyperEVM and Elysium. These describe the pool, not a particular wallet's claimable balance. They are not fields in a Python trade record.

| Field                    | Meaning                                                                 |
| ------------------------ | ----------------------------------------------------------------------- |
| `apr`                    | Reported total pool APR, including its reward component                 |
| `fee_apr`                | APR attributed to LP swap-fee earnings                                  |
| `emissions_apr`          | APR attributed to token rewards                                         |
| `fees_usd_24h`           | Reported pool fees in USD over the previous 24 hours                    |
| `is_fee_only`            | Explicit upstream classification as a fee-only pool                     |
| `is_emissions_only`      | Explicit upstream classification as an emissions-only pool              |
| `rewards_program`        | Known pool-level reward-program status; not wallet qualification        |
| `last_epoch_rewards_usd` | Reported previous-epoch pool rewards, not an amount owed to this wallet |

Yield fields are optional. Missing metadata remains unknown, and an explicit zero is meaningful. Do not infer emissions from a gauge address, interpret gross trading volume as LP income, or add reward APR to total APR again. These are APR snapshots, not automatically compounded APY. See [Nest execution](/providers-execution/nest#rewards-and-current-claim-support) for staking and claim limitations.

### Position estimates [#position-estimates]

Concentrated-liquidity earnings depend on the position's tick range, token amounts and active share. Nest's official HyperEVM deposit client uses the public `/api/blaze/liquidity/apr/estimate` endpoint with `poolAddress`, `minTick`, `maxTick`, `token0Amount` and `token1Amount`. Amounts are raw integer token units; the response contains an `apr` string. A full-range position can have a materially different APR from the pool headline.

Use a position-specific estimate when projecting hypothetical rewards, and retain the pool's fee/reward distinction. This endpoint does not establish a wallet's claim eligibility, return a guaranteed payout, or expose a verified Elysium estimator. Furge uses this endpoint for supported HyperEVM emissions-only position estimates. Token amounts are converted to exact raw units using the selected pool's decimals; range ticks are validated. Estimates use a 364-day annual basis and are not claimable balances. Unsupported or missing personal reward estimates remain unknown.

Primary references: [Nest's pool API](https://app.usenest.xyz/api/blaze/liquidity-pools), [Nest's liquidity interface](https://app.usenest.xyz/liquidity), [LP reward mechanics](https://docs.usenest.xyz/liquidity-types/4.1-lping-on-nest.md).

## Cloud and standalone connections [#cloud-and-standalone-connections]

The regional node refreshes the pool catalog separately from the trade feed. When configured with a HyperEVM WebSocket RPC, the consumer subscribes to live swap logs and updates the subscription as initialized pools change. It sends decoded trades through the shared processor for storage and streaming. HyperEVM nodes without a WebSocket RPC use bounded HTTP polling. Elysium uses the configured Elysium mainnet WebSocket to receive PoolManager swaps for registered Nest pool IDs.

Managed runtimes use their assigned node. The standalone CLI uses Furge for pool discovery, Elysium live trades, candles, and volume. HyperEVM’s direct trade provider can also read live swaps from its configured RPC. Set `MLAB_CLOUD_URL` to use another Furge market data endpoint. For standalone contract quotes and execution, use `MLAB_HYPEREVM_RPC_URL` for HyperEVM or `MLAB_ELYSIUM_MAINNET_RPC_URL` for Elysium.

See [Nest execution](/providers-execution/nest) for wallet and transaction behavior.
