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.

Escape to Key West, Florida

@TheTravelEdit · 26 Sept 2026

Stamp ID
STAMP-2026-0926-RXRKV2HK
Content hash
c7885d5470ff07d491f345843375c1a2ee67712a7492323aaeebfdac05b17855
Day recorded
2026-09-27
Articles recorded that day
19
Attestation UID
0x84cb5f3777a1d6bf11bc9929df9416c96f83e77a90905fa5ee406bde170afbe4
View on EAS
Transaction
0x2bc739663021c9616f855df1349f0c9e05f39f843e986166a72ea6bd60bfa4ec
View on Basescan
Stamped
27 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0xd5a686ad9259dc321c10c2847d83a260fc7d504a3ea500e585c5bad334c30496

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
    0xbc161e37963e0517c42522d2b5af25f607a94de40e888799f2d0abe3dcf538c6
    0xed7e9fa21fb7f139cc3eae727d5cc16868903070d0f1dc3cef229facefa2bdf7
  2. Step 2, combined with the value before it
    0xfca0379caa18a48c5b4f07220a4ce0b97808d41a504002c7f63dc1b99e74a69b
    0xd0e0b412aee8466306d92f2337533d441e1c3251e88565b1bb6c1b80ad82eb29
  3. Step 3, combined with the value before it
    0xc4375f4d0e7a1db38994a2e132b58610366f1888e0d58795ee74b99c867a738e
    0x57711de9e370bc645f82e3badf941f656fd3ba3e7114bf721e696aad647fff65
  4. Step 4, combined with the value before it
    0xd06cf380e63c7e122ed0df0fc07ba07ded91a9bc4130807f0831afb110cf774d
    0x43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b
  5. Step 5, combined with the value after it
    0xd5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0
    0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

    This is the value for the whole day.

Value these steps arrive at
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

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
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
Read from Base
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
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":"Key West, Florida feels like a little slice of the Caribbean without leaving the …

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-0926-RXRKV2HK/canonical" | shasum -a 256

    Should print c7885d5470ff07d491f345843375c1a2ee67712a7492323aaeebfdac05b17855

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

    Should print d5a686ad9259dc321c10c2847d83a260fc7d504a3ea500e585c5bad334c30496

  3. 3. Combine step 1

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

    printf '01%s%s' "bc161e37963e0517c42522d2b5af25f607a94de40e888799f2d0abe3dcf538c6" "d5a686ad9259dc321c10c2847d83a260fc7d504a3ea500e585c5bad334c30496" | xxd -r -p | shasum -a 256

    Should print ed7e9fa21fb7f139cc3eae727d5cc16868903070d0f1dc3cef229facefa2bdf7

  4. 4. Combine step 2

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

    printf '01%s%s' "fca0379caa18a48c5b4f07220a4ce0b97808d41a504002c7f63dc1b99e74a69b" "ed7e9fa21fb7f139cc3eae727d5cc16868903070d0f1dc3cef229facefa2bdf7" | xxd -r -p | shasum -a 256

    Should print d0e0b412aee8466306d92f2337533d441e1c3251e88565b1bb6c1b80ad82eb29

  5. 5. Combine step 3

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

    printf '01%s%s' "c4375f4d0e7a1db38994a2e132b58610366f1888e0d58795ee74b99c867a738e" "d0e0b412aee8466306d92f2337533d441e1c3251e88565b1bb6c1b80ad82eb29" | xxd -r -p | shasum -a 256

    Should print 57711de9e370bc645f82e3badf941f656fd3ba3e7114bf721e696aad647fff65

  6. 6. Combine step 4

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

    printf '01%s%s' "d06cf380e63c7e122ed0df0fc07ba07ded91a9bc4130807f0831afb110cf774d" "57711de9e370bc645f82e3badf941f656fd3ba3e7114bf721e696aad647fff65" | xxd -r -p | shasum -a 256

    Should print 43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b

  7. 7. Combine step 5

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

    printf '01%s%s' "43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b" "d5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0" | xxd -r -p | shasum -a 256

    Should print d5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

  8. 8. 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/0x84cb5f3777a1d6bf11bc9929df9416c96f83e77a90905fa5ee406bde170afbe4

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

Read the specification