How to verify a tokenized stock is genuine

1. Establish the issuer independently

Reach the issuer through an independently checked official domain. Find the product page, legal issuing entity, final terms, underlying security, and supported networks. Avoid taking a token’s own metadata URL or an unsolicited message as your starting authority.

Distinguish the issuer from the company whose stock is referenced, the exchange listing the token, and a wallet displaying it. An exchange integration is not proof that the underlying company authorized the product.

Sources: xStocks: product documentation · Ondo Stocks: product details and eligibility FAQ

2. Match the chain and full contract address

Copy the deployment address from the issuer’s current list and compare every character with the token’s contract or mint on the intended chain. An EVM contract address and a Solana mint are different identifier formats. Neither a symbol match nor matching first and last characters is enough.

Use the token contract or mint, not your wallet address, a token account, a pool, or a transaction hash. If the official list and explorer disagree, resolve the discrepancy before interacting. An issuer may migrate a contract, but the migration needs an independently verified notice.

• Record the network name and chain ID where applicable.
• Compare the complete contract or mint address.
• Check that the token represents the intended security and issuer.
• Follow the issuer’s own explorer link where one is published.

3. Understand what an explorer badge proves

Source-code verification can show that published code matches a deployed contract. It does not establish that the deployer is the intended issuer or that offchain shares exist. A fake contract can expose a function with a reassuring name and return true.

Check issuer-controlled registries or factories only when the issuer documents them and the registry address itself has been authenticated. Inspect administrative upgrade, mint, freeze, pause, and transfer controls. These powers can be legitimate product features, but they affect what holding the token means.

4. Read the backing evidence and legal claim

Locate the custody description, reserve report or attestation, its date, and the assets and liabilities it covers. Ask whether reported reserves correspond to the current token supply and conversion ratio, and whether cash in transit or other assets are included.

A reserve snapshot is not continuous assurance, deposit insurance, or a promise of recovery in insolvency. Read who has the enforceable claim, any security interest, and how claims are processed if an issuer or custodian fails.

Sources: Kraken: xStocks risk disclosure

5. Check whether a real exit exists

An authentic deployment can have little trading activity. Inspect the supported venues, price timestamp, spread, depth, and redemption process separately. An indicative portfolio value does not establish that a buyer will take your full balance at that value.

Determine who can redeem, which checks are required, and whether the destination network is supported. A functioning transfer or a small successful sale does not prove that a larger exit will work under stressed conditions.

How to use Tokenzo as a cross-check

Use the issuer directory and the security’s token list to compare the registry’s chain-and-address mapping with the issuer’s current publication. The registry is a dated reference with differing source coverage; it is not a substitute for the legal documents or a live reserve audit.

During this project’s registry research, searches returned unrelated tokens using familiar equity tickers, and issuer-like metadata led to incorrect candidate addresses. The general lesson is reproducible: search labels help you find candidates; chain and address establish which candidate you are looking at.

If a token appears unexpectedly in your wallet, viewing its balance requires no token approval or signature. Do not follow an unsolicited claim link to ‘verify’ it. Verification should begin with public, read-only information.