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.

A ROBOT BARTENDER?! And it already exists in the U.S.!

Models & Coffee · 25 Sept 2026

Stamp ID
STAMP-2026-0925-FVTVOP73
Content hash
a952122d17b37750b89dc0113f5627a75d0e092b861e9ee06dc2ec2bd8ce9c31
Day recorded
2026-09-26
Articles recorded that day
20
Attestation UID
0xeca6201b1118aac08c5e90852685560efcd865d7b92d8dd755536bd900121d44
View on EAS
Transaction
0x8773b62d3c7fe3c39180795fdbf303e39a988305339fd36d0f85017972c0bcd5
View on Basescan
Stamped
26 Sept 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 19 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
0x142206ad069f6684880fd23701c4d081b1c4eea92cb3e4bd78a98457dc931e22

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
    0xafcd773d2a74e925223e314f65744048f9b82986dd72d906e58930e0421ead2e
    0x1265139a8659b04fea439c45b13247c4b1458a1d2659e9cbb8615679b2066a94
  2. Step 2, combined with the value before it
    0x6d01e708b54bd6c4efcde20be52ea000e06cbf90dc83696997e7f7d14fcabdca
    0x05967956cb96f55c72efd784ed2ba4c9b76cbc3de44da55badc6e61268baf8ba
  3. Step 3, combined with the value before it
    0x1c5d1cde4ed9dea8d73f35b4cc2ee74b79eb30e07b51291d2e3481404139ab29
    0x97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb
  4. Step 4, combined with the value after it
    0xeef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba
    0xc1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c
  5. Step 5, combined with the value after it
    0x338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f
    0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

    This is the value for the whole day.

Value these steps arrive at
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

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
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
Read from Base
0x8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab
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":"singularity","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Here comes AI. Say goodbye to the 9–5","type":"text"}],"type":"paragraph"}],"type":…

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-0925-FVTVOP73/canonical" | shasum -a 256

    Should print a952122d17b37750b89dc0113f5627a75d0e092b861e9ee06dc2ec2bd8ce9c31

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

    Should print 142206ad069f6684880fd23701c4d081b1c4eea92cb3e4bd78a98457dc931e22

  3. 3. Combine step 1

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

    printf '01%s%s' "afcd773d2a74e925223e314f65744048f9b82986dd72d906e58930e0421ead2e" "142206ad069f6684880fd23701c4d081b1c4eea92cb3e4bd78a98457dc931e22" | xxd -r -p | shasum -a 256

    Should print 1265139a8659b04fea439c45b13247c4b1458a1d2659e9cbb8615679b2066a94

  4. 4. Combine step 2

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

    printf '01%s%s' "6d01e708b54bd6c4efcde20be52ea000e06cbf90dc83696997e7f7d14fcabdca" "1265139a8659b04fea439c45b13247c4b1458a1d2659e9cbb8615679b2066a94" | xxd -r -p | shasum -a 256

    Should print 05967956cb96f55c72efd784ed2ba4c9b76cbc3de44da55badc6e61268baf8ba

  5. 5. Combine step 3

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

    printf '01%s%s' "1c5d1cde4ed9dea8d73f35b4cc2ee74b79eb30e07b51291d2e3481404139ab29" "05967956cb96f55c72efd784ed2ba4c9b76cbc3de44da55badc6e61268baf8ba" | xxd -r -p | shasum -a 256

    Should print 97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb

  6. 6. Combine step 4

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

    printf '01%s%s' "97c1335bc96ed40e4db026f00b899cdeec1bc932550d0e2bfbb6dc3f3ccb2bfb" "eef2fc0c052d8690543265b12fc46b2f16349bfff03b4fc8e4347b463c876bba" | xxd -r -p | shasum -a 256

    Should print c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c

  7. 7. Combine step 5

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

    printf '01%s%s' "c1d5d231b268f46906a4da83c556378223bf6096ded3827d3cd87ed49e6fd45c" "338087d57076385362f8b946b1aeb173dce23ad0a0d0e2a793f84da82df6b81f" | xxd -r -p | shasum -a 256

    Should print 8b2476a9102c6f8fddeaea8b440d390005d5d4f4ebd31a5e0f185dd330f209ab

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

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

Read the specification