Transfer Sui Token Authority - Treasury, Deny Cap, and more

The 20lab Sui transfer authority tool lets you reassign control of a Sui coin's capability objects (caps) to a different wallet address. On Sui, authority is managed through capability objects rather than authority flags - this tool handles the secure transfer of each cap type through a single interface.

It's essential for handing off a project to new team members, moving control to a multisig, or transitioning to DAO governance. The tool supports all major Sui coin caps and works with both standard and regulated Move-based coins. If you want to permanently disable a cap instead of moving it, use the revoke authority tool.

The 20lab tool supports transferring all major capability objects for Sui coins:

• Treasury cap - Controls minting new tokens and updating coin metadata
• Metadata cap - Standalone cap for metadata updates on some coin configurations
• Upgrade cap - Controls upgrades to the token's Move smart contract
• Deny cap / Deny cap V2 - Controls freezing addresses and (on V2) pausing the entire token

Each cap can be transferred to a different address independently. The interface auto-detects which caps exist for your token and only shows the ones that are currently active and transferable.

To transfer the Sui treasury cap:

1. Connect the wallet that currently holds the treasury cap
2. Enter your token's coin type or address
3. Select Treasury Cap from the cap types
4. Enter the new holder's wallet address (carefully - this is irreversible)
5. Confirm the transaction

After confirmation, only the new holder can mint additional tokens or update metadata. The transfer is recorded on-chain and visible on Sui Explorer. The previous treasury cap holder loses all minting rights immediately. Full walkthrough: how to transfer or revoke treasury cap on Sui.

To transfer Sui deny cap (or deny cap V2), follow the same flow as transferring treasury cap but select Deny Cap instead. The destination wallet becomes the only address that can freeze or unfreeze Sui token accounts for your coin - and, if your token uses Deny Cap V2 with pause enabled, the only address that can pause or unpause the entire token.

Common scenarios for transferring deny cap:

• Moving from a hot wallet to a multisig for security
• Handing off compliance responsibilities to a regulated entity
• Transferring control to a custom freeze program with its own rules

Yes - you can transfer any Sui token cap to a multisig wallet address. This is the recommended approach for any coin with meaningful value or active community.

Transferring to a multisig provides:

• Multiple-signature security - No single key can act unilaterally
• Protection against compromised wallets - One leaked key isn't catastrophic
• Decentralized governance - Cap decisions require team or community consensus

The tool works with native Sui multisig and popular multisig solutions. Cap transfers to multisigs are otherwise identical to standard wallet transfers.

Yes - you can split caps across different wallet addresses. This enables role-based security models:

• Treasury cap to a DAO treasury for community-controlled minting
• Metadata cap to a marketing team for branding updates
• Deny cap to a compliance multisig for security responses
• Upgrade cap to a development team for contract upgrades

Each cap operates independently after transfer. Splitting caps reduces the blast radius if any one wallet is compromised - an attacker who gets the metadata cap, for example, can't mint tokens or freeze addresses.

No - cap transfers are not reversible through standard means. Once a cap is transferred:

• The previous holder loses all rights immediately
• Only the new holder can perform actions requiring the cap (including transferring it back)
• If the new holder's private key is lost, the cap is permanently inaccessible

Because of this permanence, always verify the destination address twice before confirming. For high-stakes transfers, send a small test coin first to confirm the receiving wallet is functional.

Transferring a cap to an incorrect address has serious, often permanent consequences:

• If sent to a nonexistent address or one without a known private key, the cap becomes permanently inaccessible - effectively the same as using the revoke authority tool
• If sent to a valid wallet you don't control, only that wallet's owner can now use the cap
• There is no built-in recovery mechanism - the transfer is final once confirmed on-chain

To prevent errors: double-check the destination on Sui Explorer, label addresses you use frequently, and test with a low-value coin first if you're unfamiliar with cap transfers.

Yes - the tool works with all Sui coins built on the standard Move Coin module. The available caps depend on which features your token was created with:

• Standard Sui coins - Treasury, metadata, and upgrade caps
• Regulated Sui coins - Plus deny cap or deny cap V2 (for freezable and pausable tokens)
• Tokens created with 20lab's Sui token generator - Full cap set depending on the features enabled at creation

The interface auto-detects which caps exist for your token and only displays the ones that can currently be transferred.