Verify

Sign inSign up

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.

Your cat has a secret built-in GPS for finding the warmest spot in the house

@ThePetTales · 5 Nov 2026

Stamp ID
STAMP-2026-1105-QZZGQSU3
Content hash
94ef5b3359e7cfda7d9e9ac818e9b40096fa5f0db27899d9f375844a9902a9a7
Day recorded
2026-11-06
Articles recorded that day
12
Attestation UID
0xf18b4a820f1ceeeeb38ce9fccab69ef519d3effbb8d1bd928e7bcba4536cb592
View on EAS
Transaction
0x14693aefb1bbea4f15075a913bb23e04319b39086cdc62f7b9c08d1a2e5a89db
View on Basescan
Stamped
6 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 11 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
0x2bad6ef01a7271bd75ffb23c88f4ccd9a60aa034755c3cb35a9779a2bc3695e1

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
    0xec7850c73c21b5d5b41980b499058347578fbc6b9f110c9731eed78a4019b1f5
    0xcaf3ae26ad2fdd130dc83f8fd90b7028fbf9cd00cae4742eeabdf296dcb2562f
  2. Step 2, combined with the value before it
    0xcbd3445a0c0b6f536166cc692d527902aa0c17e4fa7b1293fe7e8abc94fecb96
    0x0cf6688e1cdc08cbcaa58a4fd695e64c1564ae7fac0b7082d3f93984d4cbdc7b
  3. Step 3, combined with the value before it
    0xe156cfe28a9842521746b77acf0f16111e12e343f22b6d877577f6f6d01639e0
    0x44df682a6023b81e87ff829ccca3e146cb12d98ec2a65d04100ea772c6deb9ef
  4. Step 4, combined with the value after it
    0xf119904624d5c3eec5a49f2357ad6ebe30995fe5bb8735024047c82ce6f4b376
    0xefb0a2841ae86a42f2cad5934d41fc3fe4e5eb0afa96bca6b150b3ea749097db

    This is the value for the whole day.

Value these steps arrive at
0xefb0a2841ae86a42f2cad5934d41fc3fe4e5eb0afa96bca6b150b3ea749097db

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
0xefb0a2841ae86a42f2cad5934d41fc3fe4e5eb0afa96bca6b150b3ea749097db
Read from Base
0xefb0a2841ae86a42f2cad5934d41fc3fe4e5eb0afa96bca6b150b3ea749097db
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":"A sunny windowsill, freshly dried laundry, the laptop you desperately need, or the …

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-1105-QZZGQSU3/canonical" | shasum -a 256

    Should print 94ef5b3359e7cfda7d9e9ac818e9b40096fa5f0db27899d9f375844a9902a9a7

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

    Should print 2bad6ef01a7271bd75ffb23c88f4ccd9a60aa034755c3cb35a9779a2bc3695e1

  3. 3. Combine step 1

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

    printf '01%s%s' "ec7850c73c21b5d5b41980b499058347578fbc6b9f110c9731eed78a4019b1f5" "2bad6ef01a7271bd75ffb23c88f4ccd9a60aa034755c3cb35a9779a2bc3695e1" | xxd -r -p | shasum -a 256

    Should print caf3ae26ad2fdd130dc83f8fd90b7028fbf9cd00cae4742eeabdf296dcb2562f

  4. 4. Combine step 2

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

    printf '01%s%s' "cbd3445a0c0b6f536166cc692d527902aa0c17e4fa7b1293fe7e8abc94fecb96" "caf3ae26ad2fdd130dc83f8fd90b7028fbf9cd00cae4742eeabdf296dcb2562f" | xxd -r -p | shasum -a 256

    Should print 0cf6688e1cdc08cbcaa58a4fd695e64c1564ae7fac0b7082d3f93984d4cbdc7b

  5. 5. Combine step 3

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

    printf '01%s%s' "e156cfe28a9842521746b77acf0f16111e12e343f22b6d877577f6f6d01639e0" "0cf6688e1cdc08cbcaa58a4fd695e64c1564ae7fac0b7082d3f93984d4cbdc7b" | xxd -r -p | shasum -a 256

    Should print 44df682a6023b81e87ff829ccca3e146cb12d98ec2a65d04100ea772c6deb9ef

  6. 6. Combine step 4

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

    printf '01%s%s' "44df682a6023b81e87ff829ccca3e146cb12d98ec2a65d04100ea772c6deb9ef" "f119904624d5c3eec5a49f2357ad6ebe30995fe5bb8735024047c82ce6f4b376" | xxd -r -p | shasum -a 256

    Should print efb0a2841ae86a42f2cad5934d41fc3fe4e5eb0afa96bca6b150b3ea749097db

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

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

Read the specification