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.

Honey Walnut Greek Yogurt Bowl

@simple_recipes_daily · 18 Sept 2026

Stamp ID
STAMP-2026-0918-JVHJX252
Content hash
f723bdce1e5f4d239ff51927d94eef4696366ffe92d7c9fddcebfbeeee8d54ec
Day recorded
2026-09-19
Articles recorded that day
15
Attestation UID
0xc48bcdaed99a48da29d734b69296d6330e0615c96d1384813677657a4f8d3d81
View on EAS
Transaction
0x12fc338f9a8535386d71a005752fe80f728ee3d4b7106c34514c764ca2057f9b
View on Basescan
Stamped
20 Sept 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
0xaf514cefbbbef8c518cdc00a1e5f04a29f01bb5f9d7904d2948f2cf76e818a21

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
    0x8a3aa36b941601deb90172ac7f0cf55027b980f622aa1261096e5be200fbc65a
    0x6a46c0efee45667948a39c4cb581b62d71e6c1c73962135825cbe536b31e4d47
  2. Step 2, combined with the value after it
    0x62eaa16fbf4f53dabbf76b4f75b6423fb14daf5c89d5c88d28ea22b5d5f114b5
    0x3a04a5700e2aa12b37474b39f9d22fd274d22ea6f253ba1c08aa30379ac76238
  3. Step 3, combined with the value after it
    0xafe400b84a49765afc417cae98c68fce1df5c28f3eba92c39ef90888e5d5f552
    0x515b55281df5784e98cbad465386a2275a74de0c9ea58616bb751482c219f11d
  4. Step 4, combined with the value before it
    0x4129c5ad64d926f37c538109754f0e9263f89c02ced93bdd213ba4405e4e9531
    0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

    This is the value for the whole day.

Value these steps arrive at
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

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
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f
Read from Base
0x5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f
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":[{"attrs":{"alt":"greek yogurt","src":"https://media.vitahash.org/articles/94bc321a-1824-4f08-94…

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-0918-JVHJX252/canonical" | shasum -a 256

    Should print f723bdce1e5f4d239ff51927d94eef4696366ffe92d7c9fddcebfbeeee8d54ec

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

    Should print af514cefbbbef8c518cdc00a1e5f04a29f01bb5f9d7904d2948f2cf76e818a21

  3. 3. Combine step 1

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

    printf '01%s%s' "8a3aa36b941601deb90172ac7f0cf55027b980f622aa1261096e5be200fbc65a" "af514cefbbbef8c518cdc00a1e5f04a29f01bb5f9d7904d2948f2cf76e818a21" | xxd -r -p | shasum -a 256

    Should print 6a46c0efee45667948a39c4cb581b62d71e6c1c73962135825cbe536b31e4d47

  4. 4. Combine step 2

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

    printf '01%s%s' "6a46c0efee45667948a39c4cb581b62d71e6c1c73962135825cbe536b31e4d47" "62eaa16fbf4f53dabbf76b4f75b6423fb14daf5c89d5c88d28ea22b5d5f114b5" | xxd -r -p | shasum -a 256

    Should print 3a04a5700e2aa12b37474b39f9d22fd274d22ea6f253ba1c08aa30379ac76238

  5. 5. Combine step 3

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

    printf '01%s%s' "3a04a5700e2aa12b37474b39f9d22fd274d22ea6f253ba1c08aa30379ac76238" "afe400b84a49765afc417cae98c68fce1df5c28f3eba92c39ef90888e5d5f552" | xxd -r -p | shasum -a 256

    Should print 515b55281df5784e98cbad465386a2275a74de0c9ea58616bb751482c219f11d

  6. 6. Combine step 4

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

    printf '01%s%s' "4129c5ad64d926f37c538109754f0e9263f89c02ced93bdd213ba4405e4e9531" "515b55281df5784e98cbad465386a2275a74de0c9ea58616bb751482c219f11d" | xxd -r -p | shasum -a 256

    Should print 5c87f8e69f2c982a1152aee23624c8f3684d400af4fd78b690d8ebfd3a21ee7f

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

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

Read the specification