docs: chain routes are /v1/chain

luxd serves chain APIs under one segment from constants.ChainAliasPrefix
(constants v1.6.4, node v1.36.181):

  /v1/bc/<alias>/...   -> /v1/chain/<alias>/...
  /ext/bc/<alias>/...  -> /v1/chain/<alias>/...

Observations keep their original addresses: a dated note or a recorded status
code is a fact about when it was written, not an instruction to follow.
This commit is contained in:
2026-08-30 16:41:57 -07:00
parent dfb9c57fc3
commit c287fa46b3
+1 -1
View File
@@ -161,7 +161,7 @@ The `dex` subgraph (markets/fills/orders/orderbook) can be fed from either or bo
trade engine IS the D-Chain (dexvm): a trade is a consensus state transition at
`Block.Verify`, NOT an EVM event, so it NEVER appears on the EVM RPC. `CLOBSource`
(`indexer/clob.go`) polls the committed-state read RPC
`…/v1/bc/<D>/dex/clob_get_{markets,trades,orders}` (GET/JSON, READ-ONLY, zero
`…/v1/chain/<D>/dex/clob_get_{markets,trades,orders}` (GET/JSON, READ-ONLY, zero
consensus impact — see `luxfi/dex pkg/dchain/read.go`) and writes the SAME
Market/Fill/Order entities the resolvers serve. Enabled by `Config.DexRPC` (graph)
/ `dex_rpc:` per-chain (explorer `chains.yaml`); empty = source 1 only.