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-1107-UU5F726W
Content hash
9db8a1cb73fedec0a0cc74e0c9125938a0318f79ce37483bb49de0e277739988
Day recorded
2026-11-08
Articles recorded that day
11
Attestation UID
0xc2975ac9bda3dbf71c204dcdb6342aea7652638251f29e40790db1f99df9607c
View on EAS
Transaction
0x47ec2bd8544decaf23f3fc4d96ed07efe94c731c138126e66eceef1c66948a38
View on Basescan
Stamped
8 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 10 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
0x37742e3c1424724e8bb7868198a33ced2b2aca0d9a9a9a4f9dc3fcc3095a2be5

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
    0x6540c922e3da28c13b33da948100ca4b009c7d970acde9eba321a9060c12448c
    0x450f126713ab98aba4587a2faad61cf2ae2c10a7a0618009e25b0bea07eea2d3
  2. Step 2, combined with the value after it
    0xac414491a75298fbb50382fc3e881c947391a53fe7860c3a93c9b253d9ce0b29
    0x652543937c6ec0cb1cac2019fc1342400b419b4ce6f9e0b696ae93a40e23eea2
  3. Step 3, combined with the value before it
    0xb464e8637cc8300217b504ca5620866817225bf01732ab7519efe2b4379d4f87
    0x47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41

    This is the value for the whole day.

Value these steps arrive at
0x47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41

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
0x47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41
Read from Base
0x47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41
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":"If you grew up in the 90s, you probably remember the excitement of getting a McD…

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-1107-UU5F726W/canonical" | shasum -a 256

    Should print 9db8a1cb73fedec0a0cc74e0c9125938a0318f79ce37483bb49de0e277739988

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

    Should print 37742e3c1424724e8bb7868198a33ced2b2aca0d9a9a9a4f9dc3fcc3095a2be5

  3. 3. Combine step 1

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

    printf '01%s%s' "6540c922e3da28c13b33da948100ca4b009c7d970acde9eba321a9060c12448c" "37742e3c1424724e8bb7868198a33ced2b2aca0d9a9a9a4f9dc3fcc3095a2be5" | xxd -r -p | shasum -a 256

    Should print 450f126713ab98aba4587a2faad61cf2ae2c10a7a0618009e25b0bea07eea2d3

  4. 4. Combine step 2

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

    printf '01%s%s' "450f126713ab98aba4587a2faad61cf2ae2c10a7a0618009e25b0bea07eea2d3" "ac414491a75298fbb50382fc3e881c947391a53fe7860c3a93c9b253d9ce0b29" | xxd -r -p | shasum -a 256

    Should print 652543937c6ec0cb1cac2019fc1342400b419b4ce6f9e0b696ae93a40e23eea2

  5. 5. Combine step 3

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

    printf '01%s%s' "b464e8637cc8300217b504ca5620866817225bf01732ab7519efe2b4379d4f87" "652543937c6ec0cb1cac2019fc1342400b419b4ce6f9e0b696ae93a40e23eea2" | xxd -r -p | shasum -a 256

    Should print 47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41

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

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

Read the specification