Kusama Data on Dune+BigQuery (9 months, 7/1/25-3/31/26)

Deciding
Content
AI Summary
Reply
Up
Share
Request
9,055KSM
Status
Decision14d
Confirmation
2d
Attempts
0
Tally
35%Aye
65%Nay
Aye
70.69KKSM
Nay
131.4KKSM
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Support
0.15%
23.66KKSM
Issuance
16.24MKSM
Votes
Nested
Flattened
Actions
Or do delegation here, check wiki.
Call
Metadata
Timeline3
Votes Bubble
Statistics
Comments

PolkaWorld votes NAY

Our concerns remain consistent with those we raised in the Polkadot proposal.

In theory, facilitating collaboration between Polkadot and Dune is a positive step. However, in this proposal, the infrastructure costs alone (Dune + Google Cloud) total $197,440 USDC per quarter, accounting for over 83% of the total quarterly budget. We’d like to better understand the breakdown and justification for these expenses.

Additionally, while many X posts were cited to show community usage, a more meaningful approach—especially for a data analytics team—would be to provide concrete usage metrics from the past year to demonstrate impact. For example, data points like:

•	Total dashboard pageviews and most-visited datasets
•	Query counts across various parachains
•	Growth in active dashboard users over time
•	Volume and depth of user behavior insights derived from the platform

Moreover, the proposal lacks clearly defined outcome-oriented goals. The current objective seems to be “maintaining the existing service,” without any proactive efforts to drive usage or engagement through improved data offerings. This passive approach limits the product’s potential to support ecosystem growth.

Full feedback available here.

Reply
Up