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.

šŸ¤–šŸ¾ Would You Want a Robot Pet?

@RoboNextGen Ā· 27 Sept 2026

Stamp ID
STAMP-2026-0927-ARWQ5UI7
Content hash
9c10da247fec94269e3963053d71c19f35723011b0d18becca2a01978817bfaa
Day recorded
2026-09-28
Articles recorded that day
16
Attestation UID
0xf90e9bc451eee5367128ecc6c707fc5352ef0515b57dec1f5af014911dd29347
View on EAS
Transaction
0x0f2874f7536c4d6526c65e0119f22d2ba40a142cf577fc5ab655a4834d402d41
View on Basescan
Stamped
28 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 15 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
0xa65147af4833c1f7dbfa13f28218732ba760527fc8f847e5303b96885d3c9f21

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
    0x6418044e82e03139e38fbac1aab847af85a8d0b45507e4e1df7e781b6f08d744
    0xce6c8d52ea4eeb48fdfa8d80ba623ac7cf34e27d5506308aeabda989059c640f
  2. Step 2, combined with the value before it
    0xcf8e8b8cf21ef16139446ff6377193b0985a3337af036dde433d87f7918121ec
    0x7fe40eea1bad2bdb93609aa8e573a82f09091eb8006a6e0767682226d1a75fe1
  3. Step 3, combined with the value after it
    0xaa578ddfcefd3ad1326c523a92417afa15727ca3825ec5b50289ac1d7e795dc3
    0x6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73
  4. Step 4, combined with the value after it
    0x189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e
    0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

    This is the value for the whole day.

Value these steps arrive at
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

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
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94
Read from Base
0x01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94
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":"Robot pets are becoming more realisticā€”and they might change what companionship looā€¦

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-0927-ARWQ5UI7/canonical" | shasum -a 256

    Should print 9c10da247fec94269e3963053d71c19f35723011b0d18becca2a01978817bfaa

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

    Should print a65147af4833c1f7dbfa13f28218732ba760527fc8f847e5303b96885d3c9f21

  3. 3. Combine step 1

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

    printf '01%s%s' "a65147af4833c1f7dbfa13f28218732ba760527fc8f847e5303b96885d3c9f21" "6418044e82e03139e38fbac1aab847af85a8d0b45507e4e1df7e781b6f08d744" | xxd -r -p | shasum -a 256

    Should print ce6c8d52ea4eeb48fdfa8d80ba623ac7cf34e27d5506308aeabda989059c640f

  4. 4. Combine step 2

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

    printf '01%s%s' "cf8e8b8cf21ef16139446ff6377193b0985a3337af036dde433d87f7918121ec" "ce6c8d52ea4eeb48fdfa8d80ba623ac7cf34e27d5506308aeabda989059c640f" | xxd -r -p | shasum -a 256

    Should print 7fe40eea1bad2bdb93609aa8e573a82f09091eb8006a6e0767682226d1a75fe1

  5. 5. Combine step 3

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

    printf '01%s%s' "7fe40eea1bad2bdb93609aa8e573a82f09091eb8006a6e0767682226d1a75fe1" "aa578ddfcefd3ad1326c523a92417afa15727ca3825ec5b50289ac1d7e795dc3" | xxd -r -p | shasum -a 256

    Should print 6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73

  6. 6. Combine step 4

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

    printf '01%s%s' "6eaca6f8fad3941a58480910f7552e56ce37d770b0737e6b02e39bbbe2017c73" "189f16615f033de7dd9a4b992b1aef6470f63541e5680e16fcbbeed9fdc2af1e" | xxd -r -p | shasum -a 256

    Should print 01089cc494102438cf94dcf8e1f212fa7cd9533e8e954ccc633bfbcec4587c94

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

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

Read the specification