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.

We are so back !!

iSpace · 10 Sept 2026

Stamp ID
STAMP-2026-0910-USKGFK4Z
Content hash
bb2703a368c84dc1a6175afdd81f19c025188882abc49993cf62b7ed2d422fc6
Day recorded
2026-09-11
Articles recorded that day
7
Attestation UID
0x43dd040a36ca280cd09cc8ecc6139eac09edbe31e9fc66b954bcb354e6632ac8
View on EAS
Transaction
0x3bcb5ee308c0e96aeb2462c554339d1f273ddc4af14e018f66d66740b22a0dd6
View on Basescan
Stamped
11 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 6 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
0x308b852478c37fb99ed3183740da686d034df5d4463a5b8bf6e29c25fe822f4a

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
    0xebe0e6489baaa60c289f5ad1c214b29e34414d724561f8481ecfcade2a2f63f5
    0x38be2a6e9726c78a683f3e6c029aca3b66d2dd2df6c32c5bb063084cce6bd82a
  2. Step 2, combined with the value after it
    0xe5f03b124907bdd191ce1569e094d888419c93e07109ec093475ad8b00b60a1e
    0x9d219722d7b5ca1b6b93640cb99cb26872d115b20f8fb163e9367b343dff4564
  3. Step 3, combined with the value before it
    0x5e650b8006d2a7eda81bb5d4ed9c0d4d00a341c3830745859eaba27f43433dfa
    0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

    This is the value for the whole day.

Value these steps arrive at
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

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
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7
Read from Base
0x23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7
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.

The exact text is not available for this article right now. The command below still reaches it.

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-0910-USKGFK4Z/canonical" | shasum -a 256

    Should print bb2703a368c84dc1a6175afdd81f19c025188882abc49993cf62b7ed2d422fc6

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

    Should print 308b852478c37fb99ed3183740da686d034df5d4463a5b8bf6e29c25fe822f4a

  3. 3. Combine step 1

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

    printf '01%s%s' "ebe0e6489baaa60c289f5ad1c214b29e34414d724561f8481ecfcade2a2f63f5" "308b852478c37fb99ed3183740da686d034df5d4463a5b8bf6e29c25fe822f4a" | xxd -r -p | shasum -a 256

    Should print 38be2a6e9726c78a683f3e6c029aca3b66d2dd2df6c32c5bb063084cce6bd82a

  4. 4. Combine step 2

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

    printf '01%s%s' "38be2a6e9726c78a683f3e6c029aca3b66d2dd2df6c32c5bb063084cce6bd82a" "e5f03b124907bdd191ce1569e094d888419c93e07109ec093475ad8b00b60a1e" | xxd -r -p | shasum -a 256

    Should print 9d219722d7b5ca1b6b93640cb99cb26872d115b20f8fb163e9367b343dff4564

  5. 5. Combine step 3

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

    printf '01%s%s' "5e650b8006d2a7eda81bb5d4ed9c0d4d00a341c3830745859eaba27f43433dfa" "9d219722d7b5ca1b6b93640cb99cb26872d115b20f8fb163e9367b343dff4564" | xxd -r -p | shasum -a 256

    Should print 23678bd26e188a26b1928f578d79388c822fad626d52b886eeb90f6955eef1b7

  6. 6. 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/0x43dd040a36ca280cd09cc8ecc6139eac09edbe31e9fc66b954bcb354e6632ac8

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

Read the specification