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-1119-MYJLJ5WZ
Content hash
5a698cc6f3618a2dde88b0ae370ecd83de0f52b19b7687643b8db969cef4795b
Day recorded
2026-11-20
Articles recorded that day
10
Attestation UID
0x54f0795401f43cad97a1485f36be5ae0b8a2bc6c652ad5b17c956e84014baea4
View on EAS
Transaction
0x007cbb69f07c2c153747036812b6b31225331855ee8742d218fe8ef470534087
View on Basescan
Stamped
20 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 9 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
0xee769740ab74a252ea676c89f0a8694fe3d1bddc84314f158c3d01a5a21fe0cb

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
    0x49e2794c8ac0c43defb3fd4c7c14710fde5be0d9ff17f71410822e59cb975d2d
    0x62b233a6b02fa01376d70c454b2af05567f8c2e8d6ceed318311c59a94397d38
  2. Step 2, combined with the value after it
    0x0c5dc24627a3f3e375550e47a138461c4ad726eab6a461957d7deb32940bfe2e
    0xbc98be84f5809eba442b3a6fe49f3be58e50fef50e9fe0f4e97398b59436cb7c
  3. Step 3, combined with the value before it
    0xeb3c02a9449e093b9fc8c6f252e7f3e839d2e3276195d1bafbe5c7137a46593f
    0xfdfe92149d49e8cd2bd37f48013765b802f40e05b7450573fc1440e087298670
  4. Step 4, combined with the value after it
    0xad0860d0da85b69cb88e80cff97ece70462e1c99ac687aa5b1113f83946fd767
    0x2c9df57b7c56f7929a7e7ab3424a0c79cb24fdd7e82b21108f7318902ec95db6

    This is the value for the whole day.

Value these steps arrive at
0x2c9df57b7c56f7929a7e7ab3424a0c79cb24fdd7e82b21108f7318902ec95db6

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
0x2c9df57b7c56f7929a7e7ab3424a0c79cb24fdd7e82b21108f7318902ec95db6
Read from Base
0x2c9df57b7c56f7929a7e7ab3424a0c79cb24fdd7e82b21108f7318902ec95db6
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":"Have you ever considered having a white pigeon as a pet? These beautiful birds are …

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-1119-MYJLJ5WZ/canonical" | shasum -a 256

    Should print 5a698cc6f3618a2dde88b0ae370ecd83de0f52b19b7687643b8db969cef4795b

  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-1119-MYJLJ5WZ CONTENT=5a698cc6f3618a2dde88b0ae370ecd83de0f52b19b7687643b8db969cef4795b DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print ee769740ab74a252ea676c89f0a8694fe3d1bddc84314f158c3d01a5a21fe0cb

  3. 3. Combine step 1

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

    printf '01%s%s' "49e2794c8ac0c43defb3fd4c7c14710fde5be0d9ff17f71410822e59cb975d2d" "ee769740ab74a252ea676c89f0a8694fe3d1bddc84314f158c3d01a5a21fe0cb" | xxd -r -p | shasum -a 256

    Should print 62b233a6b02fa01376d70c454b2af05567f8c2e8d6ceed318311c59a94397d38

  4. 4. Combine step 2

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

    printf '01%s%s' "62b233a6b02fa01376d70c454b2af05567f8c2e8d6ceed318311c59a94397d38" "0c5dc24627a3f3e375550e47a138461c4ad726eab6a461957d7deb32940bfe2e" | xxd -r -p | shasum -a 256

    Should print bc98be84f5809eba442b3a6fe49f3be58e50fef50e9fe0f4e97398b59436cb7c

  5. 5. Combine step 3

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

    printf '01%s%s' "eb3c02a9449e093b9fc8c6f252e7f3e839d2e3276195d1bafbe5c7137a46593f" "bc98be84f5809eba442b3a6fe49f3be58e50fef50e9fe0f4e97398b59436cb7c" | xxd -r -p | shasum -a 256

    Should print fdfe92149d49e8cd2bd37f48013765b802f40e05b7450573fc1440e087298670

  6. 6. Combine step 4

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

    printf '01%s%s' "fdfe92149d49e8cd2bd37f48013765b802f40e05b7450573fc1440e087298670" "ad0860d0da85b69cb88e80cff97ece70462e1c99ac687aa5b1113f83946fd767" | xxd -r -p | shasum -a 256

    Should print 2c9df57b7c56f7929a7e7ab3424a0c79cb24fdd7e82b21108f7318902ec95db6

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

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

Read the specification