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 Sep 27, 2023. It is now read-only.
After bridging the BAL token for the first time, I wanted to transfer back to Ethereum from NEAR. However, the BAL token did not appear in the token list. I'm creating this issue as a placeholder, because I'm not sure yet what's the best solution. Pasting the contract address into the token selector works, but I wouldn't think to paste an Ethereum contract address in the NEAR token selector window.
The text was updated successfully, but these errors were encountered:
Released v3.4.3
If the user didn't first transfer to NEAR which would have recorded the custom token at that time, then the user still has to input the Ethereum address of the token (inputing the nToken address not suported)
If the user doesn't input the original erc20 address, the frontend can handle that and convert it. This can be done offline since the bridged nep141 address contains the erc20 address, or via on-chain query. #86
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After bridging the BAL token for the first time, I wanted to transfer back to Ethereum from NEAR. However, the BAL token did not appear in the token list. I'm creating this issue as a placeholder, because I'm not sure yet what's the best solution. Pasting the contract address into the token selector works, but I wouldn't think to paste an Ethereum contract address in the NEAR token selector window.
The text was updated successfully, but these errors were encountered: