Email the desk
Editorial enquiries, corrections and reports: [email protected]
Please include the page address (the URL), what you believe is incorrect or unclear, and — for factual corrections — a link to the official documentation that shows the correct position. Corrections that cite a source are the quickest to act on, and the desk aims to reply within five working days.
What this desk can help with
| Enquiry | What to send | What happens next |
|---|---|---|
| A factual correction | Page URL, the sentence, the correct position, and the official source | The page is corrected and its review date updated |
| An out-of-date figure | Page URL and the current value from official documentation | The page is re-verified against the source and updated |
| A broken or incorrect link | Page URL and the link text | The link is fixed or replaced |
| An accessibility problem | Page URL, the device and browser, and what did not work | The issue is investigated and fixed where possible |
| A topic request | What you were trying to do and where you got stuck | Recurring requests become new or expanded pages |
| Reporting a site impersonating this one | The domain and a screenshot if you have one | We investigate and report it to the relevant registrar and platform |
| A privacy question about this site | Your question | Answered directly; see the privacy policy first |
What this desk cannot help with
This is an independent documentation site. It has no access to any wallet, account, device, exchange or service, and it cannot intervene in anything on a blockchain.
- Wallet access or recovery. We cannot unlock a device, restore an account, or help with a lost recovery phrase. Nobody legitimate can restore an account without the recovery phrase — treat any service promising otherwise as a fraud.
- Transaction problems. We cannot cancel, reverse, speed up or trace a transaction. Confirmed blockchain transactions are permanent.
- Software support for the application itself. Installation failures, crashes and device-detection problems are covered in the troubleshooting library; anything beyond that belongs with the developer's official support channel, reached by typing the developer's domain yourself.
- Hardware faults and warranty. Contact the vendor or the reseller you bought the device from.
- Financial, tax or legal advice. We do not provide it, and nothing on this site should be read as advice.
We will never ask for your Secret Recovery Phrase, your recovery words, your private keys, your PIN or any password. We will never ask you to send funds to an address, to install remote-access software, or to "verify" a wallet. If a message claiming to come from this site asks for any of those things, it is not from us — report it to the address above and do not reply to it.
Why there is no contact form
This site deliberately contains no forms, no accounts and no upload fields. Two reasons:
- Nothing to leak. A form that collects messages also collects names, addresses and whatever else a reader types into it. Not having one means there is nothing to lose, nothing to secure and nothing to sell.
- Nothing to imitate. Fake support forms are a standard phishing technique — a page that looks like a help desk, asks for a problem description, and then asks for recovery words "to investigate". By not having a form at all, this site cannot be imitated in that particular way, and readers can verify that instantly.
Email is the only channel, and it is the same address on every page.
Reporting impersonation
Wallet-related domains are frequently cloned, and clones of an independent guide are no exception. If you find a site that copies this publication's text or design while operating from a different domain — particularly if it offers downloads, "verification" or support — please send:
- the domain name,
- a screenshot or the page URL,
- and, if the site asks for wallet credentials, a note of exactly what it requests.
Reports about sites that ask for recovery phrases are treated as a priority, because that is the point at which imitation becomes a direct risk to readers.