Verify

Sign inSign up

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 We Had to Wait for Our Favorite Song to Come on the Radio?

@90sTimeCapsule · 6 Nov 2026

Stamp ID
STAMP-2026-1106-5VO45YLV
Content hash
5fd3dc41ee1fb1c47f41fc39ef4fbbe5b4016450c9accea8524c0a8ed604f658
Day recorded
2026-11-07
Articles recorded that day
15
Attestation UID
0xd9793b77ba6b93783bcd5b0a359aaf1a7dee2e68a083fadff2ae4ee8a5871e4c
View on EAS
Transaction
0x35ed9a40d9a3b461b78b4731280547047519bbb2a3e24003beb379fc5ef38813
View on Basescan
Stamped
7 Nov 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
0x8b5e21ccc86ada9d00637c3ff24b03e1f1c748b2c26b18eab011096cac4c5034

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
    0xdc4b18f253e1a5342db660c3bde16138ebeed387d2929f68e3cf7c9addff898f
    0xbbe7de08f8e283e66c9711fd96e2ed333e9a0fdf8680c7da0318a5c1e732feac
  2. Step 2, combined with the value after it
    0xec64c1f109fed9aaa92e72d8ee45c5482999c0bdc75190f05d121864c3ccdb80
    0x5f4c78878c433a20977edba36ce661e2bfc4a13b082d50cb735666d4d977c052
  3. Step 3, combined with the value after it
    0x40d6abd9880e85daf66fb10db9f264cd25bc42786f13e6c09e177a86e9d1ce55
    0x5d636f88f0b1927ea271d4422d94dd394c2b112107a20025f4b5399f89482ee5
  4. Step 4, combined with the value after it
    0x3a1f5efbf571f237939e6f56cf06693a664dfee09c4563ab88af10d1650a51ae
    0x48f47fdbe0ece678c7d5078af9cd7e1430e1b809937216598ff09da61fbe69df

    This is the value for the whole day.

Value these steps arrive at
0x48f47fdbe0ece678c7d5078af9cd7e1430e1b809937216598ff09da61fbe69df

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
0x48f47fdbe0ece678c7d5078af9cd7e1430e1b809937216598ff09da61fbe69df
Read from Base
0x48f47fdbe0ece678c7d5078af9cd7e1430e1b809937216598ff09da61fbe69df
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":"You heard the first few seconds of your favorite song and immediately grabbed a …

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-1106-5VO45YLV/canonical" | shasum -a 256

    Should print 5fd3dc41ee1fb1c47f41fc39ef4fbbe5b4016450c9accea8524c0a8ed604f658

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

    Should print 8b5e21ccc86ada9d00637c3ff24b03e1f1c748b2c26b18eab011096cac4c5034

  3. 3. Combine step 1

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

    printf '01%s%s' "dc4b18f253e1a5342db660c3bde16138ebeed387d2929f68e3cf7c9addff898f" "8b5e21ccc86ada9d00637c3ff24b03e1f1c748b2c26b18eab011096cac4c5034" | xxd -r -p | shasum -a 256

    Should print bbe7de08f8e283e66c9711fd96e2ed333e9a0fdf8680c7da0318a5c1e732feac

  4. 4. Combine step 2

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

    printf '01%s%s' "bbe7de08f8e283e66c9711fd96e2ed333e9a0fdf8680c7da0318a5c1e732feac" "ec64c1f109fed9aaa92e72d8ee45c5482999c0bdc75190f05d121864c3ccdb80" | xxd -r -p | shasum -a 256

    Should print 5f4c78878c433a20977edba36ce661e2bfc4a13b082d50cb735666d4d977c052

  5. 5. Combine step 3

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

    printf '01%s%s' "5f4c78878c433a20977edba36ce661e2bfc4a13b082d50cb735666d4d977c052" "40d6abd9880e85daf66fb10db9f264cd25bc42786f13e6c09e177a86e9d1ce55" | xxd -r -p | shasum -a 256

    Should print 5d636f88f0b1927ea271d4422d94dd394c2b112107a20025f4b5399f89482ee5

  6. 6. Combine step 4

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

    printf '01%s%s' "5d636f88f0b1927ea271d4422d94dd394c2b112107a20025f4b5399f89482ee5" "3a1f5efbf571f237939e6f56cf06693a664dfee09c4563ab88af10d1650a51ae" | xxd -r -p | shasum -a 256

    Should print 48f47fdbe0ece678c7d5078af9cd7e1430e1b809937216598ff09da61fbe69df

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

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

Read the specification