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.

Remember When You Had to Rewind a VHS Tape? 📼

@90sTimeCapsule · 2 Oct 2026

Stamp ID
STAMP-2026-1002-KUJSY6LC
Content hash
cfaade6bcd0dc42fc3948fc288bc0a79d6207c20c32c3ab7af6cf9f4479d4af1
Day recorded
2026-10-03
Articles recorded that day
16
Attestation UID
0xef4f7164340d74127588865a66f8ad6b4a147adaddfe66714768f453ef45889a
View on EAS
Transaction
0x323083d5c9fba3e5a84957bc6699b4170b174ca5622bd6b53ff3582408e1e794
View on Basescan
Stamped
3 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
0x27f8381a2a231e5fe3e06f98af6bae76b85265518dee62effe5c2d15aea21c3f

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
    0x7b9c50b490c4d0bd53139a0d2c20f0f6f7b933aa65a6d03bfdad77091aab0d13
    0xab9e90de93ca45c63efb8c80a5b1425349f0cdf75087755cdc81de994b198cc5
  2. Step 2, combined with the value before it
    0x8235d39e3194012e68a245eb60e3387ded28f9648cceea0232da0372015d0a09
    0x9c5035deee8f866c7c076d44ae632db013efd5551df898064e6014c6e3287580
  3. Step 3, combined with the value before it
    0x72ecfbda71fe255e28fe1d3ce8b7fd1522d709ac0fc9ce557d4d5db354afa8cf
    0x17f2f01650272ea450367707dd019f7a18228797c30fcd563c069675dcd2d3ab
  4. Step 4, combined with the value after it
    0x0a8735948a3473ac9a9a57e04d8fadf11d680d37b43511e41e0f3a293772c19d
    0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

    This is the value for the whole day.

Value these steps arrive at
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

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
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec
Read from Base
0xff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec
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":"90sTimeCapsule","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Before streaming and instant playback, watching a movie meant popping a VHS tape…

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-1002-KUJSY6LC/canonical" | shasum -a 256

    Should print cfaade6bcd0dc42fc3948fc288bc0a79d6207c20c32c3ab7af6cf9f4479d4af1

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

    Should print 27f8381a2a231e5fe3e06f98af6bae76b85265518dee62effe5c2d15aea21c3f

  3. 3. Combine step 1

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

    printf '01%s%s' "7b9c50b490c4d0bd53139a0d2c20f0f6f7b933aa65a6d03bfdad77091aab0d13" "27f8381a2a231e5fe3e06f98af6bae76b85265518dee62effe5c2d15aea21c3f" | xxd -r -p | shasum -a 256

    Should print ab9e90de93ca45c63efb8c80a5b1425349f0cdf75087755cdc81de994b198cc5

  4. 4. Combine step 2

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

    printf '01%s%s' "8235d39e3194012e68a245eb60e3387ded28f9648cceea0232da0372015d0a09" "ab9e90de93ca45c63efb8c80a5b1425349f0cdf75087755cdc81de994b198cc5" | xxd -r -p | shasum -a 256

    Should print 9c5035deee8f866c7c076d44ae632db013efd5551df898064e6014c6e3287580

  5. 5. Combine step 3

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

    printf '01%s%s' "72ecfbda71fe255e28fe1d3ce8b7fd1522d709ac0fc9ce557d4d5db354afa8cf" "9c5035deee8f866c7c076d44ae632db013efd5551df898064e6014c6e3287580" | xxd -r -p | shasum -a 256

    Should print 17f2f01650272ea450367707dd019f7a18228797c30fcd563c069675dcd2d3ab

  6. 6. Combine step 4

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

    printf '01%s%s' "17f2f01650272ea450367707dd019f7a18228797c30fcd563c069675dcd2d3ab" "0a8735948a3473ac9a9a57e04d8fadf11d680d37b43511e41e0f3a293772c19d" | xxd -r -p | shasum -a 256

    Should print ff8c2ed92267ef3ed3a91f1bd05eb91ed004c664072f546dd5a646157bdd70ec

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

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

Read the specification