The protocol supports tokens with multiple addresses, as stated in the README. When executing messages, balance tracking is initiated for new token deployments on destination chains. However, the current implementation fails to account for tokens with multiple addresses.
The start_token_balance function only checks if a token is already registered using a single address:
This allows different balance tracking logic to be applied for the same token using its multiple addresses, potentially resetting tracked balances.
Accurate balance tracking becomes impossible for multi-address tokens, as new balances can be initiated for each address, effectively resetting the tracked balance for the token.
Consider not supporting tokens with multiple addresses, or implement a mechanism to link all addresses of a token to a single balance tracking entry which seems impossible since some of these tokens are upgradeable.
