Attention

Slow Fog: All parties need to pay attention to the new risks brought by the new features after the Ethereum Pectra upgrade

ChainCatcher news, security company Slow Mist stated on platform X that the Ethereum Pectra upgrade (EIP-7702) is now live------this is a significant leap, but the new features also bring new risks. Here are some points that users, wallet providers, developers, and exchanges should pay attention to:For users: Private key protection should always be a top priority; be aware that the same contract address on different chains may not always have the same contract code; understand the details of the delegation target before proceeding with operations.For wallet providers: Check if the delegation chain matches the current network; remind users of the risks associated with delegation signatures that have a chainID of 0, as these signatures may be replayed on different chains; display the target contract when users sign the delegation to reduce the risk of phishing attacks.For developers: Ensure permission checks are performed during wallet initialization (e.g., verify the signature address through Ecrecover); follow the namespace formula proposed in ERC-7201 to mitigate storage conflicts; do not assume Tx.Origin is always an externally owned account (EOA), using Msg.Sender == Tx.Origin as a defense against reentrancy attacks will no longer be effective; ensure that the target contract of user delegation implements the necessary callback functions to ensure compatibility with mainstream tokens.For centralized exchanges (CEXs): Conduct tracking checks on deposits to reduce the risk of false deposits from smart contracts.

Matrixport: Liquidity indicators may not accurately predict BTC trends; attention should be paid to native crypto driving factors or policy impacts

ChainCatcher news, according to Matrixport analysis, the correlation between the rise in global liquidity and the increase in Bitcoin prices has certain limitations. The global liquidity indicator, measured by the total money supply of 28 central banks (in USD terms), although visually correlated with Bitcoin price trends, has its predictive accuracy questioned due to the non-stationarity of the time series and scale differences.The analysis points out that while the growth of money supply may have a lagging effect on the Bitcoin market, this lag time lacks strong theoretical support. Furthermore, although the correlation between Bitcoin and Nasdaq has slightly increased in recent years, it remains below the 60% peak during COVID, indicating that Bitcoin trading is more driven by its own dynamics rather than acting entirely as a proxy asset for tech stocks.Matrixport believes that the broad consolidation of Bitcoin prices may continue, and solely relying on liquidity indicators to predict market trends may not be reliable enough. In contrast, focusing on native driving factors of cryptocurrencies or macro variables with direct policy impacts (such as political leaders supporting cryptocurrencies) may be more valuable. Although market perceptions may have mathematical flaws, their widespread acceptance could still have a tangible impact on market behavior.

Slow Fog Cosine: Users need to pay attention to the permission requests of browser extensions and maintain an isolated mindset

ChainCatcher message, Slow Mist Yuxian posted on platform X stating: "An extension can be malicious, such as stealing cookies from the target page, privacy in localStorage (like account permission information, private key information), DOM tampering, request hijacking, clipboard content retrieval, etc. Relevant permission configurations can be made in manifest.json. If users are not careful about the permissions requested by the extension, it can be troublesome.However, for an extension to be malicious and directly target other extensions, such as well-known wallet extensions, it is still not easy... because of sandbox isolation... For example, it is unlikely to directly steal private key/mnemonic-related information stored in the wallet extension. If you are concerned about the permission risks of a certain extension, it is actually easy to assess this risk. After installing the extension, you can choose not to use it first, check the extension ID, search for the local path on your computer, and find the manifest.json file in the root directory of the extension. You can then directly throw the file content to AI for permission risk interpretation. If you have an isolation mindset, you might consider enabling a separate Chrome Profile for unfamiliar extensions, at least making malicious actions controllable; most extensions do not need to be enabled all the time."
ChainCatcher Building the Web3 world with innovators