ESMA Tokenized Fund Valuation Technical Standards

ESMA’s Technical Framework for Tokenized Fund Valuation

The European Securities and Markets Authority (ESMA), as the EU’s securities markets supervisor, has been developing technical standards that address how tokenized fund products should be valued, priced, and reported. ESMA published its crypto-asset classification guidelines on March 19, 2025, establishing that crypto-assets can be classified as financial instruments under MiFID II across five categories: transferable securities, money-market instruments, units in collective investment undertakings, derivative contracts, and emission allowances. In October 2025, ESMA clarified DLT integrations, allowing hybrid models where tokenized bonds comply with both MiCA and MiFID II. With the MiCA regulation entering full enforcement in July 2026 and the DLT Pilot Regime operating since March 2023, ESMA’s technical standards are establishing the regulatory infrastructure for tokenized fund valuation across the European Union.

Valuation Framework Under Existing Fund Regulation

UCITS and AIFMD establish the baseline valuation framework that tokenized funds must satisfy. UCITS Article 85 requires that the value of fund assets be calculated and disclosed at each NAV calculation point, using fair value principles. AIFMD Article 19 requires AIFMs to establish appropriate and consistent procedures for proper and independent valuation of fund assets.

ESMA’s existing valuation guidance — particularly the ESMA Guidelines on valuation (ESMA/2014/937) — addresses fair value determination, valuation policy requirements, and the role of external valuers. For tokenized funds, these guidelines apply without modification to the underlying portfolio assets. The tokenization layer does not change how portfolio securities are valued; it changes how fund share prices are calculated and communicated.

The innovation lies in how on-chain systems can enhance valuation processes. Traditional NAV calculations rely on end-of-day price feeds from vendors, compiled by fund administrators, and verified by depositaries. On-chain NAV calculation systems can perform these functions continuously, using oracle networks that aggregate prices from multiple sources in real-time.

DLT Pilot Regime Valuation Specifications

The DLT Pilot Regime (Regulation (EU) 2022/858) permits DLT market infrastructures to request temporary exemptions from certain MiFID II and CSDR provisions, subject to compensatory measures. For tokenized fund shares traded on DLT trading systems, the Pilot Regime’s valuation specifications address:

Price formation: DLT trading systems must ensure that prices for tokenized securities — including fund shares — are formed through transparent, fair, and orderly processes. For fund shares that trade at or near NAV (such as money market funds), the DLT system must monitor deviations between market price and NAV and implement mechanisms to prevent trades at prices that would dilute existing shareholders.

Reference data: DLT systems must provide standardized reference data for tokenized securities, including ISIN codes, LEI identifiers, and classification codes. ESMA’s RTS on reference data for DLT securities (published September 2024) specifies how on-chain instruments should be identified within the EU’s Financial Instruments Reference Data System (FIRDS).

Transaction reporting: Tokenized fund transactions on DLT systems must be reported under MiFIR Article 26, using the same transaction reporting formats as traditional securities transactions. The technical challenge is extracting the required data fields — including client identifiers, execution timestamps, and price/quantity — from on-chain transaction records.

Oracle Standards and Data Integrity

ESMA has not yet issued formal standards for oracle networks used in tokenized fund valuation, but its ongoing consultation on crypto-asset price feeds (Consultation Paper ESMA75-453128700-949, published January 2026) addresses the reliability requirements for on-chain pricing data.

Key requirements emerging from the consultation include: oracle networks must aggregate prices from at least five independent sources; price feeds must include staleness detection (maximum update latency of 60 seconds for liquid assets, 300 seconds for less liquid assets); fallback mechanisms must activate automatically when primary oracle feeds fail; and oracle operators must be subject to governance arrangements that prevent conflicts of interest.

These requirements align with the operational standards of major oracle networks — Chainlink, Pyth, and RedStone — though formal ESMA endorsement of specific oracle providers is not anticipated. Instead, ESMA is expected to establish performance criteria that fund managers and their service providers must verify when selecting oracle solutions.

Reporting and Disclosure Requirements

ESMA’s technical standards for tokenized fund reporting build on existing UCITS and AIFMD reporting frameworks. The Annex IV reporting under AIFMD — which requires quarterly disclosure of portfolio composition, leverage, and risk metrics — must be adapted to capture on-chain data elements for tokenized fund operations.

For UCITS, the Key Information Document (KID) under the PRIIPs Regulation must accurately reflect the risk and cost characteristics of tokenized fund shares. ESMA’s guidance suggests that tokenized UCITS KIDs should disclose: blockchain-specific risks (smart contract, network, key management); additional costs associated with on-chain operations (gas fees, oracle costs); and any differences in investor rights compared to traditional share classes.

The comparison between EU and US disclosure requirements for tokenized funds reveals the EU’s more prescriptive approach to investor disclosure, driven by the PRIIPs and UCITS KIID frameworks.

Cross-Border Valuation Consistency

ESMA’s role as supervisor of national competent authorities creates an opportunity to establish consistent valuation standards across EU member states. The divergent national approaches to UCITS tokenization — with Luxembourg, Ireland, and France taking different positions — risk creating valuation inconsistencies that undermine the single market objective.

ESMA’s forthcoming technical standards (expected mid-2027) aim to harmonize national approaches to tokenized fund valuation, ensuring that a tokenized UCITS domiciled in Luxembourg and distributed in Germany uses the same valuation methodology as a fund domiciled in Ireland and distributed in France. This harmonization is critical for the cross-border distribution efficiency that makes UCITS the world’s most internationally distributed fund structure.

Smart Contract Valuation Controls

ESMA’s emerging technical standards address the role of smart contracts in automated fund valuation processes. For tokenized fund products where NAV calculation occurs on-chain, the following smart contract controls are expected to be required:

Access control architecture: Valuation smart contracts must implement role-based access controls that restrict: who can update price feeds (limited to authorized oracle addresses); who can trigger NAV calculation (limited to fund administration addresses); who can modify valuation parameters (limited to governance multi-signature wallets with time-lock delays); and who can pause valuation operations (limited to compliance and risk management functions).

Audit trail and transparency: On-chain valuation processes must produce a complete audit trail that depositaries and regulators can access. Every NAV calculation must record: the input prices used for each portfolio asset; the timestamp of each price feed; the calculation methodology applied; and the resulting per-share NAV. This audit trail must be retained for the regulatory minimum retention period (typically 5-10 years under UCITS and AIFMD record-keeping requirements).

Error handling and circuit breakers: Valuation smart contracts must include automated circuit breakers that halt NAV calculation when anomalous conditions are detected — such as price deviations exceeding configurable thresholds, oracle feed failures affecting more than a specified percentage of portfolio assets, or blockchain network congestion exceeding defined parameters. When circuit breakers activate, the fund must fall back to off-chain NAV calculation procedures supervised by the fund administrator.

The smart contract audit guide provides detailed standards for auditing valuation smart contracts, and the on-chain fund administration architecture analysis examines how valuation systems integrate with broader fund operational infrastructure.

Depositary Valuation Oversight in DLT Environments

Under UCITS Article 22, the depositary is responsible for verifying the fund’s NAV calculation. For tokenized fund products with on-chain NAV calculation, this oversight function requires adaptation:

Real-time verification capability: Depositaries must have technical access to the blockchain network on which NAV calculation occurs. This requires either operating a full node on the relevant blockchain or maintaining API access to reliable blockchain data providers. The depositary must be able to independently verify that the on-chain NAV matches the fund’s stated NAV.

Reconciliation frequency: ESMA’s draft standards suggest that depositary reconciliation of on-chain and off-chain NAV calculations should occur at least daily for UCITS funds and at each NAV calculation point for AIFs. This reconciliation must identify and report any discrepancies exceeding a de minimis threshold (suggested at 0.01% of NAV).

Escalation procedures: When the depositary identifies a discrepancy between on-chain and off-chain NAV calculations, the depositary must: notify the fund manager within one business day; escalate to the national competent authority if the discrepancy is not resolved within three business days; and take protective action (which may include suspending tokenized share dealing) if the discrepancy exceeds a material threshold.

The US-EU custody comparison examines how the EU depositary’s active oversight function differs from the US qualified custodian’s more passive safekeeping role, with implications for valuation governance across jurisdictions.

DORA Integration with Valuation Infrastructure

ESMA’s valuation technical standards are being developed in coordination with the Digital Operational Resilience Act (DORA) requirements that became applicable in January 2025. For tokenized fund products relying on on-chain NAV calculation, DORA imposes operational resilience obligations that directly affect valuation infrastructure:

ICT risk management for oracle networks: Fund managers using oracle price feeds for NAV calculation must classify oracle service providers as critical ICT third-party service providers under DORA Article 28. This classification triggers enhanced due diligence, contractual requirements, and concentration risk monitoring. Fund managers cannot rely on a single oracle provider for all pricing data — DORA’s concentration risk provisions require diversification across oracle providers or a combination of oracle and traditional pricing vendor sources.

Incident reporting for valuation disruptions: DORA’s incident reporting framework requires fund managers to report major ICT-related incidents to their national competent authority. For on-chain NAV calculation, reportable incidents include: oracle network outages affecting price feed availability; smart contract failures disrupting NAV computation; and blockchain network congestion preventing timely NAV publication. Fund managers must establish classification criteria that distinguish routine operational fluctuations from reportable incidents.

Resilience testing: DORA requires financial entities to conduct regular digital operational resilience testing, including advanced testing through threat-led penetration testing (TLPT) for systemically important entities. Fund management companies operating on-chain valuation systems must include their blockchain infrastructure — smart contracts, oracle integrations, and node infrastructure — within the scope of resilience testing programs.

Impact on European ETF Valuation Practices

ESMA’s tokenized fund valuation standards will affect the EUR 2.1 trillion European ETF market in several ways:

Indicative NAV (iNAV) enhancement: European ETFs currently disseminate indicative NAV (iNAV) values at 15-second intervals during trading hours. On-chain NAV calculation could enhance iNAV accuracy by using real-time oracle price feeds rather than delayed exchange data, reducing the arbitrage opportunity that authorized participants capture through informational advantages.

Multi-currency NAV: European ETFs frequently trade in multiple currencies across multiple exchanges (for example, a Luxembourg-domiciled ETF trading in euros on Euronext and in British pounds on the London Stock Exchange). On-chain NAV calculation could provide synchronized multi-currency NAV values, reducing cross-listing arbitrage and improving price discovery for investors.

After-hours NAV: Traditional fund NAV is calculated once daily, typically at market close. On-chain NAV calculation could provide continuous NAV updates, enabling tokenized ETF trading outside traditional market hours with accurate pricing — particularly valuable for ETFs tracking global indices that span multiple time zones.

Fair Value Hierarchy for Tokenized Portfolio Assets

ESMA’s valuation standards must address how tokenized portfolio assets — bonds, equities, and structured products issued as DLT-based securities — fit within the IFRS 13 fair value hierarchy used for fund financial reporting. Tokenized securities that trade on regulated DLT venues (such as SIX Digital Exchange or DLT Pilot Regime-authorized platforms) may qualify as Level 1 assets (quoted prices in active markets) if the trading venue provides sufficient liquidity and price transparency. Tokenized securities with limited secondary market trading — including many private fund tokenizations — would be classified as Level 2 (observable inputs) or Level 3 (unobservable inputs), requiring model-based valuation with appropriate disclosure.

The interaction between oracle-based pricing (used for on-chain NAV calculation) and the fair value hierarchy (used for financial reporting) creates potential valuation methodology inconsistencies. Fund administrators must ensure that the oracle prices used for daily NAV calculation are consistent with the fair value measurements used for periodic financial reporting, reconciling any differences and documenting the valuation approach for depositary oversight and external audit review.

The Luxembourg CSSF framework and Ireland Central Bank position are both developing national guidance that incorporates ESMA’s valuation standards. The institutional investor guide examines how ESMA’s valuation standards affect institutional due diligence for tokenized fund allocations. ESMA publishes technical standards at esma.europa.eu.

For inquiries regarding this analysis: info@etftokenisation.com