Verify

Sign inSign up

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.

NVIDIA’s Biggest Risk: What Happens After Jensen Huang?

financeguy · 9 Nov 2026

Stamp ID
STAMP-2026-1109-7KRZKE2E
Content hash
85cdbf93c5fde6307f4d9f9eed9666855453f2960e3cc4b7d3e40dc5f0633fac
Day recorded
2026-11-10
Articles recorded that day
11
Attestation UID
0xa323e3cebb9f889ea1434673caf1ca13a456901cde7e0d2cba4685ffde9cd2ca
View on EAS
Transaction
0xe5c5bfe5a4fb4dc6c5c8e7bf991dadee8e63968d3c2119ac7b231a31e17a03ab
View on Basescan
Stamped
10 Nov 2026

Recorded on Base using canonicalization v2 and record format v1.

How this article reaches the blockchain

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

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
    0x176fd67ff54f99ca765fb5174f0ff30bd2d50fe8fcc2ec7b7f6eeb19de595fea
    0xafa20d194e97dfc4d3b2adc82dea57e2da116aeb81d5f108b994b241c24448db
  2. Step 2, combined with the value after it
    0x5ec2b872c79b3ae735e09f36367bf0c90758e2f475ee963921b88e3cb6e1ac5f
    0x14f012a848990fef43cd059829a9ef205a63dd41056e616243de85731920b95a
  3. Step 3, combined with the value after it
    0xb6334a5710a80ce87654b441954392a02a6db8e6285ec2e0940523dc4e2706b7
    0x70987eecfb16f1f9f9813c6631161ba08d7e875d3130d37348455e40168acc5c
  4. Step 4, combined with the value after it
    0x473293bd3500511361f702c615e98e7af95380898270ffd641393ca7717455c4
    0xbc74bba2ca689c89aa18eaf69b3f6b47ddf4677a4a5cb56239b9935d47efc72d

    This is the value for the whole day.

Value these steps arrive at
0xbc74bba2ca689c89aa18eaf69b3f6b47ddf4677a4a5cb56239b9935d47efc72d

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
0xbc74bba2ca689c89aa18eaf69b3f6b47ddf4677a4a5cb56239b9935d47efc72d
Read from Base
0xbc74bba2ca689c89aa18eaf69b3f6b47ddf4677a4a5cb56239b9935d47efc72d
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":"financeguy","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"NVIDIA’s biggest risk may not be competition from AMD or other AI chipmakers as it m…

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-1109-7KRZKE2E/canonical" | shasum -a 256

    Should print 85cdbf93c5fde6307f4d9f9eed9666855453f2960e3cc4b7d3e40dc5f0633fac

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

    Should print ce32c2282b7ca87e3b4cc3e3dc0477a2577c7002ec56f41af109740066af5c37

  3. 3. Combine step 1

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

    printf '01%s%s' "176fd67ff54f99ca765fb5174f0ff30bd2d50fe8fcc2ec7b7f6eeb19de595fea" "ce32c2282b7ca87e3b4cc3e3dc0477a2577c7002ec56f41af109740066af5c37" | xxd -r -p | shasum -a 256

    Should print afa20d194e97dfc4d3b2adc82dea57e2da116aeb81d5f108b994b241c24448db

  4. 4. Combine step 2

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

    printf '01%s%s' "afa20d194e97dfc4d3b2adc82dea57e2da116aeb81d5f108b994b241c24448db" "5ec2b872c79b3ae735e09f36367bf0c90758e2f475ee963921b88e3cb6e1ac5f" | xxd -r -p | shasum -a 256

    Should print 14f012a848990fef43cd059829a9ef205a63dd41056e616243de85731920b95a

  5. 5. Combine step 3

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

    printf '01%s%s' "14f012a848990fef43cd059829a9ef205a63dd41056e616243de85731920b95a" "b6334a5710a80ce87654b441954392a02a6db8e6285ec2e0940523dc4e2706b7" | xxd -r -p | shasum -a 256

    Should print 70987eecfb16f1f9f9813c6631161ba08d7e875d3130d37348455e40168acc5c

  6. 6. Combine step 4

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

    printf '01%s%s' "70987eecfb16f1f9f9813c6631161ba08d7e875d3130d37348455e40168acc5c" "473293bd3500511361f702c615e98e7af95380898270ffd641393ca7717455c4" | xxd -r -p | shasum -a 256

    Should print bc74bba2ca689c89aa18eaf69b3f6b47ddf4677a4a5cb56239b9935d47efc72d

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

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

Read the specification