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.

Stamp ID
STAMP-2026-0912-WF46PXLH
Content hash
5da2c0e040783b9336a815d9e6d2bb717ea001a26b7df0db8e3ba813e36839c8
Day recorded
2026-09-13
Articles recorded that day
12
Attestation UID
0xe3d8bd2eb8f03a62049ad18692cb77891d5172e148e4d05da8c0caa3a3d19861
View on EAS
Transaction
0x805d0579370308945e4cd9dcbcee7ba593bbae37a839bbee40333a5f4845cf0a
View on Basescan
Stamped
13 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

It was combined with the other 11 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
0x7bed0a21655a03e17a94cb02d84f910ea3b29257ed3292c514789819fb546629

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 after it
    0x20315b0997c2bfe4c264a0d74d259f1ab2fd4ce8d2b1e3451b3994a57481c89a
    0x93e6b7be8d3dac139659027698adb5d3466b5e5adb8b31d62176d496d6f35e01
  2. Step 2, combined with the value after it
    0x9fd359cf554370f4d68be8d2d72dbb1c30a7e1ebc4ab240496d42aaae482bc1a
    0x8d23c52490116aed9c6806c460a82c2867e0d8fa16cde80f349574b442de9011
  3. Step 3, combined with the value before it
    0x7a5d92dadcf9090e0ca98ca0332b44c973c20ce01f4370a0e1e7c59929bb124b
    0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3

    This is the value for the whole day.

Value these steps arrive at
0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3

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
0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3
Read from Base
0xafe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3
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-0912-WF46PXLH/canonical" | shasum -a 256

    Should print 5da2c0e040783b9336a815d9e6d2bb717ea001a26b7df0db8e3ba813e36839c8

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

    Should print 7bed0a21655a03e17a94cb02d84f910ea3b29257ed3292c514789819fb546629

  3. 3. Combine step 1

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

    printf '01%s%s' "7bed0a21655a03e17a94cb02d84f910ea3b29257ed3292c514789819fb546629" "20315b0997c2bfe4c264a0d74d259f1ab2fd4ce8d2b1e3451b3994a57481c89a" | xxd -r -p | shasum -a 256

    Should print 93e6b7be8d3dac139659027698adb5d3466b5e5adb8b31d62176d496d6f35e01

  4. 4. Combine step 2

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

    printf '01%s%s' "93e6b7be8d3dac139659027698adb5d3466b5e5adb8b31d62176d496d6f35e01" "9fd359cf554370f4d68be8d2d72dbb1c30a7e1ebc4ab240496d42aaae482bc1a" | xxd -r -p | shasum -a 256

    Should print 8d23c52490116aed9c6806c460a82c2867e0d8fa16cde80f349574b442de9011

  5. 5. Combine step 3

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

    printf '01%s%s' "7a5d92dadcf9090e0ca98ca0332b44c973c20ce01f4370a0e1e7c59929bb124b" "8d23c52490116aed9c6806c460a82c2867e0d8fa16cde80f349574b442de9011" | xxd -r -p | shasum -a 256

    Should print afe50b3f022867873ac74178a7f6d82f520d3161a2fc7d09780bd513b8ba39e3

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

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

Read the specification