Standardised (Base) Analytics & KPI Reconciliation

[b3nedictvs]

Is your feature request related to a problem? Please describe.
Fragmented Base network data prevents accurate performance reporting for retroactive funding. Current Dune dashboards lack methodology for tracking unique wallets, non-ETH treasury assets, and canonical DAO deployment counts.

Describe the solution you'd like
Implement a high-density analytics suite on Base using the following data types and requirements:

• Total Transactions: Single-query aggregation of bids, settlements, proposals, and votes using varbinary (hashes) and timestamp (block time).
• Treasury Visibility: Real-time tracking of ETH and ERC-20 balances using uint256 (raw values) and address (contract mapping).
• Unique Engagement: Metric for Unique Active Wallets (UAW) using address (distinct voter/bidder/proposer identification).
• DAO Classification: Standardised varchar flags to filter "Live" vs "Test" vs "Migrated" DAOs.
• Valuation Accuracy: Conversion of non-ETH treasury assets into current USD value using decimal (precision-adjusted price feeds).

Describe alternatives you've considered

• Manual scrubbing of disparate Dune tables (non-reproducible).
• Off-chain tracking (lacks transparency for grant verification).

Additional context

• Original Report Links:
  • https://fractalnouns.notion.site/data-reporting-gaps
  • https://fractalnouns.notion.site/dune-data
• Baseline (2023–2025): 89 launches, ~60.5 ETH revenue, 1,360 proposals, ~119 avg monthly voters.
• https://dune.com/0xsatori/nouns-builder
• https://dune.com/sealaunch/nouns-builder-protocol?utm_source=substack&utm_medium=email