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.

Just watched Swiped on Hulu

Maya Hale · 8 Oct 2026

Stamp ID
STAMP-2026-1008-NFAZMND3
Content hash
0de200a510058c3ab0900990a412ec18a957c294785bc0d09738669fe13a8fcb
Day recorded
2026-10-09
Articles recorded that day
18
Attestation UID
0xc9f2778eaabda8f3825b12ccddbe0d2fe021b9fdb858c7bf7ef391d02a1bd650
View on EAS
Transaction
0x772581b0c402c238fb58b0e907078d4c05f8f9566bea1e401e4b2ac07d7e4996
View on Basescan
Stamped
10 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 17 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
0xb260ddcd3b10e6dad3c4a0ff7e18a47f9f161c1e1bee04b646fcfcdfc61a0541

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
    0x7bffdbe6a3e07edbacb82dc61e8525e5bfcfe55226fac3e2a62013c9dfb341fd
    0xb49f9cf37d82be03bb5e014b97ffc525dc506dd57cd5dab2c21db7483bdf2523
  2. Step 2, combined with the value after it
    0xa52da08070a61983d76fefac5053890a2a79509b8841b6fb0122ff6100fe79b4
    0x64537a68fabe7c81da356e02071072c5eb75f42856857734ef290a16d289ea60
  3. Step 3, combined with the value before it
    0xc73e7f2c9c616a30eb56bd6b33fac81d7cc7c805a8b34862224399fdcec319e6
    0x366704e51be5339bcfbd2dadf5673d4c73b3d9628408711d9dedcf5b792e4aac
  4. Step 4, combined with the value after it
    0x730b741698ce1e44832a12a50a945b3fa53dc581c3a8346cb6c8125d23b358a3
    0xc08b27e8a2d549dec72fb176403f4f93fa2e2351f43dff765d15a7ffbc41574f
  5. Step 5, combined with the value after it
    0xefe67e8818fed37489d7df9f4ccef876c449a371f6aa50ca6c7ee89876435ae8
    0xeb001c580d29d4587f4a3e8aafc9e961640c7ff2d9442e2f96576d645b8f22a8

    This is the value for the whole day.

Value these steps arrive at
0xeb001c580d29d4587f4a3e8aafc9e961640c7ff2d9442e2f96576d645b8f22a8

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
0xeb001c580d29d4587f4a3e8aafc9e961640c7ff2d9442e2f96576d645b8f22a8
Read from Base
0xeb001c580d29d4587f4a3e8aafc9e961640c7ff2d9442e2f96576d645b8f22a8
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":"mayahale","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Everyone knows Bumble. Fewer people know the messy story behind how it was built.","ty…

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-1008-NFAZMND3/canonical" | shasum -a 256

    Should print 0de200a510058c3ab0900990a412ec18a957c294785bc0d09738669fe13a8fcb

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

    Should print b260ddcd3b10e6dad3c4a0ff7e18a47f9f161c1e1bee04b646fcfcdfc61a0541

  3. 3. Combine step 1

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

    printf '01%s%s' "7bffdbe6a3e07edbacb82dc61e8525e5bfcfe55226fac3e2a62013c9dfb341fd" "b260ddcd3b10e6dad3c4a0ff7e18a47f9f161c1e1bee04b646fcfcdfc61a0541" | xxd -r -p | shasum -a 256

    Should print b49f9cf37d82be03bb5e014b97ffc525dc506dd57cd5dab2c21db7483bdf2523

  4. 4. Combine step 2

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

    printf '01%s%s' "b49f9cf37d82be03bb5e014b97ffc525dc506dd57cd5dab2c21db7483bdf2523" "a52da08070a61983d76fefac5053890a2a79509b8841b6fb0122ff6100fe79b4" | xxd -r -p | shasum -a 256

    Should print 64537a68fabe7c81da356e02071072c5eb75f42856857734ef290a16d289ea60

  5. 5. Combine step 3

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

    printf '01%s%s' "c73e7f2c9c616a30eb56bd6b33fac81d7cc7c805a8b34862224399fdcec319e6" "64537a68fabe7c81da356e02071072c5eb75f42856857734ef290a16d289ea60" | xxd -r -p | shasum -a 256

    Should print 366704e51be5339bcfbd2dadf5673d4c73b3d9628408711d9dedcf5b792e4aac

  6. 6. Combine step 4

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

    printf '01%s%s' "366704e51be5339bcfbd2dadf5673d4c73b3d9628408711d9dedcf5b792e4aac" "730b741698ce1e44832a12a50a945b3fa53dc581c3a8346cb6c8125d23b358a3" | xxd -r -p | shasum -a 256

    Should print c08b27e8a2d549dec72fb176403f4f93fa2e2351f43dff765d15a7ffbc41574f

  7. 7. Combine step 5

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

    printf '01%s%s' "c08b27e8a2d549dec72fb176403f4f93fa2e2351f43dff765d15a7ffbc41574f" "efe67e8818fed37489d7df9f4ccef876c449a371f6aa50ca6c7ee89876435ae8" | xxd -r -p | shasum -a 256

    Should print eb001c580d29d4587f4a3e8aafc9e961640c7ff2d9442e2f96576d645b8f22a8

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

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

Read the specification