This avoids people leveraging the token list from having to match symbols/names against eachother, which is a fairly perilous process with the larger token lists. Any suggestions here would be greatly appreciated.
It's recommended to use the schema outlined here that utilizes the extensions field. You can use this package to automatically add the mappings to your existing token lists.
Token lists are currently geared towards one-chain-per-token, and lead to workarounds such as Optimism's:
Rather than doing this, I'd like to propose an update to the format along the following structure:
This avoids people leveraging the token list from having to match symbols/names against eachother, which is a fairly perilous process with the larger token lists. Any suggestions here would be greatly appreciated.