SixStar Recovery

A common mistake

Sent tokens to a token contract

A common slip: pasting the token's own contract address as the recipient. The tokens are now held by the token contract itself.

Free check · read-only · no wallet needed to check

Where did the funds go?

Paste the address the funds were sent to, or the transaction hash if that is easier. Your browser reads the public chain live and tells you what is there and who is able to move it.

Not sure which? Open the transfer in your wallet or exchange history and copy either the recipient address or the transaction hash.

Check the address

What the checker does here

A token contract has no private key. Whether the tokens can leave depends on the contract's code: some token contracts expose a function their controller is able to call to move stray tokens; many do not.

The checker reads the balance and probes the contract's standard control surface (owner, admin, proxy slots, Safe owners). With a verified source, the developer page goes further: it looks for a recognised rescue function in the verified ABI and reports whether the live controller is able to call it, or states plainly that no path was found among what it checked.

When a controller exists, the checker prepares a message to the team with the evidence and a link to the developer page, where the team can build and simulate the exact call.

Questions

I sent tokens to the token's own contract. Are they gone?
Not necessarily. It depends on the contract's code and on who controls it. The checker reads both and reports what it found and what it could not determine.
What can the token's team do?
If the verified contract exposes a rescue function its controller is able to call, the team can move the tokens out. The developer page builds and simulates that call for them.