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-1116-YYBN4ZOE
Content hash
a19fadee8723c59c3bcd6281695c2053e82a90072745b755b84391896d716b6e
Day recorded
2026-11-17
Articles recorded that day
18
Attestation UID
0x880330856028af49645da78f1ecccf8b50b0c5e33df5d9d7f590f67aa5504077
View on EAS
Transaction
0x08ed8ba6a46b18249f5d7ec42bfca0e9d9a07f39cfe3408522d07fa1be405639
View on Basescan
Stamped
17 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 17 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
0xf6ee42ec902c49c527e2d287437550b97aa8ce04decd93eb1d6c0d80ebb646f1

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
    0x871bfbc2d0526df42e3ff53d6957838e7d389c67ecceb5fe7c6d0703c83ed356
    0x65d0ad7fbf9ea058840b312b1e1ea8ebb5e9b6fa4e44f5a63c273ef099dbc44c
  2. Step 2, combined with the value before it
    0x2ac4d87c6baa38526edc7c925eb46d07eeb6e535307bdf2ff8a8e1ff56b3ab0e
    0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

    This is the value for the whole day.

Value these steps arrive at
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

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
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2
Read from Base
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2
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":"As pets get older, taking care of them can become more challenging. They may need m…

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-1116-YYBN4ZOE/canonical" | shasum -a 256

    Should print a19fadee8723c59c3bcd6281695c2053e82a90072745b755b84391896d716b6e

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

    Should print f6ee42ec902c49c527e2d287437550b97aa8ce04decd93eb1d6c0d80ebb646f1

  3. 3. Combine step 1

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

    printf '01%s%s' "871bfbc2d0526df42e3ff53d6957838e7d389c67ecceb5fe7c6d0703c83ed356" "f6ee42ec902c49c527e2d287437550b97aa8ce04decd93eb1d6c0d80ebb646f1" | xxd -r -p | shasum -a 256

    Should print 65d0ad7fbf9ea058840b312b1e1ea8ebb5e9b6fa4e44f5a63c273ef099dbc44c

  4. 4. Combine step 2

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

    printf '01%s%s' "2ac4d87c6baa38526edc7c925eb46d07eeb6e535307bdf2ff8a8e1ff56b3ab0e" "65d0ad7fbf9ea058840b312b1e1ea8ebb5e9b6fa4e44f5a63c273ef099dbc44c" | xxd -r -p | shasum -a 256

    Should print f888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

  5. 5. 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/0x880330856028af49645da78f1ecccf8b50b0c5e33df5d9d7f590f67aa5504077

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

Read the specification