internet-court/internet-court-skill / vendored/metaplex/metaplex
metaplex
VerifiedMetaplex development on Solana — NFTs, tokens, compressed NFTs, candy machines, token launches, autonomous agents. Use when working with Token Metadata, Core, Bubblegum, Candy Machine, Genesis, Agent Registry, or the mplx CLI.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.6 KB |
| SKILL.md | skill md | 9.7 KB |
| references/cli-agent.md | markdown | 8.8 KB |
| references/cli-bubblegum.md | markdown | 5.8 KB |
| references/cli-candy-machine.md | markdown | 10.2 KB |
| references/cli-config.md | markdown | 1.5 KB |
| references/cli-core.md | markdown | 8.9 KB |
| references/cli-genesis.md | markdown | 24.6 KB |
| references/cli-initial-setup.md | markdown | 2.7 KB |
| references/cli-token-metadata.md | markdown | 3.3 KB |
| references/cli-toolbox.md | markdown | 4.3 KB |
| references/cli-troubleshooting.md | markdown | 2.2 KB |
| references/cli.md | markdown | 5.4 KB |
| references/concepts.md | markdown | 12.0 KB |
| references/metadata-json.md | markdown | 1.8 KB |
| references/sdk-agent.md | markdown | 21.7 KB |
| references/sdk-bubblegum.md | markdown | 11.3 KB |
| references/sdk-core.md | markdown | 20.5 KB |
| references/sdk-genesis-low-level.md | markdown | 21.7 KB |
| references/sdk-genesis.md | markdown | 24.4 KB |
| references/sdk-token-metadata-kit.md | markdown | 8.4 KB |
| references/sdk-token-metadata.md | markdown | 13.7 KB |
| references/sdk-umi.md | markdown | 6.1 KB |
references/cli-core.md
View on GitHub# Core CLI Reference
Commands for creating and managing Core NFTs and collections via the `mplx` CLI.
> **Prerequisites**: CLI must be configured (RPC, keypair, funded wallet). If not yet verified this session, see `./cli-initial-setup.md`.
---
## Commands
```bash
# Core Assets
mplx core asset create --name <NAME> --uri <URI>
mplx core asset create --name <NAME> --uri <URI> --owner <ADDR> # Mint to a different wallet — --owner works on all asset create variants
mplx core asset create --name <NAME> --uri <URI> --collection <ADDR>
mplx core asset create --files --image <PATH> --offchain <PATH>
mplx core asset fetch <ADDR>
mplx core asset update <ASSETID> --name <NAME>
mplx core asset update <ASSETID> --uri <URI>
mplx core asset update <ASSETID> --image <PATH> # Re-uploads image via Irys
mplx core asset update <ASSETID> --collectionId <ADDR> # Move to different collection
mplx core asset transfer <ASSETID> <NEW_OWNER> # Collection is auto-detected from the asset
mplx core asset burn <ADDR> # Also: --collection <ADDR>, --list <file.json>
mplx core asset template # Generate template files
# Core Collections
mplx core collection create --name <NAME> --uri <URI>
mplx core collection create --name <NAME> --uri <URI> --pluginsFile <PATH>
mplx core collection fetch <ADDR>
mplx core collection template # Generate template files
# Execute (Asset-Signer Wallets)
mplx core asset execute info <ASSETID> # Show signer PDA address and SOL balance
```
> **Collection authority**: `asset create --collection` works from the CLI because the configured wallet is the collection's update authority. This does NOT translate to apps — end users' wallets can't sign assets into your collection, and the authority key must never live in a frontend. If the user is building an app that mints into a collection (and isn't using Candy Machine), read the "Minting into a Collection from an App" section in `./sdk-core.md` before designing anything.
---
## Core Plugins
**Plugin file format** (for `--pluginsFile`):
```json
[{
"type": "Royalties",
"basisPoints": 500,
"creators": [{"address": "<CREATOR_ADDRESS>", "percentage": 100}],
"ruleSet": {"type": "None"}
}]
```
**Available Types:** `Royalties`, `FreezeDelegate`, `BurnDelegate`, `TransferDelegate`, `Attributes`, `ImmutableMetadata`, `PermanentFreezeDelegate`, `PermanentTransferDelegate`, `PermanentBurnDelegate`
**RuleSet Options:**
- `{"type": "None"}`
- `{"type": "ProgramAllowList", "programs": [...]}`
- `{"type": "ProgramDenyList", "programs": [...]}`
**Example - Collection with Royalties:**
```bash
# Create plugins.json
echo '[{
"type": "Royalties",
"basisPoints": 500,
"creators": [{"address": "<CREATOR_ADDRESS>", "percentage": 100}],
"ruleSet": {"type": "None"}
}]' > plugins.json
# Create collection with plugins
mplx core collection create \
--name "My Collection" \
--uri "https://gateway.irys.xyz/xxx" \
--pluginsFile ./plugins.json
```
Note: `basisPoints: 500` = 5%. Creator percentages must total 100.
---
## Metadata Workflow
### Before Creating - Gather from User:
- Name
- Description (optional)
- Attributes (optional)
- Image file
- For collections: Ask if they want royalties
### Creating Single NFT Asset/Collection
> **Note**: When creating an NFT with option A do not treat the metadata json file as broken if it has a placeholder value for the uri. This will update within the command.
```bash
# Option A: Local files (one step) - recommended. Oneliner that uploads the image file and then
# updates the metadata json file with the uploaded image uri then creates the NFT in a singal command.
mplx core asset create --files --image ./image.png --offchain ./metadata.json
# Option B: Manual upload workflow
# Provides manual steps to recreate the option A.
# 1. Upload image
mplx toolbox storage upload ./image.png
# Returns: https://gateway.irys.xyz/<IMAGE_HASH>
# 2. Create metadata.json — follow the NFT schema in metadata-json.md, set image URI to above
# 3. Upload metadata
mplx toolbox storage upload ./metadata.json
# Returns: https://gateway.irys.xyz/<META_HASH>
# 4. Create asset
mplx core asset create --name "My NFT" --uri "https://gateway.irys.xyz/<META_HASH>"
```
### Creating Multiple NFTs Assets (Batch)
```bash
# 1. Upload all images at once
mplx toolbox storage upload ./images --directory
# 2. Create metadata files — one per NFT, each following the NFT schema in metadata-json.md
# Set each "image" + properties.files[0].uri to the corresponding uploaded image URI
# 3. Upload all metadata at once
mplx toolbox storage upload ./meta --directory
# 4. Create all assets (ONE command)
mplx core asset create --name "NFT #1" --uri "<META_URI_1>" --collection <ADDR> && \
mplx core asset create --name "NFT #2" --uri "<META_URI_2>" --collection <ADDR> && \
mplx core asset create --name "NFT #3" --uri "<META_URI_3>" --collection <ADDR>
```
---
## Execute (Asset-Signer Wallets)
Every MPL Core asset has a deterministic **signer PDA** that can hold SOL, tokens, and own other assets. Asset-signer wallets let you use this PDA as your active wallet — all CLI commands automatically operate through the PDA.
> **How it works**: When an asset-signer wallet is active, `umi.identity` and `umi.payer` are set to the PDA. At send time, the transaction is wrapped in MPL Core's `execute` instruction, which signs on behalf of the PDA on-chain. The real wallet (asset owner) signs the outer transaction.
### Setup
```bash
# 1. Check the PDA info for any asset
mplx core asset execute info <ASSETID>
# 2. Fund the PDA
mplx toolbox sol transfer 0.1 <signerPdaAddress>
# 3. Register as a wallet
mplx config wallets add vault --asset <ASSETID>
# 4. Switch to the asset-signer wallet
mplx config wallets set vault
# 5. Use any command as the PDA
mplx toolbox sol balance
mplx toolbox sol transfer 0.01 <destination>
mplx core asset create --name "PDA Created NFT" --uri "https://example.com/nft"
# Switch back to normal wallet
mplx config wallets set my-wallet
```
> Pass `-k /path/to/wallet.json` to bypass the asset-signer wallet for a single command.
> Use `-p /path/to/fee-payer.json` to have a different wallet pay transaction fees.
### Supported Commands
Most CLI commands work with asset-signer wallets. The transaction wrapping is transparent.
- **Core**: `asset create`, `asset transfer`, `asset burn`, `asset update`, `collection create`
- **Toolbox SOL**: `balance`, `transfer` (`wrap`/`unwrap` may fail; see CPI limitations)
- **Toolbox Token**: `transfer`, `create`, `mint`
- **Toolbox Raw**: `raw --instruction <base64>`
- **Token Metadata**: `transfer`, `create`, `update`
- **Bubblegum**: `nft create` (public trees), `nft transfer`, `nft burn`, `collection create`
- **Genesis**: `create`, `bucket add-*`, `deposit`, `withdraw`, `claim`, `finalize`, `revoke`
### Raw Instructions
```bash
# Execute arbitrary base64-encoded instructions as the PDA
mplx toolbox raw --instruction <base64>
mplx toolbox raw --instruction <ix1> --instruction <ix2>
echo "<base64>" | mplx toolbox raw --stdin
```
### CPI Limitations
Some operations cannot be wrapped in `execute()` due to Solana CPI constraints:
- **Large account creation** — Merkle trees, candy machines (exceed CPI account allocation limits)
- **Native SOL wrapping** — `transferSol` to a token account fails in CPI context
For these, use a normal wallet to create the infrastructure first, then switch to the asset-signer wallet for subsequent operations.
## For more info
Consult these Metaplex docs when you need deeper detail than this reference provides:
- Core overview: https://metaplex.com/docs/smart-contracts/core
- Create asset: https://metaplex.com/docs/smart-contracts/core/create-asset
- Collections: https://metaplex.com/docs/smart-contracts/core/collections
- Transfer: https://metaplex.com/docs/smart-contracts/core/transfer
- Update: https://metaplex.com/docs/smart-contracts/core/update
- Burn: https://metaplex.com/docs/smart-contracts/core/burn
- Fetch: https://metaplex.com/docs/smart-contracts/core/fetch
- Plugins: https://metaplex.com/docs/smart-contracts/core/plugins
- Update delegate (app minting): https://metaplex.com/docs/smart-contracts/core/plugins/update-delegate
- Execute / asset signing: https://metaplex.com/docs/smart-contracts/core/execute-asset-signing
- CLI create asset: https://metaplex.com/docs/dev-tools/cli/core/create-asset
- CLI create collection: https://metaplex.com/docs/dev-tools/cli/core/create-collection
- CLI transfer: https://metaplex.com/docs/dev-tools/cli/core/transfer-asset
- CLI update: https://metaplex.com/docs/dev-tools/cli/core/update-asset
- CLI plugins: https://metaplex.com/docs/dev-tools/cli/core/plugins
- CLI execute: https://metaplex.com/docs/dev-tools/cli/core/execute
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |