COINOTAG News reported on **May 8th** that cybersecurity firm **SlowMist** has issued a warning about potential risks associated with the **Ethereum Pectra upgrade**. Users must prioritize **private key protection**, as contract codes may vary across different chains, even if they share the same address. It is crucial to thoroughly understand the intricacies of delegated targets before proceeding with any transactions.
Wallet providers are urged to verify that the delegated chain aligns with the current network. Users should be informed about the potential dangers of using a **delegation signature** with **chainID 0**, which poses a risk of replay attacks on alternate chains. To minimize phishing threats, it’s advisable to display the target contract when users sign a delegation.
Developers must implement stringent **permission checks** during wallet initialization, ensuring verification of the signature address via **ecrecover**. Adopting the **namespace formula** outlined in ERC-7201 can help prevent storage collisions. Additionally, it’s important to remember that **tx.origin** may not always represent an externally owned account (EOA), making the use of **msg.sender == tx.origin** ineffective against **reentrancy attacks**. Ensuring that delegated target contracts have the necessary callback functions is vital for compatibility with mainstream tokens.
Centralized exchanges should diligently monitor deposits to mitigate the risks associated with false deposits emanating from smart contracts.