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.

Easy Halloween Mummy Pizza Toasts

@simple_recipes_daily · 10 Oct 2026

Stamp ID
STAMP-2026-1010-SYUV275M
Content hash
c0dc5749f4ea6734e55feb33a7b6a631922c84d40fce1a4b64dcdeb4441ad363
Day recorded
2026-10-11
Articles recorded that day
15
Attestation UID
0xe7374a439adaae60fa76c479707b4cb8715b94c18650f7e4be153f5afd862a6a
View on EAS
Transaction
0x31cb8434022ddab43a418971f60ad5a9c23200c1edf7c788f7e5a9f9b4bd03c0
View on Basescan
Stamped
11 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
0x1b5e6e4c527d4b52f8d149a3639e85abf02d49bc5add2027bceab5ef29cd443b

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
    0x241f3ae8f400223890e9836cb76f097eed5ee59d2995d67de89ed4eae6848f43
    0xf8c38748326418db665f53e2be04e7ca5d6b19a8d11c3c0b2c65667b071fe608
  2. Step 2, combined with the value after it
    0xc49c24a7b72856baf08fce72f56cccb02de56e29b6cbaf848a27d95643651afd
    0xb393c447ccb3f707e81d3e404b724241afe1db1541be2ba7b03a3a0be6b1a5e3
  3. Step 3, combined with the value before it
    0xd71669495b15132484309582fa3f7bf6626dabc1ed049fc5158fa7ef5366a475
    0x8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8
  4. Step 4, combined with the value after it
    0x5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef
    0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

    This is the value for the whole day.

Value these steps arrive at
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

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
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b
Read from Base
0x815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b
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":"simple_recipes_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Make a spooky snack in just 10 minutes!","type":"text"}],"type":"paragraph…

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-1010-SYUV275M/canonical" | shasum -a 256

    Should print c0dc5749f4ea6734e55feb33a7b6a631922c84d40fce1a4b64dcdeb4441ad363

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

    Should print 1b5e6e4c527d4b52f8d149a3639e85abf02d49bc5add2027bceab5ef29cd443b

  3. 3. Combine step 1

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

    printf '01%s%s' "241f3ae8f400223890e9836cb76f097eed5ee59d2995d67de89ed4eae6848f43" "1b5e6e4c527d4b52f8d149a3639e85abf02d49bc5add2027bceab5ef29cd443b" | xxd -r -p | shasum -a 256

    Should print f8c38748326418db665f53e2be04e7ca5d6b19a8d11c3c0b2c65667b071fe608

  4. 4. Combine step 2

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

    printf '01%s%s' "f8c38748326418db665f53e2be04e7ca5d6b19a8d11c3c0b2c65667b071fe608" "c49c24a7b72856baf08fce72f56cccb02de56e29b6cbaf848a27d95643651afd" | xxd -r -p | shasum -a 256

    Should print b393c447ccb3f707e81d3e404b724241afe1db1541be2ba7b03a3a0be6b1a5e3

  5. 5. Combine step 3

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

    printf '01%s%s' "d71669495b15132484309582fa3f7bf6626dabc1ed049fc5158fa7ef5366a475" "b393c447ccb3f707e81d3e404b724241afe1db1541be2ba7b03a3a0be6b1a5e3" | xxd -r -p | shasum -a 256

    Should print 8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8

  6. 6. Combine step 4

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

    printf '01%s%s' "8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8" "5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef" | xxd -r -p | shasum -a 256

    Should print 815430e2a00179e7b99823b21562548a6ed5521009efbd974ba470d1b529c64b

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

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

Read the specification