[Bug] QueryFunTokenMapping Returns Invalid erc20Addr - Non-Hex, Non-ETH Address #392
Labels
prio: p0 (critical)
critical/urgent priority
S-triage
Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
With QueryFunTokenMapping, the resulting erc20Addr ends up being a non hex, non eth addr
Example:
This is more difficult to trace back since we just perform a request and decode the result
Although, we can note that FunToken in ts Proto has erc20Addr as string as well
The text was updated successfully, but these errors were encountered: