Urd Atlas methodology
Publication Freshness Policy
Expected publication lag by chain, soft-warning and hard-fail boundaries, and how freshness should be interpreted alongside confidence.
Current public freshness policy
| Chain | Expected lag | Soft warning | Hard fail |
|---|---|---|---|
| Bitcoin | 1 day | > 2 days | > 4 days |
| Ethereum | 1 day | > 2 days | > 4 days |
| Arbitrum | 7 days | > 10 days | > 15 days |
| Base | 7 days | > 10 days | > 15 days |
How to read freshness correctly
Freshness and confidence are related but different. Freshness tells you how current the supporting row is relative to expected publication cadence. Confidence tells you how much evidence supports the analytical state of that row.
- A row can be on schedule and still low-confidence.
- A row can be delayed and still mathematically valid as the latest available state.
- A degraded label means the confidence gate prevented a normal-confidence named label, not that the raw files necessarily disappeared.
Freshness fields
updated_through= latest Gold observation date actually available to the Meta calculationlag_days_vs_asof_date= publication-time freshness relative to the row datelag_days_vs_utc_today= runtime freshness relative to the current UTC date