> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/tools/secure/revoke-update-authority.md).

# Revoke Update Authority

[Revoke Update Authority](https://j.tools/en/tools/revoke-update-authority) sets your token's metadata update authority to null in one transaction. Once it confirms, no wallet can edit the name, symbol, image, description, or social links from that [authority](/concepts/authorities.md) ever again. Teams use it to lock a token's identity before a [DEX listing](/concepts/dexes-and-liquidity.md), so holders know the branding cannot be swapped out after launch.

{% hint style="danger" %}
**This cannot be undone.** Once this transaction confirms on-chain, there is no way to reverse it. Check every field before you sign.
{% endhint %}

## When to use this

* You have finished branding the token (name, symbol, image, links) and want to lock it before listing.
* You want to signal to holders that the token identity cannot be silently changed after launch.
* You hold the metadata update authority for an existing [SPL](/concepts/spl-vs-token2022.md) mint and want to retire it for good.

If you want to remove every authority at once (mint, freeze, and update), use [Make Immutable](/tools/secure/make-immutable.md) instead. To lock supply only, use [Revoke Mint](/tools/secure/revoke-mint.md); to lock account freezing, use [Revoke Freeze](/tools/secure/revoke-freeze.md).

## Before you start

* A connected wallet ([how to connect](/getting-started/quick-start.md)) that currently holds the token's metadata update authority. This is the wallet that signs.
* The token's [mint address (CA)](/getting-started/glossary.md). Pick it with the built-in token selector.
* A token that already has a Metaplex metadata account. The status check must show **Metadata Found** before you can proceed.
* Enough SOL in that wallet for the network fee and the platform fee.

{% hint style="warning" %}
Finish every metadata edit first. Get the name, symbol, image, and links exactly right with [Update Metadata](/tools/token/update-metadata.md), because once you revoke the update authority there is no way back. The Metaplex program exposes no instruction to reassign the authority once it is set to null.
{% endhint %}

## Step by step

{% stepper %}
{% step %}

### Connect and paste the mint

Connect the wallet that holds the update authority (the header wallet or an imported private key through the Wallet Source selector). Paste the token mint address into the selector.
{% endstep %}

{% step %}

### Check the metadata status

J Tools derives the metadata account for the mint and shows a status badge: **Metadata Found**, **Metadata Missing / Invalid**, or **Loading**. You cannot continue if metadata is missing, so confirm the badge reads **Metadata Found**.
{% endstep %}

{% step %}

### Read the warning, then revoke

Review the irreversible-action notice. When you are sure the branding is final, click **Revoke Update Authority**. J Tools builds the transaction that sets the update authority to null, adds the platform fee to the same transaction, and asks you to sign. Approve it in your wallet.
{% endstep %}

{% step %}

### Confirm and copy the signature

The page waits for confirmation and records the fee. On success it shows the signature with **Copy Signature** and **View On Solscan** so you can verify the change on-chain.
{% endstep %}
{% endstepper %}

[**Open Revoke Update Authority in the app →**](https://j.tools/en/tools/revoke-update-authority)

{% hint style="info" %}
**About wallet warnings.** Some tools sign more than one thing in a single step, for example creating a token and its metadata together. Phantom can show a caution banner for these multi-step transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve.
{% endhint %}

## The options, explained

| Field                   | What it does                                                                                                                                                              |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Token Mint Address (CA) | The SPL token whose update authority will be revoked. Entered through the built-in token selector. J Tools derives the metadata account and shows its status as you type. |
| Connected wallet        | The wallet that signs. It must be the current update authority on the mint's metadata. There is no separate owner field; the connected wallet is used directly.           |

## If something goes wrong

* **Metadata account was not found.** The mint has no Metaplex metadata account, or the address is wrong. Double-check the CA. A token with no metadata account has no update authority to revoke.
* **Wrong wallet.** The connected wallet does not hold the update authority. Connect the wallet that does.
* **Not enough SOL.** Revoking needs SOL for the network fee plus the platform fee. Top up the wallet and try again.

For the full list, see the [Error codes reference](/reference/error-codes.md).

## FAQ

<details>

<summary>Can I undo this?</summary>

No. Once the transaction confirms, the update authority is set to null and can never be restored. After that, no wallet can change the name, symbol, image, description, or social links from this authority. That permanence is the point: it is what makes the locked identity trustworthy.

</details>

<details>

<summary>Does this change my supply, mint, or freeze settings?</summary>

No. It only removes metadata edit permission. Token balances, total supply, the mint authority, and the freeze authority all stay exactly as they were.

</details>

<details>

<summary>Is my token fully immutable after this?</summary>

Not on its own. Revoking update authority locks the metadata, but the token's `isMutable` flag stays true and the mint and freeze authorities are untouched. For a full lock across all three authorities, use [Make Immutable](/tools/secure/make-immutable.md).

</details>

<details>

<summary>Should I lock metadata before or after editing it?</summary>

After. Set the name, symbol, image, and links exactly right with [Update Metadata](/tools/token/update-metadata.md) first. Once you revoke the update authority, none of it can be changed again.

</details>

<details>

<summary>Does J Tools hold my token or keys?</summary>

No. You sign the transaction in your own wallet, and the change happens directly on-chain. J Tools never holds or requests your private keys.

</details>

## Related tools

{% content-ref url="/pages/gclVFAjMJFchUipqQNOZ" %}
[Update Metadata](/tools/token/update-metadata.md)
{% endcontent-ref %}

{% content-ref url="/pages/gbx1RbByQOVKZzt0PQkP" %}
[Make Immutable](/tools/secure/make-immutable.md)
{% endcontent-ref %}

{% content-ref url="/pages/dDKMIJDsaV6TyBZPgRLH" %}
[Revoke Mint](/tools/secure/revoke-mint.md)
{% endcontent-ref %}

{% content-ref url="/pages/3mfyP8upN3tiDTB59aRi" %}
[Revoke Freeze](/tools/secure/revoke-freeze.md)
{% endcontent-ref %}

{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.j.tools/tools/secure/revoke-update-authority.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.