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.

Stamp ID
STAMP-2026-1116-GGK37BD6
Content hash
4b10b304d4dc0a46754f9fcba47539ff0072bd7e125ef4f1d07da8bbe8b739f0
Day recorded
2026-11-17
Articles recorded that day
18
Attestation UID
0x880330856028af49645da78f1ecccf8b50b0c5e33df5d9d7f590f67aa5504077
View on EAS
Transaction
0x08ed8ba6a46b18249f5d7ec42bfca0e9d9a07f39cfe3408522d07fa1be405639
View on Basescan
Stamped
17 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 17 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
0xe0c1298eb5745c71cbb4903d5e5644da17b560f40862eb74aa3d732808b075c9

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
    0xacd5dd8dda0fb4da2849b4304182694c08b8fa6ad345a9ba7802f179b5b697b3
    0xcf88e56176c59c5356f30cdd50f1adb48a541dd1696dcf6e41f216af16cc1b58
  2. Step 2, combined with the value before it
    0xecd45b5fd14e1dcfad15f8b3ffdabf421f39ce6006fe37305be7b2a504ea1c2a
    0x94d15d143df6c7fde50759b87248896f5e7b611ac17c0c1f6ff9c31298b21ddd
  3. Step 3, combined with the value before it
    0x3a1c5f374818797aa83173b0333aa1c5cc3a33bb77ca1de07f9a518106c7dc33
    0xd4d157bda656e6c531d0b6c0543341daa82c85d7f3d3ad8dd96df966246f0822
  4. Step 4, combined with the value after it
    0xd8c96aad556c6ab451de1a8f9eb77e32d4c692b40a8a166e54b701cbe367c4a1
    0x2ac4d87c6baa38526edc7c925eb46d07eeb6e535307bdf2ff8a8e1ff56b3ab0e
  5. Step 5, combined with the value after it
    0x65d0ad7fbf9ea058840b312b1e1ea8ebb5e9b6fa4e44f5a63c273ef099dbc44c
    0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

    This is the value for the whole day.

Value these steps arrive at
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

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
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2
Read from Base
0xf888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2
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":"NYCUnlocked","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Exploring NYC's Chinatown is always a must! From the incredible dumpling spots and …

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-1116-GGK37BD6/canonical" | shasum -a 256

    Should print 4b10b304d4dc0a46754f9fcba47539ff0072bd7e125ef4f1d07da8bbe8b739f0

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

    Should print e0c1298eb5745c71cbb4903d5e5644da17b560f40862eb74aa3d732808b075c9

  3. 3. Combine step 1

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

    printf '01%s%s' "e0c1298eb5745c71cbb4903d5e5644da17b560f40862eb74aa3d732808b075c9" "acd5dd8dda0fb4da2849b4304182694c08b8fa6ad345a9ba7802f179b5b697b3" | xxd -r -p | shasum -a 256

    Should print cf88e56176c59c5356f30cdd50f1adb48a541dd1696dcf6e41f216af16cc1b58

  4. 4. Combine step 2

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

    printf '01%s%s' "ecd45b5fd14e1dcfad15f8b3ffdabf421f39ce6006fe37305be7b2a504ea1c2a" "cf88e56176c59c5356f30cdd50f1adb48a541dd1696dcf6e41f216af16cc1b58" | xxd -r -p | shasum -a 256

    Should print 94d15d143df6c7fde50759b87248896f5e7b611ac17c0c1f6ff9c31298b21ddd

  5. 5. Combine step 3

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

    printf '01%s%s' "3a1c5f374818797aa83173b0333aa1c5cc3a33bb77ca1de07f9a518106c7dc33" "94d15d143df6c7fde50759b87248896f5e7b611ac17c0c1f6ff9c31298b21ddd" | xxd -r -p | shasum -a 256

    Should print d4d157bda656e6c531d0b6c0543341daa82c85d7f3d3ad8dd96df966246f0822

  6. 6. Combine step 4

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

    printf '01%s%s' "d4d157bda656e6c531d0b6c0543341daa82c85d7f3d3ad8dd96df966246f0822" "d8c96aad556c6ab451de1a8f9eb77e32d4c692b40a8a166e54b701cbe367c4a1" | xxd -r -p | shasum -a 256

    Should print 2ac4d87c6baa38526edc7c925eb46d07eeb6e535307bdf2ff8a8e1ff56b3ab0e

  7. 7. Combine step 5

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

    printf '01%s%s' "2ac4d87c6baa38526edc7c925eb46d07eeb6e535307bdf2ff8a8e1ff56b3ab0e" "65d0ad7fbf9ea058840b312b1e1ea8ebb5e9b6fa4e44f5a63c273ef099dbc44c" | xxd -r -p | shasum -a 256

    Should print f888679da36a81e88fcd934fda87753c26a962f2e9b1404e3eb0b380b9ea4ee2

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

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

Read the specification