zeekayandHanzo Dev a5a691e31b Our nodes serve /v1/, so ask them for /v1/ ...

luxd registers /v1/ and nothing else; api.lux.network, api.zoo.ngo,
api.hanzo.network, api.pars.network and api.osage.network all answer 200 on
/v1/bc/C/rpc and 404 on /ext/bc/C/rpc. Every /ext/ path aimed at one of our
hosts was a request that could only fail.

/ext/ is Avalanche's prefix. Endpoints on api.avax.network keep it — they are
someone else's convention and a real bridge corridor depends on them.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-29 10:45:22 -07:00

..

src

Our nodes serve /v1/, so ask them for /v1/

2026-08-29 10:45:22 -07:00

package.json

feat(pkg/bridge): add @luxfi/bridge SDK + publish workflow

2026-05-21 14:02:03 -07:00

tsconfig.json

server and new-bridge are using types only from @luxfi/core

2024-12-24 18:33:13 -08:00