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.

Easy Pigs in a Blanket 🌭

iSpace · 5 Oct 2026

Stamp ID
STAMP-2026-1005-2UTLYGIU
Content hash
f9c72ec9e672b8133ee5f5b658540d38aa6efabed175977333219c2586b73cf1
Day recorded
2026-10-06
Articles recorded that day
15
Attestation UID
0xa9df93f9287fa980c704294972498aa806fc4b33381236688843cf306b429249
View on EAS
Transaction
0xaa5931a912bc6fc948af848f821a21951d10120547c65c820efa653b1545aeeb
View on Basescan
Stamped
7 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 14 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
0xf4aa28c71ba67bf0b9d4aa1db4f0e610dfaf5422789938a1e2f0e9339634aafb

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
    0x3494f21b0eb11607c66690edcecc35b2fa03b1f045eaad6c5d5ad79a3b8f4985
    0xc342c6e3f61642a45ac6265a2a24743c3e2ce7a426462d8fd61a10582d26bf08
  2. Step 2, combined with the value after it
    0x002ee7ef16bfc560ed584b4da7df8488a1bf4222b451e3e1c14041eed23cc101
    0x2984af38d8e55376ecb9d6cd12b5db21fe73adb96d4d8edff5127cbeec9513d1
  3. Step 3, combined with the value after it
    0xdb370880b6954311cdd1a54ca92c8fa431829e1c1779fa227f25a99d896add5d
    0xa9f799966a483b5e226937bad04c452defeec34e6edcd62f9a25542551c7c5b8
  4. Step 4, combined with the value after it
    0xf6e9bee092ca40c02a96ef8ee26ca39530effb9351665feb3ba92e44033f0037
    0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

    This is the value for the whole day.

Value these steps arrive at
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

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
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9
Read from Base
0x38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9
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":"iSpace","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Yummy!!","type":"text"}],"type":"paragraph"}],"type":"doc"},"disclosures":null,"keywords…

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-1005-2UTLYGIU/canonical" | shasum -a 256

    Should print f9c72ec9e672b8133ee5f5b658540d38aa6efabed175977333219c2586b73cf1

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

    Should print f4aa28c71ba67bf0b9d4aa1db4f0e610dfaf5422789938a1e2f0e9339634aafb

  3. 3. Combine step 1

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

    printf '01%s%s' "f4aa28c71ba67bf0b9d4aa1db4f0e610dfaf5422789938a1e2f0e9339634aafb" "3494f21b0eb11607c66690edcecc35b2fa03b1f045eaad6c5d5ad79a3b8f4985" | xxd -r -p | shasum -a 256

    Should print c342c6e3f61642a45ac6265a2a24743c3e2ce7a426462d8fd61a10582d26bf08

  4. 4. Combine step 2

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

    printf '01%s%s' "c342c6e3f61642a45ac6265a2a24743c3e2ce7a426462d8fd61a10582d26bf08" "002ee7ef16bfc560ed584b4da7df8488a1bf4222b451e3e1c14041eed23cc101" | xxd -r -p | shasum -a 256

    Should print 2984af38d8e55376ecb9d6cd12b5db21fe73adb96d4d8edff5127cbeec9513d1

  5. 5. Combine step 3

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

    printf '01%s%s' "2984af38d8e55376ecb9d6cd12b5db21fe73adb96d4d8edff5127cbeec9513d1" "db370880b6954311cdd1a54ca92c8fa431829e1c1779fa227f25a99d896add5d" | xxd -r -p | shasum -a 256

    Should print a9f799966a483b5e226937bad04c452defeec34e6edcd62f9a25542551c7c5b8

  6. 6. Combine step 4

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

    printf '01%s%s' "a9f799966a483b5e226937bad04c452defeec34e6edcd62f9a25542551c7c5b8" "f6e9bee092ca40c02a96ef8ee26ca39530effb9351665feb3ba92e44033f0037" | xxd -r -p | shasum -a 256

    Should print 38256faf2512c46a9e2a74487a2b8a28fd1c0c136819a67fdf612f505b6e96b9

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

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

Read the specification