[ Thread 05 · read-only ]

“Explorer links: how to ask a useful question”

by goodpost_guide 2026-03-30 18 replies 1990 views
Troubleshooting Public data Etiquette
Original post

A lot of wallet questions get no useful reply because they leave out the basic facts. This thread is a checklist for asking a question that someone can actually answer.

Section 1

Include in every troubleshooting post

  • Network name (be specific: Ethereum mainnet, Arbitrum One, Polygon, BSC, Tron, Bitcoin, Litecoin, Aptos, etc).
  • Transaction hash, when one exists.
  • A public explorer link to that hash. Pick the explorer that matches the network.
  • Approximate time and timezone.
  • What you expected to happen and what actually happened, in plain language.
Section 2

Never include

  • Seed phrase, private key, wallet password, 2FA backup code, KYC documents, wallet file, screen-share access.
Section 3

Why this works

  • Public data lets anyone independently verify the situation without asking for trust.
  • It removes the social-engineering surface where a stranger asks for “just one more detail” that turns out to be a secret.
  • It usually narrows the answer down quickly: network mismatch, pending fee issue, approval scope, bridge timing, address format and so on.