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.

What to Order Vegan at Olive Garden!

@poweredbyplants · 9 Oct 2026

Stamp ID
STAMP-2026-1009-5NNQADXP
Content hash
a1c51832a12930590706432df139ff8f2d5aefe59ee5978a77a4414a06f83fd4
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
0xece8dac171ce88a16027f004f190754d9b929044466070d5321a29397a0e7e75

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
    0x769a12ef8726527122d301caa11b338d0820c4ad84572c5bb16506462087fa02
    0xf94586c3a04b1cd9b3f75af6d58583dda926042a9b1853ab2b95a71e74a83728
  2. Step 2, combined with the value before it
    0x9108f3ca45772e8c2cb0e391b4b3ce6a4906840263289b4ad007648570547d77
    0xecdeedcd7dffbffe7af22d93dd4a3a8d1993720324e6eb9748a29f2dd5ebdc1e
  3. Step 3, combined with the value after it
    0x8978a0b18be5c3656f9aef73199e9d6f8706cac1ca8c64792a790bab4740c956
    0x2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d
  4. Step 4, combined with the value after it
    0x2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d
    0xfe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac
  5. Step 5, combined with the value after it
    0x180f27a5e63b918783e114c2441ae403faefb0077b18cf1a1eecc5aca0d0aa0f
    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":"poweredbyplants","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Craving Italian food while eating plant-based? You can still enjoy a meal at Ol…

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-5NNQADXP/canonical" | shasum -a 256

    Should print a1c51832a12930590706432df139ff8f2d5aefe59ee5978a77a4414a06f83fd4

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

    Should print ece8dac171ce88a16027f004f190754d9b929044466070d5321a29397a0e7e75

  3. 3. Combine step 1

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

    printf '01%s%s' "769a12ef8726527122d301caa11b338d0820c4ad84572c5bb16506462087fa02" "ece8dac171ce88a16027f004f190754d9b929044466070d5321a29397a0e7e75" | xxd -r -p | shasum -a 256

    Should print f94586c3a04b1cd9b3f75af6d58583dda926042a9b1853ab2b95a71e74a83728

  4. 4. Combine step 2

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

    printf '01%s%s' "9108f3ca45772e8c2cb0e391b4b3ce6a4906840263289b4ad007648570547d77" "f94586c3a04b1cd9b3f75af6d58583dda926042a9b1853ab2b95a71e74a83728" | xxd -r -p | shasum -a 256

    Should print ecdeedcd7dffbffe7af22d93dd4a3a8d1993720324e6eb9748a29f2dd5ebdc1e

  5. 5. Combine step 3

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

    printf '01%s%s' "ecdeedcd7dffbffe7af22d93dd4a3a8d1993720324e6eb9748a29f2dd5ebdc1e" "8978a0b18be5c3656f9aef73199e9d6f8706cac1ca8c64792a790bab4740c956" | xxd -r -p | shasum -a 256

    Should print 2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d

  6. 6. Combine step 4

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

    printf '01%s%s' "2ecef9dbf25e08daa8263ffbfff2a454ffa33a24827239aa072bafc40e22825d" "2e2b7a98c527abb764ea88e886dd169e6d135e7fefec2a5590ba44b68219312d" | xxd -r -p | shasum -a 256

    Should print fe61a3e7f1f8747a9f673767cd49f1fcaa5b415b85ddf5a046e009b0d2f4ebac

  7. 7. Combine step 5

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

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

    Should print 828135a5df501e3d746b93ce06b7d89cc9b5b24449ef7dddc051f36e67c59d68

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

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

Read the specification