Skip to content
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.

Newly bridged token not present in token selector on NEAR side #193

Open
dafacto opened this issue Apr 6, 2021 · 2 comments
Open

Newly bridged token not present in token selector on NEAR side #193

dafacto opened this issue Apr 6, 2021 · 2 comments

Comments

@dafacto
Copy link

dafacto commented Apr 6, 2021

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.

@paouvrard
Copy link
Member

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)

@paouvrard paouvrard removed their assignment Apr 14, 2021
@paouvrard
Copy link
Member

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants