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.

2026 Rug pull

financeguy · 15 Aug 2026

Stamp ID
STAMP-2026-0815-SG2Z7BEY
Content hash
170e3407cc94acb230b5668d7ac38f9a9bd6d92ccc59c042ce79349a2c975ad3
Day recorded
2026-08-16
Articles recorded that day
12
Attestation UID
0xbd466171c9269a1553b500cf540d4d833a73a86f8b5340dd05858ee67a202cc1
View on EAS
Transaction
0xc1f0a5866a230fc2c051c4d0a8e0f3267db91356ab65c0a169047f0e8bf72525
View on Basescan
Stamped
16 Aug 2026

Recorded on Base Sepolia using canonicalization v1 and record format v1.

How this article reaches the blockchain

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

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
    0x0479d56e84ae3fa6d7feb86388f026a8e40612dd6e5a6599c8d430c9e6254d65
    0x79d106789b8accc9a880d334c2b1b0a8b2a845c6f8f29337e66d43e8c2767ebc
  2. Step 2, combined with the value after it
    0xd2e9c048cd6ee0d52f7085d8f50cc90ac3096d39385588e6e8702e9dbf11a113
    0x7ec5e373ad571f9b92df693781e92ada98745598eb8e1ffb28fac8b8743de56f
  3. Step 3, combined with the value before it
    0x9a459029e464b4d8a058f4a436b5f2ef4ee164eef22c325501317a042faf4e2c
    0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

    This is the value for the whole day.

Value these steps arrive at
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

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
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef
Read from Base
0x7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef
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,"authors":[{"identity":"financeguy","position":1,"role":"solo","weight":1.0000}],"body":{"content":[{"content":[{"text":"We’re watching what might go down as the biggest fake pump and rug pull of 2026. Stay sharp — hype isn…

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-0815-SG2Z7BEY/canonical" | shasum -a 256

    Should print 170e3407cc94acb230b5668d7ac38f9a9bd6d92ccc59c042ce79349a2c975ad3

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

    Should print 3818fd4ccf7b3b7d8aafa8d88043c66e0b0595430aec58742896575d96470a5a

  3. 3. Combine step 1

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

    printf '01%s%s' "0479d56e84ae3fa6d7feb86388f026a8e40612dd6e5a6599c8d430c9e6254d65" "3818fd4ccf7b3b7d8aafa8d88043c66e0b0595430aec58742896575d96470a5a" | xxd -r -p | shasum -a 256

    Should print 79d106789b8accc9a880d334c2b1b0a8b2a845c6f8f29337e66d43e8c2767ebc

  4. 4. Combine step 2

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

    printf '01%s%s' "79d106789b8accc9a880d334c2b1b0a8b2a845c6f8f29337e66d43e8c2767ebc" "d2e9c048cd6ee0d52f7085d8f50cc90ac3096d39385588e6e8702e9dbf11a113" | xxd -r -p | shasum -a 256

    Should print 7ec5e373ad571f9b92df693781e92ada98745598eb8e1ffb28fac8b8743de56f

  5. 5. Combine step 3

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

    printf '01%s%s' "9a459029e464b4d8a058f4a436b5f2ef4ee164eef22c325501317a042faf4e2c" "7ec5e373ad571f9b92df693781e92ada98745598eb8e1ffb28fac8b8743de56f" | xxd -r -p | shasum -a 256

    Should print 7087efc2d674dbe642dc177888d3e9b5ba01a5253e24be3f8056524c155c46ef

  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-sepolia.easscan.org/attestation/view/0xbd466171c9269a1553b500cf540d4d833a73a86f8b5340dd05858ee67a202cc1

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

Read the specification