Tokenized Collateral Is Not Just Plumbing: What Cayman Fund Boards Must Control

Société Générale's Prime Services has confirmed it will accept tokenised collateral and act as counterparty in tokenised repo on the Canton Network, with its regulated EURCV and USDCV stablecoins providing the cash leg. Broadridge has extended the engine behind its Distributed Ledger Repo platform across equities, funds, alternative assets and money market instruments. The week's headlines are about collateral mobility. The governance question, which the headlines do not answer, is where fund boards sit when collateral starts moving on chain.

The Live Market Event

On 12 May 2026 Broadridge announced an integrated infrastructure for tokenised securities, extending the tokenisation engine that already underlies its Distributed Ledger Repo platform across equities, funds, alts and money market instruments. The DLR platform reportedly tokenises in the region of 365 billion dollars in repo activity each day. The next day, on 13 May 2026, Société Générale confirmed that its Prime Services business will accept tokenised collateral as margin and act as counterparty in tokenised repo transactions on the Canton Network, with EURCV and USDCV deployed for settlement, financing and cash management in permitted jurisdictions. The bank also joined Canton as an Ecosystem Super Validator.

These two announcements, made within a day of each other, are the clearest signal yet that tokenised collateral has moved past pilot status. The plumbing is being built by the institutions that already run the conventional plumbing for repo, margin and post-trade. The market should take that seriously. What needs equal attention, and is consistently absent from the coverage, is where board-level fund governance sits when an institutional fund engages with these workflows as a participant rather than as an observer.

What Collateral Mobility Means for a Fund

A fund's relationship with tokenised collateral is not a single relationship. It is at least two distinct relationships, and the governance obligations of each are different. The board's framework must address both, separately, with full visibility into each.

A fund that does both, which is most of them, carries both sets of questions and must answer them separately. When the assets in either direction are tokenised, the workflow accelerates and the operational mechanics change. The fiduciary question does not.

Five Board-Level Control Points

The institutional governance framework for tokenised collateral activity rests on five control points. Each sits at the fund-document and board-resolution level, not at the protocol level. None is delegable to the infrastructure provider.

Eligible collateral policy

The board approves what the fund may post and what the fund may accept. For a tokenised collateral workflow this is not a question that can be left to an operating manual. The eligibility schedule must specify the categories of tokenised asset that are permitted, the issuer and venue criteria, the concentration limits, the minimum credit quality where applicable, and the treatment of stablecoins as cash equivalent. The schedule must distinguish, on its face, between collateral the fund may post and collateral the fund may accept. The risk profiles are not the same, and a single combined list almost always understates one side.

Valuation methodology and waterfall design

A tokenised collateral position has a value, and the value must be derived through a documented methodology. For listed securities the methodology is well established. For stablecoins used as collateral the question is more nuanced. The price is nominally par, but the policy must address the conditions under which par is not held and the source of any haircut applied. For tokenised funds used as collateral the underlying NAV process is the reference, and the board must understand whether the NAV is struck by a qualified administrator at a frequency appropriate to the use as collateral. The waterfall, the order in which different collateral types are valued, marked, called and liquidated, must be in the policy. Operational due diligence reads the waterfall under stress, not under normal conditions.

Custody and segregation

Custody for tokenised collateral is multiple, not single. There is the custody of the fund's own assets before they are pledged. There is the custody of assets the fund has accepted as collateral until they are released. There is the operational status of assets that have been pledged but not yet transferred, and assets that have been transferred but for which a reverse leg is contractually due. Each of these requires a documented arrangement, with the custodian, the counterparty and the administrator each understanding their respective responsibilities. Segregation of pledged assets from the counterparty's own balance sheet, where the structure permits it, is the standard a prudent board will require the counterparty agreement to address explicitly. Custody cannot be reduced to a single sentence in a fund policy. It rarely is in practice, and the documents must reflect that complexity.

Rehypothecation permissions and limits

Rehypothecation is the right of a counterparty receiving the fund's collateral to use that collateral in its own financing transactions onward. It is a powerful operational efficiency for the counterparty and a material extension of risk for the fund. The board's position on rehypothecation cannot be implicit. It must be set out: whether rehypothecation is permitted at all, the categories of asset to which it applies, any quantitative limits, the disclosure the fund must receive on the onward use of its collateral, and the conditions under which the right may be revoked. For tokenised collateral the speed of onward transfer makes the policy more important, not less. Once a token has moved, the operational ability to recall it depends entirely on the legal terms, not on the protocol.

Service-provider accountability and audit rights

The fund's administrator, custodian and any platform partner involved in the tokenised collateral workflow must be accountable to the fund under contract. The service-provider agreements should specify reporting frequency, escalation procedures on a settlement failure or valuation dispute, the audit rights the fund and its administrator hold over the platform's records, the indemnities applicable on operational error, and the conditions under which the fund may exit the platform without disruption to existing positions. Integration with a tokenisation platform does not transfer the fund's governance obligation to the platform. The fund retains it. The contracts must reflect that.

The Cayman SPC Angle: Ring-Fencing the Collateral Pool

For a platform manager operating an umbrella fund structure, the segregated portfolio company under Cayman law provides a structural tool for tokenised collateral activity that is hard to replicate in other vehicles. Each segregated portfolio of an SPC is a statutory ring-fence. The assets and liabilities of one segregated portfolio are segregated from those of every other segregated portfolio and from the general assets of the SPC. The legal effect is that a collateral exposure in one segregated portfolio does not become a creditor claim against another.

For tokenised collateral activity this matters in three places. The eligible collateral policy can be set at the segregated portfolio level, calibrated to the strategy of each portfolio. The custody and counterparty arrangements can be opened in the name of the segregated portfolio, with segregation reflected at the account level and on the tokenisation platform's records. The board reporting can present each segregated portfolio's collateral position separately, without the visibility being clouded by the aggregate platform position.

For a manager onboarding to a platform, the implication is that the SPC architecture is not just a launch convenience. It is a governance instrument, and where the strategy involves tokenised collateral workflows, the architecture should be selected and documented with that use in view. At CV5 Capital we operate CV5 SPC and CV5 Digital SPC on this principle: segregation as a structural property of the vehicle, not a contractual addition layered on after the fact.

What Must Be Addressed Before the First Workflow Goes Live

Before a fund engages with tokenised collateral workflows of any kind, three categories of document must have answered the questions above.

The offering documents must reflect that the fund may engage in tokenised collateral activity and the basis on which it may do so. Eligible collateral, valuation methodology, rehypothecation policy and the principal risks of operating in a tokenised environment must be disclosed to investors with specificity. Generic language about digital assets is not sufficient where the workflow is itself on chain.

The board resolutions must approve the eligible collateral schedule, the valuation policy, the rehypothecation policy, the counterparty list and the platform partners. The resolutions must be reviewable, amendable and presented in the board pack with sufficient context to support active oversight rather than passive sign-off.

The service-provider agreements with the custodian, the administrator, the counterparty and the platform must reflect the policies the board has approved. The audit rights, the reporting frequencies, the escalation procedures and the indemnities must be drafted, not assumed. Tokenised collateral mobility is a powerful operational capability. It does not change the fund's governance obligation. It raises the standard at which that obligation must be discharged.

Key Takeaways

• A fund's relationship with tokenised collateral is not a single relationship. Collateral the fund posts and collateral the fund accepts carry distinct governance obligations, and both must be addressed at board level.
• Five control points sit at the fund-document and board-resolution level: eligible collateral policy, valuation methodology and waterfall design, custody and segregation, rehypothecation permissions and limits, and service-provider accountability with audit rights.
• The eligible collateral schedule must distinguish on its face between assets the fund may post and assets the fund may accept. The risk profiles are different and a single combined list almost always understates one side.
• Rehypothecation is a material extension of risk for the fund. The board's position must be explicit in every relevant counterparty agreement, with disclosure and recall mechanics defined in advance.
• The Cayman segregated portfolio company provides a statutory ring-fence between portfolios, allowing tokenised collateral pools to be isolated by strategy with custody and reporting reflected at the segregated portfolio level.
• Tokenisation accelerates the workflow. It does not transfer the governance obligation to the platform. The fund's documents, board resolutions and service-provider agreements must reflect that.