Sui Revoke Authority

The Sui revoke authority tool helps token creators permanently remove control features for Sui tokens. This tool is useful for:

• Making tokens have a fixed supply by removing treasury cap
• Making metadata completely immutable by revoking metadata cap
• Creating unchangeable token rules
• Building trust with community and investors

This tool allows you to permanently remove management controls, showing your long-term commitment to your token rules and helping decentralize your project.

The 20lab Sui revoke authority tool lets you permanently remove these key control types for Sui tokens:

• Treasury cap - Stops all future token creation and metadata updates
• Metadata cap - Stops all future changes to token information
• Upgrade cap - Stops all future upgrades to token's Move smart contract
• Deny cap - Stops all future freezing of addresses or pausing of the token

Removing these authorities means those features are gone forever from your token, making it more decentralized and unchangeable.

No, removing authority cannot be undone. After you revoke an authority:

• The authority is permanently removed and can't be brought back
• Nobody, including the token creator, can use that authority anymore
• There's no way to restore the authority once it's gone

Since this is permanent, think carefully before removing any authority. Only revoke an authority when you're sure you'll never need that function again.

Both methods permanently disable an authority, but they work differently:

• Clear Purpose - Revoking shows clearly that the authority was removed on purpose
• Better for Blockchain - Revoking saves space on the Sui network and even allows to claim back some SUI
• Different Process - Revoking publicly freezes authority object, while transferring gives it to a burn address
• Easier to Check - Revoking makes it simpler for auditors to see the authority is really gone

Both achieve the same result, but revoking is cleaner, more obvious, and the preferred method.

Yes, you can choose which authorities to remove and which to keep. This lets you:

• Fix the supply (by removing treasury cap) while keeping security options (keeping deny cap)
• Lock token details (by removing metadata cap) while keeping other management features
• Mix permanent rules with adjustable ones
• Remove control gradually as your project develops

For example, you might remove treasury cap to prevent inflation, but keep deny cap for security, then remove that too later when your project is more established.

Projects remove authorities for different strategic reasons:

• Removing Treasury Cap - Creates truly fixed supply tokens that build trust in your tokenomics
• Removing Deny Cap - Guarantees that token holders' coins can never be frozen
• Removing Metadata Cap - Makes token name, symbol, and other details unchangeable forever
• Removing Upgrade Cap - Locks the smart contract code so it can't be modified

Many successful projects remove authorities as part of their decentralization plan to show commitment to their community and remove central control points.

Yes, the revoke tool works with all Sui tokens on the blockchain, including:

• Standard Sui tokens (with treasury, metadata and upgrade caps)
• Regulated Sui coins with freezing or pausing features (with deny cap)

Which authorities you can remove depends on what features your token was created with and which authorities are currently active. You can't remove an authority that's already gone or was never there to begin with.

Think about these things when deciding whether to remove authorities:

• Project Stage - Only consider removing authorities when your token has reached a stable state
• Community Promises - Make sure your decisions match what you've told your community
• Security Needs - Think about what happens when you can't control certain features anymore
• Future Plans - Be sure you won't need those authorities later

Many projects take it step by step, first moving authorities to multisig governance and then removing them completely when the ecosystem is mature. There's no single right answer - the best choice depends on your specific token design and project plans.