The StakingFactory contract deploys new proxy instances of the StakingBase implementation using create2() in the createStakingInstance() function. The salt used for create2() is based on block.chainid and a nonce value. However, it does not include msg.sender.
In the case of a reorg, a users transaction to stake a service may end up depositing to a proxy contract deployed at the same address but by a different user, with potentially very different staking parameters.
Consider including msg.sender in the salt used for create2() to ensure each users deployed proxy is unique to them, even in the case of a reorg.
