Minted Help Centre
  • 🚀Welcome to Minted Network
  • ⭐Getting Started
    • Essential NFT Terms
    • Do Your Own Research (“DYOR”)
    • Setting Up Your Wallet
    • User Profile
    • Setting Notifications
    • Earn with Minted
      • Listing Rewards
      • Trading Rewards
      • Claiming Listing & Trading Rewards
      • MTD Staking
        • Increasing Your Deposit and Upgrading Your Locking Period
        • Withdrawing and Harvesting
      • NFT Staking
  • 🎯Minted How-To Hub
    • Buying NFTs
      • Buying a fixed-price NFT
      • Bulk purchasing NFTs
    • Floor sweeping NFTs
    • Making an offer for an NFT
    • Accepting an offer
    • Listing an NFT for sale
    • Setting a lower price or cancelling a listing
  • 💡Creators
    • Listing Your Collection
    • Verification Badge
    • Launchpad
    • Royalties
      • Collections royalties verification
      • Using CronoScan to set royalties
      • Using Etherscan to set royalties
  • 👾MEMETED & INSCRIPTIONS
    • MEMETED
      • Make-Your-Own-Meme
      • Token Airdrop Tool
      • Verify your meme token
      • Add token image
      • Renounce ownership
      • Add liquidity
    • Inscriptions Marketplace Standard
  • ❓FAQs
    • General Questions
    • Troubleshooting
      • Error Message Directory
    • Fees
    • Wrapped Tokens (WCRO/WETH)
  • ⚒️DEVELOPERS
    • API Endpoints & SDK
      • List of Collection Stat
      • Collection Stat
  • 📑Docs
    • Brand Assets & Usage
    • Audits
    • Smart Contracts
    • Production IP Addresses
Powered by GitBook
On this page
  • Method 1
  • Method 2
  1. Creators
  2. Royalties

Using CronoScan to set royalties

PreviousCollections royalties verificationNextUsing Etherscan to set royalties

Last updated 1 year ago

NFT collection owners can adjust creator earnings on-chain with cronoscan.com.

Method 1

*For collections using the EIP-2981 standard.

  1. Launch in your preferred web browser.

  2. Enter the collection’s contract address in the Cronos Chain Explorer section.

  3. Click Contract in the Contract Overview section and select Write Contract.

  4. Click Connect to Web3.

  5. Scroll down the list and update the royalties setting section. *if you’re not able to find this section, consider using Method 2 below.

  6. Click Write to confirm the update.


Method 2

  1. Open the in your preferred web browser.

  2. Click on Connect to Web3 and note that functions are only executable by the smart contract owner or administrator.

  3. Select the function that is applicable to your role:

    1. updateRoyaltyInfoForCollectionIfAdmin: If your contract does not have an owner or setter, but it has an admin.

    2. updateRoyaltyInfoForCollectionIfOwner: If your contract does not have a setter, but it has an owner.

    3. updateRoyaltyInfoForCollectionIfSetter: If you have already set royalties previously and are currently editing them.

  4. Expand the function and you’ll be able to set the royalties for the entire collection.

  5. Fill in the required information for your selected function:

    • Collection address - Your collection’s contract address.

    • Setter address - The address that you would like to use to manage the collection. Can be the same as the owner or admin.

    • Receiver address - The address that receives your royalties. You’re not recommended to input the same address for both the receiver and setter fields, as this would cause a potential operational security risk.

    • Fee - The royalty percentage that you would like to receive in uint256 standard. E.g. 500 = 5%, 1,000 = 10%.

  6. Click Write to submit. You will then be asked to pay gas fees and confirm the transaction in your wallet.


Disclaimer: Minted bears no responsibility or obligation to set royalties for collections listed on our platform. For collections where royalties have not been set by the collection owners, Minted will not set, accrue, charge or collect royalties on behalf of the collection owners.

Creator royalty above 13% will cause a bad_request error. See for more information.

💡
CronoScan
royalties setter
What are the potential causes of BAD_REQUEST error?