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.

Stamp ID
STAMP-2026-1118-D2B4VTDA
Content hash
c61971d0dd793de3b052f4c7fa7ff95a070eebef019379db06fe8a63e770374f
Day recorded
2026-11-19
Articles recorded that day
10
Attestation UID
0x212a2f6feee6fd7afcae9f393d0b14bfd9fe2a1448b5b642005d7a291fb5f957
View on EAS
Transaction
0xccecd54895ec9318f5544746cf1ed5dda4a7b7ad5b240ba100e58c71d9f648dd
View on Basescan
Stamped
19 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 9 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
0x5888bfc056296e739f23c0ea0043c4fe0d33e966fc4afce78d7282f1130ea774

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
    0x127f934a73022b5710b55ca6cc8d50036e27dfa359dbefd70b30f7dc0a10e99f
    0xea8a01b11c381bfbf650eb940f3066827cc9a817d5e8584c4500126318ec17d9
  2. Step 2, combined with the value before it
    0x857a05d99d391c0e979fc9627c7c240027f04cb0614f7d713ea40491d37c7d00
    0x1636ecdf06f32a233b948dff867a98f3482e08bae7defd0b3c02e407e6e05e78
  3. Step 3, combined with the value after it
    0xa71f1112aba013e636899d4a51b1ac8c1c299079eadcb28c467aa0a1e4ef5b66
    0xd47b5f4e5e92413bb3fd2df0f0766ca24ad12b47c20e241a6b8645dce5ed3007
  4. Step 4, combined with the value after it
    0x5403878482bfedd755fb9211d1890a74953f376506fcf3a108f03c72c4814c28
    0x14d985a5c54d9c16638cd6dbe7b054860ea61589aa550172245ffc0175cdd78d

    This is the value for the whole day.

Value these steps arrive at
0x14d985a5c54d9c16638cd6dbe7b054860ea61589aa550172245ffc0175cdd78d

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
0x14d985a5c54d9c16638cd6dbe7b054860ea61589aa550172245ffc0175cdd78d
Read from Base
0x14d985a5c54d9c16638cd6dbe7b054860ea61589aa550172245ffc0175cdd78d
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":"Looking for an unexpected ingredient in your skincare routine? Crickets are mak…

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-1118-D2B4VTDA/canonical" | shasum -a 256

    Should print c61971d0dd793de3b052f4c7fa7ff95a070eebef019379db06fe8a63e770374f

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

    Should print 5888bfc056296e739f23c0ea0043c4fe0d33e966fc4afce78d7282f1130ea774

  3. 3. Combine step 1

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

    printf '01%s%s' "5888bfc056296e739f23c0ea0043c4fe0d33e966fc4afce78d7282f1130ea774" "127f934a73022b5710b55ca6cc8d50036e27dfa359dbefd70b30f7dc0a10e99f" | xxd -r -p | shasum -a 256

    Should print ea8a01b11c381bfbf650eb940f3066827cc9a817d5e8584c4500126318ec17d9

  4. 4. Combine step 2

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

    printf '01%s%s' "857a05d99d391c0e979fc9627c7c240027f04cb0614f7d713ea40491d37c7d00" "ea8a01b11c381bfbf650eb940f3066827cc9a817d5e8584c4500126318ec17d9" | xxd -r -p | shasum -a 256

    Should print 1636ecdf06f32a233b948dff867a98f3482e08bae7defd0b3c02e407e6e05e78

  5. 5. Combine step 3

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

    printf '01%s%s' "1636ecdf06f32a233b948dff867a98f3482e08bae7defd0b3c02e407e6e05e78" "a71f1112aba013e636899d4a51b1ac8c1c299079eadcb28c467aa0a1e4ef5b66" | xxd -r -p | shasum -a 256

    Should print d47b5f4e5e92413bb3fd2df0f0766ca24ad12b47c20e241a6b8645dce5ed3007

  6. 6. Combine step 4

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

    printf '01%s%s' "d47b5f4e5e92413bb3fd2df0f0766ca24ad12b47c20e241a6b8645dce5ed3007" "5403878482bfedd755fb9211d1890a74953f376506fcf3a108f03c72c4814c28" | xxd -r -p | shasum -a 256

    Should print 14d985a5c54d9c16638cd6dbe7b054860ea61589aa550172245ffc0175cdd78d

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

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

Read the specification