Collection Owner Guide
Everything you need to list and manage your collection on MANGOES
Getting Started
To list your collection on MANGOES, follow these steps to get your inscriptions indexed, your metadata uploaded, and your royalties configured.
Submit your collection
Provide the parent inscription ID (for on-chain collections) or a curated list of inscription IDs. On-chain parent-child collections are automatically detected by our indexer.
Connect your wallet
Connect the wallet that owns the parent inscription or was used to create the collection. This proves ownership and grants access to the management portal.
Upload metadata
Upload a JSON or CSV file mapping each inscription ID to its trait attributes. These traits power the filter sidebar and rarity calculations on your collection page.
Configure royalties
Set your creator royalty percentage (0-10%) and the wallet address that should receive royalty payments. Royalties are enforced on-chain through PSBTs.
Go live
Once your collection is reviewed and verified, it will appear on the marketplace with a verified badge, filterable traits, and automatic royalty enforcement.
Metadata Format
Trait metadata maps each inscription in your collection to a set of attributes. These attributes appear as filterable traits on the collection page, enable rarity scoring, and enrich the individual inscription detail view.
Two formats are supported: JSON and CSV. Choose whichever is more convenient for your workflow.
JSON Format
A JSON array of objects, each containing an inscriptionId and a traits object with key-value pairs for each attribute.
[
{
"inscriptionId": "6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0",
"traits": {
"Background": "Blue",
"Fur": "Golden",
"Eyes": "Laser",
"Hat": "Crown",
"Mouth": "Smile"
}
},
{
"inscriptionId": "7ca087bc50edfd128g2f312f95406a94315bf2b8d3bcg8dfe1b96e7a3f553800i0",
"traits": {
"Background": "Red",
"Fur": "Black",
"Eyes": "Normal",
"Hat": "None",
"Mouth": "Open"
}
}
]Requirements:
- Must be valid JSON
- Top-level must be an array
inscriptionIdmust be the full inscription ID including thei0suffix- Trait values must be strings
- All objects should have the same set of trait keys for consistency
CSV Format
A comma-separated file where the first row is the header. The first column must be inscriptionId, and subsequent columns are trait categories.
inscriptionId,Background,Fur,Eyes,Hat,Mouth 6fb976ab49dcec017f1e201e84395983204ae1a7c2abf7ced0a85d692e442799i0,Blue,Golden,Laser,Crown,Smile 7ca087bc50edfd128g2f312f95406a94315bf2b8d3bcg8dfe1b96e7a3f553800i0,Red,Black,Normal,None,Open 8db198cd61fege239h3g423g06517b05426cg3c9e4cdh9egf2ca07f8b4g664911i0,Green,White,Closed,Beanie,Grin
Requirements:
- First row must be the header with column names
- First column must be
inscriptionId - Values containing commas should be wrapped in double quotes
- UTF-8 encoding
Validation
After uploading, the system validates each inscription ID against your collection's indexed inscriptions. You'll see a summary of matched, unmatched, and duplicate entries before publishing. Only matched entries are stored.
Parent-Child vs Curated
MANGOES supports two types of collections, each with different properties and trade-offs. Understanding the distinction is important for choosing the right approach for your project.
Parent-Child Inscriptions
- Provenance proven on-chain via parent inscription
- Automatically detected by indexers
- Immutable collection membership
- No trust required -- fully verifiable
Curated Collections
- Manually curated list of inscription IDs
- Flexible -- add or remove items over time
- Works for inscriptions without parent-child
- Requires platform verification for trust
Recommendation: If your collection uses the parent-child inscription model, prefer the on-chain type. It provides the strongest provenance guarantees and is automatically detected by our indexer. Use the curated type only when parent-child is not available for your inscriptions.
Royalties
Creator royalties on MANGOES are enforced on-chain through Partially Signed Bitcoin Transactions (PSBTs). When a buyer purchases an inscription from your collection, the royalty is automatically included as a transaction output.
How It Works
A seller creates a PSBT that transfers the inscription ordinal. The PSBT includes outputs for the seller, the platform fee, and the creator royalty.
When a buyer finalizes the transaction, the PSBT is completed with the buyer's payment inputs. The transaction is broadcast to the Bitcoin network.
The transaction settles on-chain. The seller receives the sale price minus fees, the platform receives its fee, and the creator receives the royalty -- all in a single atomic transaction.
Fee Breakdown Example
For a sale at 0.5 BTC with a 5% creator royalty and 2% platform fee:
Sale Price: 0.50000000 BTC Platform Fee (2%): 0.01000000 BTC Creator Royalty (5%): 0.02500000 BTC ─────────────────────────────── Seller Receives: 0.46500000 BTC Creator Receives: 0.02500000 BTC Platform Receives: 0.01000000 BTC
Configuration
- Percentage: Set between 0% and 10% in 0.5% increments. Stored as basis points (e.g., 500 = 5%).
- Royalty Address: The Bitcoin address that receives royalty payments. Must be a valid Taproot (bc1p...) or SegWit address.
- Updates: You can change the royalty percentage and address at any time through the management portal. Changes apply to new listings only.
Important
Royalties are only enforced for sales that occur through the MANGOES marketplace. Direct peer-to-peer transfers or sales on other platforms are outside the scope of this royalty system. This is a fundamental limitation of optional royalties on Bitcoin.
Frequently Asked Questions
Ready to list your collection?
Connect your wallet and start managing your collection on MANGOES. Set up royalties, upload trait metadata, and reach thousands of collectors.