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 Chocolate Chip Banana Bread🍌🍫

@simple_recipes_daily · 6 Oct 2026

Stamp ID
STAMP-2026-1006-IOOZBSCP
Content hash
c73b167f8f76119bf078431ba20f652135bb030c12768ecb4d483d7185af4b50
Day recorded
2026-10-07
Articles recorded that day
16
Attestation UID
0x2838e247dcdc03d7e5d3def4582bb14c0fd666fbfbca325ed921536c8267f446
View on EAS
Transaction
0x70789bf19e02a7f6c3d6d64f551810889fee56d00e65909f037a2b329b146784
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 15 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
0xddf1f2c4be1da43532dc6828f9c55f4daf2c6e67244529f7b0bf1652435f612c

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
    0xa7748f404a45c56d6496aacd19ae9008b07c65da16531b04e6609a2219dbe0a0
    0x7a64f201e7db64d6a36718004c9e79bea1063fe00f3b7f2df5d7f86f44c5831b
  2. Step 2, combined with the value before it
    0xb807a4aee9c2c2e74bfa1d48fc1aff37cc8b8c5b0aabfe0a23b87c522c1cedfd
    0xfe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae
  3. Step 3, combined with the value before it
    0xaae3dbfe1e75ecdb701a8693a80198ff7daad62daa02bb5a7061ee9a35094929
    0x531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5
  4. Step 4, combined with the value after it
    0xf7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4
    0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

    This is the value for the whole day.

Value these steps arrive at
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

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
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07
Read from Base
0xfd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07
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":"simple_recipes_daily","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"Have a few overripe bananas? Turn them into a soft, moist banana bread loa…

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-1006-IOOZBSCP/canonical" | shasum -a 256

    Should print c73b167f8f76119bf078431ba20f652135bb030c12768ecb4d483d7185af4b50

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

    Should print ddf1f2c4be1da43532dc6828f9c55f4daf2c6e67244529f7b0bf1652435f612c

  3. 3. Combine step 1

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

    printf '01%s%s' "a7748f404a45c56d6496aacd19ae9008b07c65da16531b04e6609a2219dbe0a0" "ddf1f2c4be1da43532dc6828f9c55f4daf2c6e67244529f7b0bf1652435f612c" | xxd -r -p | shasum -a 256

    Should print 7a64f201e7db64d6a36718004c9e79bea1063fe00f3b7f2df5d7f86f44c5831b

  4. 4. Combine step 2

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

    printf '01%s%s' "b807a4aee9c2c2e74bfa1d48fc1aff37cc8b8c5b0aabfe0a23b87c522c1cedfd" "7a64f201e7db64d6a36718004c9e79bea1063fe00f3b7f2df5d7f86f44c5831b" | xxd -r -p | shasum -a 256

    Should print fe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae

  5. 5. Combine step 3

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

    printf '01%s%s' "aae3dbfe1e75ecdb701a8693a80198ff7daad62daa02bb5a7061ee9a35094929" "fe4c6bd997e85bc624f473a19977e5af67365305a12f06b94f0a7f784c16b0ae" | xxd -r -p | shasum -a 256

    Should print 531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5

  6. 6. Combine step 4

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

    printf '01%s%s' "531a6b70abcbe82e2280a36686fb422b2bf4ab51dc08735d24801f65a0ebcbf5" "f7a52ff416ea618bf777fa9a60ce33e8df0053120825188265e8c19eb17cd3a4" | xxd -r -p | shasum -a 256

    Should print fd9e684812519ac6d8c98f64d83e894da5011da68f6f62f5262cf66b04b0ac07

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

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

Read the specification