Collection types (EVM contract, parent-child, gallery, curated), the community submission and voting process, conflict detection, burn verification, and royalty distribution.
Collections group related assets together and define royalty policies. The system supports four collection types across all chains.
EVM_CONTRACT -- Smart contract collections (Ethereum, Base, Arbitrum, Optimism)
contractAddress and contractChainIdPARENT_CHILD -- Bitcoin ordinal parent-child relationships
parentInscriptionIdGALLERY -- Explicit inscription lists
galleryManifest JSONB array of inscription IDsCURATED -- Generic custom collections
Anyone can propose a new collection through the submission system:
- Collection type and chain-specific identifiers
- Proposed name, description, image URL
- For ordinal ranges: inscriptionNumberStart and inscriptionNumberEnd
collectionSubmissions record with: - If no conflicts and the collection is new: it is shown immediately (softApproved). A submission never makes a collection verified; the verified badge comes only from the governance setting verifiedCollections
- If conflicts found: hasConflict = true, conflictDetails stored, 7-day voting period begins
inscriptionCache for overlaps:- System checks if parent inscription has been burned
- Detection methods: Satoshi's address, standard burn address, OP_RETURN, zero output value
- parentBurnDetected and parentBurnMethod are recorded
- Each node can vote once per submission
- verifyVotes and rejectVotes tallied
- 7-day deadline for conflicted proposals
- Requires supermajority to resolve
- Status moves to VERIFIED, resolvedAt timestamp set
- Metadata merged into collectionMetadata
- Listings can now reference this collection for royalty enforcement
Each collection can have multiple royalty recipients defined in collectionRegistry:
| Field | Purpose |
|---|---|
collectionId | Which collection |
recipientAddress | Wallet to receive royalties |
bps | Basis points (0-10000, i.e. 0% to 100%) |
Multiple recipients supported -- co-creators can split royalties. For example:
Listings can override royalties via royaltyBpsOverride (0-10000). The computeRoyaltyOutputs function calculates exact recipient amounts using deterministic integer arithmetic -- no floating point, no rounding errors.
On purchase, royalties are deducted from the seller's proceeds before the marketplace fee:
sellerReceives = price - marketplaceFee - totalRoyaltiesBitcoin ordinal metadata is cached locally in inscriptionCache:
| Field | Purpose |
|---|---|
inscriptionId | Primary key -- the inscription identifier |
inscriptionNumber | Sequential Bitcoin ordinal number |
contentType / contentUrl | Media type and source URL |
owner | Current owner address |
satRarity | Rarity classification of the underlying satoshi |
parentInscriptionId | Parent for child inscriptions |
collectionId | Resolved collection assignment |
This cache is populated from the ord indexer and updated periodically. It enables fast lookups without hitting the indexer for every query.