Burn Delegate

The Burn Delegate Plugin allows a designated authority to burn Core Assets on behalf of the owner. Useful for game mechanics, subscription services, and automated asset lifecycle management.

Summary

The Burn Delegate is an Owner Managed plugin that allows a delegate to burn an Asset. Once added, the delegate can burn the Asset at any time without owner approval.

• Delegate burn authority to a program or wallet
• Authority is revoked on Asset transfer
• Use Permanent Burn Delegate for irrevocable burn authority
• No additional arguments required

Out of Scope

Collection burning (different process), permanent burn authority (see Permanent Burn Delegate), and Token Metadata burn authority (different system).

Quick Start

Jump to: Add Plugin · Delegate Authority · Revoke

1. Add the Burn Delegate plugin: addPlugin(umi, { asset, plugin: { type: 'BurnDelegate' } })
2. Optionally delegate to another address
3. The delegate can now burn the Asset at any time

Common Use Cases

• Game mechanics: Burn NFTs when items are consumed, destroyed, or lost in-game
• Subscription services: Auto-burn expired subscription tokens
• Crafting systems: Burn ingredient NFTs when crafting new items
• Achievement redemption: Burn achievement tokens when redeemed for rewards
• Event tickets: Burn tickets after event check-in
• Limited-time assets: Burn assets after expiration period

Works With

Arguments

The Burn Plugin doesn't contain any arguments to pass in.

Adding the Burn Plugin to an Asset

import { publicKey } from '@metaplex-foundation/umi'
import { addPlugin } from '@metaplex-foundation/mpl-core'
(async () => {
    const asset = publicKey('11111111111111111111111111111111')
    await addPlugin(umi, {
    asset: asset,
    plugin: { type: 'BurnDelegate' },
    }).sendAndConfirm(umi)
})();

Delegating Burn Authority

The Burn Delegate plugin authority can be delegated to a different address using the approvePluginAuthority function. This allows you to change who can burn the Asset.

import { publicKey } from '@metaplex-foundation/umi'
import { approvePluginAuthority } from '@metaplex-foundation/mpl-core'
(async () => {
    const assetAddress = publicKey('11111111111111111111111111111111')
    const newDelegate = publicKey('22222222222222222222222222222222')
    await approvePluginAuthority(umi, {
    asset: assetAddress,
    plugin: { type: 'BurnDelegate' },
    newAuthority: { type: 'Address', address: newDelegate },
    }).sendAndConfirm(umi)
})();

Revoking Burn Authority

The burn authority can be revoked using the revokePluginAuthority function, returning control to the asset owner.

import { publicKey } from '@metaplex-foundation/umi'
import { revokePluginAuthority } from '@metaplex-foundation/mpl-core'
(async () => {
    const assetAddress = publicKey('11111111111111111111111111111111')
    await revokePluginAuthority(umi, {
    asset: assetAddress,
    plugin: { type: 'BurnDelegate' },
    }).sendAndConfirm(umi)
})();

Common Errors

Authority mismatch

Only the burn delegate authority can burn the Asset. Verify you're signing with the correct keypair.

Asset is frozen

Frozen Assets cannot be burned. The freeze authority must thaw the Asset first.

Notes

• Owner Managed: requires owner signature to add
• Authority is automatically revoked when the Asset transfers
• Frozen Assets cannot be burned
• Use Permanent Burn Delegate if authority must persist after transfer
• Burning is immediate and irreversible

Quick Reference

Who Can Burn?

FAQ

What's the difference between Burn Delegate and Permanent Burn Delegate?

Burn Delegate authority is revoked on transfer. Permanent Burn Delegate authority persists forever and uses forceApprove, meaning it can burn even if the Asset is frozen.

Can the owner still burn if there's a Burn Delegate?

Yes. The owner can always burn their own Asset regardless of delegates.

Does Burn Delegate work on frozen Assets?

No. Regular Burn Delegate cannot burn frozen Assets. Use Permanent Burn Delegate if you need to burn frozen Assets.

When is Burn Delegate revoked?

When the Asset is transferred to a new owner. The new owner would need to add a new Burn Delegate.

Related Plugins

• Permanent Burn Delegate - Irrevocable burn authority with forceApprove
• Freeze Delegate - Block transfers and burns temporarily
• Transfer Delegate - Allow delegate to transfer Assets

Glossary