Reclaim unclaimed SUI links from your wallet’s pending link history by selecting “Reclaim” and confirming the transaction.

Recover unclaimed SUI links from your wallet’s pending history—just tap “Reclaim” and confirm, simple as ABC.

Reclaim unclaimed SUI links from your wallet’s pending link history by selecting “Reclaim” and confirming the transaction.

If you’ve sent out a SUI link and want to reclaim the funds, you can do so as long as the recipient has not yet claimed it. A SUI link works like a temporary object holding your tokens, and until someone redeems it, you still control the funds. To reclaim it, you just need to open your wallet that created the link, locate the unclaimed link in the “Sent” or “Transactions” section, and choose the option to reclaim or cancel. Once you do this, the SUI is returned directly to your wallet balance. If the link has already been claimed by someone else, you can’t reverse it.

Here’s a typical transaction block to reclaim an unclaimed link:

sui client call \
  --package <SUI_LINK_PACKAGE_ID> \
  --module sui_link \
  --function reclaim \
  --args <LINK_OBJECT_ID> <YOUR_WALLET_ADDRESS> \
  --gas-budget 10000

In this block, <SUI_LINK_PACKAGE_ID> is the package ID of the Sui Link contract, <LINK_OBJECT_ID> is the unique identifier of the link object you sent, and <YOUR_WALLET_ADDRESS> is where the SUI will return.

You should always double-check if the link shows as “unclaimed” in your wallet before running a reclaim, otherwise the transaction won’t succeed.

How to Reclaim a Sent SUI Link

I’m trying to understand this aspect of the Sui Network because I’m either building, debugging, or deploying something that touches this area. I want a detailed explanation of how this mechanism or feature works, along with relevant CLI usage, Move code structure, or architectural concepts. My goal is to gain enough clarity to apply this knowledge in a real project—whether that’s a wallet integration, an NFT system, or a DeFi tool. The Sui Network has unique features compared to EVM chains, so I’m particularly interested in what sets it apart and how that affects development best practices. It would help to have sample code, command line examples, or typical errors to watch for, especially when using the Sui CLI, SDK, or deploying on localnet/testnet. Ultimately, I want to avoid common mistakes, follow the best security principles, and ensure that the functionality I’m working on behaves as expected under realistic conditions.

🔹 What a SUI Link Actually Is

On Sui, a SUI link is basically a transfer object (a coin packaged into a URL) that lets you send tokens without needing the recipient’s address. The link encodes:

• The coin object ID (the SUI you’re sending).
• Transfer metadata (how much, who can claim it).
• A one-time claim authority.

Until the recipient clicks the link and “claims” the SUI, you can still reclaim it, since the coin hasn’t yet left your ownership in the global object store.

🔹 How to Reclaim a SUI Link

If the recipient hasn’t claimed the link yet:

1. Using Wallet UI (easiest):

   • Open your wallet (e.g., Sui Wallet, Ethos, Suiet).
   • Navigate to History → Links Sent.
   • There’s usually a “Reclaim” or “Cancel” option.
   • Confirm the reclaim transaction (this reverts the coin back to your wallet).

2. Using Sui CLI (manual way):

   • First, list objects to find the coin that was wrapped in the link:

     sui client objects --owner <your-address>
     

   • If the object is still in your ownership but marked as “transferable,” you can reclaim by executing a cancel transaction.

   • In some wallets, reclaim is implemented as a call to a Move module function that resets the transfer authority.

🔹 Important Edge Cases

• If the recipient has already claimed the link → You cannot reclaim; it’s already transferred.
• If you delete the link but don’t reclaim → The coin is still in limbo until claimed or reclaimed, meaning funds are temporarily inaccessible.
• Multiple attempts to reclaim → Only the first reclaim works; others fail with object already consumed errors.

🔹 Best Practices

• Always reclaim unclaimed links quickly if you realize you sent it to the wrong person.
• For dApps: implement a timeout mechanism (e.g., links expire in 24h, after which the sender auto-reclaims).
• Log both the link ID and coin object ID in your app so you can trace coins on-chain if needed.

You need to go to your transaction history. There, you'll find the option to reclaim your sent SUI.

To reclaim SUI from a sent link, you must first cancel the claimable link if it hasn't been claimed by the recipient. Use the original platform or service (e.g., Sui Wallet, Slush) that generated the link to revoke it—this typically requires signing a transaction to invalidate the pending transfer. If the link remains unclaimed, the SUI will return to your wallet automatically after the expiration period set during creation. Always check the link’s status via the issuing platform’s dashboard or transaction history to confirm revocation success.

You can’t reclaim a sent SUI link—it’s now controlled by the recipient.

If You Sent to Yourself:

• The link is already in your wallet (check hidden/spam).

If Sent to Someone Else:

• Ask them to return it manually.

If Lost/Stolen:

• Funds are irrecoverable (like cash).

Prevention:
✔ Always double-check addresses before sending.

(SUI links are transfers, not revocable requests.)

If you sent SUI to someone via a link, you can't just reclaim it on your own. That link gives the recipient control to claim those funds.

Your best move is to ask the recipient to send the SUI back to you. If it was a mistake and they're honest, they might do it. If you sent it to the wrong person, you’ll have to reach out and explain the situation.

If the link hasn't been claimed yet, and you used a service like Slush, check their platform. Some have a 'cancel' or 'expire' feature for unclaimed links. But once it's claimed, the coins are gone unless the receiver returns them. It’s a good reminder to always double-check addresses before sending. I’ve had a few close calls myself.