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.

Glow-Up Tip: Try Switching to Decaf Coffee!

@glowguide_daily · 9 Oct 2026

Stamp ID
STAMP-2026-1009-RGWVVPVK
Content hash
56408ce40815e916b4b4425e55b9ec258aad332aa45d95cfe85cac5db2cb4fb5
Day recorded
2026-10-10
Articles recorded that day
19
Attestation UID
0xb5876e55d95e5c9dd72430517b418d7e00db9efadd7c258e2a99bed5d50d278b
View on EAS
Transaction
0xdb7e81090abd4ba966e61ef8e62756a94bcf19b7c809c51e90b31991e1231c26
View on Basescan
Stamped
10 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0x7c7ffe1f0e5f7aa59806c2a6cab274951c30375230ecb3318670c5b708fb5ea1

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
    0xfcf6718bd789018d18e1cf1c055cd4ae3ba306571b904b0d2655f91ade7638ee
    0xfb1fce5e47a1a7690a878e3357df58753baa5d1a1e310cac1c8e9fa76089e1e9
  2. Step 2, combined with the value before it
    0xf7187a57ca6819ea24cb35da8bfe317f6afb09a8b390b8d7a3d01abcb4e59649
    0xe82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8
  3. Step 3, combined with the value after it
    0x9544434adc4bff681dabbe85f0bed8127c8ebc681826cd5b6a618d47b1a3a76c
    0x2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d
  4. Step 4, combined with the value before it
    0x2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d
    0xfe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac
  5. Step 5, combined with the value after it
    0x180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f
    0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

    This is the value for the whole day.

Value these steps arrive at
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

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
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68
Read from Base
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68
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":"glowguide_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Love your morning coffee but want to give your skin a little extra care? Try sw…

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-1009-RGWVVPVK/canonical" | shasum -a 256

    Should print 56408ce40815e916b4b4425e55b9ec258aad332aa45d95cfe85cac5db2cb4fb5

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

    Should print 7c7ffe1f0e5f7aa59806c2a6cab274951c30375230ecb3318670c5b708fb5ea1

  3. 3. Combine step 1

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

    printf '01%s%s' "7c7ffe1f0e5f7aa59806c2a6cab274951c30375230ecb3318670c5b708fb5ea1" "fcf6718bd789018d18e1cf1c055cd4ae3ba306571b904b0d2655f91ade7638ee" | xxd -r -p | shasum -a 256

    Should print fb1fce5e47a1a7690a878e3357df58753baa5d1a1e310cac1c8e9fa76089e1e9

  4. 4. Combine step 2

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

    printf '01%s%s' "f7187a57ca6819ea24cb35da8bfe317f6afb09a8b390b8d7a3d01abcb4e59649" "fb1fce5e47a1a7690a878e3357df58753baa5d1a1e310cac1c8e9fa76089e1e9" | xxd -r -p | shasum -a 256

    Should print e82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8

  5. 5. Combine step 3

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

    printf '01%s%s' "e82bccf903e51ff8a1e4be6fef64676bc83ac2f8527ac26dd97c522b30eb20e8" "9544434adc4bff681dabbe85f0bed8127c8ebc681826cd5b6a618d47b1a3a76c" | xxd -r -p | shasum -a 256

    Should print 2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d

  6. 6. Combine step 4

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

    printf '01%s%s' "2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d" "2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d" | xxd -r -p | shasum -a 256

    Should print fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac

  7. 7. Combine step 5

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

    printf '01%s%s' "fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac" "180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f" | xxd -r -p | shasum -a 256

    Should print 828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

  8. 8. 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/0xb5876e55d95e5c9dd72430517b418d7e00db9efadd7c258e2a99bed5d50d278b

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

Read the specification