Product updates
Product updates explain changes in wallet entry points, asset display, network management, and task flows. When reading a notice, distinguish interface changes from blockchain rules: a new screen arrangement does not mean transaction confirmation, gas, or contract behavior has changed.
If an update concerns installation or downloading, use the site-wide download entry. Wallet creation and recovery information belongs only in a trusted wallet environment; the website content does not ask you to enter a seed phrase, private key, recovery phrase, or verification code.
Asset viewing, transaction history, and network selection are organized around tasks so checks happen before sending or connecting.
Getting-started, network, Web3, and security content is connected in a practical learning order.
Network notices
Network notices focus on network selection, gas, confirmations, Layer 2, and cross-layer flows. Networks can share familiar address formats while retaining different chain IDs, gas assets, block histories, and contract deployments, so verify the active network before sending or using a DApp.
If confirmation is taking longer than expected, inspect the transaction hash before sending again. Cross-layer movement also requires separating source-network confirmation from destination-network availability.
Security notices
Security notices cover seed phrases, private keys, DApp approvals, lookalike domains, malicious signatures, and device conditions. Official personnel will not ask for a seed phrase, private key, or verification code; stop any request that asks you to provide them through a web form, chat, or remote-control tool.
Review each signature and approval independently. Connecting a wallet does not make later requests automatically acceptable, and token approvals should be checked for spender and allowance. Review permissions you no longer need and revoke them when appropriate.
Service notices
Service notices explain FAQ, support, download maintenance, and content availability without countdowns, artificial scarcity, or unverified institutional claims. For a transaction issue, start with information that can safely be checked, such as the network name, public address, and transaction hash.
Support does not require a seed phrase or private key. Confirmed on-chain transactions usually cannot be reversed unilaterally by a wallet, so support focuses on diagnosing network, transaction-state, approval, and device issues rather than promising to alter a confirmed result.