Root InsideROOT INSIDE
Record seals · daily-updated status

The time of our records is attested by three independent clocks — not by our word.

Every day Root Inside signs a fingerprint of its core records (review, decision and agent-work ledgers) and pins that fingerprint in Bitcoin and with an independent time-stamp authority. This page shows the result as-is. A seal proves the state of the records at that time, not that their content is correct.

Our signature
2026-10-16T17:10:48+09:00
key 29b8c0462adbc700 · seal #897
Time-stamp authority
Oct 16 08:10:53 2026 GMT
https://freetsa.org/tsr
Bitcoin block
Pending confirmation (usually hours)
3 external receipts (Bitcoin pending, Bitcoin confirmed and TSA tokens counted separately)
Latest seal
cc1a13b7d1b9113518705e4eb4cee04b2e131a03c0205f551bc932b1cd72a29e
— h ago (as of now) · status at 2026-10-16T17:10:48+09:00 · self-verify failed · 183 seals so far
Public-key fingerprint (SHA-256)
29b8c0462adbc700b147b634e18021fb58e34478272be5a56547d7aa4e7889d8
SHA-256 of the raw 32-byte key (not of the PEM file): openssl base64 -d -in pubkey.pem | tail -c 32 | shasum -a 256 (macOS and Linux). The same value is posted on GitHub (ri-seal README) — the two must match.
Check it in this browser

One button checks the signature and the hashes.

What is published and what is not
PublishedNot published
  • Seal hash
  • Signature
  • Public-key fingerprint
  • Signing time
  • External receipts (Bitcoin, time-stamp authority)
  • Hash and size of each sealed file
  • Row counts (these reveal the amount of activity)
  • Record contents
  • Internal file paths (replaced by opaque IDs from the next seal on)
  • Private key
  • Personal data

This is not a system where encrypted content is opened with a key — what is published is only evidence that the record existed and has not changed.

There is no token or coin.

Runs inside this browser. It fetches only this site's public files and sends nothing anywhere.
Check a downloaded bundle: drop latest_seal.json, latest_seal.bin and pubkey.pem (optionally .ots and .tsr) here, or . Files are read in this browser only and are not uploaded (2 MB per file).

This shows the state of the record; it does not vouch for whether the content is right or for any investment performance.

Verify it yourself

Verifiable with public tools alone, without any involvement from us.

  1. Bitcoin: drop the .ots and latest_seal.bin files below onto opentimestamps.org; it prints the block number. It should match the block linked above.
  2. Time-stamp authority: openssl ts -verify -data latest_seal.bin -in latest_seal.tsr -CAfile cacert.pem -untrusted tsa.crt (certificates from freetsa.org/files) → Verification: OK
  3. Our signature: verify the DSSE envelope (in-toto Statement v1) in latest_seal.json against pubkey.pem with any DSSE verifier or a short script (PAE: DSSEv1 len(type) type len(body) body).
  4. shasum -a 256 latest_seal.bin must equal the seal hash above.
latest_seal.binSeal bytes (what was time-stamped — its sha256 is the seal hash)latest_seal.jsonSeal row (DSSE envelope)pubkey.pemPublic keylatest_seal.pending.otsBitcoin proof (.ots, pending)latest_seal.tsrTime-stamp authority token (.tsr)VERIFY.mdHow to verify
Open source · ri-seal

The sealing method behind this page (work receipts → signed seals → external time anchors → third-party verification) is published as a standalone tool so that anyone can apply it to their own AI-agent work. Licensed under Apache-2.0, with no server and no telemetry; it records SHA-256 fingerprints, never file contents. Repository: github.com/leekangyeop-cpu/ri-seal. The README explains limits and assumptions before features. Not yet on PyPI — install directly from GitHub.

Only the 32-byte seal hash was sent to the external services (two OpenTimestamps calendars and FreeTSA); no record content or personal data left our systems. This page is not a certification service and makes no claim of legal effect.