mirror of
https://github.com/luxfi/bridge.git
synced 2026-09-24 00:26:46 +00:00
zeekay
1db09c1f72
BRIDGE_API_HOST fell back to https://bridge-api.lux.network. That is a different server — the older Express backend — and it serves a different set of networks. So an unset environment variable moved every user onto another backend, silently. Measured rather than assumed. bridge-api offers 22 networks, this origin offers 13, and the nine extra are not nine extra capabilities: Celo, Zora, Blast, Linea real teleporter and vault. Genuinely missing from this origin's config. Gnosis, Fantom, Aurora teleporter and vault are EMPTY STRINGS. Offered to users and cannot bridge. Cardano, Polkadot no contract entry at all. Three of those nine are the Arbitrum bug again: a chain a user can select, send funds to, and then discover has nowhere to go. A default is not the place to change which backend answers. Same origin is the one answer that cannot be wrong — whatever serves the page serves its API — and it removes the whole class rather than correcting the hostname. The end state is neither server. B-Chain is the bridge, and the SDK already has BridgeConfig.rpc to reach it. Today B-Chain answers a canned stub — identical bytes for a real method, a nonsense method, or an empty body — so it is not yet somewhere to point. The comment says that instead of implying the switch is available. Still to do, and not done here: the four real networks belong in this origin's config, and the three fictional ones should stop being advertised anywhere.