Where to write
Email the desk at [email protected]. There is no contact form on this site, no chat widget and no support queue. A plain email is easier to answer accurately and it does not require you to hand over anything beyond an address you already control.
What is worth sending
- A correction. If a step is wrong, unsafe as written, or no longer matches how the network or a tool behaves, say which page and which step. If you can point at documentation or a transaction that shows the discrepancy, that is enough for us to act on it quickly.
- A gap. A procedure you had to work out yourself because nothing here covered it. These are the most useful messages the desk receives, and they decide what gets written next.
- An ambiguity. If two people could read a step differently, that is a defect even when the step is technically correct. Tell us which sentence and what you thought it meant.
What the desk cannot do
We cannot recover funds, reverse a transaction, review or endorse a specific product, or tell you whether a particular trading approach is a good idea. Nothing on this site is financial, legal or tax advice, and no message to this address creates a professional relationship of any kind.
Never send a key
Do not send a seed phrase, a private key, a keypair file, an endpoint URL containing an API key, or a screenshot of any of those, to this address or to anyone else. There is no situation in which a publication needs your secrets to answer a question. If you have already shared one somewhere, treat it as public and work through the incident response playbook instead of waiting for a reply.
Response expectations
The desk is small and replies are not immediate. Corrections that affect safety are handled first, and in most cases the page is fixed before the reply is sent, so the fastest way to know a report landed is to reload the page you reported. Requests for individual consulting, guest posts, paid placements or link exchanges are not answered.
Before you write about a failed run
If something has gone wrong and you want a second opinion, the message is far more useful with the transaction signature, the wallet public key involved, the approximate time in UTC, and what the software was configured to do. Public keys and signatures are public data and safe to share. Private keys, keypair files and seed phrases are not, and are never needed to diagnose anything. The fields worth capturing are listed in reading bot logs.