Information first, dates only when verified
Updates should be understood through the real network context rather than through labels shown in an interface. Check the network, account or contract involved before acting.
For updates, review what the request changes on-chain, which permissions it asks for, and whether the address or contract matches the task you intended to perform.
Current notice categories
Wallet usage path
A clearer route across creation, backup, network selection and transaction review
Gas and confirmation review
Check the transaction hash and network conditions before repeating a pending action
Signature and approval awareness
Connections do not make later signature or approval requests automatically trustworthy
Self-service support checks
Review network, contract and transaction details without sending sensitive credentials
What is not implied by an update
Use transaction hashes and the appropriate block explorer to verify public on-chain facts. A local interface can summarize status, but the underlying network record is the reference for confirmations and outcomes.
Protect seed phrases and private keys offline, never send them to support staff or third parties, and treat unfamiliar signatures, approvals, remote-control requests and rushed instructions as reasons to stop and verify.
How to use a notice safely
- Verify the network and transaction independently when an action affects assets.
- Do not provide seed phrases, private keys or verification codes in response to an announcement.
- Use the support section for structured troubleshooting.