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-1012-YHPPGSXL
Content hash
2559c7a9d4f12a7ad89d68344d7061911f82a1f38690414c1d44145dc43fabef
Day recorded
2026-10-12
Articles recorded that day
17
Attestation UID
0x2e6002254b6e58dfd691f88021eba75f139a7fceabe080bcaea3f926e17a8535
View on EAS
Transaction
0xc466e1b5d6b669ba6f3b98a5dec0c69328919ba1bcca48f1cf24392e24f7b114
View on Basescan
Stamped
12 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
0x5ec68c542eea6b8cb27350e578960f9f5ca4f28040f00769a0d993e4fd638b87

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
    0xe2d2528340512d22ce4d34dadad6fdb0f00918fb4ffaa42f9d372ee6129201d6
    0xfa3cf93c8619ec0973bc426e5320964dcbdad2e13eff9e03e25f25c342c3abc0

    This is the value for the whole day.

Value these steps arrive at
0xfa3cf93c8619ec0973bc426e5320964dcbdad2e13eff9e03e25f25c342c3abc0

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
0xfa3cf93c8619ec0973bc426e5320964dcbdad2e13eff9e03e25f25c342c3abc0
Read from Base
0xfa3cf93c8619ec0973bc426e5320964dcbdad2e13eff9e03e25f25c342c3abc0
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":"glowguide_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Watermelon isn’t just a refreshing summer snack! It’s packed with water to help…

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-1012-YHPPGSXL/canonical" | shasum -a 256

    Should print 2559c7a9d4f12a7ad89d68344d7061911f82a1f38690414c1d44145dc43fabef

  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-1012-YHPPGSXL CONTENT=2559c7a9d4f12a7ad89d68344d7061911f82a1f38690414c1d44145dc43fabef DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 5ec68c542eea6b8cb27350e578960f9f5ca4f28040f00769a0d993e4fd638b87

  3. 3. Combine step 1

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

    printf '01%s%s' "e2d2528340512d22ce4d34dadad6fdb0f00918fb4ffaa42f9d372ee6129201d6" "5ec68c542eea6b8cb27350e578960f9f5ca4f28040f00769a0d993e4fd638b87" | xxd -r -p | shasum -a 256

    Should print fa3cf93c8619ec0973bc426e5320964dcbdad2e13eff9e03e25f25c342c3abc0

  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/0x2e6002254b6e58dfd691f88021eba75f139a7fceabe080bcaea3f926e17a8535

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

Read the specification