Send a Correction

The address

Write to [email protected]. There is no contact form on this site, no newsletter, no chat widget and no other channel operated by the desk. Any account, group or profile claiming to be Trace Rack elsewhere is not connected to this site, and the desk will never contact anyone first asking for keys, funds, credentials or personal details.

Sending a correction

Corrections are the most valuable message the desk receives, and the useful ones share a shape. Name the page, quote the exact sentence you think is wrong, and state what the record or the documentation actually shows. Where a protocol behaviour is at issue, a link to the documentation settles it faster than an explanation. Where arithmetic is at issue, showing the recomputed figure is enough.

• The page URL and the sentence you are challenging, quoted.
• What you believe the correct statement is.
• The source: documentation, a protocol constant, or a reproducible query.
• Whether the error changes the conclusion of the page or only a detail.

A correction that changes what a page claims is made in the text rather than patched quietly, and the desk would rather say plainly that an earlier version was wrong than present a fix as though nothing had happened. You will not be credited by name unless you ask to be, and the desk does not publish correspondence.

Method questions

Questions about how a procedure works, why a signal carries the weight it does, or where a limit comes from are welcome and may end up shaping a future page. Questions that amount to "please run this for me" are not, even when they are phrased as method questions, because the answer would be a piece of tracing work.

What the desk will not do

Some requests arrive regularly and all of them get the same answer. The desk does not identify who controls an address, does not investigate a specific wallet, token or project, does not produce reports for clients, does not maintain or share address lists, and does not comment on whether a named product or project is trustworthy.

The reasoning is on the casework page and it is not a matter of capacity. Identifying a person from public ledger data means combining datasets in ways that misfire onto uninvolved people, and a wrong answer in that direction cannot be taken back by whoever it lands on. The methods published here stop short of that line deliberately, and the desk does not do privately what it declines to publish.

If you have lost funds

This desk cannot help recover anything and cannot tell you where your funds went beyond what the guides here would let you establish yourself. Confirmed transactions on Solana are final: there is no reversal, no chargeback and no support channel that can undo one. Anybody who contacts you offering recovery in exchange for a fee, a seed phrase, a private key or a wallet connection is running a second fraud on top of the first.

What you can do without help is preserve evidence. Record the transaction signatures, the addresses involved and the times in UTC, before anything else. That record is what any legitimate process would need, and it does not expire.

Press and republication

Short quotations with a link back are fine and no permission is needed. Please do not republish a page in full, and please do not present material from this site as an assessment of any named wallet, token or project, since no page here contains one. If you are quoting a limit or a refusal, quote it with the reasoning attached, because those two are the part most often stripped in retelling.

Response times

The desk is small and messages are read in batches, so a reply may take a while and routine questions already answered on a page may not get an individual response. Corrections are prioritised over everything else. Messages requesting tracing work, address identification or a verdict on a project are not answered individually, and the policy is not personal.