Product and service notices
Information without invented dates
The updates center uses descriptive labels such as Recent Update, Product Notice, Security Notice and Service Notice when no verified publication date is available. This avoids creating a false timeline while still giving users a clear way to understand what kind of change or reminder they are reading.
Updates focus on wallet behavior, network conditions, security reminders and service explanations. They do not claim funding rounds, partnerships, licenses, rankings, user counts or trading volumes that have not been confirmed.
- Use descriptive notice labels when dates are not verified
- Keep operational details separate from promotional claims
- Verify network and security notices before acting
Network and security reminders
Changes that can affect an operation
A network notice should help a user understand what to re-check before sending, signing or bridging: active network, gas conditions, transaction status and any third-party service dependency. It should not create urgency for its own sake.
A security notice should focus on observable behavior such as lookalike domains, requests for seed phrases, suspicious approvals or remote-control prompts. The goal is to improve decision quality, not to cause panic.
- Re-check network names and addresses
- Do not enter recovery information into websites
- Review approvals after suspicious interactions
Product explanations
Explain behavior, not hidden download targets
Product notices can explain changes in navigation, wallet flows or educational material, but they should not expose the final mobile download target or device-detection implementation. All download calls to action remain routed through /download.html.
When a product behavior changes, the notice should explain what the user can observe and what they should verify, without describing internal implementation details that do not help safe use.
- Keep download entry points consistent
- Describe user-visible behavior clearly
- Avoid internal implementation details in visitor-facing copy
How to read an update
Separate facts, guidance and risk
Treat each update as context for a decision rather than as a command to act immediately. Check whether the notice concerns a wallet feature, a network condition, a security issue or a service limitation, and then follow the relevant verification path.
If an update refers to staking or validators, remember that rewards, waiting periods and network penalties can change. If it refers to a DApp, review the domain, signature and approval scope again before interacting.
- Identify the category of the update
- Verify the affected network or service
- Re-check signatures and approvals before action