Add Bridging page and Bridging UI

[dib542]

New Bridging page design so far:

Bridging modals are in:

• https://github.com/duality-labs/duality-web-app/issues/360

[dib542]

Potential CORS issues:

The current solution requires the web app to send IBC transfer requests directly to the FROM chain (as that is where the tokens will come from). When bridging to Duality that means querying an external chain and we cannot guarantee that an external chain node will allow a CORS request from our web app site to it. This poses an issue about how to reliably message or query the external chain.

We need to:

• request an IBC transfer to start from an external chain

We would like to:

• request the bank balances of an external account on an external chain

Solutions:

• create light server HTTP proxies:
  • we could add this as a container in our environments setup: route eg. cosmos-hub-1.dev.duality.xyz to light client proxy
  • the proxy would have a primary node it would connect to which we control
  • docs: https://docs.cometbft.com/v0.37/core/light-client#running-a-light-client-as-an-http-proxy-server
  • see docker images: https://hub.docker.com/r/cometbft/cometbft/tags/
• we could run our own full nodes for each connected chain: route eg. cosmos-hub-1.dev.duality.xyz to our full node
  • costly
• without full control over outcomes
  • use Keplr/wallet extensions
  • extension background pages can get around CORS issues, so Keplr has the ability to query and message any chain
  • I don't think each wallet will expose these endpoints or this information
  • we could create a whitelist of IBC connected chain nodes (which are not under our direct control and they may change CORS settings)
  • we could assume at least one node out of the Chain Registry apis.rest list will return a Access-Control-Allow-Headers: * header which allow us to query the node directly (and get a response). We can set up a process to test the endpoints in series (or batches of series) or all at once to determine the node that responds the quickest, either at the point in time that the data is needed or a slower test (one by one) could be done before the data is needed
  • do any validators provide this as a paid service?
  • we could assume no CORS errors will come from any node we try to connect to

[dib542]

May need to get fee data from

• https://github.com/cosmos/ibc-go/blob/main/proto/ibc/applications/fee/v1/query.proto
• https://lcd.dev.duality.xyz/ibc/apps/router/v1/params
• https://lcd.dev.duality.xyz/ibc/apps/fee/v1/fee_enabled