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.

Could Robots Take Over the Restaurant Industry?

@RoboNextGen · 9 Oct 2026

Stamp ID
STAMP-2026-1009-U4WN5LCF
Content hash
0bb012930dfbde5a3b11c7a23aead13ac01780348d0a9c6d443b99ec11511234
Day recorded
2026-10-10
Articles recorded that day
19
Attestation UID
0xb5876e55d95e5c9dd72430517b418d7e00db9efadd7c258e2a99bed5d50d278b
View on EAS
Transaction
0xdb7e81090abd4ba966e61ef8e62756a94bcf19b7c809c51e90b31991e1231c26
View on Basescan
Stamped
10 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
0x24eda3d31efd9225b8c6fc1c63921b15f439b4e681d48923cb2d395066781ece

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
    0xe12ad16df4fd41f6dc19a7de71f1effa6c94d73af613b4db6a23a71c734c6dc0
    0x0be1a2c7b95176129bb03806cbb8513fe253f711e45766e5f0e2145d3d9c53b4
  2. Step 2, combined with the value after it
    0x4cd82ba7d89363913160b9e37ebca70abc53f2af82cbb43d649910d41fb33596
    0x180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f
  3. Step 3, combined with the value before it
    0xfe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac
    0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

    This is the value for the whole day.

Value these steps arrive at
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

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
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68
Read from Base
0x828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68
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":"Imagine walking into a restaurant where a robot takes your order, another prepares …

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-1009-U4WN5LCF/canonical" | shasum -a 256

    Should print 0bb012930dfbde5a3b11c7a23aead13ac01780348d0a9c6d443b99ec11511234

  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-1009-U4WN5LCF CONTENT=0bb012930dfbde5a3b11c7a23aead13ac01780348d0a9c6d443b99ec11511234 DIGEST=$(printf '%s' "$STAMP" | shasum -a 256 | cut -d' ' -f1) printf '00%s%s' "$DIGEST" "$CONTENT" | xxd -r -p | shasum -a 256

    Should print 24eda3d31efd9225b8c6fc1c63921b15f439b4e681d48923cb2d395066781ece

  3. 3. Combine step 1

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

    printf '01%s%s' "24eda3d31efd9225b8c6fc1c63921b15f439b4e681d48923cb2d395066781ece" "e12ad16df4fd41f6dc19a7de71f1effa6c94d73af613b4db6a23a71c734c6dc0" | xxd -r -p | shasum -a 256

    Should print 0be1a2c7b95176129bb03806cbb8513fe253f711e45766e5f0e2145d3d9c53b4

  4. 4. Combine step 2

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

    printf '01%s%s' "0be1a2c7b95176129bb03806cbb8513fe253f711e45766e5f0e2145d3d9c53b4" "4cd82ba7d89363913160b9e37ebca70abc53f2af82cbb43d649910d41fb33596" | xxd -r -p | shasum -a 256

    Should print 180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f

  5. 5. Combine step 3

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

    printf '01%s%s' "fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac" "180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f" | xxd -r -p | shasum -a 256

    Should print 828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

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

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

Read the specification