Tokenized Assets6 min read
MB
Editorial Team
·November 22, 2026

How Does the PRA Assess Tokenised Asset Capital?

PRA tokenised asset capital treatment is the application of the UK prudential framework to an asset recorded through tokenisation. The PRA letter of May 18, 2026 says traditional tokenised assets can generally receive equivalent treatment where legal rights are identical and underlying risks are comparable. For issuers seeking bank holders, that creates an evidence task across legal rights, custody and token operations.

TL;DR — Key Takeaways

  • ✓The PRA test concerns identical legal rights and comparable risk; a chain label does not answer it.
  • ✓Equivalent treatment is conditional. It is not a blanket capital approval for tokenised assets.
  • ✓The PRA position is interim and sits within the existing prudential framework.
  • ✓Issuers should document powers, settlement dependencies and recovery evidence for bank reviewers.

Ready to get started?

Join others who are already using our platform.

How Does the PRA Assess Tokenised Asset Capital?

Sources checked on November 22, 2026. Operational examples are illustrative.

What is the PRA test for a tokenised traditional asset?

The PRA asks whether the tokenised version confers identical legal rights and has comparable underlying risks. That comparison must concern the actual instrument and operating arrangement.

The May 18, 2026 PRA Dear CEO letter treats ledger type as secondary to those risk characteristics. Existing rules remain the starting point, with Basel classification conditions a reference where appropriate. This is a conditional framework, not a capital ruling for a named token.

“the legal rights conferred are identical and the underlying risks are comparable”

PRA letter, page 4

The RWA tokenization guide explains the instrument-level context. This page focuses on the proposed evidence an issuer can prepare for a bank assessment; it does not calculate a risk weight for a specific holding.

How can an issuer demonstrate identical legal rights?

A rights comparison should connect the token to the claim a bank would own in the conventional instrument. A name, ticker and matching coupon are insufficient evidence of that equivalence.

Our suggested legal matrix compares issuer, obligor, ranking, cash-flow rights, enforcement, governing law and transfer effectiveness. Ask counsel to identify which register establishes ownership and what happens when the wallet balance and legal record differ.

Illustrative issue: a token gives a claim against a wrapper vehicle while the reference bond gives a direct claim against the original issuer. That difference needs explicit assessment even if both show the same economic price on the screen. Do not describe the two as legally identical based only on price tracking.

The review should name the document and clause supporting each conclusion. Keep open questions visible for the bank team rather than converting incomplete legal evidence into a yes/no badge in a platform dashboard.

Which operational changes challenge comparable risk?

Compare the control and failure paths introduced by tokenisation: privileged keys, upgradeability, custody recovery and settlement dependencies. An unchanged obligor does not eliminate those operating differences.

Review areaEvidence to requestPotential break
Administrative powersRole inventory and authorization recordAn agent can change a bank position
UpgradesImplementation versions and change approvalsAccepted behavior changes after purchase
Custody recoveryKey-loss and re-registration procedureThe bank cannot exercise its claim
Settlement and cashFinality map and cash-leg dependenciesOne leg completes while the other remains pending

Our suggested review asks the operator to walk through one failed settlement and one compromised-agent scenario. Which party can stop a transfer? Which can restore the record? Which evidence survives the incident? The answer should identify a person or legal entity, not only a contract function.

The ERC-3643 agent-key governance analysis provides a focused example of the powers that need this treatment.

How should bank reviewers treat network labels?

Use the network description to identify risks, then test those risks against the instrument. A permissioned or permissionless label does not itself settle legal enforceability or operational resilience.

Our proposed comparison uses the same questions for both: who controls admission, who can alter state, what determines finality, which external providers are required, and how a disputed transaction is handled. The evidence can differ, but the questions remain tied to the holder outcome.

For instance, a closed network can depend on one operator while a public-network wrapper can depend on one administrator key. Counting validators does not describe either concentration fully. Document dependencies at the service and legal-party levels.

Institutions using contract custody wallets also need a compatible signature and approval path. A capital review may accept the asset structure while an incomplete wallet integration still prevents the bank from subscribing or redeeming.

What changed in the Basel review timetable?

The Basel Committee said on October 1, 2026 that its targeted cryptoasset-standard review was advancing and that it expected an update by year end. A planned update is not an adopted revision.

The October 1, 2026 Basel Committee release expected an update on the targeted review by the end of the year.

Basel Committee, October 1, 2026 release

The October Basel Committee communication is later than the May release cited in the original article brief. Our November 22 source check did not establish a subsequent completed framework change. No new Basel risk weight is inferred here.

The PRA letter also keeps its own approach interim and points to a future consultation no earlier than 2028. A bank should therefore retain a policy version and review date with its decision, and reassess when binding rules or relevant supervisory expectations change.

What belongs in the issuer pack for a bank?

An issuer pack should connect legal equivalence to operating evidence and name unresolved differences. It should let the bank assess the specific holding under its own prudential obligations.

Our proposed pack has a rights matrix, contract-and-role inventory, custody and cash-flow diagrams, incident procedures, and sample reconciliation records. Attach implementation identifiers and the dates on which the evidence was checked. A generic white paper is insufficient for a deployment-specific assessment.

For the Digital Securities Sandbox example, preserve the instrument terms and the conditions relied on; participation is not a substitute for the comparability review. The bank remains responsible for its own assessment and any supervisory engagement.

For Blockmaze procurement, request verifiable control evidence and change records. This article makes no claim of PRA approval for Blockmaze or any tokenisation product. The practical goal is a reviewable file explaining which rights and risks match the conventional asset and where the bank must make a further judgment.

Frequently Asked Questions

Does permissioned DLT guarantee traditional capital treatment?

No. The PRA letter asks firms to focus on risk characteristics and outcomes rather than the ledger type. A permissioned network can still have different legal rights, settlement risks or administrative powers. A bank needs a documented assessment under the applicable prudential framework; the network label does not supply it.

Does the letter approve every tokenised government bond?

No. The letter discusses Digital Securities Sandbox issuances and the Digital Gilt Issuance Pilot under the same condition that underlying risks are comparable. That example does not determine every bank holding or every token wrapper. Review the specific instrument, rights and operating arrangement before drawing a capital conclusion.

What should an issuer give a bank risk team?

Our proposed pack includes the legal-rights comparison, custody and settlement map, privileged-role inventory, upgrade process, incident and recovery procedures, and reconciliation evidence. Each item should identify the deployed contracts and accountable legal parties. This is an operating proposal rather than a prescribed PRA submission template.

Is the May 2026 letter the final UK cryptoasset framework?

No. The PRA describes its approach as interim. It links a future framework to the Basel Committee targeted review, with consultation expected no earlier than 2028 in the letter. Firms should check later rules and supervisory communications when making a live decision, rather than treating the letter as permanent approval.

Ready to get started?

Join others who are already using our platform.