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.

Stop Comparing

@PositiveVibez · 7 Oct 2026

Stamp ID
STAMP-2026-1007-2GG5D3J7
Content hash
e76a7bf3c19e578b664ed18aad1e90a4bd2adb736a1c9f164b6fcb990c74b4ff
Day recorded
2026-10-08
Articles recorded that day
16
Attestation UID
0x3fd72ca76c79be099aa7f432c6fb16edc08982e9c7ef6528aa816dccff3b4ac8
View on EAS
Transaction
0x3379a1fcacf0777d45b279ac455541dcaee6ec6fdf7c604fb5a904496de0a459
View on Basescan
Stamped
8 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
0x2670b6a493942027250e00e68170cc072b2e5d16a99671bb008cc1aaa4c4920e

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
    0xffcd1a4a89979c835251818b020e73285158d6938824fb616eae22dcd5375e94
    0xc48ddd06c606fbc68fb00909853e8163ec87486a1a04a3853a66de7be4d11821
  2. Step 2, combined with the value after it
    0xb56c360999184d89294b29816bb084d8f5cc435fc7dda9cc8456bbd57bc1b6c7
    0x56a825d661eedef74814c6317c32e5ecebdbbab058f72f4434d2501e8f69f442
  3. Step 3, combined with the value after it
    0xa792b34de4a606dc5cbfc48203b2af1f6ded83bdb09048459fb5a6f9ded76794
    0x21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823
  4. Step 4, combined with the value after it
    0x4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787
    0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

    This is the value for the whole day.

Value these steps arrive at
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
Read from Base
0x4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66
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":"PositiveVibez","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"marks":[{"attrs":{"color":"blue"},"type":"textColor"},{"attrs":{"font":"comic"},"type":"…

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-1007-2GG5D3J7/canonical" | shasum -a 256

    Should print e76a7bf3c19e578b664ed18aad1e90a4bd2adb736a1c9f164b6fcb990c74b4ff

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

    Should print 2670b6a493942027250e00e68170cc072b2e5d16a99671bb008cc1aaa4c4920e

  3. 3. Combine step 1

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

    printf '01%s%s' "ffcd1a4a89979c835251818b020e73285158d6938824fb616eae22dcd5375e94" "2670b6a493942027250e00e68170cc072b2e5d16a99671bb008cc1aaa4c4920e" | xxd -r -p | shasum -a 256

    Should print c48ddd06c606fbc68fb00909853e8163ec87486a1a04a3853a66de7be4d11821

  4. 4. Combine step 2

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

    printf '01%s%s' "c48ddd06c606fbc68fb00909853e8163ec87486a1a04a3853a66de7be4d11821" "b56c360999184d89294b29816bb084d8f5cc435fc7dda9cc8456bbd57bc1b6c7" | xxd -r -p | shasum -a 256

    Should print 56a825d661eedef74814c6317c32e5ecebdbbab058f72f4434d2501e8f69f442

  5. 5. Combine step 3

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

    printf '01%s%s' "56a825d661eedef74814c6317c32e5ecebdbbab058f72f4434d2501e8f69f442" "a792b34de4a606dc5cbfc48203b2af1f6ded83bdb09048459fb5a6f9ded76794" | xxd -r -p | shasum -a 256

    Should print 21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823

  6. 6. Combine step 4

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

    printf '01%s%s' "21d60ef530a8e34d26e46969e912c3ac24439afd41c03e19b1f0a425ae50a823" "4a7e55906677934f282aad9bf8d6658b1cfac6ca362c39ff6e7dc5733f6b6787" | xxd -r -p | shasum -a 256

    Should print 4367ff8d14658640bf775bef7c1b160f231f55acfd93a7ecdc15680b2cb39e66

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

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

Read the specification