Record integrity

Each week's client report is sealed when the week closes, and every price, research entry and report is linked into hash chains that independent timestamp services attest once a week. Anyone who keeps a proof can later show that what it covers has not changed since.

WKS

Sealed weeks

Nothing is sealed in this sample

This public sample runs on synthetic data for fictional companies, so no report in it is sealed and no anchor is timestamped. In a client terminal on licensed prices, this page lists every week sealed for the team; choose one and the terminal checks its proof here, in the browser.

HOW

How it works

Every price version is kept. When the data provider revises a day's figures, the revision is stored as a new version with the time it arrived, and the old one stays. Each security's versions form a hash chain.
The record and the reports join the team's chain. Each research entry, and the report sealed for the client every Saturday, is linked into the team's own chain, which no other client's check can see.
Once a week, everything is anchored. The head of every chain goes into one Merkle root, written into a short statement that two RFC 3161 timestamp authorities (DigiCert and FreeTSA) sign and OpenTimestamps commits to the Bitcoin blockchain.

A sealed report records the position of every price chain it used, so it can be rebuilt exactly from the prices known at the time, even after a later revision. The proof shows that the records it covers existed in this form when the anchor was made; it says nothing about whether any reading in them is right.

CLI

Check it yourself

Save the statement and the timestamps from a checked week, then run, in the folder you saved them to:

DigiCert, whose root certificate is in the operating system's store:

openssl ts -verify -data anchor-DATE.txt -in anchor-DATE-timestamp.digicert.com.tsr -CAfile /etc/ssl/cert.pem

FreeTSA, with the root certificate it publishes at freetsa.org/files/cacert.pem:

openssl ts -verify -data anchor-DATE.txt -in anchor-DATE-freetsa.org.tsr -CAfile cacert.pem

OpenTimestamps, with its reference client, once the proof is in a Bitcoin block:
```
ots verify anchor-DATE.txt.ots
```

Each prints "Verification: OK" for a genuine timestamp of the statement and fails for any other file. On Linux the system store is usually /etc/ssl/certs/ca-certificates.crt. The statement names the Merkle root that the checks above lead to.