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.

Movement, fun, and good vibes!

@moveandthriveclub · 29 Oct 2026

Stamp ID
STAMP-2026-1029-H4NQIC7J
Content hash
edd1bdc7a3efe3a2d4e809237b38f04ca5247d6561df78d318219ef0fe7517a2
Day recorded
2026-10-30
Articles recorded that day
15
Attestation UID
0x8a0c10ce03592e13c4ce122e3babd8fcc9ffed2a274e6bad4a519029f53173c8
View on EAS
Transaction
0xe649e16f8f76c6fb5515456bd972c25015f49a6f03c541c81135262804602ab5
View on Basescan
Stamped
30 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 14 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
0xd21c7ab5c4ce95e05e32666848978014a2baa023f6f74093fcae1fed5e8de231

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
    0xcc283afb577f0e30aa57c3d80a46f5a3045b419bdea6fda2836289075d6b453b
    0xe5044f3ca8bcb8bd277130510a19a2c910407a8c8d64f0772d8b416b7a09046d
  2. Step 2, combined with the value after it
    0x10f622ded015b21d321ce08111ecec0432ecb11bb3584bee3c556311dd9b8999
    0xf75797c5194ce7a3f069b51ee5b5b7f9bf314ab20f70cc940bc0b6b440aaf783
  3. Step 3, combined with the value before it
    0x9a51ccacffd40851f29e80ccd0662dada4150d8c1eb54753d1463b3f479f315b
    0xa25067886337ab5683d494cb956e6fe08115f907cc4e1f59a5cae62147d46624
  4. Step 4, combined with the value after it
    0xc25eb6e9187995c8dc97a8ed32371aa6eca00d9612aa823971dd23febed2f330
    0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

    This is the value for the whole day.

Value these steps arrive at
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

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
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84
Read from Base
0x4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84
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":"moveandthriveclub","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Today’s fun activity: ","type":"text"},{"marks":[{"type":"bold"}],"text":"ICE…

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

    Should print edd1bdc7a3efe3a2d4e809237b38f04ca5247d6561df78d318219ef0fe7517a2

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

    Should print d21c7ab5c4ce95e05e32666848978014a2baa023f6f74093fcae1fed5e8de231

  3. 3. Combine step 1

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

    printf '01%s%s' "cc283afb577f0e30aa57c3d80a46f5a3045b419bdea6fda2836289075d6b453b" "d21c7ab5c4ce95e05e32666848978014a2baa023f6f74093fcae1fed5e8de231" | xxd -r -p | shasum -a 256

    Should print e5044f3ca8bcb8bd277130510a19a2c910407a8c8d64f0772d8b416b7a09046d

  4. 4. Combine step 2

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

    printf '01%s%s' "e5044f3ca8bcb8bd277130510a19a2c910407a8c8d64f0772d8b416b7a09046d" "10f622ded015b21d321ce08111ecec0432ecb11bb3584bee3c556311dd9b8999" | xxd -r -p | shasum -a 256

    Should print f75797c5194ce7a3f069b51ee5b5b7f9bf314ab20f70cc940bc0b6b440aaf783

  5. 5. Combine step 3

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

    printf '01%s%s' "9a51ccacffd40851f29e80ccd0662dada4150d8c1eb54753d1463b3f479f315b" "f75797c5194ce7a3f069b51ee5b5b7f9bf314ab20f70cc940bc0b6b440aaf783" | xxd -r -p | shasum -a 256

    Should print a25067886337ab5683d494cb956e6fe08115f907cc4e1f59a5cae62147d46624

  6. 6. Combine step 4

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

    printf '01%s%s' "a25067886337ab5683d494cb956e6fe08115f907cc4e1f59a5cae62147d46624" "c25eb6e9187995c8dc97a8ed32371aa6eca00d9612aa823971dd23febed2f330" | xxd -r -p | shasum -a 256

    Should print 4ef6f2c20db5e6c396b7ce044ae0c4fc565d3af3a34fa8c8d588a2f3ca3eac84

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

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

Read the specification