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.

🍭🤖 Cotton Candy, Made by a Robot!

@RoboNextGen · 23 Sept 2026

Stamp ID
STAMP-2026-0923-MLNFPNRA
Content hash
373eb4232500e4d6b3d72ccbce958c7cc195ecda70905a49e250f4eeeb06fe42
Day recorded
2026-09-24
Articles recorded that day
17
Attestation UID
0x762e6311ed34312a3f3132a6182a8042fbfb824a36d9ae6d78578c9b6b802645
View on EAS
Transaction
0xe6f94b9a91b705afc7d83ce1a42a74215dde7d1a18a31b24220210388e2cdc0a
View on Basescan
Stamped
24 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 16 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
0x67c110981d14a7ba2cbd3c58d6eac4d176d6bba50318a4b42a03a24f5d23b71f

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
    0xaa6cb50bdac622f5e4b6591dc00a33e7107124b66a55999f6bc8b4ea6ba5c14a
    0x1950ac7116c73f1e471bf99ae6f7154b09d94be5dcb65b94ab49cebf93b81209
  2. Step 2, combined with the value before it
    0x6733d448dfed11a0f3f2c9a0a3e39a7467bfa2148fe1e45df8a86283f2d53953
    0x79c97426b6d5af0c24b132e7c21885809d5aa0e258e0356e29afdfc367a22a3f
  3. Step 3, combined with the value after it
    0x5d299f76b15d87a285a923ad58638ee9eefc14472d3875e5b932ae939dc96ab7
    0x7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39
  4. Step 4, combined with the value before it
    0x580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44
    0xcc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26
  5. Step 5, combined with the value after it
    0x84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d
    0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

    This is the value for the whole day.

Value these steps arrive at
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

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
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec
Read from Base
0x0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec
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":"RoboNextGen","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Sweet Robo is giving the classic cotton candy experience a futuristic twist with it…

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-0923-MLNFPNRA/canonical" | shasum -a 256

    Should print 373eb4232500e4d6b3d72ccbce958c7cc195ecda70905a49e250f4eeeb06fe42

  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-0923-MLNFPNRA CONTENT=373eb4232500e4d6b3d72ccbce958c7cc195ecda70905a49e250f4eeeb06fe42 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 67c110981d14a7ba2cbd3c58d6eac4d176d6bba50318a4b42a03a24f5d23b71f

  3. 3. Combine step 1

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

    printf '01%s%s' "aa6cb50bdac622f5e4b6591dc00a33e7107124b66a55999f6bc8b4ea6ba5c14a" "67c110981d14a7ba2cbd3c58d6eac4d176d6bba50318a4b42a03a24f5d23b71f" | xxd -r -p | shasum -a 256

    Should print 1950ac7116c73f1e471bf99ae6f7154b09d94be5dcb65b94ab49cebf93b81209

  4. 4. Combine step 2

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

    printf '01%s%s' "6733d448dfed11a0f3f2c9a0a3e39a7467bfa2148fe1e45df8a86283f2d53953" "1950ac7116c73f1e471bf99ae6f7154b09d94be5dcb65b94ab49cebf93b81209" | xxd -r -p | shasum -a 256

    Should print 79c97426b6d5af0c24b132e7c21885809d5aa0e258e0356e29afdfc367a22a3f

  5. 5. Combine step 3

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

    printf '01%s%s' "79c97426b6d5af0c24b132e7c21885809d5aa0e258e0356e29afdfc367a22a3f" "5d299f76b15d87a285a923ad58638ee9eefc14472d3875e5b932ae939dc96ab7" | xxd -r -p | shasum -a 256

    Should print 7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39

  6. 6. Combine step 4

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

    printf '01%s%s' "580d6d082fcf997e54f43a3f5f085f2eb5c5b3cde109d36b33728895d8991e44" "7dcc8df902700240f2b3ddefd2a04e65571613e3d606be7befe0b477acf5bf39" | xxd -r -p | shasum -a 256

    Should print cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26

  7. 7. Combine step 5

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

    printf '01%s%s' "cc726d408f6663dfb1f79c45763d310611376625219557511a10ed3811ec5e26" "84d06f2996b75c16b1c3c5db27e3adbaa6dab69087e72ab178d8fb7e4870e64d" | xxd -r -p | shasum -a 256

    Should print 0aba8b378f589186a4d34d785b3ad3e11e9061ced9213874765a71427669c3ec

  8. 8. 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/0x762e6311ed34312a3f3132a6182a8042fbfb824a36d9ae6d78578c9b6b802645

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

Read the specification