What "Fully Backed" Actually Means on a Stock Token's Reserve Page

A tokenized equity is a liability. Somebody has promised that a token in your wallet corresponds to a share held somewhere, and that the promise can be converted back into either that share or its cash value. Everything else about the product, the chain it runs on, the swap fee, the trading hours, sits on top of that promise. The reserve page is where the issuer tries to convince you the promise is good. Most of them are harder to read than they look, and the hardest part is working out which question each piece of evidence actually answers.

The four questions a reserve page can answer

There are only four. Does the underlying exist. Is it held in a way that survives the issuer's failure. Is there enough of it for every token outstanding. Can you get it, or its value, back. A reserve page that answers the first three and says nothing about the fourth is common, and it is the one worth noticing, because redemption is where retail holders usually find out they are not the customer.

Attestation is not audit

The most frequently published artefact is an attestation report from an accounting firm. An attestation is an agreed-upon-procedures engagement: the issuer tells the firm what to check, the firm checks exactly that and nothing more, and reports what it found at a stated moment. An audit, by contrast, involves an opinion on financial statements as a whole, prepared against a standard, with the auditor choosing the scope. The difference is not pedantry. An attestation that confirms a custodian account held a certain number of shares at 23:59 on the last day of the month tells you nothing about the other 43,199 minutes, nothing about whether those shares were pledged elsewhere, and nothing about the issuer's other liabilities.

Read for three things. The as-of timestamp, because a point-in-time count can be assembled and then unwound. The scope paragraph, which says which accounts were examined and, by omission, which were not. And the counting basis: shares held at a custodian is a different claim from shares plus cash plus receivables from a prime broker, and the latter sneaks credit exposure into something sold as a one-for-one holding.

Proof of reserve is a price feed about a number, not a proof

Several issuers now publish a continuous feed, usually an oracle contract that an onchain reader can query, reporting the reserve balance. This is a real improvement in frequency and a real degradation in assurance, and the two are a trade. The feed is fast because a machine reads a custodian API and signs the result. It is weak because the only thing cryptography proves is that the signer said so. There is no chain of custody from the share register to the signature. If the API is wrong, misconfigured, or reporting an account that has been rehypothecated, the feed faithfully publishes a wrong number on time.

The useful variant is a feed with a circuit breaker: the token contract, or the venue quoting it, reads the reserve figure and halts minting when reserves fall below supply. That turns a disclosure into a control. Ask whether anything consumes the feed, or whether it merely exists for a dashboard. A number nobody acts on is decoration.

Where the shares actually sit

The legal question underneath all of this is whether the shares are the issuer's property or yours. Three structures recur. Shares held on the issuer's own balance sheet, with token holders as unsecured creditors, which is the weakest and also the simplest to run. Shares held by a custodian in an account titled for the benefit of token holders, which gets you segregation and, in most jurisdictions, protection from the issuer's general creditors. And a bankruptcy-remote special purpose vehicle that owns the shares and issues the tokens, which is strongest and most expensive, because it requires separate governance, separate accounts and a trustee who will act when the sponsor does not.

The giveaway is in the terms rather than the reserve page. Look for the words segregated, for the benefit of, trustee, and the name of the entity that is actually the account holder. If the holdings table is impressive and the terms say the issuer may use the assets in the ordinary course of business, the table is describing the issuer's inventory, not your collateral.

What a one-for-one ratio hides

Supply divided by reserves equals one is a weaker statement than it reads. It is consistent with reserves consisting partly of cash rather than shares, which is sometimes deliberate and should be disclosed as a hedging policy rather than discovered. It is consistent with the issuer having lent the shares out against collateral it considers equivalent. And it is consistent with a sizeable share of supply sitting in the issuer's own treasury wallet, which inflates both sides of the ratio and tells you nothing about float. The honest version of the table reports reserves, total supply, and supply excluding issuer-held tokens, separately.

Where it breaks

Reserve disclosure fails in a predictable sequence. It fails first at the corporate action, when a split or a spin-off changes the share count and the attestation, published monthly, has not caught up. It fails second at the venue boundary, when tokens have been bridged to a chain the issuer does not monitor and supply onchain exceeds what the issuer believes it minted. It fails third at redemption, when the queue is longer than the stated settlement window and the reserve page, perfectly accurate, continues to report full backing while nobody can get out. Backed and liquid are different properties, and only one of them is on the dashboard.

What to watch

Three habits are worth more than any single document. Compare the attestation's as-of date to today and treat the gap as the size of your blind spot. Check whether any contract consumes the reserve feed, rather than merely publishing it. And read the redemption clause before the backing claim, because an instrument with impeccable reserves and a discretionary redemption gate is, functionally, an issuer IOU with good paperwork.