zeekay e661decabb chain routes: /v1/bc -> /v1/chain ...

luxd serves chain routes under /v1/chain, and the node, cli and sdk releases
already ship it. The deployed gateways still answer the old prefix, so remote
reads break until they are redeployed; the estate moves together rather than
sitting half converted.

Lines that record an observation - a probe, a status code, a past release -
keep the prefix they were written against, as do URLs on hosts that are not
ours. Avalanche endpoints move to /ext/bc, which is the path that host serves.

2026-09-01 08:20:22 -07:00

..

chains

chain routes: /v1/bc -> /v1/chain

2026-09-01 08:20:22 -07:00

tenants

brand: audit, rip non-lux references, add .well-known/bridge.json

2026-05-29 14:25:39 -07:00

schema.yaml

docs+manifest: align protocol references with new union (NIT from red review)

2026-05-21 14:57:19 -07:00