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.

The Shell-Shopping Life of Hermit Crabs

@ThePetTales · 28 Sept 2026

Stamp ID
STAMP-2026-0928-OVHGQDBZ
Content hash
290dff5668b12e55eaa9e1eca3c6ec63e9f176c5393550b5a9065e9eceda4944
Day recorded
2026-09-29
Articles recorded that day
15
Attestation UID
0xbae130a241adf69f2744a98f825c09f1191365141388269e4536aea3291c1f4a
View on EAS
Transaction
0x248e8396d3b4daab287e00cbf1d99cbd304b2f4cba6d9f96b9de502ad796f815
View on Basescan
Stamped
29 Sept 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
0x560bafc68d216ae19a18984b8433c202ec5596135096736f89ac9ff530a67570

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
    0x78b174421ccb0f84609f815d31c4b32b9335188fc11a5366a3b7dda47743debb
    0xf79359bdec76d24ab8514ed7005a6bb020b535c855c644b9db849c781f1e0796
  2. Step 2, combined with the value before it
    0xb0666aa5cc88157545610a8fa97f65acbc04c9726dca4bddd12e2573670ca495
    0x64eb6433328d0b5b9cfdd9f7443ab402e493a959c1c62b5f5e543da784ca0568
  3. Step 3, combined with the value before it
    0x3a03e1e8b269d777799e06a1aefa615c784a6080fff56abe863f40fb9c4d2eeb
    0xaeba74fffac203168c9e8679dff289c46068d3aa7187159a5a80bd68d14bbe80
  4. Step 4, combined with the value after it
    0xc65464b4a068838d2f3c0320f93f50a28d75e0ef26c5687ed982636e91f80736
    0x07e1300a3e6f8521c7f03b03ece094e28a0493b55ebcf18fb86861af40487318

    This is the value for the whole day.

Value these steps arrive at
0x07e1300a3e6f8521c7f03b03ece094e28a0493b55ebcf18fb86861af40487318

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
0x07e1300a3e6f8521c7f03b03ece094e28a0493b55ebcf18fb86861af40487318
Read from Base
0x07e1300a3e6f8521c7f03b03ece094e28a0493b55ebcf18fb86861af40487318
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":"ThePetTales","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"attrs":{"alt":"hermit crab","src":"https://media.vitahash.org/articles/e4f0ce3f-dc5a-4c22-92e9-4ce0a2d…

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

    Should print 290dff5668b12e55eaa9e1eca3c6ec63e9f176c5393550b5a9065e9eceda4944

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

    Should print 560bafc68d216ae19a18984b8433c202ec5596135096736f89ac9ff530a67570

  3. 3. Combine step 1

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

    printf '01%s%s' "78b174421ccb0f84609f815d31c4b32b9335188fc11a5366a3b7dda47743debb" "560bafc68d216ae19a18984b8433c202ec5596135096736f89ac9ff530a67570" | xxd -r -p | shasum -a 256

    Should print f79359bdec76d24ab8514ed7005a6bb020b535c855c644b9db849c781f1e0796

  4. 4. Combine step 2

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

    printf '01%s%s' "b0666aa5cc88157545610a8fa97f65acbc04c9726dca4bddd12e2573670ca495" "f79359bdec76d24ab8514ed7005a6bb020b535c855c644b9db849c781f1e0796" | xxd -r -p | shasum -a 256

    Should print 64eb6433328d0b5b9cfdd9f7443ab402e493a959c1c62b5f5e543da784ca0568

  5. 5. Combine step 3

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

    printf '01%s%s' "3a03e1e8b269d777799e06a1aefa615c784a6080fff56abe863f40fb9c4d2eeb" "64eb6433328d0b5b9cfdd9f7443ab402e493a959c1c62b5f5e543da784ca0568" | xxd -r -p | shasum -a 256

    Should print aeba74fffac203168c9e8679dff289c46068d3aa7187159a5a80bd68d14bbe80

  6. 6. Combine step 4

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

    printf '01%s%s' "aeba74fffac203168c9e8679dff289c46068d3aa7187159a5a80bd68d14bbe80" "c65464b4a068838d2f3c0320f93f50a28d75e0ef26c5687ed982636e91f80736" | xxd -r -p | shasum -a 256

    Should print 07e1300a3e6f8521c7f03b03ece094e28a0493b55ebcf18fb86861af40487318

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

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

Read the specification