Lock your Solana token's metadata for good

A Solana token's name, symbol and logo live in a Metaplex Token Metadata account, not in the mint. While that account is mutable, its update authority can rename the token, change the ticker and swap the logo at any time with a single UpdateMetadataAccountV2 instruction. That is how a token bought as one project can be rebranded overnight into an imitation of another, or how a scammer changes the image after listing. Wallets cache the old values for a while, so holders often notice late.

Screeners flag this. RugCheck lists Mutable metadata as a risk item, and DEX aggregators and token lists give more weight to immutable tokens. Making the metadata immutable removes the concern in one step: the Metaplex program refuses every later update, from anyone, forever. Together with revoked mint and freeze authorities it is what most people mean when they call a token renounced.

Locking freezes the on-chain fields of the metadata account: name (up to 32 bytes), symbol (up to 10 bytes), URI (up to 200 bytes), the seller fee, the creators list and the collection reference. The URI points to a JSON file with the description and image link, so the logo is locked only as far as the file behind the URI is fixed. A URI on IPFS or Arweave, or a SOLTidy upload link (named after the file's SHA-256 hash), is content-addressed and cannot change; a URI on a web server you control can still serve a different image tomorrow. Check the URI before you lock.

It does not touch the mint account. Supply, decimals, the mint authority and the freeze authority are separate fields with separate instructions, so an immutable token can still be minted or have holder accounts frozen if those authorities are active. The panel shows both authorities next to the metadata so you can see what is left, and the Revoke Mint Authority and Revoke Freeze Authority pages handle them, each for the same 0.054 SOL.

People search for revoking the update authority, but Metaplex has no way to set it to nobody: the field must always hold a public key. Sending it to a burn address is possible but pointless and risky, because the authority is still needed for one thing, verifying the token as a member of a collection, and you would lose that for nothing. Setting is-mutable to false is the real lock. Afterwards the update authority cannot edit anything, no matter who holds it.

This page does exactly one thing: it sends an UpdateMetadataAccountV2 instruction whose data block is a copy of the current account, with is-mutable set to false and the update authority unchanged. If you also want a new name or logo, make those edits first with Update Token Metadata, since this is the last edit the account will ever accept. The Metaplex program only allows the flag to move from true to false, so there is no undo.

Token-2022 mints that store their name, symbol and URI in the token metadata extension instead of a Metaplex account are not supported here; the panel says so when it detects the extension. Those fields are controlled by the extension's own update authority, and the equivalent lock is setting that authority to none through the Token-2022 program, which this page does not do.

Mints with no metadata account at all show as unknown tokens in wallets and have nothing to lock; the mint authority can create metadata with Update Token Metadata first and lock it in the same transaction. If the update authority is a launchpad program or a multisig, the lock has to be signed from there, because the panel can only build a transaction for the wallet you connect.

To change the name, image or links before you lock them, use Update Metadata first.