Share Useful Wallet Troubleshooting Details Carefully

A useful problem report explains what happened and where to look. It does not need your wallet recovery material, passwords or a complete export of browser and wallet data.

Start with symptoms rather than a data dump

Write the page or feature you used, the network shown, the approximate time and the exact visible error message after checking it for sensitive information. Explain what you expected and what appeared instead. For example, “the Base native-balance row remained unavailable” is more precise than “my wallet broke.” You can initially omit a full address until you decide whether a public lookup is necessary.

Decide what a public identifier reveals

A public address or transaction hash can make an on-chain issue reproducible, but sharing it links your report to visible financial activity. Send only the identifiers relevant to the issue and consider who will see them. A shortened address can distinguish entries in a discussion but cannot support an exact account lookup. Do not claim that redaction makes a report anonymous if its other details identify the transaction.

Exclude material that grants access

Never include recovery phrases, private keys, passwords, authentication codes or wallet backup files. Inspect screenshots for unrelated accounts and recovery screens before sharing them. Avoid exporting local storage, complete request headers or browser profiles as a troubleshooting shortcut; these can include sensitive material. A public-address question should not require importing your wallet into a form supplied by someone responding to the report.

Keep a quote problem separate from a transaction claim

For a RunixCoin quote issue, record the WETH amount format and visible quote status, not a signing key or approval. A timeout does not supply a transaction hash. If the issue concerns a transaction from another workflow, identify that workflow and network explicitly. RunixCoin’s public form reports unavailable execution, so do not describe an estimate as a failed completed swap. This guide does not establish a support channel or invite sending information to an unverified contact.

References and verification

Reviewed 10 November 2026. Product details reflect inspected interface code; camera scanning, browser behavior and mainnet execution were not verified.