The first wave of asset tokenization proved that funds, bonds and other assets can be represented digitally and transacted on-chain. Yet despite a growing number of tokenized products, adoption remains fragmented and concentrated in isolated use cases. The next challenge is not creating more tokenized assets, but making them useful. How can tokenized assets be mobilised as collateral, deployed in funding markets, transferred seamlessly across institutions, and integrated into liquidity and treasury operations?

Building on Guardian's work in tokenized collateral and tokenized funds, this roundtable explores how tokenized assets can evolve from investment products into operational instruments that support financing, margining, collateral management and liquidity optimisation. Participants will discuss the legal, regulatory and infrastructure enablers needed to unlock collateral mobility, the role of tokenized money market funds and sovereign debt instruments, and whether a more connected ecosystem can create the scale necessary for institutional adoption.

The GDF Global Stablecoin Regulatory Playbook, published in January 2026, set out shared terminology and outcome-based principles for stablecoin regulation across jurisdictions. The subsequent report ‘Global Stablecoin Regulatory Frameworks: Closing the Gap’ drawn from insights at the Point Zero Forum in June 2026 took this work a step further. It mapped where regulators already agree and isolated the one problem that domestic frameworks were never designed to solve: how a stablecoin issued under one jurisdiction's rules can circulate safely under another's.

The report framed two models for scaling beyond domestic rules. The first keeps issuance local while seeking to preserve a unified token, through multiple licensed entities issuing a fungible stablecoin under comparable standards. The second permits a foreign-issued stablecoin to operate through recognition based on comparable, rather than identical, regulatory outcomes. It also recorded differing regulatory perspectives on the perceived risk associated with multi-issuance, particularly correlated redemption pressure and the resilience of a stablecoin’s fungibility under stress.

The roundtable convenes policymakers, global standard-setters and industry leaders to examine how these models could operate in practice. When is multi-issuance necessary to meet host-jurisdiction objectives? When can unilateral or mutual recognition provide sufficient safeguards? Where a combination of the two is appropriate, how should responsibility for reserves, redemption, supervision and crisis management be allocated? The session will focus on the conditions needed to make each approach workable while preserving fungibility and avoiding unnecessary regulatory fragmentation.

As money becomes programmable, across central bank digital currencies, tokenized deposits, and stablecoins, a real question is emerging about where compliance should live: embedded directly in the asset as a rule that travels with it, layered on top through richer messaging and real-time screening, or enforced separately by whichever party touches the transaction last.

Players are all building credible but different answers in parallel, and none has converged on how these should interoperate across jurisdictions with different compliance regimes. The stakes are rising on every front — real-time cross-border settlement, tokenized securities, and increasingly, autonomous agents initiating transactions on their own — all of which need a compliance check at the moment value moves, not after. What would each of these approaches to programmable compliance actually need to interoperate, and which rules win when they conflict across borders?

Discussion questions:

1\.         Should compliance logic live in the asset itself, in the messaging/settlement layer, or in a separate real-time screening service, and does the answer change depending on whether it's a CBDC, a tokenized deposit, or a stablecoin?

2\.         When a transaction crosses borders, whose compliance rule actually governs — sender's jurisdiction, receiver's, or the rail's — and what happens when they conflict?

3\.         Retrofitting compliance onto existing settlement infrastructure and building it in from scratch are both live strategies right now — what would each need to prove to become the default, and is convergence between them actually possible?

4\.         As more transactions — including those initiated by autonomous agents — require a compliance check the moment value moves, what are the minimum interoperability standards needed for rules to actually travel with money across rails?