Metaplex

Metaplex Development Skill

Overview

Metaplex provides the standard infrastructure for NFTs and tokens on Solana:

• Agent Registry: On-chain agent identity, wallets, and execution delegation for MPL Core assets
• Genesis: Token launch protocol with fair distribution + liquidity graduation
• Core: Next-gen NFT standard (recommended for new NFT projects)
• Token Metadata: Fungible tokens + legacy NFTs/pNFTs
• Bubblegum: Compressed NFTs (cNFTs) using Merkle trees — massive scale at minimal cost
• Candy Machine: NFT drops with configurable minting rules

Tool Selection

Prefer CLI over SDK for direct execution. Use SDK only when user specifically needs code.

Task Router

IMPORTANT: You MUST read the detail file for your task BEFORE executing any command or writing any code. The command syntax, required flags, setup steps, and batching rules are ONLY in the detail files. Do NOT guess commands from memory.

CLI Capabilities

The mplx CLI can handle most Metaplex operations directly. Read ./references/cli.md for agent guidelines (batching, JSON output, explorer links), then the program-specific file.

CLI v0.1.0 breaking changes (for agents/scripts migrating from older versions):

• --json <file> (used to pass an offchain metadata file path) is now --offchain <file>. --json is now the standard OCLIF flag for machine-readable output.
• All commands now return structured JSON when --json is passed — use this for programmatic/agent use.

Program IDs

Agent Identity:  1DREGFgysWYxLnRnKQnwrxnJQeSMk2HmGaC6whw2B2p
Agent Tools:     TLREGni9ZEyGC3vnPZtqUh95xQ8oPqJSvNjvB7FGK8S
Genesis:         GNS1S5J5AspKXgpjz6SvKL66kPaKWAhaGRhCqPRxii2B
Core:            CoREENxT6tW1HoK8ypY1SxRMZTcVPm7R94rH4PZNhX7d
Token Metadata:  metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s
Bubblegum V1:    BGUMAp9SX3uS4efGcFjPjkAQZ4cUNZhtHaMq64nrGf9D
Bubblegum V2:    BGUMAp9Gq7iTEuizy4pqaxsTyUCBK68MDfK752saRPUY
Core Candy:      CMACYFENjoBMHzapRXyo1JZkVS6EtaDDzkjMrmQLvr4J

Quick Decision Guide

Autonomous Agents

Use Agent Registry to register on-chain identity and execution delegation for MPL Core assets. The Mint Agent API (mintAndSubmitAgent) is the recommended path — it creates the Core asset and registers identity in a single transaction. For existing assets, use registerIdentityV1 directly. Any Core asset already has a built-in wallet (Asset Signer PDA) via Core's Execute hook — the registry adds discoverable identity records and lets owners delegate an off-chain executive to operate the agent. Agents can optionally link a Genesis token via setAgentTokenV1. Read ./references/cli-agent.md (CLI) or ./references/sdk-umi.md + ./references/sdk-agent.md (SDK).

Token Launches (Token Generation Event / Fair Launch / Bonding Curve)

Use Genesis. The Launch API (genesis launch create / createAndRegisterLaunch) is recommended — it handles everything in one step. Two launch types:

• launchpool (default): Configurable allocations, 48h deposit, team vesting support
• bonding-curve: Instant bonding curve (constant product AMM) — no deposit window, trading starts immediately, auto-graduates to Raydium CPMM on sell-out. Supports creator fees, first buy, and agent mode.

Read ./references/cli.md + ./references/cli-genesis.md (CLI) or ./references/sdk-genesis.md (SDK launch flow). For custom buckets/presale/vesting, use ./references/sdk-genesis-low-level.md.

NFTs: Core vs Token Metadata

Compressed NFTs (Massive Scale)

Use Bubblegum when minting thousands+ of NFTs at minimal cost. See ./references/cli-bubblegum.md (CLI) or ./references/sdk-bubblegum.md (SDK).

Fungible Tokens

Always use Token Metadata. Read ./references/cli-toolbox.md for CLI commands.

NFT Drops

Use Core Candy Machine. Read ./references/cli.md + ./references/cli-candy-machine.md.

App Mints into a Core Collection WITHOUT Candy Machine

Creating an asset into a Core collection requires the collection's update authority (or an UpdateDelegate) to sign — a user's wallet can't, and the authority key must never be in a frontend. The app needs either a custom on-chain program (PDA granted UpdateDelegate, mint logic in the program) or a backend/API holding a delegate keypair that signs mints. Read the "Minting into a Collection from an App" section in ./references/sdk-core.md before designing the minting flow.

Asset as Agent / Vault / Wallet (Execute)

Use Core Execute when an asset (NFT, agent, vault) needs to hold SOL/tokens, transfer funds, sign transactions, or own other assets. Every Core asset has a signer PDA that can act as an autonomous wallet. Read ./references/cli-core.md (CLI) or ./references/sdk-core.md (SDK), execute section.

For more info

When a task needs deeper detail than the skill references provide (edge cases, full API surfaces, guides), consult the Metaplex docs:

• Documentation home: https://metaplex.com/docs
• Agent Registry: https://metaplex.com/docs/agents
• Genesis: https://metaplex.com/docs/smart-contracts/genesis
• Core: https://metaplex.com/docs/smart-contracts/core
• Token Metadata: https://metaplex.com/docs/smart-contracts/token-metadata
• Bubblegum: https://metaplex.com/docs/smart-contracts/bubblegum-v2
• Candy Machine: https://metaplex.com/docs/smart-contracts/core-candy-machine
• Tokens: https://metaplex.com/docs/tokens
• NFTs: https://metaplex.com/docs/nfts
• CLI: https://metaplex.com/docs/dev-tools/cli
• Umi SDK: https://metaplex.com/docs/dev-tools/umi
• DAS API: https://metaplex.com/docs/dev-tools/das-api
• Protocol fees: https://metaplex.com/docs/protocol-fees