Epic: Reduce Warp UI tech debt

[jmrossy]

Patterns 5 points of complexity with lots of branching:

• Balance checking
• IGP quoting
• Input validation
• Transfer crafting
• Adapter Factory

Rossy's Questions:

• VMs: Are there new protocols that will not fit in the EVM, Solana, Cosmos buckets? e.g. adjacent to EVM like zkSync or Move or Fuel
• ISM: Changes to gas: native chain token(s), token(s) for IGP, token you're transferring, token you're receiving (wrapping)
• Warp Ui needs to understand which token is collateral vs synthetic in the context of multi-collateral

Architecture & Design Schedule meeting with Nam, Rossy, Yorke, Avi, Paul to discuss

• [x] Make warp UI resilient to RPC failures during init (whole app fails)
• [ ] Refactor balance checking to be more flexible
• [ ] Refactor AdapterFactory to be smarter
• [ ] Handle IBC nuances at Adapter layer
• [ ] Handle Cosmos naked vs wasm divide better
• [ ] Migrate logic from 4 pain points above in to adapters
• [ ] Consider moving some IGP determination logic into the adapters
• [ ] Consider removing NFT support (it's evm-only and maybe broken anyway)
• [ ] Consider refactor of Route model

Diagram: https://docs.google.com/drawings/d/1eeOlLwfHQtcJ1b2gSYkyWvXf3vZz6QmrJxOVa5nrC1Q/edit?usp=sharing

Completed

• [x] Refactor IGP related code: https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/pull/98
• [x] Add support for async form validation

  
  ### Tasks

• [ ] https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/116
• [ ] https://github.com/hyperlane-xyz/issues/issues/956
• [ ] https://github.com/hyperlane-xyz/hyperlane-warp-ui-template/issues/129
• [ ] https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/3259

[avious00]

@jmrossy is the Warp UI tech debt design conversation tied to the SDK boundary convo here https://github.com/hyperlane-xyz/issues/issues/916 or can happen first independently?

[jmrossy]

@avious00 independently. They're only relation is that they both may involve SDK changes but in pretty different ways

[avious00]

@jmrossy should we put the architecture diagram SVG in the monorepo's typescript readme + the protocol section of our docs?

[jmrossy]

@avious00 I don't recommend putting it in the docs, it wouldn't be that useful for someone not actually working on these packages I think.

As for the monorepo and/or warp UI, I'm open to it. I haven't forgotten about it. I'm just waiting because the Warp Core works is going to shake things up. I'll need to update the diagram when things settle.