What the stock-token issuer can do

a tokenized stock is not an ordinary token. it is a claim on a real share held by an issuer, and the contract gives that issuer powers over your balance that a memecoin's contract does not have. nobody else publishes this, so we read it off the chain and publish it here.

what the issuer can do

A tokenized stock is a claim on a real share held by an issuer, and the contract gives that issuer powers an ordinary token does not have. These are read from the deployed bytecode, not from a document. A capability listed here exists in the code — that is not the same as saying it has ever been used.

burn from any wallet — the issuer can destroy these tokens in any address without that address approving it — including tokens sitting inside a liquidity pooladminBurn(address,uint256)
mint new supply — new tokens can be created, which is how a backed asset stays backed as demand growsmint(address,uint256)
freeze all transfers — transfers can be halted; the flag is shared, so it stops every tokenized stock at oncepause()
block a specific address — an address can be denied sending or receiving, and the check also covers the callerisBlocked(address)
rename the asset — name and symbol are mutable, so neither is a safe identifier — only the address issetMetadata(string,string)
corporate-action multiplier — splits and stock dividends are applied as a display multiplier; balances themselves never rebaseuiMultiplier()

shared implementation 0xb354…5ae2 · 11,614 bytes · 89 tokens point at one beacon · read 1h ago · what this means →

why we publish this

Every price on this site that involves a tokenized stock — a premium, a drift, a settlement figure, a launch anchored to one — inherits these powers. A liquidity pool holding a stock token can have that token destroyed inside it without any transaction from the pool or its owner. So "locked liquidity" quoted against a tokenized equity is bounded by something the lock does not control, and anyone claiming otherwise is describing a guarantee they cannot give.

This is not an accusation. Backed assets need these controls: a redemption needs a burn, a sanctions regime needs a block, and an issuer with no ability to freeze a compromised address would be the more alarming design. The point is that the powers exist, that holders should know before they buy rather than after something happens, and that a terminal claiming to read the equity layer should say so plainly.

what it does NOT mean

· A function existing in bytecode is not evidence it has been used. We report presence, never intent.
· The corporate-action multiplier does not change your balance. Splits are applied as a display scalar; the raw ERC-20 amount you hold is untouched, which is why pool accounting survives them.
· None of this says anything about whether the shares behind the tokens exist. That is a question about the issuer's books, and no amount of chain reading answers it.

verify it yourself

Read the beacon slot on any stock token, follow it to the implementation, and search the bytecode for the selectors above. The beacon slot is keccak256("eip1967.proxy.beacon") - 1.

implementation 0xb354…5ae2 on blockscout ↗

source: robinhood chain rpc (eth_getStorageAt, eth_getCode, eth_call) · updated 1h ago · capabilities are detected by 4-byte selector presence in the deployed bytecode; the pause state is a live call. a reading older than its ceiling is withheld rather than shown.

New to these terms? The glossary explains tokenized stocks, multipliers and the rest in plain English.

loading chain data…

what the issuer can do

burn from any wallet — the issuer can destroy these tokens in any address without that address approving it — including tokens sitting inside a liquidity pooladminBurn(address,uint256)

mint new supply — new tokens can be created, which is how a backed asset stays backed as demand growsmint(address,uint256)

freeze all transfers — transfers can be halted; the flag is shared, so it stops every tokenized stock at oncepause()

block a specific address — an address can be denied sending or receiving, and the check also covers the callerisBlocked(address)

rename the asset — name and symbol are mutable, so neither is a safe identifier — only the address issetMetadata(string,string)

corporate-action multiplier — splits and stock dividends are applied as a display multiplier; balances themselves never rebaseuiMultiplier()

shared implementation 0xb354…5ae2 · 11,614 bytes · 89 tokens point at one beacon · read 1h ago · what this means →

why we publish this

what it does NOT mean

· A function existing in bytecode is not evidence it has been used. We report presence, never intent.

· The corporate-action multiplier does not change your balance. Splits are applied as a display scalar; the raw ERC-20 amount you hold is untouched, which is why pool accounting survives them.

· None of this says anything about whether the shares behind the tokens exist. That is a question about the issuer's books, and no amount of chain reading answers it.