How to manage a token contract

Read the live state before acting

Managing a token means using permissions the deployed asset already has. An app setting cannot add minting, replace deployed bytecode or restore revoked authority. Open the token detail page and inspect the live network, address, supply, owner or authorities, and paused state before choosing an action.

An imported token can be tracked, but importing it does not make the signed-in wallet its owner. The wallet must hold the relevant on-chain permission for a management transaction to succeed. CryptoMuz's supported management controls depend on the token's implementation, not just its ERC-20 label.

Manage an EVM token

1. Select the token on the Tokens page and confirm its contract address and network against the explorer.
2. Read which controls are enabled. Minting needs a mintable token and the authorized owner. Pausing needs a pausable token and owner access. Burning spends this wallet's own balance.
3. Enter the exact amount or destination, review the operation and approve the wallet transaction. A paused token must be unpaused before actions that its transfer rules prohibit.
4. Wait for the receipt and refresh the on-chain state. Record the transaction id and communicate any supply or permission change to holders.

Transfer ownership without losing control

The CryptoMuz ERC-20 template uses a two-step ownership transfer. The current owner offers control to a destination, then that destination accepts it from its own wallet. A pending owner is not the owner yet. Verify the destination and its ability to accept ownership before making the offer; a copied address error should not become an irreversible handover.

Renouncing ownership removes owner powers permanently. It does not remove a pool, change holder allocations or certify the contract. Unpause the token first: new template deployments refuse renunciation while paused, but older contracts may not protect against that mistake. Do not renounce merely to complete a checklist.

Manage Solana authorities separately

SPL mint authority, freeze authority and metadata update authority are different controls. Revoking mint authority fixes future issuance; revoking freeze authority stops future freezing or thawing by that authority. A token can have one authority removed and another retained.

• Before revoking freeze authority, check whether any token accounts are frozen and resolve them first. Removing the authority does not automatically thaw accounts.
• When transferring an authority, verify the new public key and use the relevant authority control. Solana authority changes are not the EVM template's two-step ownership flow.
• Metadata edits depend on the update authority and metadata mutability. Changing the displayed name is different from changing the mint identity.

Keep an operations record

Keep the token address, network, treasury and owner addresses, retained permissions and confirmed transaction ids together. Separate treasury custody from routine publishing where practical. Use a custody arrangement appropriate to the project, and verify that it can call the actual management functions before handing it control.

For every operation, verify the outcome in the explorer. If confirmation times out, inspect the original transaction before retrying. A dashboard refresh does not reverse a chain action. Continue with source verification and the launch checklist.