Thonest Selftest called it:
“Thonest will publish a page titled 'Transparency Report' on thonest.com before September 30, 2026.”
We find out by Sep 30, 2026. 40 days to go · on the record 0 days, before anyone knew the answer
Open until 2026-09-30 — 40 days away. Settlement rests on public evidence, gathered and checked after the deadline.
Thonest Selftest: “Thonest will publish a page titled 'Transparency Report' on thonest.com before September 30, 2026.”
MET if A publicly accessible web page titled 'Transparency Report' is live on the thonest.com domain. Verified by direct observation of the live site or by an archived snapshot dated before the deadline. A page bearing a materially different title, an internal/unpublished draft, or a page first published on or after 2026-09-30 does not count at any point, before 2026-09-30 00:00 (UTC).
Resolves true if, at any time before 00:00 UTC on 2026-09-30, a publicly accessible page titled 'Transparency Report' exists on the thonest.com domain. Archived snapshots (e.g. Wayback Machine) or direct observation of the live page count as evidence. A page with a different title, or a page published on or after 2026-09-30, does not count.
Thonest does not settle this one automatically — there is no supported data source for it. A documented review applies these locked criteria against public evidence; the test is fixed, so anyone can check it and nobody can change what counts.
Written here by its author
Self-recorded by @thonest_selftest · Identity not independently verified
CONTROLLED PRODUCTION TEST by Thonest itself — created to verify automatic settlement end to end. Not a market view.
Resolution criteria
Resolves true if, at any time before 00:00 UTC on 2026-09-30, a publicly accessible page titled 'Transparency Report' exists on the thonest.com domain. Archived snapshots (e.g. Wayback Machine) or direct observation of the live page count as evidence. A page with a different title, or a page published on or after 2026-09-30, does not count.
History — append-only
Proof
2 hashes from this record to the anchored root
- 0xed319ca591a2ff72a2a87dc71fa68cdf0a2342b91b7517883d45ca7b2e256576
- 0xed222f1d90d63091abf3aa07c0e5b4030befc8719f62bf67225d3850707c0ef0
batch #49 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
0x5f91fd8f…c8b783 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 canonical capture · exactly what the author typed, kept verbatim and covered by the evidence hash
✓ The anchored proof cannot be rewritten, and the published record is append-only by default. Everything that happened afterward is in the history above — corrections are appended, never silently edited in.
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.