Rarible vs SuperRare: Contract Standards, Royalties, and Indexing Differences

Rarible and SuperRare offer some top-notch NFT experiences, but they take different paths when it comes to contract structures, royalty enforcement, and data indexing. In this deep-dive, we'll break down the key trade-offs for product, engineering, and business leaders who are figuring out the best approach for their next NFT project.

---

TL;DR for decision‑makers

• Go with Rarible if you're after multichain support, a marketplace that pulls together various options, the ability to execute order flows, and some solid choices for enforcing hard royalties via the RARI Chain (Ethereum L3). Check it out here: (docs.rarible.org).
• Pick SuperRare if you’re looking for curated ERC‑721 primary markets, a standard 10% creator royalty through the SuperRare protocol, and a neat GraphQL for diving into platform-native analytics. Find more details here: (docs.superrare.com).

---

1) Contract standards: how tokens are minted and represented

Rarible: ERC‑721, ERC‑1155, lazy minting, and protocol contracts

• Token standards: Rarible plays nicely with ERC‑721 and ERC‑1155 on EVM networks. Check it out here.
• Core contracts (Here are some examples from the Ethereum mainnet):
  • ERC721Rarible: 0xc9154424B823b10579895cCBE442d41b9Abd96Ed
  • ERC1155Rarible: 0xB66a603f4cFe17e3D27B87a8BfCaD319856518B8
  • ExchangeV2: 0x9757F2d2b135150BBeb65308D4a91804107cd8D6
  • RoyaltiesRegistry (this one's for EVM-wide royalty resolution): 0xEa90CFad1b8e030B8Fd3E63D22074E0AEb8E0DCD (more info here).
• Lazy minting: This cool feature uses signature-based minting to delay on-chain creation until someone makes a purchase. It's available on Ethereum under Rarible’s shared collections, which keeps gas fees off the creator and helps gauge demand before diving in. Learn more about it here.
• Royalty interfaces supported at the exchange layer include Rarible RoyaltiesV1, RoyaltiesV2, and ERC‑2981. This enables the protocol to discover and pay royalties, even for contracts that are minted externally. Get all the details here.

Why It Matters

When it comes to shipping mass collections or game assets, ERC‑1155 is definitely the way to go because it’s more cost-effective. You can batch mints and transfers, which saves you some serious cash. On the other hand, if you’re dealing with unique items (1/1s) or smaller editions where provenance is key, ERC‑721 does the trick just fine. The cool thing? Rarible has got your back with support for both standards!

SuperRare: ERC‑721‑only with shared “SuperRare” and sovereign/series contracts

• Standard: SuperRare sticks to the ERC‑721 standard since it's all about that unique 1/1 art vibe. You can dive into more details here: (help.superrare.com).
• Shared V2 contract (also known as “SUPR” on explorers): Check out the address 0xb932a70A57673d89f4acfFBE830E8ed7f75Fb9e0. This is the official, verified ERC‑721 contract for SuperRare V2--pretty cool, right? (etherscan.io).
• Series/Sovereign contracts: Artists and Spaces can create their own branded ERC‑721 minting contracts. This way, they can keep their unique style and provenance intact while still being part of the SuperRare family. Get more info here: (help.superrare.com).

Why It Matters

If you're working with curated 1/1 art or exclusive primary drops that come with a gallery vibe, then SuperRare’s use of ERC‑721 and their emphasis on provenance really fits the bill.

---

2) Royalties: standards, enforcement, and edge cases

The standards landscape

• ERC‑2981 serves as the go-to interface for checking royalties, but keep in mind that it’s just for info; it's up to the marketplaces to decide whether to actually pay out. It gives you one recipient and the amount based on the sale price. (eips.ethereum.org)
• A lot of platforms also tap into older interfaces like Rarible Royalties v1/v2 or a Royalties Registry to figure out overrides and splits. (docs.rarible.org)

Rarible’s approach

• Multi-standard support: Rarible ExchangeV2 taps into RoyaltiesV1, RoyaltiesV2, and ERC‑2981. This means that when trades go down through the protocol, royalties get paid out automatically. You can check out more details here.
• Set/override royalties:
  • In-app: You can easily add recipients and basis points right in the app (it's compatible with EIP‑2981, so it applies to trades on Rarible). For guidance, take a look here.
  • Externally: If you're feeling adventurous, you can write to the RoyaltiesRegistry through Etherscan (for both ETH and Polygon) to handle things at the collection level. Find out more about this process here.
• Policy toward marketplaces: Back in 2023, Rarible made the choice to stop aggregating orders from marketplaces that turned off royalties. Fast forward to 2025, and their docs now show that API/front-end aggregation includes OpenSea listings again (just the Blur activity for now). If you’re depending on cross-market liquidity through Rarible’s API, be sure to check what the current aggregation scope looks like during your integration. More details can be found here.
• Hard enforcement option: Enter RARI Chain, which uses Ethereum L3 and Arbitrum tech to introduce node-level royalty checks for ERC‑721/1155 transfers. If any transactions try to bypass the specified royalty payments, they’ll revert--this shifts royalties from being just a “best practice” to a “protocol rule.” For creators and brands looking to guarantee revenue share, this is the cleanest on-chain enforcement you can find right now. Check it out here.

Practical Implication

When it comes to Ethereum L1 and most L2s, royalties are still more about policy than protocol--they're not strictly enforced. If you're looking for a surefire way to guarantee royalties in secondary markets, consider minting and transacting on RARI Chain. You can also bridge in while keeping your ERC‑2981 metadata intact. Check it out at rarichain.org!

SuperRare’s approach

• So, here’s the deal with creator royalties: there’s a default of 10% on secondary sales when you're using the SuperRare protocol. Any works minted after the current Terms kick in will automatically go into the Royalty Registry at that 10% rate (but artists can tweak this in specific situations). On top of that, buyers usually have to cough up a separate marketplace fee, which you’ll often see as around 3%, going to the DAO. When it comes to primary sales, 85% goes straight to the artist, while 15% heads over to the SuperRare DAO. (campaigns.superrare.com)
• Now, about the Royalty Registry: SuperRare has rolled this out for certain contracts. Just a heads up, though--some of their support docs mention that the registry overrides won’t apply to certain V2 tokens. This is important to keep in mind if you’re looking to reroute royalties after minting. (help.superrare.com)
• Here’s something new: collector royalties! The first collector can snag a 1% decreasing royalty that’s funded by the SuperRare network fee (not touching that artist’s 10% at all). This kicks in during the first secondary sale where the first collector isn’t involved (think mint sale +2). It’s a nice way to boost early demand for primary sales while ensuring creators keep their earnings intact. (medium.com)
• Let’s break down an example split: for some drops like RarePass, there’s a clear secondary split (think 45% for artists / 45% for DAO / 10% for the company) coming from that 10% royalty. Just make sure your legal and integrator teams are on the same page with these specific splits. (campaigns.superrare.com)

Practical Implication

SuperRare makes sure that creator royalties are enforced right at the protocol level for any trades that go through their platform. But if you’re trading on a different platform, it really comes down to that venue's own policy and whether they respect the Royalty Registry. You can check out more about this here.

---

3) Indexing and APIs: how you’ll ship data‑rich experiences

Rarible API and indexer

• Scope: We're talking about a multichain NFT indexer that covers ownership, metadata, search functionality, and live market data (like order books and bids) across major marketplaces. It’s like having a one-stop shop for all your needs, plus there's CDN-backed media delivery to ensure quick access. Check it out at (rarible.org).
• Supported marketplaces: According to the docs (which are expected to be updated by mid-2025), you can find listings from Rarible and OpenSea, along with activity tracking from Blur. Just remember to double-check the current coverage as you build. More details can be found here: (docs.rarible.org).
• Scale: Rarible has some ambitious plans! They’re aiming for up to 20 million requests a month, with 100 requests per second and a solid 99.99% uptime. This is crucial for consumer apps and analytics dashboards. See their pricing options at (rarible.org).
• Indexer performance: Rarible has put out some pretty detailed tuning notes for their indexer (think Kafka pipeline, time-marks, and node selection) to reduce the mint-to-index latency and tackle spam on Polygon. This info is super valuable for architects who are working on SLAs. Dive into the details here: (docs.rarible.org).

Takeaway: If you're on the hunt for cross-chain search, floor tracking, and transaction building all wrapped up in one SDK/API that can handle production-grade rate limits, Rarible’s stack has got you covered. Check it out at rarible.org!

SuperRare Public API (GraphQL)

• Scope: This is all about the GraphQL endpoint for NFTs, collections, sales, auctions, and events in the SuperRare ecosystem. You’ll find fields like universalTokenId, along with profiles for creators and owners, plus the auction state. Check it out here.
• Rate limits: The standard tier lets you make 5 requests per minute. So, definitely keep caching and pagination in mind while you work with it. More details can be found here.
• Currency support: When diving into the marketplace docs, you'll notice support for currencies like ETH, USDC, and $RARE splits on listings. If you want to learn more, head over to this link: here.

Takeaway: This is fantastic for tailored experience analytics and its built-in marketplace features; however, it’s not designed to be a wide-ranging NFT aggregator.

---

4) Concrete examples you can reuse

A. Query SuperRare activity with GraphQL

Check out SR’s public playground to give it a spin. Just keep in mind the rate limit, and don’t forget to paginate!

# Recent events with basic NFT context
query GetRecentNftEvents {
  getNftEvents(filter: {}, pagination: { take: 10 }) {
    events {
      eventType
      createdAt
      nft {
        universalTokenId
        contractAddress
        tokenId
        metadata { name }
      }
      agent { defaultAddress }
      patient { defaultAddress }
    }
  }
}

The result fields line up perfectly with the documentation (think eventType and agent/patient actors). Make sure to cache like crazy in production. Check it out here: (help.superrare.com)

B. Resolve and set royalties for a Rarible‑indexed collection

• First things first, make sure your NFT is using ERC‑2981 (royaltyInfo) and/or Rarible Royalties v2. If it doesn't, you can still register your collection's recipients in the RoyaltiesRegistry using the verified proxy contracts on ETH or Polygon. Check it out here: (docs.rarible.org).
• If you've minted your collections through Rarible, setting up royalties is a breeze! You can do it right in the UI (it's EIP‑2981 compatible), and Rarible’s Exchange will take care of it for any protocol trades. Need guidance? Take a look: (help.rarible.com).

C. Hard‑enforce royalties by design: deploy on RARI Chain

• RARI Chain performs royalty checks right at the node level for ERC‑721 and ERC‑1155 transfers. If a transaction doesn’t meet the required royalty payments, it simply reverts. So, if you're gearing up for a marketplace launch and want to ensure creators get their revenue, you can either mint and settle directly on RARI Chain or bridge your assets in while keeping ERC‑2981 intact. Check it out at (rarichain.org).

D. Lazy mint to de‑risk gas on primary drops (Rarible)

• Turn on “Free minting” for Ethereum to let users list items and mint them when they buy. This approach cuts down on initial costs and can boost conversion rates, especially for experimental or niche products. Just keep in mind that items won’t show up on different markets until they're minted after the purchase. (help.rarible.com)

---

5) Emerging best practices (late‑2025)

• Combine ERC‑2981 with a registry: Start by implementing ERC‑2981 in your contracts and then register any overrides in a Royalties Registry. This combo allows for multi-recipient splits and post-mint routing, which really amps up your cross-market compatibility. Check it out here: (eips.ethereum.org).
• Decide early on enforcement vs reach:
  • If you want guaranteed payouts, then RARI Chain is the way to go for on-chain enforcement. You can find more info here: (rarichain.org).
  • On the flip side, if you're aiming for the widest secondary reach, consider using ERC‑2981 alongside a registry on Ethereum mainnet/L2. Just remember to plan for different marketplace policies.
• Engineer for indexer realities: If you’re looking for that real-time user experience after mints or listings, you’ll want to design with Rarible’s speedy indexer in mind and publish SLAs accordingly. If not, a good fallback is to cache SuperRare GraphQL responses and set up queues for hydration. Need more details? Check out this link: (docs.rarible.org).
• Communicate royalties clearly to collectors: If you're tapping into SuperRare’s 1% Collector Royalty (which comes from network fees), make sure to highlight this benefit on your primary drop pages. It’s a great way to encourage early buys without cutting into artist royalties. You can read more about it here: (medium.com).
• Verify marketplace aggregation at build time: Just a heads up--Rarible's 2023 stance put a pause on aggregation from certain venues, but their 2025 docs show that OpenSea listings are back in the game, while Blur listings still aren’t. It’s crucial to check the docs and run end-to-end tests before you go live. Get all the details here: (theblock.co).

---

6) Decision guide by use case

• Brand/gaming drops with tons of items across chains:
  • Check out the Rarible API combined with ERC‑1155 for some serious scaling. You’ve got the option for lazy minting, plus the Execute API to help with order building. And if royalties need to be locked in, consider using the RARI Chain. (docs.rarible.org)
• Fine art, curated 1/1s, gallery partnerships:
  • For something more polished, SuperRare Spaces or Series contracts are the way to go for brand-aligned ERC‑721s. They come with a standard 10% royalty, fees that sync up with DAOs, and a super helpful events API. (docs.superrare.com)
• Data products and analytics:
  • When it comes to data, Rarible’s got your back with multichain and multi-market floor/activity insights. And for a deeper dive into the artist/auction context, check out the SuperRare API. (rarible.org)

---

7) Implementation pitfalls to avoid

• Just a heads up: While it’s a good bet that all SuperRare tokens will work with Royalty Registry overrides, the SR docs do mention that the Registry might not play nice with some V2 tokens. So, make sure to double-check before you start rerouting any addresses. (help.superrare.com)
• Don’t underestimate those rate limits! SuperRare’s public API on the standard tier will only let you make 5 requests per minute. So, it’s a smart move to batch, cache, and paginate your requests. Rarible might offer higher limits, but it’s still wise to plan for retries and implement a backoff strategy. (help.superrare.com)
• Keep an eye on how marketplace policies are changing! Since 2023, royalty enforcement has been in flux. If you’re building for cross-market royalties, it’s best to stick with standards like ERC-2981 plus the registry. And you might want to consider anchoring your trades on RARI Chain for those guaranteed payouts. (theblock.co)
• Don’t expect to see lazy-minted items pop up everywhere right away! They aren’t officially on-chain until someone makes a purchase, which is why aggregators can’t index them just yet. Make sure to communicate this clearly in your user experience. (help.rarible.com)

---

8) Quick reference: what’s unique right now

• Rarible
  • They've got this awesome multi-standard royalty setup (Royalties v1/v2 + ERC‑2981) baked right into the exchange. Check it out here: (docs.rarible.org)
  • The RARI Chain features node-level royalty checks which means the rules are set in stone. Learn more at: (rarichain.org)
  • Plus, they offer a multichain indexer with executable market data and some serious enterprise-grade quotas. More info at: (rarible.org)
• SuperRare
  • They keep things simple with a default 10% creator royalty, all managed on the protocol side of their curated ERC‑721 network. Dive into the details here: (campaigns.superrare.com)
  • Their Spaces/Series feature lets you have branded ERC‑721 contracts within SuperRare’s curated model. It's pretty cool. Check it out: (docs.superrare.com)
  • And there's a new Collector Royalty incentive for those early buyers, funded straight from network fees. Get the scoop here: (medium.com)

---

9) If you asked us to pick (contextual recommendations)

• Got an enterprise IP and strict rev-share goals? Ship on RARI Chain to make those royalties a must-have. If you want to get discovered on Ethereum too, just mirror your listings through bridges while keeping that ERC‑2981 metadata intact. Check it out here: (rarichain.org).
• Running a museum or gallery and want to keep curatorial control? Use a SuperRare Space to launch! You can set your own commissions and schedules, plus you get to take advantage of SR’s standard 10% creator royalty and their auction features. More details here: (docs.superrare.com).
• If you’re building a consumer app and need wide coverage and search capabilities, consider integrating the Rarible API as your main indexer and data layer. You can also enhance it with SuperRare’s GraphQL for more detailed SR-specific insights. Dive in here: (rarible.org).

---

Appendix: standards you’ll likely touch

• ERC‑2981 (royaltyInfo): This allows a straightforward royalty lookup for a single recipient, which is pretty handy for markets. If you want to handle splits with multiple recipients, it’s best to pair it with a registry. Check it out here: (eips.ethereum.org).
• EIP‑712 (typed signatures): This one’s become a go-to across different marketplaces and lazy mint processes. It’s super relevant for things like order signing and making gasless listings smooth and user-friendly. More info can be found here: (eips.ethereum.org).

---

By carefully choosing your contracts (like ERC‑721 or ERC‑1155), figuring out your royalty approach (whether you go for policy or protocol enforcement), and deciding on your indexing strategy (will it be an aggregator or a curated API?), you can deliver NFT products that are not only friendly for creators but also scalable for operations. Plus, this way, you’ll sidestep the pitfalls that have caught many teams off guard between 2023 and 2025.