Verifying it yourself
You will be able to check a block, a release and an anchored file without trusting any page on this site.
A block
Rebuild the header, take the hash, compare.
The home page does this in your browser, and you can do it anywhere: take a block header’s fields in their exact encoding, hash them twice with SHA-256, and compare the result with the hash the network reports. If they match, the block you were shown is the block the chain committed to. If they did not, no amount of design would make the page trustworthy.
Illustration to come
Real photograph: a laptop terminal showing a hash next to a handwritten note of the same value on paper, ticked off. Human verification of a machine result.
A release
The signature says who built it; the provenance says what from.
verify-release.sh checks the whole package: the binary, its detached signature, the signed checksum manifest, the signed provenance binding that digest to one source commit and tag, and the dependency inventory. It refuses on any missing piece. Running it before running a node is the single highest-value habit an operator can have.
Illustration to come
Real screen capture of scripts/verify-release.sh run against a real published release, showing its ok lines. Never a mock-up, never invented output.
A file
Vigi Data proves integrity without holding the file.
Hash a document locally, then ask the chain whether that hash was anchored and when. A match proves the file has not changed since the anchor and that whoever anchored it held it at that moment. It proves nothing about the contents being true — the same boundary as every other proof on this network, stated for the same reason.
Illustration to come
Real photograph: a paper document on a desk next to a screen displaying a hash string. The pairing of the physical and the digital is the point.
The habit
Verify the claim, not the claimant.
Every lesson in this academy points at something checkable, for one reason: a network whose properties you have to take on trust has no advantage over a database. Where a claim cannot be verified from outside — the burn-in, the number of independent operators, audits still in progress — the pages say so, and that is where the honest boundary of this technology sits today.
Illustration to come
Real photograph of a mechanical balance being read carefully at eye level. Measurement rather than judgement — no courtroom imagery.
In short
- A block header can be re-hashed and compared in your own browser.
- A release is verified as a package: binary, signature, manifest, provenance and inventory.
- An anchored file proves integrity and timing, never truth.
- Where something cannot be verified from outside, this site says so instead of asserting it.