Real World Asset Tokenization: The Billions Nobody Protects Enough

A market growing faster than its defenses

In three years, the real-world asset (RWA) tokenization market has grown from about $5.5 billion to over $25 billion — a growth exceeding 300%. In 2025 alone, tokenized US Treasuries surpassed $8 billion, while commodities and private credit continued to expand rapidly.

BCG and Ripple projections indicate a potential of $18.9 trillion by 2033.

This growth attracts institutional capital — but also targeted attacks. In the first half of 2025, exploits on RWA protocols caused losses of approximately $14.6 million — more than double the entirety of 2024.

The figure remains modest compared to the roughly $2.4–2.5 billion stolen across the broader crypto space in the same period, but the growth trajectory of RWA attacks is significant.

Anatomy of attacks: not the DeFi we knew

Attacks on RWA protocols diverge from typical DeFi patterns. Flash loans and pool manipulations don't dominate — instead, hybrid vulnerabilities between technical infrastructure and operational processes prevail.

Compromised keys and weak governance

In March 2025, Zoth lost approximately $8.4 million: a compromised private key enabled the malicious upgrade of a smart contract lacking multisig and timelock.

Unauthorized permissions and minting

The Curio case shows the same pattern: approximately $16 million stolen through illegitimate token creation. The event, however, dates back to March 2024, not 2025.

Misconfigured oracles

In April 2025, Loopscale lost approximately $5.8 million through manipulation of a low-liquidity pair used as a price reference. Other minor incidents stemmed from basic errors in exchange rate management.

The pattern is structural: the most critical vulnerabilities emerge at the interface between on-chain and off-chain, not in the code itself.

The five-layer model: security beyond code

According to CertiK, RWA protocol security is distributed across five layers:

1. Physical asset custody
2. Legal framework
3. Operational processes
4. Oracle infrastructure
5. Smart contracts

Audits predominantly focus on the last layer. Recent exploits demonstrate that the first four are often more decisive.

An insolvent custodian or a compromised operational process renders code security irrelevant.

The architectural question: where compliance lives

A central decision concerns where compliance logic resides.

The ERC-3643 standard integrates requirements directly into the token through decentralized identities (ONCHAINID): only verified subjects can hold or transfer assets.

Other approaches delegate compliance to external contracts or network layers.

The choice is structural and hardly reversible.

MiCA: the European regulator raises the bar

MiCA introduces a paradigm shift: security requirements transformed into regulatory obligations.

Timelines

• June 30, 2024: Titles III and IV (ART and EMT)
• December 30, 2024: full application, including CASPs (Title V)
• Art. 143(3) — transitional regime: existing CASPs may continue operations until July 1, 2026 at the latest; in Italy, following DL 95/2025, the application deadline is December 30, 2025

For RWA issuers

• fully collateralized and segregated reserves
• independent audits (variable frequency, often at least semi-annual for significant assets)
• stringent governance and disclosure requirements

Compliance costs remain high and depend on jurisdiction and operational complexity; estimates in the hundreds of thousands of euros are neither uniform nor regulatory.

Real effect: security becomes a legal requirement, no longer just a best practice.

The giants move: convergence or capture?

Institutional entry confirms that tokenization is taken seriously. But it's worth distinguishing between those adopting the technology and those seeking to absorb it.

• BlackRock's BUIDL fund has surpassed $2 billion and is used as collateral
• JP Morgan launched a tokenized money-market fund on Ethereum
• Kinexys enables real-time cross-border settlements

The BIS, for its part, has formalized the concept of a unified ledger, proposing an architecture that integrates:

• tokenized central bank reserves
• tokenized commercial deposits
• tokenized government securities

All under central bank control. This move is worth reading with critical distance: the BIS presents itself as an innovator, but its model brings the entire infrastructure back within the perimeter of the institutions it represents. Atomic settlement and operational efficiency are real — tokenized bonds show significantly tighter bid-ask spreads — but the direction is clear: capture the benefits of tokenization while neutralizing decentralization.

Projects like Agorá test this architecture with central banks and private institutions. The data is useful; the conclusions should be weighed carefully.

What this means for decision-makers today

• • Security is systemic, not just technical
• • Key management remains the most fragile point
• • Compliance must be designed, not bolted on
• • Architectural choices are irreversible in the medium term
• • The main risk lies in the integration between traditional finance and blockchain infrastructure

There's also a less technical but equally real risk: that tokenization gets adopted stripped of its foundational principles — transparency, decentralization, user sovereignty. Efficiency without openness is just a faster database.

The RWA market is growing faster than its defenses. The competitive advantage isn't in adoption, but in the ability to build open infrastructures that don't collapse under stress.