agorix
AirdropMarketsCollectionsLeaderboardActivity
Agorix · Decentralized Marketplace
Independent · Resilient · Community-Run

A cross-chain marketplace, run by the community.

Discover, list, and trade across Bitcoin, Ethereum, and Solana on an open, community-run network.

Marketplace
CollectionsMarketsLeaderboardActivity
Network
GovernanceExplorerAirdropDocs
Account
ProfileSettings
Legal
Terms of ServicePrivacy PolicyYour Privacy Choices
agorix.io — Lasting Access
CID: 0xA60R1X · v0.1
AirdropMarketsCollections
D
Protocol Docs
Marketplace OverviewAtomic Buy LocksDatabase ArchitectureProfiles & AuthenticationCollections & RoyaltiesCreator Royalty SystemMedia Cache & OptimizationModeration & ReputationSearch & DiscoveryCollection Rarity AlgorithmsLive Activity & LeaderboardsCollection Preseed Queue
Docs/Marketplace/Collections & Royalties
Marketplace

Collections & Royalties

Collection types (EVM contract, parent-child, gallery, curated), the community submission and voting process, conflict detection, burn verification, and royalty distribution.

#Collections & Royalties

Collections group related assets together and define royalty policies. The system supports four collection types across all chains.

#Collection Types

EVM_CONTRACT -- Smart contract collections (Ethereum, Base, Arbitrum, Optimism)

  • Identified by contractAddress and contractChainId
  • Supports ERC-721 and ERC-1155 token standards
  • Verified against actual on-chain contract state

PARENT_CHILD -- Bitcoin ordinal parent-child relationships

  • Identified by parentInscriptionId
  • Child inscriptions are automatically grouped under the parent
  • Parent can be burned to "finalize" the collection (prevents new children)

GALLERY -- Explicit inscription lists

  • Defined by a galleryManifest JSONB array of inscription IDs
  • Manual curation -- no automatic parent linking
  • Used for curated ordinal collections that don't share a parent

CURATED -- Generic custom collections

  • No on-chain verification requirements
  • User-defined metadata only
  • Useful for thematic groupings across chains

#Collection Submission & Voting

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

  • Submit -- User creates a 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

  • Conflict Detection -- System scans 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

  • Burn Detection (PARENT_CHILD only):

- Each node can vote once per submission

- verifyVotes and rejectVotes tallied

- 7-day deadline for conflicted proposals

- Requires supermajority to resolve

  • Community Voting -- Nodes vote to verify or reject:

- Status moves to VERIFIED, resolvedAt timestamp set

- Metadata merged into collectionMetadata

- Listings can now reference this collection for royalty enforcement

  • Resolution -- Once approved:

#Royalty Distribution

Each collection can have multiple royalty recipients defined in collectionRegistry:

FieldPurpose
collectionIdWhich collection
recipientAddressWallet to receive royalties
bpsBasis points (0-10000, i.e. 0% to 100%)

Multiple recipients supported -- co-creators can split royalties. For example:

  • Artist A: 500 bps (5%)
  • Artist B: 300 bps (3%)
  • Total royalty: 800 bps (8%)

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:

text
sellerReceives = price - marketplaceFee - totalRoyalties

#Inscription Cache

Bitcoin ordinal metadata is cached locally in inscriptionCache:

FieldPurpose
inscriptionIdPrimary key -- the inscription identifier
inscriptionNumberSequential Bitcoin ordinal number
contentType / contentUrlMedia type and source URL
ownerCurrent owner address
satRarityRarity classification of the underlying satoshi
parentInscriptionIdParent for child inscriptions
collectionIdResolved collection assignment

This cache is populated from the ord indexer and updated periodically. It enables fast lookups without hitting the indexer for every query.

PreviousProfiles & AuthenticationNext Creator Royalty System

On this page

  • Collections & Royalties
  • Collection Types
  • Collection Submission & Voting
  • Royalty Distribution
  • Inscription Cache