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.

The Simple Bedtime Swap for Glowing Skin

@glowguide_daily · 11 Oct 2026

Stamp ID
STAMP-2026-1011-JSVCI5ZN
Content hash
c22ee862c1d3eddf4cdc1d72a89752e07e1559ed13d11bca0825fb2932b4eff6
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
0x4faceba1b936f353274d94c7fa1988bc03c6a68a1cbc0a00c674264c27aeb355

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
    0x890b4441ee745544740f01fbeb14eb61bf67374db08932422ae802b03714cc49
    0xb3fcf6597ff00dd5cb265b7dbf18c56fcb4a30fe89994320cea739ae22b0ee19
  2. Step 2, combined with the value after it
    0x468c1c266cdcdb83bdce849c8a50f27918638fd8f38129120af913fa4222f15c
    0xc2992671017688cab3a15059fcd5a6c96a89dd9dd4690c3fff3b32389cac8cb1
  3. Step 3, combined with the value before it
    0xe072c6aff39ebd158860f98d3c495ff7fe6cfc90b57e5d2e865341d1b27eea64
    0x5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef
  4. Step 4, combined with the value before it
    0x8086bb1bd2adda0b1c3a80e77552522391f792a41c4ef9e68468bb92da74d1a8
    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":"glowguide_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Unlike some rougher fabrics, satin can create less friction against your face a…

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-1011-JSVCI5ZN/canonical" | shasum -a 256

    Should print c22ee862c1d3eddf4cdc1d72a89752e07e1559ed13d11bca0825fb2932b4eff6

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

    Should print 4faceba1b936f353274d94c7fa1988bc03c6a68a1cbc0a00c674264c27aeb355

  3. 3. Combine step 1

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

    printf '01%s%s' "4faceba1b936f353274d94c7fa1988bc03c6a68a1cbc0a00c674264c27aeb355" "890b4441ee745544740f01fbeb14eb61bf67374db08932422ae802b03714cc49" | xxd -r -p | shasum -a 256

    Should print b3fcf6597ff00dd5cb265b7dbf18c56fcb4a30fe89994320cea739ae22b0ee19

  4. 4. Combine step 2

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

    printf '01%s%s' "b3fcf6597ff00dd5cb265b7dbf18c56fcb4a30fe89994320cea739ae22b0ee19" "468c1c266cdcdb83bdce849c8a50f27918638fd8f38129120af913fa4222f15c" | xxd -r -p | shasum -a 256

    Should print c2992671017688cab3a15059fcd5a6c96a89dd9dd4690c3fff3b32389cac8cb1

  5. 5. Combine step 3

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

    printf '01%s%s' "e072c6aff39ebd158860f98d3c495ff7fe6cfc90b57e5d2e865341d1b27eea64" "c2992671017688cab3a15059fcd5a6c96a89dd9dd4690c3fff3b32389cac8cb1" | xxd -r -p | shasum -a 256

    Should print 5bf8781649ca53a6f507b6207273c32bf93eaefedab539b5ef5b50ccd4c743ef

  6. 6. Combine step 4

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

    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