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-1011-E2LYGQ2V
Content hash
84beedd7b3cf56df5f519d0b75e6ba5a2bc2ad708e453c71c33301c2fdd2bd15
Day recorded
2026-10-11
Articles recorded that day
15
Attestation UID
0xe7374a439adaae60fa76c479707b4cb8715b94c18650f7e4be153f5afd862a6a
View on EAS
Transaction
0x31cb8434022ddab43a418971f60ad5a9c23200c1edf7c788f7e5a9f9b4bd03c0
View on Basescan
Stamped
11 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 14 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
0x9632c250f0010e0adaa8521a7fb5f19befc009715ac9f7847c020ed6bd7291b8

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
    0x67d8ff9252c94f288b5c4b6ea243424508d74579a58b3e1e96b7550aa63d8898
    0x6c11a726e47983461dfd84d5380618a8bea33c10002c3a8fa9d2f6c5ecbf1aac
  2. Step 2, combined with the value before it
    0xaae5dba5cd805a49600d11b2ea5a736baba31ca7fa0df7f1cd2e0a44db830f79
    0xe072c6aff39ebd158860f98d3c495ff7fe6cfc90b57e5d2e865341d1b27eea64
  3. Step 3, combined with the value after it
    0xc2992671017688cab3a15059fcd5a6c96a89dd9dd4690c3fff3b32389cac8cb1
    0x5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef
  4. Step 4, combined with the value before it
    0x8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8
    0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

    This is the value for the whole day.

Value these steps arrive at
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

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
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b
Read from Base
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b
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":"ThePetTales","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Ever notice how your dog seems to know when you’re sad, stressed, or having a bad d…

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-1011-E2LYGQ2V/canonical" | shasum -a 256

    Should print 84beedd7b3cf56df5f519d0b75e6ba5a2bc2ad708e453c71c33301c2fdd2bd15

  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-1011-E2LYGQ2V CONTENT=84beedd7b3cf56df5f519d0b75e6ba5a2bc2ad708e453c71c33301c2fdd2bd15 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 9632c250f0010e0adaa8521a7fb5f19befc009715ac9f7847c020ed6bd7291b8

  3. 3. Combine step 1

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

    printf '01%s%s' "67d8ff9252c94f288b5c4b6ea243424508d74579a58b3e1e96b7550aa63d8898" "9632c250f0010e0adaa8521a7fb5f19befc009715ac9f7847c020ed6bd7291b8" | xxd -r -p | shasum -a 256

    Should print 6c11a726e47983461dfd84d5380618a8bea33c10002c3a8fa9d2f6c5ecbf1aac

  4. 4. Combine step 2

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

    printf '01%s%s' "aae5dba5cd805a49600d11b2ea5a736baba31ca7fa0df7f1cd2e0a44db830f79" "6c11a726e47983461dfd84d5380618a8bea33c10002c3a8fa9d2f6c5ecbf1aac" | xxd -r -p | shasum -a 256

    Should print e072c6aff39ebd158860f98d3c495ff7fe6cfc90b57e5d2e865341d1b27eea64

  5. 5. Combine step 3

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

    printf '01%s%s' "e072c6aff39ebd158860f98d3c495ff7fe6cfc90b57e5d2e865341d1b27eea64" "c2992671017688cab3a15059fcd5a6c96a89dd9dd4690c3fff3b32389cac8cb1" | xxd -r -p | shasum -a 256

    Should print 5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef

  6. 6. Combine step 4

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

    printf '01%s%s' "8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8" "5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef" | xxd -r -p | shasum -a 256

    Should print 815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

  7. 7. 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/0xe7374a439adaae60fa76c479707b4cb8715b94c18650f7e4be153f5afd862a6a

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

Read the specification