Open verification
Check Upvera without trusting Upvera.
Four checks you can run right now. They read public files and public endpoints, and they run in your browser or on your machine.
The day root chain
Fetches every day file from upvera-co/ledger-roots, checks that it is canonical, recomputes its SHA-256 digest and follows the prev links back to genesis (2026-10-13).
| Day | Root | Day digest | Rules in force | Status |
|---|---|---|---|---|
| 2026-10-21 | days@1 | |||
| 2026-10-20 | days@1 | |||
| 2026-10-19 | days@1 | |||
| 2026-10-18 | days@1 | |||
| 2026-10-17 | value.shadow@2 | |||
| 2026-10-16 | money@18 | |||
| 2026-10-15 | money@18 | |||
| 2026-10-14 | money@18 | |||
| 2026-10-13 | watch@13 |
The rule registry
Recomputes the chain of every rule version and finds the latest day file's rules_hash in it, so the rules in force are tied to a public, timestamped root.
54 rule versions, each chained to the one before it.
A value receipt
Fetches a live receipt from the public Value API and adds its rows in whole millionths. They must equal the change.
Receipt · Upvera · 24 hours
345.26359.93
+14.668908
- Worknew posts and shipping drew a response+12.539872
- Momentumnew events raised its pace against its own average+3.024910
- Peopleindependent people engaged+1.562561
- Peopletrust of the people engaging rose+0.995928
- Other7 small reasons−0.569189
- Catch-upvalue hasn't caught up with its new target yet−2.885174
A real receipt, served by the public Value API for Upvera's own startup. Captured 2026-10-22 12:01 UTC.
Offline, and your own record
The same chain check runs with Node and no network. OpenTimestamps proofs verify against Bitcoin with the standard client.
$ git clone https://github.com/upvera-co/ledger-roots
$ node ledger-roots/tools/days.mjs verify
$ pip install opentimestamps-client
$ ots verify ledger-roots/days/2026/10/2026-10-21.json.ots