Skip to main content

Data updates

Changes to Dune’s base, decoded, and curated tables: new datasets and columns, schema changes, methodology updates, fixes, and deprecations.
This page tracks changes to the data itself. For product and platform updates, see the product changelog. For live operational status, see status.dune.com. For persistent data caveats, see known issues.Subscribe to this page’s RSS feed to get every entry as it is published.

Breaking changes

  • kalshi.ohlcv_hourly: candles stop at settlement. Forward-filled candles after settlement are removed and market_end_time now marks the final candle. Update queries that relied on post-settlement rows.
  • polymarket_polygon.market_details: columns retyped. Eleven varchar columns become native booleans, timestamps, integers, and arrays; the Snowflake datashare follows. Remove text casts, and markets previously dropped by the type mismatch reappear in polymarket_polygon.ohlcv_hourly.
  • Stablecoin tables are now a premium dataset. Free public access to the stablecoins_* schemas ended on August 3; provisioned teams are unaffected.

Fixes

  • polymarket_polygon.market_trades: missing trades restored. Trades on tokens the original exchange contracts never listed were dropped; historical volumes from late June onward revise upward.
  • tokens_xrpl.transfers: issued-token transfers complete. Every successful issued-token balance change is now covered (payment paths, offers, AMMs, issuance, redemption); holder histories change.

Deprecations

  • tokens_{chain}.balances_daily_agg removed. Replaced by the premium balances_<chain> dataset (latest, updates, daily_updates), which carries a different schema. Migrate queries that reference the removed tables.

Methodology

  • Stablecoins: finer entity subcategories. address_subcategory now distinguishes custodians, prime brokers, market makers, derivatives exchanges, issuers, lending desks, and wallet providers instead of a single cex bucket; aggregations grouped by subcategory shift.

New data & improvements

  • Entity labels: enriched address dataset. The new entity_labels_evm.addresses_enriched table serves one row per address with the owner’s identity inline, including wallet-level role_tags, so reading a label needs no join.