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.

Cancún, Mexico: Where Turquoise Water Meets Paradise

@TheTravelEdit · 27 Sept 2026

Stamp ID
STAMP-2026-0927-Y7GRZYWU
Content hash
4d461db065ba886f0c383d20d04a540bc8746221554fb9ec0d9509749d95e58a
Day recorded
2026-09-28
Articles recorded that day
16
Attestation UID
0xf90e9bc451eee5367128ecc6c707fc5352ef0515b57dec1f5af014911dd29347
View on EAS
Transaction
0x0f2874f7536c4d6526c65e0119f22d2ba40a142cf577fc5ab655a4834d402d41
View on Basescan
Stamped
28 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 15 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
0xa061daba9f9c4756f14a2cb95191f4c7fc59bf86892553f51061336be63f77c7

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
    0x58fc624e6c0dd23c3f8ec0fb402b7ba9dd29292a9cd8b0ce8ed47232662193e4
    0x5d1c7bfd843242f2ad1fe89866ca257f29e5bf47a9c54c525d7f6c19a534edd5
  2. Step 2, combined with the value after it
    0xf2e28bae3cabd4b3648a42dc6a3a87b4132e8d1be48fc43872ebbd3a3617574f
    0x38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20
  3. Step 3, combined with the value before it
    0xd3c2f94c5c767cdb10be31c6ddf7bc5882f37bdff20906c367194ada68ba2524
    0x189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e
  4. Step 4, combined with the value before it
    0x6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73
    0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

    This is the value for the whole day.

Value these steps arrive at
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

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
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94
Read from Base
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94
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":[{"content":[{"text":"Dreaming of crystal-clear Caribbean water, soft white-sand beaches, and sunshine?…

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-0927-Y7GRZYWU/canonical" | shasum -a 256

    Should print 4d461db065ba886f0c383d20d04a540bc8746221554fb9ec0d9509749d95e58a

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

    Should print a061daba9f9c4756f14a2cb95191f4c7fc59bf86892553f51061336be63f77c7

  3. 3. Combine step 1

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

    printf '01%s%s' "58fc624e6c0dd23c3f8ec0fb402b7ba9dd29292a9cd8b0ce8ed47232662193e4" "a061daba9f9c4756f14a2cb95191f4c7fc59bf86892553f51061336be63f77c7" | xxd -r -p | shasum -a 256

    Should print 5d1c7bfd843242f2ad1fe89866ca257f29e5bf47a9c54c525d7f6c19a534edd5

  4. 4. Combine step 2

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

    printf '01%s%s' "5d1c7bfd843242f2ad1fe89866ca257f29e5bf47a9c54c525d7f6c19a534edd5" "f2e28bae3cabd4b3648a42dc6a3a87b4132e8d1be48fc43872ebbd3a3617574f" | xxd -r -p | shasum -a 256

    Should print 38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20

  5. 5. Combine step 3

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

    printf '01%s%s' "d3c2f94c5c767cdb10be31c6ddf7bc5882f37bdff20906c367194ada68ba2524" "38074abb35e4ffd876d923d5db6e19e3da76b6bf9c7bd290ffdf353c791bca20" | xxd -r -p | shasum -a 256

    Should print 189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e

  6. 6. Combine step 4

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

    printf '01%s%s' "6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73" "189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e" | xxd -r -p | shasum -a 256

    Should print 01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

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

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

Read the specification