Submitted by 0xDemon, also found by Mike_Bello90
https://github.com/code-423n4/2025-03-nudgexyz/blob/88797c79ac706ed164cc1b30a8556b6073511929/src/campaign/NudgeCampaign.sol#L206
https://github.com/code-423n4/2025-03-nudgexyz/blob/88797c79ac706ed164cc1b30a8556b6073511929/src/campaign/NudgeCampaign.sol#L271-L274
https://github.com/code-423n4/2025-03-nudgexyz/blob/88797c79ac706ed164cc1b30a8556b6073511929/src/campaign/NudgePointsCampaigns.sol#L160
Users with account abstraction wallets have a different address across different chains for same account, so if user using an account abstraction wallet initiate reallocate cross-chain token, the toToken will be sent to wrong address and lost permanently. 
With 6.4 million users and 100+ billion assets, there is very high risk that safe wallet users will try to initiate cross-chain reallocations and suffering a loss
In addition, there are other impacts, the user cannot claim rewards on the destination chain and the rewards for that user end up being locked forever in the NugeCampaign.sol contract because no one cant rescue the reward token even with rescueTokens() and withdrawRewards() functions.
Based on the Nudge docs and Lifi SDK, the user flow for cross-chain reallocation is seen below:
Lets breakdown how users can loss all reallocated cross-chain tokens and the rewards:
It can be seen in step 5, toToken amount or in this example is 200_000 USDC will be transferred to userAddress. The main problem arises here, because as explained the abstraction wallet account has a different address across chains. Thus, the toToken amount will be transferred to the address at userAddress which may not be the address owned by Alice and Alice will lose all reallocated tokens.
And also keep in mind, on current implementation on the Nudge website, there is no option for users to enter the recipient address on the destination chain when performing cross-chain reallocations. Not even in the existing docs. This proves that the Nudge protocol is not aware of this issue.
User can claim rewards by calling claimRewards(). One of the checks in this function is whether msg.sender is the same as the userAddress in the participation struct:
The main problem arises here, because as explained the abstraction wallet account has a different address across chain. This means Alice cannot claim her reward on the Base chain because the address it has on the Base chain (as msg.sender) is different from the address on ethereum mainnet chain (as participation.userAddress).
Give the user the option to pass in the address. The tokens should be transferred on the destination chain. Pass in the warning for account abstraction wallet holders to not to pass the same wallet address when initiate cross-chain reallocations.
raphael (Nudge.xyz) confirmed
