bytenews.io

Archive About
English

Calendar

What is scheduled, and how each date is known. Every row says where it came from: read from a contract, published by the institution that sets it, typed here with a source, or observed happening. Dates that have passed stay on this page with what actually happened beside them.

13scheduled ahead
18on the record
—observed happening

Nothing is being watched on chain yet. None of the dates on this page names an address we could watch, so no unlock here has been seen happening — and that is why the third figure is a dash rather than a zero. A zero would say we watched and nothing moved.

Scheduled

WhenEventHow we knowSourceWhat happened
CPIConsumer Price Index for September 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for October 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for November 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—

On the record

WhenEventHow we knowSourceWhat happened
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for August 2026Published schedulebls.gov—
CPIConsumer Price Index for July 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for June 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for May 2026Published schedulebls.gov—
CPIConsumer Price Index for April 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for March 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for February 2026Published schedulebls.gov—
CPIConsumer Price Index for January 2026Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
CPIConsumer Price Index for December 2025Published schedulebls.gov—
CPIConsumer Price Index for November 2025Published schedulebls.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—
FOMC decisionRate decision, announced at the end of a 2-day meetingPublished schedulefederalreserve.gov—

The last 365 days. Earlier events are in the download — the published schedules reach back years and the file keeps all of it — but they are not this site's record and are not shown as one. “What happened” is filled for events this site watches on chain. A macro release is not one of them: we carry the date, not the print.

Where the published rows come from

DownloadCSVJSONIntegrity report69 rowshttps://bytenews.io/api/v1/calendar.jsonAPI & rate limit

How complete is this?

No recorded gaps in the last 14 days.

Every dated event this site knows about, in all four provenance classes, past ones included. It is NOT a complete unlock calendar: contract-read unlocks are an allowlist of contracts whose shape is standard, and no third-party unlock list is imported. The `observed_*` columns are filled only for rows whose address this site watches.

0recorded gaps
0minutes not looking
—thin or empty days
0corrections issued

When we were not looking

Nothing recorded in the last 14 days.

Days that are not a day’s worth

This dataset is not a continuous record: a day with nothing on it is a quiet day in the world rather than a gap in ours, so no per-day expectation is stated.

What produced these rows

Corrections

None issued against this dataset.

Our own downtime, inside this window

Anything known to be wrong?

5 problems are open in this site’s own checks; none of them is about this dataset.

Assembled from records this site already keeps — the gap ledgers, the corrections record, the incident record and the gate’s own tally. It adds no new collection. The same report ships with the download as /api/v1/calendar.integrity.txt and inside the JSON. What this site cannot see at all.

This is not a complete unlock calendar and does not try to be. Contract-read unlocks are limited to contracts whose shape we can read directly; no third-party unlock list is imported, because a date republished from somebody else inherits their errors and cannot say where it came from.