Digital Gilt Pilot Tests Interoperable Tokenized Securities

The UK’s planned Digital Gilt Instrument (DIGIT) pilot will test whether tokenized securities can move beyond single-platform issuance. Under an agreement between HM Treasury, HSBC, and LSEG, investors are expected to access and hold the digital gilt through either HSBC Orion or LSEG’s digital securities depository, while HSBC Orion remains the issuer depository and LSEG supports investor-side settlement and asset servicing. HM Treasury said the first transaction is expected by Q1 2027, subject to the pilot’s progress.

That makes the initiative more than an issuance experiment. It is a practical test of interoperability between regulated digital-securities infrastructures, including custody choice, settlement connectivity, and post-issuance workflows.

What the digital gilt link is designed to do

According to HM Treasury, HSBC and LSEG have signed a memorandum of understanding for a bilateral Digital Securities Depository link. The arrangement is intended to let investors access and hold DIGIT through either infrastructure. HSBC Orion would remain the depository for issuance, while LSEG’s platform would provide an investor-side route for settlement and asset servicing. HM Treasury

The distinction matters. In a conventional single-platform digital issuance, the issuer, investors, settlement functions, and servicing records may be closely tied to one infrastructure. A bilateral link introduces a second venue for investor-side activity without changing the designated issuance location.

Fundshing’s analysis is that this could create a more modular operating model: an issuer may select one infrastructure for creation and recordkeeping, while investors and intermediaries use another for settlement, custody, or servicing. The pilot will show whether that modularity can work without creating reconciliation, eligibility, or control gaps.

The announcement does not establish that the link is already operating at production scale. It describes an agreed direction for the pilot, with the first transaction planned for Q1 2027. HM Treasury

Why interoperability matters for tokenized securities

The market’s early tokenization projects often focus on issuing a digital representation of an asset. The harder operational questions emerge afterward: where the asset is held, how ownership changes are recorded, how settlement instructions are coordinated, and how coupons, redemptions, corporate actions, and reporting are delivered.

A linked depository model puts those questions at the centre of the pilot. Investors may gain a choice of infrastructure, but that choice must be supported by consistent records, clear transfer rules, and reliable messaging between platforms. Infrastructure teams will need to establish how balances are reconciled, how exceptions are handled, and which party has responsibility when a transaction does not complete as expected.

The pilot is also relevant to broader RWA tokenization. Real-world asset tokenization is not only a question of placing an asset on distributed-ledger infrastructure. It also depends on connecting the digital record to legally and operationally meaningful ownership, settlement, custody, and servicing processes.

IPE reported that the planned sterling digital sovereign bond is intended to test whether distributed-ledger infrastructure can improve capital-market efficiency and reduce costs. IPE Those are stated objectives for the pilot, not established outcomes. Any efficiency gain will depend on how the connected platforms handle volumes, controls, exceptions, and integration with existing market participants.

Implications for issuers and investors

For issuers, the proposed structure separates issuance design from investor distribution and servicing. That may broaden the set of intermediaries able to participate, but it also increases the need for precise operating documentation. Issuers will need clarity on the authoritative record, settlement finality, reconciliation responsibilities, reporting obligations, and procedures for events such as maturity or coupon payment.

The issuer workflow should also define who can act on investor instructions and how those instructions are validated. A digital instrument does not remove the need for permissions, participant eligibility, sanctions screening, transaction monitoring, and audit trails. Instead, those controls must be coordinated across the connected infrastructure.

For investors, access through either platform could offer greater custody and settlement flexibility. It does not necessarily mean that all investors will have identical rights, access, or economics. Eligibility, account structures, onboarding requirements, operational cut-off times, and supported servicing functions may differ between participants.

Investors and their intermediaries will therefore need to assess the full lifecycle, not just the purchase process. Questions include how holdings are displayed, how transfers are instructed, how asset servicing notices are delivered, and what happens if one platform is unavailable. These are workflow considerations rather than assurances about liquidity, performance, or investment return.

Compliance and post-issuance controls

The cross-platform design makes compliance architecture especially important. A connected model must preserve a clear chain of authority from issuance through settlement and servicing. That includes participant identification, ownership records, transfer restrictions, data retention, and access controls.

For teams building or evaluating a tokenization platform, the practical lesson is to treat interoperability as a control problem as well as a technical one. APIs or ledger connectivity may move data, but they do not by themselves determine which record prevails, how disputes are resolved, or how compliance evidence is assembled.

Post-issuance servicing deserves equal attention. Coupon calculations, payment instructions, redemptions, notifications, and corporate-action records must remain consistent across the issuer depository and the investor-side infrastructure. If different systems present different balances or statuses, the operational burden can quickly outweigh the benefits of a digital instrument.

The DIGIT pilot may provide useful evidence on those points, but its scope should not be confused with a general validation of all tokenization models. The arrangement concerns a specific planned digital gilt and a defined connection between HSBC Orion and LSEG’s digital securities depository. HM Treasury

What infrastructure teams should watch next

The most informative milestones will be the pilot’s technical and operational details: participant onboarding, settlement-cycle design, reconciliation procedures, asset-servicing responsibilities, exception management, and the treatment of platform outages or failed instructions.

Teams should also watch how the pilot defines the relationship between the issuer depository and the investor-side depository. A successful connection will require more than transferring transaction data. It will need common business rules, secure identity and permissioning, transparent status reporting, and evidence that records remain synchronized through the instrument’s lifecycle.

Fundshing analysis: if those elements work in practice, the pilot could strengthen the case for interoperable tokenized securities rather than isolated digital assets. If they prove difficult, the results could still be valuable by showing where legal, operational, or technical standards need refinement.

The practical takeaway is to evaluate tokenization as an end-to-end operating workflow: issuance, custody, settlement, servicing, compliance, and exception handling should be designed together. Which part of your asset lifecycle would benefit most from a connected digital-securities workflow? Explore the Fundshing Tokenization Engine to discuss which workflow may fit your asset.

Sources

• Update on the Digital Gilt Instrument (DIGIT) pilot issuance - HM Treasury
• UK targets first digital gilt issuance by early 2027 - IPE