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.

SCAD 2026

cardiovitahash · 26 Aug 2026

Stamp ID
STAMP-2026-0826-7QA6WL3T
Content hash
062779992b0aecbe7120a46dba2875c885cf6d69f368e02c5695efc6edda44a0
Day recorded
2026-08-27
Articles recorded that day
10
Attestation UID
0xe9594f1c42a4ac3701b860a351cf04e831783def05460049c9572d205cc57f43
View on EAS
Transaction
0xd0bb0633972b35907cdba8ec4fd69a6070b990a29412e09027453092ea78db06
View on Basescan
Stamped
27 Aug 2026

Recorded on Base Sepolia using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 9 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
0xad07a82a0ef28a08d9090b1636c59652db83a3bf1888decae6b707132f460b29

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
    0xa1df1acbb360c1f6fe4d03c0721cf11cf2d1ee4dcdf690fa766a2157c52232b6
    0xdee11797b11deb20eb8b6e59cd24b35825b0f2548ec459d05ab3dc256259846e
  2. Step 2, combined with the value after it
    0x614fcb8df70cfd7cae006fd6b8676517f8337434cc9a2789580d6c485dabe4c0
    0x6a9201a5fa622d9e3cfbfb0a4ba6051fc37c1c172f63aa6087bfb245df8b1320
  3. Step 3, combined with the value after it
    0x5f8fd93d1342e6f582a2588d1c24ba86122827e4293e14743a5edbfb0c06c744
    0xa21c8ba55f0fc6e57b545c6de25652a6b6edb54b52b930f491c0ed5edde1df08
  4. Step 4, combined with the value after it
    0x8680bcd982597baa59b5474438998fb2c932f4e7c4dc44c0962bfa4b522c7829
    0xd18600dbfb6bcb059d5c725341c007e642eceb0a8393d6b788c0fb7609a936ac

    This is the value for the whole day.

Value these steps arrive at
0xd18600dbfb6bcb059d5c725341c007e642eceb0a8393d6b788c0fb7609a936ac

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
0xd18600dbfb6bcb059d5c725341c007e642eceb0a8393d6b788c0fb7609a936ac
Read from Base
0xd18600dbfb6bcb059d5c725341c007e642eceb0a8393d6b788c0fb7609a936ac
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,"authors":[{"identity":"cardiovitahash","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Check this out ","type":"text"},{"marks":[{"attrs":{"href":"https://www.youtube.com/watch?v=VIZ-lD…

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-0826-7QA6WL3T/canonical" | shasum -a 256

    Should print 062779992b0aecbe7120a46dba2875c885cf6d69f368e02c5695efc6edda44a0

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

    Should print ad07a82a0ef28a08d9090b1636c59652db83a3bf1888decae6b707132f460b29

  3. 3. Combine step 1

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

    printf '01%s%s' "a1df1acbb360c1f6fe4d03c0721cf11cf2d1ee4dcdf690fa766a2157c52232b6" "ad07a82a0ef28a08d9090b1636c59652db83a3bf1888decae6b707132f460b29" | xxd -r -p | shasum -a 256

    Should print dee11797b11deb20eb8b6e59cd24b35825b0f2548ec459d05ab3dc256259846e

  4. 4. Combine step 2

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

    printf '01%s%s' "dee11797b11deb20eb8b6e59cd24b35825b0f2548ec459d05ab3dc256259846e" "614fcb8df70cfd7cae006fd6b8676517f8337434cc9a2789580d6c485dabe4c0" | xxd -r -p | shasum -a 256

    Should print 6a9201a5fa622d9e3cfbfb0a4ba6051fc37c1c172f63aa6087bfb245df8b1320

  5. 5. Combine step 3

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

    printf '01%s%s' "6a9201a5fa622d9e3cfbfb0a4ba6051fc37c1c172f63aa6087bfb245df8b1320" "5f8fd93d1342e6f582a2588d1c24ba86122827e4293e14743a5edbfb0c06c744" | xxd -r -p | shasum -a 256

    Should print a21c8ba55f0fc6e57b545c6de25652a6b6edb54b52b930f491c0ed5edde1df08

  6. 6. Combine step 4

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

    printf '01%s%s' "a21c8ba55f0fc6e57b545c6de25652a6b6edb54b52b930f491c0ed5edde1df08" "8680bcd982597baa59b5474438998fb2c932f4e7c4dc44c0962bfa4b522c7829" | xxd -r -p | shasum -a 256

    Should print d18600dbfb6bcb059d5c725341c007e642eceb0a8393d6b788c0fb7609a936ac

  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-sepolia.easscan.org/attestation/view/0xe9594f1c42a4ac3701b860a351cf04e831783def05460049c9572d205cc57f43

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

Read the specification