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.

Peaceful Days - A fantasy cozy farming sim for this Autumn

Cozy Game Diary · 1 Oct 2026

Stamp ID
STAMP-2026-1001-23RAYWBJ
Content hash
9019ddaaf89583671bf1b9a0734828019d4d0560ef9222000c02baa3025646f2
Day recorded
2026-10-01
Articles recorded that day
19
Attestation UID
0x603b46532a7efbd9420f294207f0abcd39e475cccc5bcbbe0e361a4bb85dbbbe
View on EAS
Transaction
0x542521066dc4058a3602b27ff9baa48863be20de6eaa6baaadb6df2c602e64ab
View on Basescan
Stamped
2 Oct 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
0x44551948fbdc068e1a968634404f7d02cd2d10e9880ac6164d471e6bfa1ee932

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 after it
    0x79d3530b1503c76fe94d90cb7c8450317719541da690b3989c7861ef8b53cbd0
    0x1f5caf42f54f67ffb6d31c50ae8e39e300e1de3e55231fbcba0cf46f60f91102
  2. Step 2, combined with the value after it
    0x17ef894d3e82d695bc441cc75ef328fb91c78d68943e1be83e92307b104de7e8
    0xcf24b85b1c54001ae98242451fdf6ac7d16199d8241d31c4592832adbcb4f53c
  3. Step 3, combined with the value before it
    0xa572e1caf0ceea7eeefbfdc95285c283f2e0c69a76251d97d02813de8af7832b
    0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be

    This is the value for the whole day.

Value these steps arrive at
0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be

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
0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be
Read from Base
0x20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be
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":"harvesthealth","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"This is such a hidden gem! 🍂✨","type":"text"}],"type":"paragraph"},{"content":[{"…

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-1001-23RAYWBJ/canonical" | shasum -a 256

    Should print 9019ddaaf89583671bf1b9a0734828019d4d0560ef9222000c02baa3025646f2

  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-1001-23RAYWBJ CONTENT=9019ddaaf89583671bf1b9a0734828019d4d0560ef9222000c02baa3025646f2 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 44551948fbdc068e1a968634404f7d02cd2d10e9880ac6164d471e6bfa1ee932

  3. 3. Combine step 1

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

    printf '01%s%s' "44551948fbdc068e1a968634404f7d02cd2d10e9880ac6164d471e6bfa1ee932" "79d3530b1503c76fe94d90cb7c8450317719541da690b3989c7861ef8b53cbd0" | xxd -r -p | shasum -a 256

    Should print 1f5caf42f54f67ffb6d31c50ae8e39e300e1de3e55231fbcba0cf46f60f91102

  4. 4. Combine step 2

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

    printf '01%s%s' "1f5caf42f54f67ffb6d31c50ae8e39e300e1de3e55231fbcba0cf46f60f91102" "17ef894d3e82d695bc441cc75ef328fb91c78d68943e1be83e92307b104de7e8" | xxd -r -p | shasum -a 256

    Should print cf24b85b1c54001ae98242451fdf6ac7d16199d8241d31c4592832adbcb4f53c

  5. 5. Combine step 3

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

    printf '01%s%s' "a572e1caf0ceea7eeefbfdc95285c283f2e0c69a76251d97d02813de8af7832b" "cf24b85b1c54001ae98242451fdf6ac7d16199d8241d31c4592832adbcb4f53c" | xxd -r -p | shasum -a 256

    Should print 20f71ac084da418fd1d5b2ebebba09656abbfd62201c9e167d4ca5a15ba514be

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

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

Read the specification