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

iSpace · 29 Sept 2026

Stamp ID
STAMP-2026-0929-EAZXK22W
Content hash
9bc80d580cf99cb0532d4bf778c0decc869f91b5aee24571d2c568c8910ba6ca
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
0xbd17e8c3e4d93a6e76ce3105143ba2e3c66eec663ef446645a15f804d7ec0b8f

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
    0xab9aa3b12f4694a3d09e2a620400fdccea50d14a86176d2b64ff0834d620a0d2
    0xe8d0d9e8225fe814089c505bc4f3bfc9cdc9111caa686f05c2b2e9d721fa3089
  2. Step 2, combined with the value after it
    0x349f21f6f5063edc7de9224e5fc2802d20ac2bdd2dc893e0bb44022f8c66ccf2
    0x18a07184359a08ea28abb8d119dae88df3682f6fc208bab608c1442582d12ffe
  3. Step 3, combined with the value before it
    0xfbb61d08dfd26cd6e384616a537f73888fd128216c8d0bed0c6579d6f80f220c
    0xc65464b4a068838d2f3c0320f93f50a28d75e0ef26c5687ed982636e91f80736
  4. Step 4, combined with the value before it
    0xaeba74fffac203168c9e8679dff289c46068d3aa7187159a5a80bd68d14bbe80
    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":"iSpace","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"That’s so cool!","type":"text"}],"type":"paragraph"}],"type":"doc"},"disclosures":null,"…

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-0929-EAZXK22W/canonical" | shasum -a 256

    Should print 9bc80d580cf99cb0532d4bf778c0decc869f91b5aee24571d2c568c8910ba6ca

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

    Should print bd17e8c3e4d93a6e76ce3105143ba2e3c66eec663ef446645a15f804d7ec0b8f

  3. 3. Combine step 1

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

    printf '01%s%s' "bd17e8c3e4d93a6e76ce3105143ba2e3c66eec663ef446645a15f804d7ec0b8f" "ab9aa3b12f4694a3d09e2a620400fdccea50d14a86176d2b64ff0834d620a0d2" | xxd -r -p | shasum -a 256

    Should print e8d0d9e8225fe814089c505bc4f3bfc9cdc9111caa686f05c2b2e9d721fa3089

  4. 4. Combine step 2

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

    printf '01%s%s' "e8d0d9e8225fe814089c505bc4f3bfc9cdc9111caa686f05c2b2e9d721fa3089" "349f21f6f5063edc7de9224e5fc2802d20ac2bdd2dc893e0bb44022f8c66ccf2" | xxd -r -p | shasum -a 256

    Should print 18a07184359a08ea28abb8d119dae88df3682f6fc208bab608c1442582d12ffe

  5. 5. Combine step 3

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

    printf '01%s%s' "fbb61d08dfd26cd6e384616a537f73888fd128216c8d0bed0c6579d6f80f220c" "18a07184359a08ea28abb8d119dae88df3682f6fc208bab608c1442582d12ffe" | xxd -r -p | shasum -a 256

    Should print c65464b4a068838d2f3c0320f93f50a28d75e0ef26c5687ed982636e91f80736

  6. 6. Combine step 4

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

    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