Verify

Sign inSign up

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.

There's Something Special About a New Friendship

@PositiveVibez · 7 Nov 2026

Stamp ID
STAMP-2026-1107-P3CB5NTO
Content hash
4a232f469df76153e0bc9f7de880b4995c3dd316bd80ddb40790ae3def69b441
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
0x56f6767b3ba12b43f2b27b21ef7a7c611b7d22bfb73d40a915a352453a1c2ad4

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
    0xc41648e7a34d21a603e4738f54f5145f3132959b97660ea913e31a7ef4da8941
    0xff55ddff8212827728ad2e43002b41de10e1d48fa11505fa6734f91d12e20e12
  2. Step 2, combined with the value after it
    0xa698596bafe108b7aff8b872190c47f6fe22c8b6a0e50074bf093546abea7c23
    0x619d9b6cf7be91f954e51ce369f4d1172e3325b1e3a685a625e767aff583084a
  3. Step 3, combined with the value before it
    0xcd1e605fd4fb27f444aa2135e9596d79e406658a66cbe5e9b1130cef0892a698
    0xb464e8637cc8300217b504ca5620866817225bf01732ab7519efe2b4379d4f87
  4. Step 4, combined with the value after it
    0x652543937c6ec0cb1cac2019fc1342400b419b4ce6f9e0b696ae93a40e23eea2
    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":"PositiveVibez","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Sometimes the best people enter your life when you least expect it. A new friends…

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

    Should print 4a232f469df76153e0bc9f7de880b4995c3dd316bd80ddb40790ae3def69b441

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

    Should print 56f6767b3ba12b43f2b27b21ef7a7c611b7d22bfb73d40a915a352453a1c2ad4

  3. 3. Combine step 1

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

    printf '01%s%s' "c41648e7a34d21a603e4738f54f5145f3132959b97660ea913e31a7ef4da8941" "56f6767b3ba12b43f2b27b21ef7a7c611b7d22bfb73d40a915a352453a1c2ad4" | xxd -r -p | shasum -a 256

    Should print ff55ddff8212827728ad2e43002b41de10e1d48fa11505fa6734f91d12e20e12

  4. 4. Combine step 2

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

    printf '01%s%s' "ff55ddff8212827728ad2e43002b41de10e1d48fa11505fa6734f91d12e20e12" "a698596bafe108b7aff8b872190c47f6fe22c8b6a0e50074bf093546abea7c23" | xxd -r -p | shasum -a 256

    Should print 619d9b6cf7be91f954e51ce369f4d1172e3325b1e3a685a625e767aff583084a

  5. 5. Combine step 3

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

    printf '01%s%s' "cd1e605fd4fb27f444aa2135e9596d79e406658a66cbe5e9b1130cef0892a698" "619d9b6cf7be91f954e51ce369f4d1172e3325b1e3a685a625e767aff583084a" | xxd -r -p | shasum -a 256

    Should print b464e8637cc8300217b504ca5620866817225bf01732ab7519efe2b4379d4f87

  6. 6. Combine step 4

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

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

    Should print 47889d0360d083dccec3fdfa62ad94f2586617a1ef045810e72f0ddba18dac41

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

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

Read the specification