Skip to content
BLUFF
BLUFF

Public evidence, not project promises

Big claims.Bring proof.

Paste a claim, post or contract. Watch BLUFF check what actually happened on Robinhood Chain.

Robinhood Chain contracts, wallets and transactions. You choose mainnet or testnet next.

Try a contractStock Token checkReal addresses from Robinhood Chain's docs.

Real case, replay of recorded receipt order

Evidence map for: Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.. Evidence map for the claim about 0xd95B44124e475743a7589e68F3D74008A5536D44. 4 receipts observed on Robinhood Chain. Finding: Supported. Use Tab to move between items and Enter for details. Focus the map and use the arrow keys to pan, plus and minus to zoom, 0 to reset.
The claim0xd95B…6D44docs.robinhood.comR-001R-002R-003R-004Robinhood Chain RPCStock Token listWeb captureSupported

“Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.”

Supported4 receipts from Robinhood Chain and the official Stock Token list.Open casefile

  1. A claim

    “Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.”

    Public source

  2. An observation

    R-001: Captured HTTP 200, “Stock Token APIs – Robinhood Chain Documentation”. The quoted claim wasn't found in it.

    See the receipt

  3. A sourced finding

    0xd95B…6D44 is listed as CRM in the official Stock Token list for Robinhood Chain. Being official says nothing about price or investment safety.

    Read the casefile

A transaction can be real.The story around it might not be.

The claim

“Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.”
As published at docs.robinhood.com

What can actually be verified

  • The official Stock Token list (194 assets, fetched 2026-10-12T16:45:15.221Z) lists 0xd95B44124e475743a7589e68F3D74008A5536D44 on Robinhood Chain as CRM (Salesforce • Robinhood Token), status ASSET_STATUS_ACTIVE.
  • The contract reports name “Salesforce • Robinhood Token”, symbol “CRM”, 18 decimals at block 86,824,465.
  • Not shown: anything about price, liquidity, or investment safety.
  • Not shown: who is promoting it or why.

Bytecode and transactions can't establish that an AI agent is acting on its own. They show that code exists or that a wallet sent something. Who or what decided to send it stays unknown, and every casefile says so.

Follow the evidence.

Every line on this map comes from a receipt in a real case. Select a point to see what was read, where it came from, and what it can't show.
Evidence map for: Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.. Evidence map for the claim about 0xd95B44124e475743a7589e68F3D74008A5536D44. 4 receipts observed on Robinhood Chain. Finding: Supported. Use Tab to move between items and Enter for details. Focus the map and use the arrow keys to pan, plus and minus to zoom, 0 to reset.
The claim0xd95B…6D44docs.robinhood.comR-001R-002R-003R-004Robinhood Chain RPCStock Token listWeb captureSupported

Finding

Supported

0xd95B…6D44 is listed as CRM in the official Stock Token list for Robinhood Chain. Being official says nothing about price or investment safety.

Receipts cited
2

Watch the check.Not just the conclusion.

Three moments from the real product. Nothing here is a mockup: the field works, the log is the stored event log of the case above, and the receipt is its first piece of evidence.

01

Say what you're checking

Paste a contract, wallet or transaction. BLUFF tells you what it detected and asks which network before anything runs.

Works today for Robinhood Chain mainnet and testnet addresses and transactions.

Robinhood Chain contracts, wallets and transactions. You choose mainnet or testnet next.

02

Watch the network answer

Each step is written to the database before it appears. Lose the connection and the room replays from the last event it showed you.

Read-only JSON-RPC at a pinned block, plus Robinhood's official Stock Token list.

Stored event log, run_01m4…jmpx

  1. #5Observed

    R-001 Claim source at docs.robinhood.com: Captured HTTP 200, “Stock Token APIs – Robinhood Chain Documentation”. The quoted claim wasn't found in it.

  2. #6Step

    Reading deployed bytecode.

  3. #8Observed

    R-002 Bytecode at 0xd95B…6D44: 283 bytes of bytecode on Robinhood Chain at block 86,824,465.

  4. #9Step

    Reading the token's name, symbol and decimals.

  5. #11Observed

    R-003 Token metadata of 0xd95B…6D44: Contract reports “Salesforce • Robinhood Token” (CRM), 18 decimals, at block 86,824,465.

  6. #12Step

    Fetching the official Stock Token list.

  7. #14Observed

    R-004 Official Stock Token list: Lists 0xd95B44124e475743a7589e68F3D74008A5536D44 on chain 4663 as CRM (Salesforce • Robinhood Token).

03

Read what holds up

The casefile keeps every receipt with its block, time and payload hash, and links to a place you can check it yourself.

Not yet: reading X posts, web pages or GitHub. Those inputs are recognised and labelled as unsupported.

Supported

R-004

Level A, independently observed

Official Stock Token list

Lists 0xd95B44124e475743a7589e68F3D74008A5536D44 on chain 4663 as CRM (Salesforce • Robinhood Token).

Source
Official Stock Token list
Observed
Payload hash
sha256 b4cddd6e70…fa2a3e

Can't show: Reflects the list at fetch time. Robinhood can add or remove assets later.

Check it yourself(opens in a new tab)

The public desk.

Every case is a real check. Newest activity first.
SupportedRobinhood Chain, updated
“Salesforce (CRM) has an official Stock Token on Robinhood Chain at 0xd95B44124e475743a7589e68F3D74008A5536D44.”

0xd95B…6D44 is listed as CRM in the official Stock Token list for Robinhood Chain. Being official says nothing about price or investment safety.

Read the casefile

R-004, official Stock Token list

Official Stock Token list

Lists 0xd95B44124e475743a7589e68F3D74008A5536D44 on chain 4663 as CRM (Salesforce • Robinhood Token).

Observed 2026-10-12 16:45:15 UTC
sha256 b4cddd6e7042…e6fa2a3e

Explore all cases

We show what the evidence says.And what it doesn't.

Labels come from code, not from a model, and an adverse finding waits for an editor. The full rules are in the methodology.

Observed directly, read-only

  • Whether bytecode exists at an address, at a pinned block
  • How many transactions a plain account has sent
  • Whether a transaction exists, which block holds it, and whether it succeeded
  • Whether an address appears in Robinhood's official Stock Token list for that chain
  • The name, symbol and decimals a token contract reports about itself

Never proven by these checks

  • Whether an AI or a person initiated a transaction
  • Who controls a wallet or deployed a contract
  • What a contract's code does, or whether it is safe
  • Price, liquidity, or whether anything is a good investment
  • Claims in X posts, web pages or GitHub, which BLUFF can't read yet

The public casefile.

What you share is a record, not a screenshot.
Case address
/cases/official-stock-token-d95b44-3f1880
Revision
1, archive sha256 2da7f01585…df2411

  • A stable address

    Every case lives at one URL that never changes, so a link in a thread keeps pointing at the same record.

  • Receipts that can't be rewritten

    The database refuses edits to receipts and revisions. A correction arrives as a new revision; the old one stays.

  • Hashes you can recompute

    Each receipt stores the SHA-256 of what the source returned. The API recomputes it every time you ask.

Every claimleaves a trail.

Check a claimExplore cases