Collection.xyz Documentation
Collection.xyz
  • What is Collection.xyz?
  • Collection Concepts
    • Liquidity Pool
      • Advanced Pool
      • Basic Pool
    • Bonding Curve and Delta
    • Fee
    • Buy / Sell
    • APR
    • The Collection Whitepaper
    • Collection 1.00: Patch Notes
  • User Guides
    • Create a Trade Pool
    • Create a Buy Pool
    • Create a Sell Pool
    • Buy & Sell NFTs instantly
    • LP Strategy Guide
  • Technical Reference
    • NFT AMM
      • What Is A CollectionPool?
      • Differences Between Individual And Communal Liquidity Pool Model
      • How do I determine if a pool has sufficient liquidity to fulfil an order?
    • Fee Structure
      • Overview of the Fee Structure in NFT AMMs
      • Calculation and Collection of Fees
    • Royalties
      • How are royalties implemented?
      • Relation between Royalties and Fees in the AMMs
      • All Possible Royalty Scenarios
    • Airdrop Compatibility
      • Can Collection.xyz handle airdrops?
    • Pool Types
      • Definition of Pool Types In NFT AMMs
      • Comparison of Different Pool Types
    • Bonding Curves
      • Parameters of the bonding curves
      • Type of bonding curves
        • Linear Curve
        • Exponential Curve
        • Sigmoid Curve
      • How are the parameters used in each of the bonding curves?
      • Customizable spread curves
    • Github Repos & Addresses
    • Audit Reports
    • Technical User Flows
      • Technical Architecture
      • Create Pool
      • Swapping and Trading: User Buying NFT
      • Swapping and Trading: User Selling NFT
      • Bonding Curves and Pricing
Powered by GitBook
LogoLogo

Collection.xyz

  • Main Website
  • NFT DEX Testnet

Connect with us

  • Discord
  • Twitter
  • Blog

© 2023 Collection. All rights reserved

On this page
  1. Technical Reference
  2. Royalties

How are royalties implemented?

PreviousRoyaltiesNextRelation between Royalties and Fees in the AMMs

Last updated 2 years ago

The main on-chain implementation of royalties is ERC2981. ERC2981 is a standard that advises on a particular amount royaltyAmount and royalty receiver address receiver given a tokenId and overall salePrice. () For example, to say that royalties are 1% would be to input 10000 in salePrice and get 100 as the royaltyAmount

Other royalties numbers can be off-chain by collection owners on third party websites such as Opensea or Looksrare, but can only be gotten periodically and thus done on a error-prone best effort basis.

The advisory nature of ERC2981 makes it an incomplete solution. As the most widely adopted royalty standard at the moment, we integrate with it in a nuanced way: We use the derived royalty percentage as an override, while in order to prevent pool creators from siphoning off royalties from NFT collections maliciously, we allow royaltyRecipient to be set as a fallback, a place to be sent if the receiver is not set to any value, as per ERC2981

https://eips.ethereum.org/EIPS/eip-2981