docs: chain routes are /v1/chain, health probes are /v1/health/ops

luxd serves chain APIs under one segment from constants.ChainAliasPrefix
(constants v1.6.4, node v1.36.181), and the health service moved onto typed
ops. Published addresses now match what a node answers on:

  /v1/bc/<alias>/...    -> /v1/chain/<alias>/...
  /ext/bc/<alias>/...   -> /v1/chain/<alias>/...
  /v1/health            -> /v1/health/ops/health     (full report)
  /v1/health/liveness   -> /v1/health/ops/liveness
  /v1/health/readiness  -> /v1/health/ops/readiness

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 17:31:37 -07:00
parent 51430e25c1
commit cce073153d
+1 -1
View File
@@ -89,7 +89,7 @@ resolves a `CreateChainTx`'s vmID. `TestVMID_IsCanonicalAndStable` pins it.
- M-Chain is in the genesis chain set of every network
(`genesis/configs/*/mchain.json`), policy `3-of-5` on
mainnet/testnet/devnet and `2-of-3` on localnet.
- Proven: boots on luxd as a genesis chain and serves `/v1/bc/m-chain/rpc`;
- Proven: boots on luxd as a genesis chain and serves `/v1/chain/m-chain/rpc`;
`TestBridgeCustody_ThreeOfFive` runs a real 5-validator CGGMP21 DKG at
degree 2 with a genuine 3-of-5 signature verified and recorded on-chain.
- **Not** yet proven: a DKG across five separate luxd OS processes over real