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
{{ message }}
This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
For circumstances where users are transferring ERC20 tokens where the source chain is that ERC20 token's native chain, the UI should:
accept/detect native currency on that chain
invoke the right smart contract to convert that native currency into wrapped assets
deposit that wrapped asset into the one-time deposit address
Example:
User wants to send WAVAX from Avalanche to Ethereum. We should detect native AVAX, convert it, then deposit it.
Counter-example:
User wants to send Axelar-wrapped WAVAX from Ethereum back to Avalanche. We should just tell the user they need to source Axelar-wrapped WAVAX on ethereum, comparable to what we currently do for our other supported assets (e.g. Axelar-wrapped UST on Ethereumm, etc).
Current Behaviour
Expected Behaviour
Steps to reproduce (for bugs)
Relevant Logs or Files
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description/Reasoning
For circumstances where users are transferring ERC20 tokens where the source chain is that ERC20 token's native chain, the UI should:
Example:
Counter-example:
Current Behaviour
Expected Behaviour
Steps to reproduce (for bugs)
Relevant Logs or Files
The text was updated successfully, but these errors were encountered: