Pond Street Ledger

How a Stock Token Handles a Dividend, and Why It Is Never Quite the Same Cash

A share pays its holder on a record date fixed by the issuer. A token pays whoever a smart contract says held it, after a custodian has been paid, after tax has been withheld, and usually in something other than the dividend itself.

✓ 1593.efrogs.eth2026-10-168 min

The question

A tokenized share is marketed as economic exposure to a listed company. Listed companies pay dividends. So what arrives in the wallet of someone holding a stock token on the day the underlying company pays out, and why is the answer rarely "the dividend"? The mechanism is worth walking through in order, because almost every difference between a token and a share shows up somewhere along this chain.

What a dividend actually is in the old plumbing

A dividend is a payment from a company to the registered holders of its shares as of a record date. Almost nobody is a registered holder. Shares sit in a chain of nominees: a central securities depository holds the position, a custodian bank holds an account at the depository, a broker holds an account at the custodian, and the retail client holds a claim on the broker. Cash flows back down that same chain, net of withholding tax levied by the company's home jurisdiction, and each layer allocates to its own clients using its own books. The record date, the ex date and the pay date are separated by days precisely because this allocation takes time.

Where the token sits

A stock token is one more layer bolted onto the bottom of that chain, with a twist: the layer below the broker is no longer a client list, it is a public ledger. The issuer, or an affiliated broker, holds the real shares with a custodian. It mints tokens against that position. Holders of those tokens are, legally, holders of a claim against the issuer, and the terms of that claim are set out in a prospectus or terms of issue, not in company law. Whatever the dividend treatment is, it is a contractual promise by the issuer, not a right against the company whose name is on the ticker.

Four ways issuers handle the payment

In practice there are four designs, and a reader can usually work out which one applies by reading the terms rather than the marketing page. The first is cash distribution: the issuer receives the dividend, withholds what it must, and pushes a stablecoin payment to holders recorded at a snapshot block. The second is reinvestment: the issuer buys more shares with the dividend and mints additional tokens pro rata, so the holder's token count rises instead of their cash balance. The third is price adjustment: no distribution at all, the token simply tracks a total return index, so the dividend shows up as a slightly higher token price relative to the share price forever after. The fourth, common on wrapped or synthetic products, is nothing: the dividend accrues to whoever is running the hedge, and the holder is explicitly told so.

The snapshot problem

Cash distribution is the design that creates the most interesting failures, because it requires the issuer to decide who held the token at a moment in time. On a blockchain, holding is not a tidy concept. Tokens sit in automated market maker pools, in lending protocol collateral vaults, in bridge contracts, in exchange omnibus wallets. A naive snapshot of token balances at a block pays the pool contract, the lending pool and the bridge, none of which has a client list the issuer can see. The usual fixes are to whitelist known contracts and distribute to them for onward allocation, or to exclude them and let the protocol capture the payment as protocol revenue, or to require that tokens be held in a registered wallet to be eligible. Each of those choices redistributes money between holders who did nothing differently except choose where to park the asset.

Tax is where the exposure stops being clean

Withholding is deducted before the issuer ever sees the cash, at a rate that depends on the treaty position of the custodian's jurisdiction, not the holder's. A holder who would be entitled to a reduced treaty rate, or to a full refund, on a directly held share generally cannot reclaim anything on a token, because the reclaim process requires documentation from the registered holder down a chain that the token sits outside of. This is the quiet reason tokenized versions of high-dividend stocks underperform the shares they track over long holding periods, and it has nothing to do with the blockchain. It is a function of where in the custody chain the tax is stripped out and who has standing to argue about it.

Timing, and the gap nobody closes

Shares go ex dividend at the opening of a specific session on a specific exchange. Tokens trade continuously. That means there is a window, often several hours long, in which the token's reference asset has gone ex dividend but the token market is still pricing it cum dividend, or the reverse. In a liquid token this gets arbitraged within minutes. In a thin one it can persist until the next session opens, which is how a holder ends up selling into a price that has not yet absorbed a payment they were about to receive. Issuers mitigate this by publishing the snapshot block well in advance. They cannot eliminate it, because the mismatch is between a market that closes and a market that does not.

Corporate actions beyond dividends

The same machinery has to handle splits, reverse splits, rights issues, spin offs, mergers and tender offers, and it handles them with less grace. A split is easy: the issuer either mints pro rata or restates the backing ratio and publishes the new one. A rights issue is hard, because it requires the holder to make an election and pay money, and a token contract has no way to ask. The common resolution is that the issuer sells the rights and distributes proceeds, which converts an optional decision into a forced one. A spin off is harder still, because it hands the issuer an asset it may not be licensed to tokenize. Reading how an issuer says it will handle a spin off is a faster test of operational seriousness than reading how it handles dividends.

Where it breaks

The failure modes are concentrated at the joints. The custodian pays the issuer late and the onchain distribution slips, which is survivable. The snapshot is taken at a block during unusual onchain activity and the allocation is wrong, which is not easily reversible once stablecoins have moved. A contract the issuer whitelisted turns out to have no mechanism to pass the payment to its own depositors. Or the issuer simply retains the dividend to cover operating costs, having disclosed as much in a document nobody read. None of these are blockchain problems in any technical sense. They are the consequence of attaching a programmatic settlement layer to a corporate actions process that was designed around business days and phone calls.

What to watch

Three documents tell the story. The terms of issue, which say whether a distribution is promised at all and in what form. The reserve or attestation page, which should show whether cash received but not yet distributed is being held separately from the share backing. And the issuer's published corporate actions policy, which should name the snapshot method and the treatment of pooled contracts. Where a product's dividend handling is described only in a footnote on a marketing page, the honest reading is that the question has not been settled yet, and the holder is the one carrying that uncertainty.