The app asks for a chain by name in the path, and only the explorer had a route
per chain — so that request went straight to the raw rows. Its token list named
bridged ether LETH beside a token page calling the same contract ETH, and Zoo's
own coin introduced itself as Wrapped LUX, because only one of those two paths
came through the service that knows what a token is.
exchange-api serves the same shape now and dresses what it forwards with the
registry for the chain in the path rather than the one it is pinned to. That is
the part the explorer cannot do: Lux and Zoo share contract addresses, so the
address alone cannot say which coin is meant and the path is what does.
Co-authored-by: Hanzo Dev <[email protected]>
zeekayandHanzo Dev
032f888d1e