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.

Aloha, Hawaii 🌺

@TheTravelEdit · 4 Oct 2026

Stamp ID
STAMP-2026-1004-TFBOGSSW
Content hash
c39cd103eec90a8ef3c07bd322be162d71e9e28f7c30d5b32a036fdc07fda2b2
Day recorded
2026-10-05
Articles recorded that day
14
Attestation UID
0x99cd6b1d642d6f453cbd531cf2d5c5dee53a3ac0f82ed61ff6b666d95537f3be
View on EAS
Transaction
0x479b7310c703e960a819dd574d78be722e75921ba6309910ae4511a65681eef2
View on Basescan
Stamped
6 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0x817b574a24e74c1b4562fa5f9b5bf5f2d35bdc17937d18ef09ded8f852caf876

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
    0xa1374a2d527c87115ef7af9706c1f5110106bcb69ba59311ae36ff48d0ebe87f
    0x60341f4ae72cc2eeac1cc3a2b9e151fdf9f3630640223ca61c7ae7a4b687dda6
  2. Step 2, combined with the value after it
    0x26bc6658e52acb409bda5f67263609fdb95de1853f2e7c57eef8c11cec660084
    0xe72a9107dad5bcbbbe65af449456470da1b29e636f9c454e424b32b82f87ea19
  3. Step 3, combined with the value after it
    0xedfbc2c105cb44edb9964028fafceba81727cdf38e8690b0c893f605492fb39d
    0x99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb
  4. Step 4, combined with the value before it
    0x56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58
    0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

    This is the value for the whole day.

Value these steps arrive at
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

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
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1
Read from Base
0x11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1
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":"TheTravelEdit","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"Hawaii","src":"https://media.vitahash.org/articles/f07b9674-f1da-4e8d-85ea-0c793c7d81…

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-1004-TFBOGSSW/canonical" | shasum -a 256

    Should print c39cd103eec90a8ef3c07bd322be162d71e9e28f7c30d5b32a036fdc07fda2b2

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

    Should print 817b574a24e74c1b4562fa5f9b5bf5f2d35bdc17937d18ef09ded8f852caf876

  3. 3. Combine step 1

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

    printf '01%s%s' "a1374a2d527c87115ef7af9706c1f5110106bcb69ba59311ae36ff48d0ebe87f" "817b574a24e74c1b4562fa5f9b5bf5f2d35bdc17937d18ef09ded8f852caf876" | xxd -r -p | shasum -a 256

    Should print 60341f4ae72cc2eeac1cc3a2b9e151fdf9f3630640223ca61c7ae7a4b687dda6

  4. 4. Combine step 2

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

    printf '01%s%s' "60341f4ae72cc2eeac1cc3a2b9e151fdf9f3630640223ca61c7ae7a4b687dda6" "26bc6658e52acb409bda5f67263609fdb95de1853f2e7c57eef8c11cec660084" | xxd -r -p | shasum -a 256

    Should print e72a9107dad5bcbbbe65af449456470da1b29e636f9c454e424b32b82f87ea19

  5. 5. Combine step 3

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

    printf '01%s%s' "e72a9107dad5bcbbbe65af449456470da1b29e636f9c454e424b32b82f87ea19" "edfbc2c105cb44edb9964028fafceba81727cdf38e8690b0c893f605492fb39d" | xxd -r -p | shasum -a 256

    Should print 99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb

  6. 6. Combine step 4

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

    printf '01%s%s' "56dbe5829c1f5917b25960243052a74b072be7aa148c2a0bfd101dd1b802bb58" "99676acb01c95df27a810313f8102234fb9152a93174cbaa168803a9a889e5bb" | xxd -r -p | shasum -a 256

    Should print 11a46c50d96ebbd795fc8028cb1a011b18f508b883d672b3d8d2842b3c699ef1

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

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

Read the specification