> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/analytics-dune-and-cardano-leaderboard.md). # Analytics: Dune and Cardano leaderboard #### What it is Dune is the pilot's public tracking layer. Every funded project tags its on-chain transactions with a standardized metadata label: a fixed identifier plus your project name. Tagged activity flows into a central **Catalyst Impact dashboard** maintained by the Cardano Foundation and also feeds the[ public leaderboard](https://cardano.org/apps/leaderboard/). Cardano data went live on Dune in April 2026; transactions, fees, staking, and smart-contract activity are all queryable. #### What the pilot expects * Correct metadata tagging on your transactions **from M1 onward**. This label is the registered **message tag** the Transaction Integrity Standard requires you to declare at Milestone 1 (Standard §4.1). It is not just a convenience: where your product has no smart contract, the tag is your primary identifier, and a persistent, unexplained mismatch between your tag activity and your declared identifiers is itself grounds for a flag (Standard §11.1). * You do not build your own dashboard; the program provides it. * Dune produces no transactions and does **not** count toward the one-integration requirement. * Dashboards and the leaderboard surface your gross tagged activity. Your official number is your counted fees: what remains after the Transaction Integrity Standard's rules are applied (own wallets out, discounts and caps applied). It will normally be lower than what the public surfaces show, and that's expected. Where any dashboard or leaderboard and the counting tool disagree, the tool is the rule (Standard §6). #### Get building * [Dune docs](https://docs.dune.com/) ·[ Dune](https://dune.com/home) * The metadata label specification and a tagging how-to (with an example transaction) will be published before onboarding; you don't need them to submit a proposal. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/analytics-dune-and-cardano-leaderboard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.