Verify

Sign inSign up

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.

When a Robot Dog Takes Another Dog for a Walk!

@RoboNextGen · 12 Nov 2026

Stamp ID
STAMP-2026-1112-UVNZFJWA
Content hash
a35726206858a1fc1b7e341703eec42ddabd9f1b41fc3c79537cc76657a0664a
Day recorded
2026-11-13
Articles recorded that day
13
Attestation UID
0x8d2d037d35d1d2f5ebd7ff95f0014255d2bcbac020bb3776b5cf710ca2ef0261
View on EAS
Transaction
0x39f12d8f2e595c717b4bce40bb59a5b28ba569bd14374bedff8237b5b15fd65f
View on Basescan
Stamped
13 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 12 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
0x7e78772fd8e21c118bf0074f267cf800deb90c5bfc582f855ece498841e45e99

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
    0x2fa0f42773eb0d2b41fbff9a6acdccaa3ae05d11913bf56a208d12e85d1af4ee
    0x5a9f275b5241850591f7714181a8f46cf307c7f71b6d4ec461f9df0ba00ac05a
  2. Step 2, combined with the value after it
    0xce3e00aeba0be9b0a4db6b4bda9b69dee2bdea0153f55a74a9a5d116ebc5b38e
    0x23d34b4880ea6a20e4495adb4aaa72757b5ad77f721c096cf4f72183e6c8c0c0
  3. Step 3, combined with the value after it
    0xc2a787206d7012a68e4bc12fcf3831969330a0a4898345bc0884862a535d7e55
    0xff35541912e2df2feec01871825d1d7f08f12c52f251394d82803cd3c7ed73aa
  4. Step 4, combined with the value before it
    0xc686ce1ad37287ba022494162d00d61e0f5cbbe1a6acba7f779824cf91156f85
    0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

    This is the value for the whole day.

Value these steps arrive at
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

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
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d
Read from Base
0x173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d
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":"Only in San Francisco would you see something this futuristic! A four-legged robot …

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-1112-UVNZFJWA/canonical" | shasum -a 256

    Should print a35726206858a1fc1b7e341703eec42ddabd9f1b41fc3c79537cc76657a0664a

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

    Should print 7e78772fd8e21c118bf0074f267cf800deb90c5bfc582f855ece498841e45e99

  3. 3. Combine step 1

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

    printf '01%s%s' "7e78772fd8e21c118bf0074f267cf800deb90c5bfc582f855ece498841e45e99" "2fa0f42773eb0d2b41fbff9a6acdccaa3ae05d11913bf56a208d12e85d1af4ee" | xxd -r -p | shasum -a 256

    Should print 5a9f275b5241850591f7714181a8f46cf307c7f71b6d4ec461f9df0ba00ac05a

  4. 4. Combine step 2

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

    printf '01%s%s' "5a9f275b5241850591f7714181a8f46cf307c7f71b6d4ec461f9df0ba00ac05a" "ce3e00aeba0be9b0a4db6b4bda9b69dee2bdea0153f55a74a9a5d116ebc5b38e" | xxd -r -p | shasum -a 256

    Should print 23d34b4880ea6a20e4495adb4aaa72757b5ad77f721c096cf4f72183e6c8c0c0

  5. 5. Combine step 3

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

    printf '01%s%s' "23d34b4880ea6a20e4495adb4aaa72757b5ad77f721c096cf4f72183e6c8c0c0" "c2a787206d7012a68e4bc12fcf3831969330a0a4898345bc0884862a535d7e55" | xxd -r -p | shasum -a 256

    Should print ff35541912e2df2feec01871825d1d7f08f12c52f251394d82803cd3c7ed73aa

  6. 6. Combine step 4

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

    printf '01%s%s' "c686ce1ad37287ba022494162d00d61e0f5cbbe1a6acba7f779824cf91156f85" "ff35541912e2df2feec01871825d1d7f08f12c52f251394d82803cd3c7ed73aa" | xxd -r -p | shasum -a 256

    Should print 173f6fd378092e865af1d499866e40bbda58a173260dc2ae347f6889884c4c7d

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

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

Read the specification