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.

A Dreamy Moisturizer

@glowguide_daily · 15 Sept 2026

Stamp ID
STAMP-2026-0915-OB24D7XB
Content hash
4e3f42d56723bf8c1b8176af820ff49be06068c700f26e559a6b1ae997c13c6d
Day recorded
2026-09-16
Articles recorded that day
11
Attestation UID
0x54e8c20577bfacf8072eb87b36b1bfa02b4db37247336a2c44ccaa82df5ef5c2
View on EAS
Transaction
0x27483e4138b3cb63387441033318cbcfa64c52adb28abf76257ce8b5aa03ef19
View on Basescan
Stamped
17 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 10 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
0x092f635e44384aaeef81fa8af2814f34d17333086f281be2d3ea8daae03087df

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
    0xa04bb51fcfae5ab671357cb7cf47f74e849ba5bec7ca8463b29f7b7266ca7828
    0x776c07063562977b52dfbec459ad0f5aa79eb14d8097a3504465610b358fc6fd
  2. Step 2, combined with the value after it
    0xf3e3ec1db8f4f11dd2bb58fd2282723c909804dadb1ec2aa98c05e9e49f455c9
    0x6efcc863bc662c4b58525e19251707bab65f11b8d1956b2e6c17ecdb9a72af62
  3. Step 3, combined with the value before it
    0x3c99f78fa4c4a6d38479d0b6ba497ecf06cd2fbe3366fec921466bb1e632f2ae
    0x45b6a0f20f993e761d8aead43f3695dbd2bccd21f8b01cb82137ebd8b84b7f6c
  4. Step 4, combined with the value after it
    0x2833408ec18f99b6743e4b1d92b1b4bbc4d9bfa009fe72217f3ffe85845091d8
    0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

    This is the value for the whole day.

Value these steps arrive at
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

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
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50
Read from Base
0x7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50
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.

The exact text is not available for this article right now. The command below still reaches it.

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-0915-OB24D7XB/canonical" | shasum -a 256

    Should print 4e3f42d56723bf8c1b8176af820ff49be06068c700f26e559a6b1ae997c13c6d

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

    Should print 092f635e44384aaeef81fa8af2814f34d17333086f281be2d3ea8daae03087df

  3. 3. Combine step 1

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

    printf '01%s%s' "092f635e44384aaeef81fa8af2814f34d17333086f281be2d3ea8daae03087df" "a04bb51fcfae5ab671357cb7cf47f74e849ba5bec7ca8463b29f7b7266ca7828" | xxd -r -p | shasum -a 256

    Should print 776c07063562977b52dfbec459ad0f5aa79eb14d8097a3504465610b358fc6fd

  4. 4. Combine step 2

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

    printf '01%s%s' "776c07063562977b52dfbec459ad0f5aa79eb14d8097a3504465610b358fc6fd" "f3e3ec1db8f4f11dd2bb58fd2282723c909804dadb1ec2aa98c05e9e49f455c9" | xxd -r -p | shasum -a 256

    Should print 6efcc863bc662c4b58525e19251707bab65f11b8d1956b2e6c17ecdb9a72af62

  5. 5. Combine step 3

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

    printf '01%s%s' "3c99f78fa4c4a6d38479d0b6ba497ecf06cd2fbe3366fec921466bb1e632f2ae" "6efcc863bc662c4b58525e19251707bab65f11b8d1956b2e6c17ecdb9a72af62" | xxd -r -p | shasum -a 256

    Should print 45b6a0f20f993e761d8aead43f3695dbd2bccd21f8b01cb82137ebd8b84b7f6c

  6. 6. Combine step 4

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

    printf '01%s%s' "45b6a0f20f993e761d8aead43f3695dbd2bccd21f8b01cb82137ebd8b84b7f6c" "2833408ec18f99b6743e4b1d92b1b4bbc4d9bfa009fe72217f3ffe85845091d8" | xxd -r -p | shasum -a 256

    Should print 7ada4849ddba18c43f15ae62dd893ec944c3f03ed2ad4968a988bf0d90f0be50

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

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

Read the specification