Collection authority rotation

OGAL collections must be controlled by the namespace-derived auth PDA so the program can verify new mints and enforce ownership invariants. If the update authority is temporarily delegated (for automation, metadata refreshes, or emergency recovery), rotate it back to the OGAL authority before minting or verifying new assets.

When to rotate

Rotate the collection update authority when any of the following are true:

• The collection NFT’s update authority no longer matches the namespace auth PDA.
• You granted a temporary signer access (automation or emergency key) and need to revert control.
• A collection verification or mint attempt fails because Metaplex detects a mismatched authority.

Required inputs

Gather these values before running the rotation helper:

• Namespace public key that scopes the OGAL PDAs.
• Collection mint address for the OGAL collection NFT.
• New update authority, which should be the namespace auth PDA or a temporary authority you intend to install.
• Config authority keypair that can sign the update.

Run the rotation helper

Use the OGAL CLI script to update the authority. The helper accepts either a base58 address or a keypair path for the new authority and logs all derived PDAs for auditing.

npm --prefix solana/owner-governed-asset-ledger run rotate-collection-authority -- \
  --namespace <NAMESPACE_PUBKEY> \
  --collection-mint <COLLECTION_MINT> \
  --new-update-authority <BASE58_OR_KEYPAIR_PATH> \
  --authority-keypair /path/to/config-authority.json \
  [--payer-keypair /path/to/payer.json] \
  [--rpc-url <RPC_ENDPOINT>] \
  [--commitment <LEVEL>]

Verify the update

1. Run the inspect-collection helper to confirm the update authority now matches the namespace auth PDA.
2. Record the transaction signature and derived addresses from the CLI output for audit tracking.
3. Retry any blocked mint or verification workflows once the new authority is confirmed.