Due in 28 days, on 2026-09-16. Settlement rests on public evidence, gathered and checked after the deadline.
Justin Kompf: “The Fed will maintain the interest rate in their September decision”
“The Fed will maintain the interest rate in their September decision”
MET if The FOMC's official policy statement concluding its September 2026 meeting (scheduled September 15-16, 2026) announces no change to the target range for the federal funds rate relative to the range in effect immediately before that meeting. Any announced hike or cut of the target range counts as FALSE; changes to other tools (IORB technical adjustments, balance-sheet policy, discount rate) do not by themselves count as a change, and dissenting votes do not count if the announced target range is unchanged. on the deadline date, before 2026-09-16 23:59 (America/New_York).
Resolves TRUE if the Federal Open Market Committee, in the official policy statement issued at the conclusion of its September 2026 meeting (scheduled September 15-16, 2026), leaves the target range for the federal funds rate unchanged from the range in effect immediately before that meeting. Resolves FALSE if the statement announces any increase or decrease in the target range. The FOMC's own published statement is the settling document.
Thonest does not settle this one automatically — there is no supported data source for it. The test is fixed all the same, so anyone can check it and nobody can change what counts.
Written here by its author
Self-recorded by @justin · Verified identity
Resolution criteria
Resolves TRUE if the Federal Open Market Committee, in the official policy statement issued at the conclusion of its September 2026 meeting (scheduled September 15-16, 2026), leaves the target range for the federal funds rate unchanged from the range in effect immediately before that meeting. Resolves FALSE if the statement announces any increase or decrease in the target range. The FOMC's own published statement is the settling document.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0x2aa79c8a6a5c93d749d71b87ca94126e2eeb6e5c16c8735a72905c3095c5b938
- 0x773622ebecc72404b27fb82a7023d9d0aa20d4d6e92e02f75a089a546b1a9c2f
batch #18 manifest · 4 entries
the contract refuses any batch that doesn’t follow the previous one, and has no function to edit or delete one — including for us
0x851b7827…a927db on block explorer
There is nothing external to check this against. What the anchor proves is the time it was written, which is the point of recording a claim before its outcome is known.
An archive copies a page that already existed somewhere else.
the Thonest account that wrote this — not a claim about who controls it unless the identity level above says so
view the raw response · exactly what the author typed, kept verbatim and covered by the evidence hash
✓ The original record is immutable. Everything that happened afterward is in the history above — nothing is ever silently edited.
The check runs in your browser and reads the anchored root straight from a public Base node — not from Thonest. How this works.
Disputes
No disputes have been filed. If something here is wrong — a misquote, a wrong date, a misattributed source — say so and it gets answered on the record. How disputes work.