When a proposer is running, it will have a list of tokenIDs to stateIDs indicating where transaction fees are sent. However, if a new token is registered while it is running, it will not be able to handle that token until a new state leaf is added on L1 and its config is updated.
This proposer feature should be hidden behind a configuration flag in case a node operator does not want to automatically update their token list and wishes to do so manually.
What's wrong
When a proposer is running, it will have a list of tokenIDs to stateIDs indicating where transaction fees are sent. However, if a new token is registered while it is running, it will not be able to handle that token until a new state leaf is added on L1 and its config is updated.
How can we fix it?
Have proposers listen for the
TokenRegistry'sRegisteredTokenevent (https://github.com/thehubbleproject/hubble-contracts/blob/master/contracts/TokenRegistry.sol#L75) and have the proposer deposit a new state leaf for that tokenID. The proposer should then update its internal configuration with the new fee receiver.This proposer feature should be hidden behind a configuration flag in case a node operator does not want to automatically update their token list and wishes to do so manually.