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.

GME-eBay deal

financeguy · 9 Sept 2026

Stamp ID
STAMP-2026-0909-HZNBELOX
Content hash
6e22c99b0743ecb5a11504812b9fb9dbc85da19893949f92ff36296673e2bc10
Day recorded
2026-09-10
Articles recorded that day
8
Attestation UID
0xf8f0e64849d3ba6f01e8709c90250a8b400b96bd9576e39e7949fa6c0043408b
View on EAS
Transaction
0x74e43b2e9ba0b4a17a30a17cd69341ab9f4af4cebcdb4747b7188b0b5e486d70
View on Basescan
Stamped
10 Sept 2026

Recorded on Base using canonicalization v1 and record format v1.

How this article reaches the blockchain

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

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
    0x80e360753b8d509b35a060e620d0045352f4e5b1f8a4b10cf4fdeb854596ec7a
    0xff7361b8ea4c7423a94d7582b2d8997810fe4826531bda8b0d731e7ac843006c
  2. Step 2, combined with the value before it
    0xba5abf707a3ee17f523cce0d326b54088c6a200875a298689627fdd34919f3c6
    0x97af53e90c4e942303167c11b3028a112931ba0b2216464cdd9d2eafcea2a2a1
  3. Step 3, combined with the value after it
    0x017a0ea40754398dd234718206ec2e41b1a8edbba60ed294acb0d81580cdbd00
    0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

    This is the value for the whole day.

Value these steps arrive at
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

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
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048
Read from Base
0xb7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048
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.

The exact text is not available for this article right now. The command below still reaches it.

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-0909-HZNBELOX/canonical" | shasum -a 256

    Should print 6e22c99b0743ecb5a11504812b9fb9dbc85da19893949f92ff36296673e2bc10

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

    Should print d496c40027c93db92c8642f105e1bf4215351ba6fe82dfcaea4f329aac56e2d1

  3. 3. Combine step 1

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

    printf '01%s%s' "d496c40027c93db92c8642f105e1bf4215351ba6fe82dfcaea4f329aac56e2d1" "80e360753b8d509b35a060e620d0045352f4e5b1f8a4b10cf4fdeb854596ec7a" | xxd -r -p | shasum -a 256

    Should print ff7361b8ea4c7423a94d7582b2d8997810fe4826531bda8b0d731e7ac843006c

  4. 4. Combine step 2

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

    printf '01%s%s' "ba5abf707a3ee17f523cce0d326b54088c6a200875a298689627fdd34919f3c6" "ff7361b8ea4c7423a94d7582b2d8997810fe4826531bda8b0d731e7ac843006c" | xxd -r -p | shasum -a 256

    Should print 97af53e90c4e942303167c11b3028a112931ba0b2216464cdd9d2eafcea2a2a1

  5. 5. Combine step 3

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

    printf '01%s%s' "97af53e90c4e942303167c11b3028a112931ba0b2216464cdd9d2eafcea2a2a1" "017a0ea40754398dd234718206ec2e41b1a8edbba60ed294acb0d81580cdbd00" | xxd -r -p | shasum -a 256

    Should print b7d6c53003650ad4e6f8678e2531b950631a1d481cd3edde23566d77738d5048

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

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

Read the specification