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.

People Are Using AI Instead of Hiring Lawyers

Models & Coffee · 23 Oct 2026

Stamp ID
STAMP-2026-1023-2RMMYNRX
Content hash
ba3456ce759da5352e536ada8edb77fedb91979127bc149c48818eb21eb53025
Day recorded
2026-10-23
Articles recorded that day
14
Attestation UID
0x32e1fe3954bfb69b552b563b349d9abee6658f0d6dae2357cd5bbaaa1a783fb5
View on EAS
Transaction
0x9955f8d31f9306d0d2d881deab8be664b29f8ede1bdac0a683bef59ab6928959
View on Basescan
Stamped
23 Oct 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

It was combined with the other 13 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
0x4751cb9a21aad52de322b2f4a151b6cec5ecd46c514938a6a07992a3ca07fd84

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
    0x532f4134c60cb33af41d5a68a7e52353ba194a2ec7f81ba425c53e9320bf4a65
    0xf2578fac6b2ac49fef3b61ec5629d603dc462c9c69adb0aadc62e1a600ddcb7c
  2. Step 2, combined with the value before it
    0xc5f2c0548f7df13140d770773ab3d184b0f4a3f11267db4b23bec3af95572e5a
    0xa2919adbc2c28e331609c9ea03235ccc129f1db24739e57199ecc0d4e54115d0
  3. Step 3, combined with the value before it
    0x5707e73d019ccf0b1c6492eea4e7b94a5ed6a73069b63ae28f91db2895490cad
    0x6a78aea8fc5d7adb97678c601d9621f5cd9d63f92fac9c3bfc45ef422a448c5e

    This is the value for the whole day.

Value these steps arrive at
0x6a78aea8fc5d7adb97678c601d9621f5cd9d63f92fac9c3bfc45ef422a448c5e

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
0x6a78aea8fc5d7adb97678c601d9621f5cd9d63f92fac9c3bfc45ef422a448c5e
Read from Base
0x6a78aea8fc5d7adb97678c601d9621f5cd9d63f92fac9c3bfc45ef422a448c5e
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":"singularity","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"In California and elsewhere, pro se litigants have used ChatGPT to draft legal docu…

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-1023-2RMMYNRX/canonical" | shasum -a 256

    Should print ba3456ce759da5352e536ada8edb77fedb91979127bc149c48818eb21eb53025

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

    Should print 4751cb9a21aad52de322b2f4a151b6cec5ecd46c514938a6a07992a3ca07fd84

  3. 3. Combine step 1

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

    printf '01%s%s' "532f4134c60cb33af41d5a68a7e52353ba194a2ec7f81ba425c53e9320bf4a65" "4751cb9a21aad52de322b2f4a151b6cec5ecd46c514938a6a07992a3ca07fd84" | xxd -r -p | shasum -a 256

    Should print f2578fac6b2ac49fef3b61ec5629d603dc462c9c69adb0aadc62e1a600ddcb7c

  4. 4. Combine step 2

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

    printf '01%s%s' "c5f2c0548f7df13140d770773ab3d184b0f4a3f11267db4b23bec3af95572e5a" "f2578fac6b2ac49fef3b61ec5629d603dc462c9c69adb0aadc62e1a600ddcb7c" | xxd -r -p | shasum -a 256

    Should print a2919adbc2c28e331609c9ea03235ccc129f1db24739e57199ecc0d4e54115d0

  5. 5. Combine step 3

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

    printf '01%s%s' "5707e73d019ccf0b1c6492eea4e7b94a5ed6a73069b63ae28f91db2895490cad" "a2919adbc2c28e331609c9ea03235ccc129f1db24739e57199ecc0d4e54115d0" | xxd -r -p | shasum -a 256

    Should print 6a78aea8fc5d7adb97678c601d9621f5cd9d63f92fac9c3bfc45ef422a448c5e

  6. 6. 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/0x32e1fe3954bfb69b552b563b349d9abee6658f0d6dae2357cd5bbaaa1a783fb5

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

Read the specification