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.

Turn a Long Layover Into a Mini Adventure

@TheTravelEdit · 1 Oct 2026

Stamp ID
STAMP-2026-1001-2B7M6RDD
Content hash
e46ab184c4aba833044fc85b646f3d4aa10bf9d752c8f7cc6e5e1e45a6c9fd70
Day recorded
2026-10-02
Articles recorded that day
15
Attestation UID
0xef3f22b3a9cc55958e4755465862526112b92e627f89ef9d8fc67aebc0e4a464
View on EAS
Transaction
0x0d04c42c85b7d9a5baf2c56ea619729fbe1338337d06aa5eaeb77eec61dd1106
View on Basescan
Stamped
2 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
0xf9594f89e91cf20370e0548c7081e12faa2b86c765ae9b7911f8486851ac408e

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
    0x931acba1d2a80c7cf42177b768fef5a94bf8630b11b7f0a277a11ccae44607c1
    0xc2342c853b1538c858a3bb13c2d032d8de903a338a6641779cd7a806bb074234
  2. Step 2, combined with the value after it
    0xed754a3ce28332285974eea9ec5829317261ea31e30eeefd5999f2f9f72e474a
    0xa50f0fbc51a99e8f4b99eaa84bcdb2a7f48c3e4eb3ad9679740346485ad36f86
  3. Step 3, combined with the value after it
    0xb5ee52d332d05a16d045f18b08d707935af7405d6aecd582f507215a02874ad4
    0x69b963a72ff774db15166fbf612b296d701fe32a57f181d9635950a5c9b83208
  4. Step 4, combined with the value after it
    0x2cd72d4bd66df07a63b5db20323f0e99df25a5f1df376f001cb13ac09996869a
    0x66fc8ec21a31705c4be9de3e933ca15d28787982a4d8b647c0bd15af650a3d3e

    This is the value for the whole day.

Value these steps arrive at
0x66fc8ec21a31705c4be9de3e933ca15d28787982a4d8b647c0bd15af650a3d3e

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
0x66fc8ec21a31705c4be9de3e933ca15d28787982a4d8b647c0bd15af650a3d3e
Read from Base
0x66fc8ec21a31705c4be9de3e933ca15d28787982a4d8b647c0bd15af650a3d3e
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":"Have a few hours between flights? If you have enough time, leave the airport and …

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-1001-2B7M6RDD/canonical" | shasum -a 256

    Should print e46ab184c4aba833044fc85b646f3d4aa10bf9d752c8f7cc6e5e1e45a6c9fd70

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

    Should print f9594f89e91cf20370e0548c7081e12faa2b86c765ae9b7911f8486851ac408e

  3. 3. Combine step 1

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

    printf '01%s%s' "f9594f89e91cf20370e0548c7081e12faa2b86c765ae9b7911f8486851ac408e" "931acba1d2a80c7cf42177b768fef5a94bf8630b11b7f0a277a11ccae44607c1" | xxd -r -p | shasum -a 256

    Should print c2342c853b1538c858a3bb13c2d032d8de903a338a6641779cd7a806bb074234

  4. 4. Combine step 2

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

    printf '01%s%s' "c2342c853b1538c858a3bb13c2d032d8de903a338a6641779cd7a806bb074234" "ed754a3ce28332285974eea9ec5829317261ea31e30eeefd5999f2f9f72e474a" | xxd -r -p | shasum -a 256

    Should print a50f0fbc51a99e8f4b99eaa84bcdb2a7f48c3e4eb3ad9679740346485ad36f86

  5. 5. Combine step 3

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

    printf '01%s%s' "a50f0fbc51a99e8f4b99eaa84bcdb2a7f48c3e4eb3ad9679740346485ad36f86" "b5ee52d332d05a16d045f18b08d707935af7405d6aecd582f507215a02874ad4" | xxd -r -p | shasum -a 256

    Should print 69b963a72ff774db15166fbf612b296d701fe32a57f181d9635950a5c9b83208

  6. 6. Combine step 4

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

    printf '01%s%s' "69b963a72ff774db15166fbf612b296d701fe32a57f181d9635950a5c9b83208" "2cd72d4bd66df07a63b5db20323f0e99df25a5f1df376f001cb13ac09996869a" | xxd -r -p | shasum -a 256

    Should print 66fc8ec21a31705c4be9de3e933ca15d28787982a4d8b647c0bd15af650a3d3e

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

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

Read the specification