Six Mechanisms That Decide Whether an Asset Can Be Tokenized
Not the token standard — the machinery underneath it. Six interactive simulations of the mechanics that govern tokenized funds: atomic settlement, the compliance subgraph, mirror-record drift, NAV staleness, liquidity transformation, and a scoring model for what gets tokenized next.
Most writing on tokenization argues about whether it will happen. That question is settled: money market funds, private credit feeders and bank deposits are already on chain. The open question is narrower and more useful — for a given asset, what has to be true mechanically before a token is anything more than a second copy of the register.
Six mechanisms answer that. Each one below is running live. Drive the controls and watch the constraint bind.
Atomic delivery versus payment
Two ledgers, one commit. A hashed timelock makes settlement all-or-nothing across systems that share no coordinator, no clock and no legal entity.
IN FUND SERVICING: a subscription where the cash leg is a tokenized deposit and the share leg is a fund share token — the entire case for T+0, and the only part of tokenization that removes a real cost line rather than moving it
Fund 0 USD
Fund 250,000.00 units
Idle. Run a settlement, then try to break it.
The compliance subgraph
Every transfer is a boolean predicate over both parties' claims. The permitted-transfer relation forms a graph, and tradable float is bounded by its largest connected component — not by the number of tokens issued.
IN FUND SERVICING: Reg D 506(c) accreditation, jurisdictional whitelists, lockups and holder caps compiled into the transfer function itself — the whole substance of the ERC-3643 style permissioned standards
Active predicates: accreditation, jurisdiction whitelist (US, EU, UK), lockup. Issued supply 1275k units; 60% of it sits inside one tradable component.
Mirror-record drift
When the official register stays off chain and the token is a mirror, the two are eventually consistent. The size of the inconsistency is not a mystery — it is Little's law.
IN FUND SERVICING: the model actually shipping today — the transfer agent keeps the master securityholder file and the chain carries a mirrored record, so every in-flight event is a position that exists in one book and not the other
Vertical rule = NAV strike. Whatever is in flight at the strike is a reconciliation break the following morning.
NAV staleness and the arbitrage band
A fund share is priced once a day. A token trades continuously. The gap between them is not mispricing — it is the accumulated diffusion since the last strike, bounded by whatever it costs to arbitrage against the primary market.
IN FUND SERVICING: the reason a tokenized share class either needs an intraday NAV capability or a creation and redemption mechanism borrowed wholesale from the ETF world
Green step = struck NAV. Shaded band = the no-arbitrage corridor. Light line = secondary token price.
Liquidity transformation and the first-mover premium
Tokenizing an illiquid asset does not make it liquid. It relocates the illiquidity into a queue, and a queue with a fixed buffer at its head pays the front of the line out of the back.
IN FUND SERVICING: tokenized private credit and private equity feeders sold on 24/7 transferability with minimums as low as $500, against an underlying that settles in weeks
No swing, no gate: early redeemers exit at the last struck NAV, funded by forced sales, and the haircut lands on whoever is still in the queue.
What gets tokenized next
Not a forecast — a scoring model. Six factors decide the order, and a fixed-cost break-even decides whether the vehicle is big enough to bother. Move the weights and watch the queue reorder.
IN FUND SERVICING: the actual question on a product roadmap — which fund lines justify a tokenized share class in the next eighteen months, and which are a pilot that never scales
Break-even compares annual run cost against bps of operating spend the format actually removes, applied to a typical vehicle size for that asset class.
The common thread: every one of these mechanisms is a constraint on who may hold, when, and at what price — and none of them is a property of the token. Atomicity is a lock ordering. Float is a subgraph. Drift is a queue. Premium is a diffusion. The run is a buffer. Tokenization does not relax any of them. What it does is make each one explicit and executable, which is genuinely valuable and considerably less than what it is usually sold as.
All simulations run client-side; parameters are illustrative and calibrated to public disclosures, not to any single fund.