mirror of
https://github.com/luxfi/bridge.git
synced 2026-09-24 00:26:46 +00:00
zeekay
88af06da11
luxd serves exactly one HTTP prefix — /v1 (node server/http/server.go baseURL). /ext/ was removed some releases ago, so every Lux and Zoo URL in this repo was pointing at a 404. Measured 2026-07-27: api.lux.network/v1/bc/C/rpc 200 eth_chainId 0x17871 (96369) api.lux.network/ext/bc/C/rpc 404 api.lux-test.network/v1/bc/C/rpc 200 eth_chainId 0x17870 (96368) api.zoo.network/v1/bc/C/rpc 200 eth_chainId 0x30e08 (200200) api.zoo-test.network/v1/bc/C/rpc 200 eth_chainId 0x30e09 (200201) control api.lux.network/v1/bc/ZZZNOPE/rpc 404 ZOO_MAINNET/ZOO_TESTNET were doubly wrong: legacy prefix AND a "Z" chain alias that 404s on both prefixes. Zoo's EVM answers under bc/C. Avalanche endpoints deliberately keep /ext/ — that is their API, not ours (measured: api.avax.network/ext/bc/C/rpc 200 0xa86a, /v1 404). B-chain/T-chain URLs move to /v1 as well; BridgeVM is still undeployed (re-verified today: /v1/bc/B/rpc 404 while /v1/bc/C/rpc 200, so the 404 is "no such chain", not "no such prefix").