AddBlocker Plugin

The AddBlocker Plugin prevents any new authority-managed plugins from being added to an Asset or Collection. Lock down your NFT configuration while still allowing owner-managed plugins.

Summary

The AddBlocker plugin is an Authority Managed plugin that prevents adding new authority-managed plugins. Owner-managed plugins (like Freeze Delegate, Transfer Delegate) can still be added.

• Authority Managed (only update authority can add)
• Blocks new authority-managed plugins permanently
• Owner-managed plugins are NOT blocked
• Collection plugin affects all Assets in that Collection

Out of Scope

Blocking owner-managed plugins (always allowed), removing existing plugins, and blocking updates to existing plugins.

Quick Start

Jump to: Add to Asset · Add to Collection

1. Add all authority-managed plugins you'll need
2. Add AddBlocker plugin as update authority
3. No new authority-managed plugins can be added

Common Use Cases

• Royalty protection: Ensure royalties cannot be changed by blocking new Royalties plugins
• Configuration finality: Guarantee collectors the NFT's plugins won't change
• Trust building: Prove to buyers that critical settings are locked
• Collection standards: Enforce consistent plugin configuration across a Collection

Works With

Arguments

The AddBlocker Plugin requires no arguments.

Adding the addBlocker Plugin to an Asset code example

import {
  addPlugin,
} from '@metaplex-foundation/mpl-core'
await addPlugin(umi, {
  asset: asset.publicKey,
  plugin: {
    type: 'addBlocker',
  },
}).sendAndConfirm(umi)

Adding the addBlocker Plugin to a Collection code example

import {
  addCollectionPlugin,
} from '@metaplex-foundation/mpl-core'
await addCollectionPlugin(umi, {
  collection: collection.publicKey,
  plugin: {
    type: 'AddBlocker',
  },
}).sendAndConfirm(umi)

Common Errors

Authority mismatch

Only the update authority can add the AddBlocker plugin.

Cannot add plugin - AddBlocker active

The AddBlocker plugin is preventing new authority-managed plugins. This is expected behavior.

Notes

• Plan your plugin configuration carefully before adding AddBlocker
• Future Metaplex plugin features cannot be added once blocked
• Owner-managed plugins (Freeze, Transfer, Burn Delegates) are always allowed
• Adding to a Collection blocks plugins on ALL Assets too

Quick Reference

What Gets Blocked

Common Authority Managed Plugins (Blocked)

• Royalties
• Attributes
• Verified Creators
• ImmutableMetadata
• AddBlocker (itself)

Owner Managed Plugins (Still Allowed)

• Freeze Delegate
• Transfer Delegate
• Burn Delegate

FAQ

Can I still add Freeze Delegate after AddBlocker?

Yes. Owner-managed plugins like Freeze Delegate, Transfer Delegate, and Burn Delegate can always be added, even after AddBlocker is active.

Can I remove AddBlocker after adding it?

Yes, if it hasn't been made immutable. The plugin can be removed by the authority. However, this defeats the purpose of using AddBlocker.

If I add AddBlocker to a Collection, can I still add plugins to individual Assets?

No. Collection-level AddBlocker prevents adding authority-managed plugins to both the Collection and all its Assets.

What if Metaplex releases a new plugin I want to use?

If AddBlocker is active, you cannot add new authority-managed plugins, even new ones released in the future. Plan accordingly.

Why would I use AddBlocker?

To guarantee that the NFT's authority-managed plugin configuration is final. This provides assurance to collectors that royalties, attributes, and other critical settings cannot be modified by adding new plugins.

Related Plugins

• ImmutableMetadata - Lock name and URI permanently
• Royalties - Set royalties before using AddBlocker
• Attributes - Add attributes before using AddBlocker

Glossary