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.

Ever slept in a glass igloo under the stars?

@TheTravelEdit · 7 Oct 2026

Stamp ID
STAMP-2026-1007-A5XIOQZA
Content hash
60a74dacb9869df5e33ba69396201b673f8b858511028c666a1cb0d1d29faf14
Day recorded
2026-10-08
Articles recorded that day
16
Attestation UID
0x3fd72ca76c79be099aa7f432c6fb16edc08982e9c7ef6528aa816dccff3b4ac8
View on EAS
Transaction
0x3379a1fcacf0777d45b279ac455541dcaee6ec6fdf7c604fb5a904496de0a459
View on Basescan
Stamped
8 Oct 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
0x787a7d96b56477ff593b7d7f64d1337b1c638dd8d0f1e4bea945e8c0b9070fd9

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
    0xcfd2f714516c995e99165be2b67cf0ea0c59a481454293dfaa7b467618a86a8b
    0x11a7a5af9497b8980fea63a826f20d6ac4ce8ef7e30d016d32a64edee11de5bf
  2. Step 2, combined with the value after it
    0xaaf85bd76fd21006e8402a227bd21923d53cf3d7371926d6a33d71c51e31be81
    0xa792b34de4a606dc5cbfc48203b2af1f6ded83bdb09048459fb5a6f9ded76794
  3. Step 3, combined with the value before it
    0x56a825d661eedef74814c6317c32e5ecebdbbab058f72f4434d2501e8f69f442
    0x21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823
  4. Step 4, combined with the value after it
    0x4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787
    0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

    This is the value for the whole day.

Value these steps arrive at
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
Read from Base
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
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":"In Finland, you can stay in a glass-roofed cabin where you can lie in bed and wat…

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-1007-A5XIOQZA/canonical" | shasum -a 256

    Should print 60a74dacb9869df5e33ba69396201b673f8b858511028c666a1cb0d1d29faf14

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

    Should print 787a7d96b56477ff593b7d7f64d1337b1c638dd8d0f1e4bea945e8c0b9070fd9

  3. 3. Combine step 1

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

    printf '01%s%s' "cfd2f714516c995e99165be2b67cf0ea0c59a481454293dfaa7b467618a86a8b" "787a7d96b56477ff593b7d7f64d1337b1c638dd8d0f1e4bea945e8c0b9070fd9" | xxd -r -p | shasum -a 256

    Should print 11a7a5af9497b8980fea63a826f20d6ac4ce8ef7e30d016d32a64edee11de5bf

  4. 4. Combine step 2

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

    printf '01%s%s' "11a7a5af9497b8980fea63a826f20d6ac4ce8ef7e30d016d32a64edee11de5bf" "aaf85bd76fd21006e8402a227bd21923d53cf3d7371926d6a33d71c51e31be81" | xxd -r -p | shasum -a 256

    Should print a792b34de4a606dc5cbfc48203b2af1f6ded83bdb09048459fb5a6f9ded76794

  5. 5. Combine step 3

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

    printf '01%s%s' "56a825d661eedef74814c6317c32e5ecebdbbab058f72f4434d2501e8f69f442" "a792b34de4a606dc5cbfc48203b2af1f6ded83bdb09048459fb5a6f9ded76794" | xxd -r -p | shasum -a 256

    Should print 21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823

  6. 6. Combine step 4

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

    printf '01%s%s' "21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823" "4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787" | xxd -r -p | shasum -a 256

    Should print 4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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

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

Read the specification