Token metadata can be one of the most visible parts of a project.
It includes information users may see in compatible wallets, explorers and applications.
One important configuration is whether supported metadata remains mutable.
What does mutable mean?
Mutable metadata can still be updated by the authorized update authority.
That can be useful when a project needs to:
- Correct a description.
- Replace an image.
- Update a website.
- Fix metadata before a final launch.
- Maintain project information.
Mutability therefore provides flexibility.
What does immutable mean?
Immutable metadata is locked against supported future updates.
Once the relevant immutable action is confirmed, the project should assume the metadata cannot be changed through the normal update mechanism.
This provides permanence at the cost of flexibility.
Why make metadata immutable?
Projects may choose immutability when the final metadata has been verified and they want users to know that the supported information can no longer be changed by the update authority.
However, immutability is not automatically the correct choice for every project.
What should you verify first?
Before making metadata immutable, carefully check:
- Token name.
- Symbol.
- Logo.
- Description.
- Website.
- Social links.
- Metadata URI.
- Any other information your project depends on.
A typo that seems small today may become permanent after locking the metadata.
Is immutable metadata proof that a token is safe?
No.
It is only one technical property.
A project's legitimacy, economic design and security cannot be determined from metadata mutability alone.
Use the correct order
If metadata needs repair, repair it first.
Verify the result.
Only then consider whether immutability matches your project's goals.
ForgeMyToken can inspect supported metadata configuration and provides selected Fix workflows when the connected wallet has the required authority.