You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Core are introducing an Arbitrum bridge with an Axelar connector so that users can bridge assets from multiple chains easily to Vega and avoid Ethereum gas fees.
The expectation is that Console will support deposits via a component called Squid Router. This epic is to work out how and where to integrate this component into the deposit flow.
Tasks
Define high level requirements
Create basic mockups
Update "API Requirements" in core spec
Update "User-Interface Spec" in relevant front end repo
Create detailed user stories using normal template
High Level Requirements
Support deposit of Arbitrum USDT via Squid Router
Support deposit of Ethereum USDT via Squid Router
Support the legacy route via legacy form if desired
Rework the standalone deposit screen to become the new "Portfolio" screen including these new functions
Rework the sidebar to support all new functions and streamline the UX on the trading screen
Core Feature
Core are introducing an Arbitrum bridge with an Axelar connector so that users can bridge assets from multiple chains easily to Vega and avoid Ethereum gas fees.
The expectation is that Console will support deposits via a component called Squid Router. This epic is to work out how and where to integrate this component into the deposit flow.
Tasks
High Level Requirements
Linked User Stories
Basic Mockups
High level diagram of bridge architecture
Squid Route App (OOTB)
UX WIP
See "Asset management redesign" on https://miro.com/app/board/uXjVOs_PBKk=/
Link to API Requirements in Core spec
https://www.squidrouter.com/
Link to User Interface Specs
The text was updated successfully, but these errors were encountered: