Counterparty Trade Data on Market Cap Websites

[davestaxcp]

I have a goal of adding Dispenser/Dex/Emblem/AtomicSwap data to Coinmarketcap (and other large info sites)

ex:

• https://www.coingecko.com/en/nft/global-stats
• https://coinmarketcap.com/nft/

(probably a few others worth applying to)

---

rarepepe last sale price marketcap:

notice how Dan uses 'match-type' to differentiate where and how it was sold on xcp.io by clicking the 'trade history' button

the entire Rare Pepe Directory last sale is worth 1/4B alone and would instantly effect these charts and data shown on the websites above

and by the way if this could be done everyone is about to 'suddenly' realize we exist
prepare your tg mods

---

but we need a solid API source for all the price data which includes:

• DEX order matches
• Dispenses
• Emblem Vault purchases
• Atomic Swap Completed Trades

---

Best one I can find so far is used on xcp.io by Dan
(but it doesnt include Atomic Swap data)

https://dune.com/droplister/counterparty-nfts

=

https://www.xcp.io/asset/RAREPEPE?view=trade-history

---

What else can you think of that we would need to submit this data to these market cap websites?

---

Whats the best plan to keep it avaliable to run for these big websites for the long haul?

---

[davestaxcp]

leaving this response from Grok AI here because the process for this seems WAY out of my wheelhouse...

is this something we need to raise a bounty for? so that someone in the community takes it seriously as soon as possible?

seems like the process needs to be started ASAP with weeks and weeks of reliable data before any of these big marketcap websites will take it seriously (even though the data is 10+ years old)

also I see endpoints like '/collections' ... I doubt that even exists on a protocol level? Maybe something Dan just added for xcp.io and the Dune data?

are we going to have to take care of this first?:
#150

---

---

---

Proposed Process to Build a Counterparty NFT Trade API and Get It Listed on CoinGecko & CoinMarketCap

1. Build the API (Realistic Timeline: 2–4 months)

Step-by-step plan:

1. Data Layer (4–12 weeks)

   • Option A (fastest): Extend the existing Dune Analytics dashboard by @droplister to include Atomic Swaps, Emblem Vault purchases, and dispensers.
   • Option B (recommended for long-term reliability): Run a lightweight indexer using counterparty-core + PostgreSQL. Index all relevant events (order matches, dispensers, atomic swaps, etc.).

2. API Layer (2–4 weeks)
   Build a simple, public REST JSON API (e.g. FastAPI or Express).

   Required endpoints (designed to match CoinGecko’s ideal integration spec):

   • GET /collections – list of collections with floor price, 24h volume, market cap, total supply, image_url, etc.
   • GET /collections/{slug} – detailed collection data + historical stats
   • GET /sales/recent – latest completed trades with timestamps and USD prices
   • GET /market – global Counterparty NFT volume and market cap

   All responses must be public (no API keys), well-documented (OpenAPI/Swagger), and include USD pricing.

3. Hosting & Reliability

   • Deploy on a stable platform (Railway, Render, Fly.io, or VPS).
   • Maintain 99.9%+ uptime with monitoring and caching.
   • Run the API publicly for 4–8 weeks to prove stability before submission.

4. Ongoing Maintenance
   A dedicated maintainer (or small community grant) is required for long-term success.

2. Submission Process

Primary Target: CoinGecko (much more receptive to NFTs)

• Use the official NFT listing form: https://support.coingecko.com/hc/en-us/articles/8429568680729-How-to-list-NFTs-on-CoinGecko
• Submit Rare Pepe first (as the flagship collection) or pitch the entire “Counterparty NFT Marketplace”.
• Provide:
  • Link to live, public API + full documentation
  • Screenshots of volume and potential market cap (~$250M for Rare Pepe directory)
  • Clear narrative about Counterparty being one of the very first NFT projects (on-chain since 2016)

CoinMarketCap

• Use the general request form: https://coinmarketcap.com/request/
• Expect slower response.

3. How to Make Acceptance as Easy as Possible

• Mirror CoinGecko’s exact JSON field names and structure.
• Keep the API public, fast, and always available.
• Run it live for 1–2 months beforehand and show consistent uptime + real data.
• Include a responsive contact email.
• Emphasize historical significance + aggregated market-cap potential.

4. Expected Probability & Timeline

CoinGecko

• Probability: 35–55%
• Time from submission to live (if accepted): 2–8 weeks
• Main deciding factor: API quality + narrative

CoinMarketCap

• Probability: 20–35%
• Time from submission to live (if accepted): 1–3 months
• Main deciding factor: Demonstrated volume

Biggest risk: Low and inconsistent daily volume.
Biggest opportunity: The “original NFT project” story combined with a large aggregated market cap could make this very attractive.

This is very achievable if the community supports one motivated developer to build and maintain the API.

[droplister]

I don't think this is a protocol-level concern.

[adamkrellenstein]

Yeah definitely not. I'm not sure if "CIP" is correct. But it's definitely an important community issue which we can discuss on this forum IMO.

[davestaxcp]

No it is not related to the protocol code, but getting the protocol seen.
I did not label it as a 'CIP', simply a general discussion.

I find this extremely important and will 'improve Counterparty' in the big picture social sphere and would be happy if this was taken more seriously.

Just influenced from the posts of others to share: #85