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.

🐱🐭 Why does your cat bring a dead mouse or animal to your window?

@ThePetTales · 16 Oct 2026

Stamp ID
STAMP-2026-1016-IGBDHQ3E
Content hash
4930d6b7542afec3858ffc2f33fd0681ed9275b568bd67e7747c1504eea7ae71
Day recorded
2026-10-17
Articles recorded that day
14
Attestation UID
0x954aae5491508351a76be05b38d4cef34ae05b9478cc1bee363f1de93bbf1681
View on EAS
Transaction
0x9c4640fb4dcea8118b9b300e3f91dc7e6f42de03d9e29eb50f4390ffdc328429
View on Basescan
Stamped
17 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0x0c3f29e88647ec190d32032dcce2074a65bb7fcc6cc52b6e5f88c965aa36842f

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 after it
    0xa06ec79cd71bee0831d42d1d6abd0682a35abcaceba0e49a0ac75b66e67b63af
    0x341dc31facfe1a09bf898ccc365fb65e97654598563518640d99e2a28747b60d
  2. Step 2, combined with the value after it
    0xeca4b9a09f819a83b26795abfe06005d348d4d7bc20e5fa3f66b5740870a3de5
    0xee7c9d80e9d74a13b199fe55be702665799eda4d042ff8118c2d2574bbc392cb
  3. Step 3, combined with the value before it
    0xaa2ee967a683562e5bc8a0c4859b938d351576276be16faab7612fc6d5ec1222
    0x243306bd12812188633ea86e0356bae8265333e85ea9c2ee24a015b3712c30e8
  4. Step 4, combined with the value after it
    0x8d12ba429b23a7d1f9710a6095c3ce05fe826bd380f48bb60fe3257ae6e338b3
    0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

    This is the value for the whole day.

Value these steps arrive at
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

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
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa
Read from Base
0xf100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa
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":"It might look like a strange gift, but your cat is following its natural hunting in…

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-1016-IGBDHQ3E/canonical" | shasum -a 256

    Should print 4930d6b7542afec3858ffc2f33fd0681ed9275b568bd67e7747c1504eea7ae71

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

    Should print 0c3f29e88647ec190d32032dcce2074a65bb7fcc6cc52b6e5f88c965aa36842f

  3. 3. Combine step 1

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

    printf '01%s%s' "0c3f29e88647ec190d32032dcce2074a65bb7fcc6cc52b6e5f88c965aa36842f" "a06ec79cd71bee0831d42d1d6abd0682a35abcaceba0e49a0ac75b66e67b63af" | xxd -r -p | shasum -a 256

    Should print 341dc31facfe1a09bf898ccc365fb65e97654598563518640d99e2a28747b60d

  4. 4. Combine step 2

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

    printf '01%s%s' "341dc31facfe1a09bf898ccc365fb65e97654598563518640d99e2a28747b60d" "eca4b9a09f819a83b26795abfe06005d348d4d7bc20e5fa3f66b5740870a3de5" | xxd -r -p | shasum -a 256

    Should print ee7c9d80e9d74a13b199fe55be702665799eda4d042ff8118c2d2574bbc392cb

  5. 5. Combine step 3

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

    printf '01%s%s' "aa2ee967a683562e5bc8a0c4859b938d351576276be16faab7612fc6d5ec1222" "ee7c9d80e9d74a13b199fe55be702665799eda4d042ff8118c2d2574bbc392cb" | xxd -r -p | shasum -a 256

    Should print 243306bd12812188633ea86e0356bae8265333e85ea9c2ee24a015b3712c30e8

  6. 6. Combine step 4

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

    printf '01%s%s' "243306bd12812188633ea86e0356bae8265333e85ea9c2ee24a015b3712c30e8" "8d12ba429b23a7d1f9710a6095c3ce05fe826bd380f48bb60fe3257ae6e338b3" | xxd -r -p | shasum -a 256

    Should print f100b10cdd559fc598ca9ae360b09546cbe0d39d08909430c26690c0b5bc31aa

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

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

Read the specification