Verify

Verified on Base

This article has not changed since Vitahash recorded it on the Base blockchain. Everything below can be checked without taking our word for any of it.

Stamp ID
STAMP-2026-1024-UNLBHLCJ
Content hash
1bf03ddc75e880dd698c50152a4dbbef18d04313a168797675dcc120bcebfc7c
Day recorded
2026-10-24
Articles recorded that day
17
Attestation UID
0x99ce65ad3e3a0d7d4e90e274691f2ed402696c16d0feac0a1c0e5793bbe9bb06
View on EAS
Transaction
0x80c40265258b1fc12f44726cd8cd1aeb5beb0fb4795a5f29bd1b1a262efdc455
View on Basescan
Stamped
24 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 16 articles published that day, one step at a time, until the whole day became a single value. That one value is what Vitahash wrote to the blockchain. Change a single character of this article and the starting value below changes, so none of the steps would land on the recorded one.

Starting value for this article
0x68f69fa84996c11465daa44ab990c45da47c0bc64ebea34ad51180cd9223a4cf

Built from this article's content hash and its stamp ID, as sha256(0x00 || sha256(utf8(stampId)) || contentHash).

  1. Step 1, combined with the value before it
    0x3a5afcf84a1bf5e336bff4d34c03792ed24edc9df5a5bbc68ade80222f91d6ed
    0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

    This is the value for the whole day.

Value these steps arrive at
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

What the blockchain says

Two values, reached two different ways. The one above was worked out from this article. The one below was read back from the record on Base.

Worked out from this article
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9
Read from Base
0x625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9
Read it yourself on EAS

They are the same value, so this article was published that day with exactly the text above.

Check it yourself

Every number on this page came from Vitahash. Copy the article's exact text below and check it against the hash above, using any SHA-256 tool.

{"abstract":null,"agreement":false,"authors":[{"identity":"Unfiltered","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Who is ELIZA?","type":"text"}],"type":"paragraph"}],"type":"doc"},"disclosures":null…

Copy this text, paste it into any SHA-256 tool, and compare the result with the hash shown above. If the two match, this is exactly what Vitahash recorded.

For a technical reader: the terminal route
  1. 1. Hash the article yourself

    This downloads the exact text Vitahash hashed, in the exact form it hashed it, and hashes it again on your machine. Nothing Vitahash wrote runs here.

    curl -s "https://api.vitahash.org/api/verify/STAMP-2026-1024-UNLBHLCJ/canonical" | shasum -a 256

    Should print 1bf03ddc75e880dd698c50152a4dbbef18d04313a168797675dcc120bcebfc7c

  2. 2. Build this article's starting value

    The stamp ID is folded in with the hash, so one article's record can never stand in for another's.

    STAMP=STAMP-2026-1024-UNLBHLCJ CONTENT=1bf03ddc75e880dd698c50152a4dbbef18d04313a168797675dcc120bcebfc7c DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 68f69fa84996c11465daa44ab990c45da47c0bc64ebea34ad51180cd9223a4cf

  3. 3. Combine step 1

    The published value goes first, then the value you have.

    printf '01%s%s' "3a5afcf84a1bf5e336bff4d34c03792ed24edc9df5a5bbc68ade80222f91d6ed" "68f69fa84996c11465daa44ab990c45da47c0bc64ebea34ad51180cd9223a4cf" | xxd -r -p | shasum -a 256

    Should print 625418f751dce48dd396a5afb4e15767fb4446e46bdf1816173249cd4297f9e9

  4. 4. Compare with the blockchain

    The last value above is what the whole day came to. Read the record on Base and check its merkleRoot field is the same. Vitahash is not involved in this step at all.

    https://base.easscan.org/attestation/view/0x99ce65ad3e3a0d7d4e90e274691f2ed402696c16d0feac0a1c0e5793bbe9bb06

The rules these commands follow are written down in full, so anyone can reimplement them.

Read the specification