Skip to main content

How to run tokenized assets: registers, NAVs and payouts

Running tokenized assets is the work that follows issuing a fund, stock or bond as tokens: keeping supply matched to the asset, the holder register current, the asset’s value readable onchain and holders paid, while the issuer, transfer agent and fund administrator keep their usual roles.

This playbook sets out the decisions in the order you’ll make them. Each one links to the use case pages and docs that cover it in detail.

Issue and back the tokens

Your issuance platform mints the tokens, so these decisions tie every mint and burn to an order, an allocation or the asset in custody.

Check launch mints against allocations

Keep the allocations set when the book closes beside the mints, so every unit minted at launch or in a tokenized IPO ties to an allocation.

Keep the holder register

The chain records wallets and balances while the transfer agent’s register names investors, so the two have to agree every time tokens move.

Combine every chain into one register

If the fund is issued on several chains, decide how units moved between chains are paired so the register reports one total and one set of investors.

Record recoveries of lost tokens

Match each recovery to the request your team approved, because the tokens move to the investor’s new wallet without the old one signing.

Value the asset and publish it onchain

Contracts can only read a value that’s on the chain, so each figure goes from the firm that sets it to every chain that uses it.

Pay holders and report to them

Every payout, vote and statement starts from who held the token at a set date, read from the same register.

Turn this plan into a working build

We can help you work through each decision and get the first stage into production.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status