Write a Useful Wallet Error Report Without Exposing Secrets
A useful error report lets someone understand a failure without gaining control of your account. Start with a small text description and add only the evidence needed to distinguish the problem.
Describe a reproducible observation
Record the page path, approximate UTC time, browser family and the visible control used. State what you expected and what appeared instead. For example: “On the public quote page, the estimate stayed unavailable after the displayed timeout.” Say whether this happened once or repeatedly, without inventing a frequency. Avoid reproducing a financial action merely to make a report more complete; describe the sequence already observed.
Separate public context from private data
A chain name, decimal chain ID and sanitized error code can often explain a mismatch. A public address or transaction hash may help a specific investigation, but sharing either can link your identity to public activity. Consider whether a report needs those details and whether the destination is public. Recovery phrases, private keys, wallet export files and passwords never belong in an issue report. Do not include account-access material to demonstrate ownership.
Review attachments before sending
Prefer a manually transcribed error over a full network capture. Provider URLs can contain access tokens, and raw request logs can include session headers or signed payloads. Crop screenshots to the relevant message and inspect tabs, notifications, QR codes and surrounding account details. Replacing only one visible secret in an otherwise complete export is not a reliable sanitization method. Keep original diagnostic files private rather than publishing them alongside a summary.
Choose an independently verified destination
Open a reporting channel from a source you already trust instead of replying to an unsolicited helper. This page does not establish an official RunixCoin support address or promise account recovery. If the report concerns this interface, identify the public estimate form separately from wallet connection, approvals and transaction inclusion. Mark anything you did not verify as unknown. A concise report can support diagnosis without anyone asking you to sign a proof, fund an account or reveal recovery information.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.