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.

Make Stretching a Daily Habit

@HealthyByHabit · 26 Sept 2026

Stamp ID
STAMP-2026-0926-XYTGUGIN
Content hash
6a99671f4101ca896411d7acd9ea9c339b0b52422a4805b9f3705c893d9c3a77
Day recorded
2026-09-27
Articles recorded that day
19
Attestation UID
0x84cb5f3777a1d6bf11bc9929df9416c96f83e77a90905fa5ee406bde170afbe4
View on EAS
Transaction
0x2bc739663021c9616f855df1349f0c9e05f39f843e986166a72ea6bd60bfa4ec
View on Basescan
Stamped
27 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 18 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
0x4d2a88675851a159eaab87131df34204985359c2b2d87af9a90764a7b5831358

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
    0x60853dc61187cfaed54f0e5ab40ef7709fe277302732ea711f011fd271a28444
    0x447e4bfd13bc5454b89f1f21073ce534ba34f492a10887316d322a617fc4bd7b
  2. Step 2, combined with the value after it
    0xce5251723dde7adf5ef694955d54de3104b1e1f0cece9d0065eae2999fce30e0
    0xd5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0
  3. Step 3, combined with the value before it
    0x43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b
    0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

    This is the value for the whole day.

Value these steps arrive at
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

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
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
Read from Base
0xd5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300
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":"HealthyByHabit","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Just a few minutes of stretching can help improve flexibility, ease stiffness, a…

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

    Should print 6a99671f4101ca896411d7acd9ea9c339b0b52422a4805b9f3705c893d9c3a77

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

    Should print 4d2a88675851a159eaab87131df34204985359c2b2d87af9a90764a7b5831358

  3. 3. Combine step 1

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

    printf '01%s%s' "60853dc61187cfaed54f0e5ab40ef7709fe277302732ea711f011fd271a28444" "4d2a88675851a159eaab87131df34204985359c2b2d87af9a90764a7b5831358" | xxd -r -p | shasum -a 256

    Should print 447e4bfd13bc5454b89f1f21073ce534ba34f492a10887316d322a617fc4bd7b

  4. 4. Combine step 2

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

    printf '01%s%s' "447e4bfd13bc5454b89f1f21073ce534ba34f492a10887316d322a617fc4bd7b" "ce5251723dde7adf5ef694955d54de3104b1e1f0cece9d0065eae2999fce30e0" | xxd -r -p | shasum -a 256

    Should print d5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0

  5. 5. Combine step 3

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

    printf '01%s%s' "43d0bf3bed65c6d72323e4f8ee304cbe8a76398161018db8037b86aac993199b" "d5acd05b3170caa30612ab1b1206ba3a18114f6e7bec9204be2832f1245f31f0" | xxd -r -p | shasum -a 256

    Should print d5bae37d71e637433d461768eb3a88245c40982e2443fd3dd56fe575a55dd300

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

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

Read the specification