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.

Hello Kitty Was a ’90s Childhood Essential!

Cozy Game Diary · 14 Oct 2026

Stamp ID
STAMP-2026-1014-DQBUTVND
Content hash
6535e6e48ae1ea88d44cf6e007204a8d5227521707540e98cb70fc54b0349fba
Day recorded
2026-10-14
Articles recorded that day
15
Attestation UID
0xc3f72bef75cdf682f1ab2577b8a8f6584a2e0f6a94ae4b13d12af1bcc12372f5
View on EAS
Transaction
0xc79154afa140843ed8fabdb976bd7470bae7e86040d3bd518fa7fe1447d75bec
View on Basescan
Stamped
14 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
0xd5e7bd0ac2cc18dca3d1e77cff36220702d881208d426c506ed38ea17fc389a8

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
    0x6418dfd8e07c9145a21f178d7c7ae117a6416972adc591f65d100d925a248c37
    0x58c8bc5e15cc5d91432b5bb0e2e532ea08be9432c4dffdc73e80691ae19ed1e6
  2. Step 2, combined with the value after it
    0x9db59858626013def3054451240fd322c58c622f35028284800bd8941434c597
    0xf3b9b5eba922b1560d6c6761254234887e9e4891e708fcb0ff3e2296e02e0a67
  3. Step 3, combined with the value before it
    0x14d5790c7574bc2d8f4571c5483d70babdc0349a94beacc392a8285e5ac1d689
    0xeff19bff23c624e6fb859d769ffa9b44093e9d7622ae027193f1b2ddc45a7e24
  4. Step 4, combined with the value before it
    0xbd0e97913154d17874427958b837d4c30f110bf25686bab273996a59ddd3dff0
    0xa5763eb39e9f6a46e7427c7694e092b0e11daab565d86f11a817859e7c8fa631

    This is the value for the whole day.

Value these steps arrive at
0xa5763eb39e9f6a46e7427c7694e092b0e11daab565d86f11a817859e7c8fa631

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
0xa5763eb39e9f6a46e7427c7694e092b0e11daab565d86f11a817859e7c8fa631
Read from Base
0xa5763eb39e9f6a46e7427c7694e092b0e11daab565d86f11a817859e7c8fa631
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":"harvesthealth","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Some childhood favorites never lose their magic!!","type":"text"}],"type":"paragr…

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-1014-DQBUTVND/canonical" | shasum -a 256

    Should print 6535e6e48ae1ea88d44cf6e007204a8d5227521707540e98cb70fc54b0349fba

  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-1014-DQBUTVND CONTENT=6535e6e48ae1ea88d44cf6e007204a8d5227521707540e98cb70fc54b0349fba DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print d5e7bd0ac2cc18dca3d1e77cff36220702d881208d426c506ed38ea17fc389a8

  3. 3. Combine step 1

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

    printf '01%s%s' "6418dfd8e07c9145a21f178d7c7ae117a6416972adc591f65d100d925a248c37" "d5e7bd0ac2cc18dca3d1e77cff36220702d881208d426c506ed38ea17fc389a8" | xxd -r -p | shasum -a 256

    Should print 58c8bc5e15cc5d91432b5bb0e2e532ea08be9432c4dffdc73e80691ae19ed1e6

  4. 4. Combine step 2

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

    printf '01%s%s' "58c8bc5e15cc5d91432b5bb0e2e532ea08be9432c4dffdc73e80691ae19ed1e6" "9db59858626013def3054451240fd322c58c622f35028284800bd8941434c597" | xxd -r -p | shasum -a 256

    Should print f3b9b5eba922b1560d6c6761254234887e9e4891e708fcb0ff3e2296e02e0a67

  5. 5. Combine step 3

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

    printf '01%s%s' "14d5790c7574bc2d8f4571c5483d70babdc0349a94beacc392a8285e5ac1d689" "f3b9b5eba922b1560d6c6761254234887e9e4891e708fcb0ff3e2296e02e0a67" | xxd -r -p | shasum -a 256

    Should print eff19bff23c624e6fb859d769ffa9b44093e9d7622ae027193f1b2ddc45a7e24

  6. 6. Combine step 4

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

    printf '01%s%s' "bd0e97913154d17874427958b837d4c30f110bf25686bab273996a59ddd3dff0" "eff19bff23c624e6fb859d769ffa9b44093e9d7622ae027193f1b2ddc45a7e24" | xxd -r -p | shasum -a 256

    Should print a5763eb39e9f6a46e7427c7694e092b0e11daab565d86f11a817859e7c8fa631

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

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

Read the specification