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-1117-7NQMYIDW
Content hash
193302dd4b9b641990c146f36bc287ff9e5ac52038df7673f08e4c89709a1a48
Day recorded
2026-11-18
Articles recorded that day
13
Attestation UID
0x8e85c088a1dfa2c1d4c61128c4b80f7ae38902ba14855ba7f9a6bb8f3af8d04a
View on EAS
Transaction
0xf97343d7eee1fac90b2c347a4d59edc12f9b69c342c1952ec384a51a3d595f42
View on Basescan
Stamped
18 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 12 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
0x62e78a101370300a226a0bb1268cb2fc6a2414e0680d44d2965c44ed642d2900

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
    0x835e5621ee590af53ef8b933e80fc4a46b12461bcb4203914dad34635a2f8d13
    0x757439a5f1257f63fbbf9c54ebf49a336e579562e3de7879d13e3548fcaffbdd
  2. Step 2, combined with the value before it
    0xa70059d97aba49c6b0a14b2946d4a4415007577b3f730705fd551c7d188dc582
    0x6e5bd5e59ad003d485e506796724c84f9f7a77e6ef50f25b76114d414dfb9b22
  3. Step 3, combined with the value after it
    0xad02bc71dc787b475181acba6e4ad9cbfa96dbaeded1fbb36349766c41b30492
    0x7fab226af8ebfe45bcfb81565ff93482a960d73483542d408eb9d41059ec0a83
  4. Step 4, combined with the value after it
    0x1536ecd854b554678e7a9a8dfce28a9136a9055ad3680595e5c5163c6917910e
    0x66d99531c4c2d99a068b9d05f894aac03f2d67079710939129666a3dcf92a53a

    This is the value for the whole day.

Value these steps arrive at
0x66d99531c4c2d99a068b9d05f894aac03f2d67079710939129666a3dcf92a53a

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
0x66d99531c4c2d99a068b9d05f894aac03f2d67079710939129666a3dcf92a53a
Read from Base
0x66d99531c4c2d99a068b9d05f894aac03f2d67079710939129666a3dcf92a53a
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":"Not every day is going to be a high-energy workout day, and that's okay! On d…

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

    Should print 193302dd4b9b641990c146f36bc287ff9e5ac52038df7673f08e4c89709a1a48

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

    Should print 62e78a101370300a226a0bb1268cb2fc6a2414e0680d44d2965c44ed642d2900

  3. 3. Combine step 1

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

    printf '01%s%s' "835e5621ee590af53ef8b933e80fc4a46b12461bcb4203914dad34635a2f8d13" "62e78a101370300a226a0bb1268cb2fc6a2414e0680d44d2965c44ed642d2900" | xxd -r -p | shasum -a 256

    Should print 757439a5f1257f63fbbf9c54ebf49a336e579562e3de7879d13e3548fcaffbdd

  4. 4. Combine step 2

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

    printf '01%s%s' "a70059d97aba49c6b0a14b2946d4a4415007577b3f730705fd551c7d188dc582" "757439a5f1257f63fbbf9c54ebf49a336e579562e3de7879d13e3548fcaffbdd" | xxd -r -p | shasum -a 256

    Should print 6e5bd5e59ad003d485e506796724c84f9f7a77e6ef50f25b76114d414dfb9b22

  5. 5. Combine step 3

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

    printf '01%s%s' "6e5bd5e59ad003d485e506796724c84f9f7a77e6ef50f25b76114d414dfb9b22" "ad02bc71dc787b475181acba6e4ad9cbfa96dbaeded1fbb36349766c41b30492" | xxd -r -p | shasum -a 256

    Should print 7fab226af8ebfe45bcfb81565ff93482a960d73483542d408eb9d41059ec0a83

  6. 6. Combine step 4

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

    printf '01%s%s' "7fab226af8ebfe45bcfb81565ff93482a960d73483542d408eb9d41059ec0a83" "1536ecd854b554678e7a9a8dfce28a9136a9055ad3680595e5c5163c6917910e" | xxd -r -p | shasum -a 256

    Should print 66d99531c4c2d99a068b9d05f894aac03f2d67079710939129666a3dcf92a53a

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

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

Read the specification