What’s changing
New columnsEPOCH_NUMBER and SLOT_NUMBER are available alongside the legacy EPOCH and SLOT columns on April 9, 2026.
| Table (fully qualified) | Legacy columns (dropped April 20, 2026) | New columns |
|---|---|---|
beacon.raw.validator_duties | EPOCH, SLOT | EPOCH_NUMBER, SLOT_NUMBER |
beacon.raw.ideal_rewards | EPOCH | EPOCH_NUMBER |
beacon.raw.total_rewards | EPOCH | EPOCH_NUMBER |
EPOCH_NUMBER and SLOT_NUMBER match the same underlying data as EPOCH and SLOT before the drop.
Timeline
| Date | Milestone |
|---|---|
| Effective by April 9, 2026 | New columns EPOCH_NUMBER and SLOT_NUMBER are available alongside EPOCH and SLOT (rollout may be staged by environment). |
| April 17, 2026 | Please complete migration — Move queries, saved reports, models, and dashboards to EPOCH_NUMBER and SLOT_NUMBER (instead of EPOCH and SLOT) everywhere you control the logic, before the legacy columns are removed. |
| April 20, 2026 | Breaking change: Legacy columns EPOCH and SLOT are dropped (see What’s changing). Queries that still reference them will fail until updated. |
What this means for you
- Until April 20, 2026: Queries that use
EPOCHorSLOTcontinue to work; migrate in parallel usingEPOCH_NUMBER/SLOT_NUMBER. - From April 20, 2026:
EPOCHandSLOTwill no longer exist on these tables — you must useEPOCH_NUMBERandSLOT_NUMBER. - Recommended path: Prefer
EPOCH_NUMBERandSLOT_NUMBERin all new or updated queries and dashboards, and complete rewrites of existing logic by April 17, 2026 (see Timeline).
Suggested migration (at your pace)
| Horizon | Action |
|---|---|
| Short term | Inventory uses of EPOCH and SLOT; test with EPOCH_NUMBER / SLOT_NUMBER in parallel. |
| By April 17, 2026 | Switch references from EPOCH → EPOCH_NUMBER and SLOT → SLOT_NUMBER, validate results, and deploy. |
| April 20, 2026 | Legacy columns EPOCH and SLOT are removed — no further action possible except using the new column names. |