Verify

Nothing here asksto be believed.

Every number on this site is derived, and each derivation is a command. If what you compute disagrees with what is published here, what is published is wrong. These are the exact calls the site makes.

001 A split is sitting inside a token contract

CrowdStrike split four for one. The multiplier on chain is exactly 4, so one token stands for four shares. Any screen that reads one token as one share reports a premium of +305.93% that is not there.

the multiplier

cast call 0xea72Ecca2d0f6bFA1394DBBCff85b52CD4233931 \
  "uiMultiplier()(uint256)" \
  --rpc-url https://rpc.mainnet.chain.robinhood.com

# 4000000000000000000   ->  4.000000000 shares per token
# pool price      $854.49
# share price     $210.50
# token worth     $842.00   (share x multiplier)
# implied basis   +305.93%
# true drift      +1.48%

002 The Chainlink price already carries the multiplier

This is the detail integrators get wrong. The feed answers the token price, not the share price. Divide by the multiplier to get a share; multiply a share by it to get a token. SGOV makes it visible because its multiplier has already moved.

feed vs issuer

cast call 0xa0DF4ee0fFf975306345875E3548Fcc519577A11 \
  "latestRoundData()(uint80,int256,uint256,uint256,uint80)" \
  --rpc-url https://rpc.mainnet.chain.robinhood.com
# answer / 1e8            = 100.98760034

curl -s "https://api.robinhood.com/rhj/prices/SGOV"
# raw underlying share    = 100.4850

cast call 0x92FD66527192E3e61d4DDd13322Aa222DE86F9B5 "uiMultiplier()(uint256)" --rpc-url https://rpc.mainnet.chain.robinhood.com
# multiplier              = 1.005101770

# share x multiplier      = 100.99765136
# which is the feed answer, to the cent

003 The chain does not know what is coming

XOM reprices on 2026-09-10. Ask the token about it now and it answers zero, because the pending fields only populate as the tick lands. The schedule exists only in the issuer’s API, which is why Collapick publishes it.

pending vs scheduled

cast call 0xf9B46d3D1B22199D4D1025a9cEDB540A33F1a2d5 "newUIMultiplier()(uint256)" --rpc-url https://rpc.mainnet.chain.robinhood.com
cast call 0xf9B46d3D1B22199D4D1025a9cEDB540A33F1a2d5 "effectiveAt()(uint256)"     --rpc-url https://rpc.mainnet.chain.robinhood.com
# both answer 0: the chain has no idea

curl -s "https://api.robinhood.com/rhj/corporate-actions" \
  | jq '.corpActions[] | select(.tokenSymbol=="XOM")'
# processDate 2026-09-10   rate 1.03 per share

004 Our API returns the same numbers

No key, no limit, no account. If the JSON disagrees with the two calls above, the JSON is wrong.

collapick api

curl -s "https://collapick.tech/api/v1/assets?symbol=CRWD,NVDA,SGOV" | jq '.assets[] | {symbol, multiplier, poolPrice, fairToken, sharePrice, trueBasisPct}'

curl -s "https://collapick.tech/api/v1/calendar?status=upcoming" | jq '.calendar[0]'

curl -s "https://collapick.tech/api/v1/shares?of=CASHCAT&in=NVDA&amount=1000000" | jq

# read at block 58,594,955
# NVDA feed 225.81470  pool 225.23  drift -0.26%

On chain and off

Where the trustboundary sits.

The multiplier, the Chainlink answer and the pool reserves are on chain and you can read them without us. The corporate-action schedule and the raw share quote come from Robinhood’s own API and cannot be verified on chain before the fact. Every number on this site is labelled with which of the two it is, and 159 of 194 tokens have no on-chain price at all.

Prices move. Numbers on this page were read 0 seconds ago and the commands will return slightly different values by the time you run them. The arithmetic is what should match, not the last decimal.