mirror of
https://github.com/luxfi/bridge.git
synced 2026-09-24 00:26:46 +00:00
zeekayandHanzo Dev
a702429811
luxd serves exactly one prefix, /v1 (node/server/http/server.go:33), and has never served /ext. createBridgeRPCClient's two defaults are the SDK's whole contract for a caller who passes only nodeUrl — both pointed at a 404, and a caller had no way to see it from the outside. Two Zoo endpoints were also aimed at the wrong network entirely: api.lux.network/ext/bc/zoo/rpc and api.zoo.network/ext/bc/Z/rpc. Zoo is sovereign on api.zoo.network (200200) and api.zoo-test.network (200201), both confirmed serving /v1/bc/C/rpc; /v1/bc/Z/rpc and /v1/bc/zoo/rpc are 404. Env is the hostname, never a path segment. Patch-bumps @luxfi/bridge 1.0.6 -> 1.0.7 so the fixed defaults ship. Note 1.0.6 was never actually on the registry — `npm view @luxfi/bridge` is a hard 404 with no versions, while @luxfi/ui resolves fine from the same scope, so this is a first publish rather than a re-publish. Tests pin both defaults and assert the overrides still win. They fail on /ext and pass on /v1. Full suite: 11 files, 94 tests. Co-authored-by: Hanzo Dev <[email protected]>