Submitted by ronnyx2017
There is a check in the TapTokenReceiver._claimTwpTapRewardsReceiver to ensure the claimed types amount is equal to the token types amount of sendParam.
The process of cross-chain claim is as follows:
The B chain is the main chain, which the twTap is deployed. And the user is on the chain A.
The issue is that, if after step 1 the LZ message sent, a new reward token is added to the twTAP on the chain B, then step 2 will be revert in the TapTokenReceiver._claimTwpTapRewardsReceiver function. So this message will be stuck in the LZ indefinitely.
Every LZ message sent by TapToken.sendPacket can carry cross-chain TAP tokens, which means the amountToSendLD of the message is not zero. It will burn the TAP token of the source chain and mint them on the target chain. If the message is stuck, these TAP token will be lost forever.
Context
0xWeiss (Tapioca) disputed
Note: For full discussion, see here.
