Digital asset platforms are reaching an inflection point.
Tokenized deposits, regulated stablecoins, central bank digital currencies, and on‑chain securities are no longer experimental, rather they are becoming core market infrastructure. As these systems mature, the central question shifts from whether distributed ledger technology can support digital assets, to how it must evolve to scale entire ecosystems: across participants, across networks, across developer communities, and across decades of security requirements.
Hyperledger Fabric‑X (in short, Fabric-X) represents a major step in that direction.
Fabric-X is an implementation of Hyperledger Fabric that offers architectural optimizations targeting (regulated, interoperable) digital asset systems while preserving the permissioned governance, privacy controls, and deterministic execution model that enterprises require.
In this post, we will discuss how scaling a digital asset ecosystem requires progress along four orthogonal dimensions — scalability enablement of a single ledger, privacy enablement of applications leveraging DLTs, seamless interoperability (with the rest of the world), application portability — and show how Fabric‑X directly address each of them. Special emphasis is put on freshly announced news of Fabric-X support for EVM smart contract, and oracle integration.
The most immediate and visible scaling challenge for digital assets is ledger performance.
Hyperledger Fabric deployments already outperform public blockchains for many enterprise workloads. However, large‑scale payment systems, settlement rails, and tokenized markets demand predictable finality, low latency, and throughput of tens of thousands of transactions per second — orders of magnitude beyond what traditional permissioned blockchains were originally designed to sustain.
Fabric‑X addresses this through the adoption of pre-order execution model and the introduction of a high degree of parallelism at all stages of transaction processing.
Figure 1 shows the different phases of transaction processing in Fabric-X. Pre-order execution positions smart contract execution (typically the heaviest, and more unpredictable part in a DLT system) outside of the critical path ( i.e., before actual consensus takes place) and by a set of nodes that are trusted to execute the smart contract correctly (aka endorsers). Once a transaction invoking the smart contract is executed by the smart contract’s endorsers, the signed execution results are submitted to the Consensus layer that produces a totally ordered set of signed execution results, handed over to the Committers of the system. Committers then check endorser signatures and resolve state dependencies to decide deterministically, and consistently which transactions will impact the ledger’s state and in what way.
Clearly the smart contract execution phase can scale horizontally, without any clear bound on the actual computation load itself. The other two phases of Fabric-X served by the orderers/consensus nodes, and committers of the system have been architected in a way to allow for horizontal scalability up to the levels for 200K TPS. In fact:
Crucially, this performance is achieved by design, without sacrificing security, determinism, governance, or auditability — properties that are non‑negotiable in regulated environments.
Figure 1. Overview of Fabric-X transaction processing stages, including smart contract execution, executed transaction ordering (consensus), and transaction validation/state commit phase.
_____________________________________________________________________________________________________________________________________________
See the recent publication in SIGMOD Conference 2026 for a detailed architecture description of Fabric-X, and comprehensive performance evaluation.
_____________________________________________________________________________________________________________________________________________
Scaling participation is another important dimension of success of digital asset systems, as it sits at the heart of all cost/time-efficiency and transparency benefits of digital assets and DLT paradigms. As digital asset networks grow, they inevitably include more organizations, more jurisdictions, but also more applications and more heterogeneous trust relationships.
In permissioned systems, scaling participation raises a second, orthogonal challenge: privacy. In regulated digital asset systems, privacy is foundational, not optional. Participants must protect transactional data, asset positions, counterparty relationships, and compliance‑sensitive information, all while operating in multi‑organization, multi‑jurisdictional networks.
At the same time, it is essential that privacy does not come at the cost of functionality or compliance, while it must scale in time.
Fabric-X was designed from the outset as a privacy‑compatible, identity‑centric system, making it fundamentally suitable for regulated digital assets. But let’s see how the two come together.
Fabric‑X builds on top of Hyperledger Fabric’s permissioned nature, with strong identity management, governance and access control models, for all entities involved in transaction processing (execution, ordering and validation/commit phases).
Flexibility in the choice of privacy‑enhancing mechanisms is therefore essential. Depending on the use case, applicable jurisdiction, and the performance–transparency trade‑offs involved, an application/smart contract developer may resort to very different privacy technologies. In some scenarios, privacy may be achieved through trusted compute infrastructure, while in others it may rely on advanced cryptographic techniques such as zero‑knowledge proofs or secure multi‑party computation, which can require additional cross‑component interactions or integration with legacy systems.
Figure 2. Overview of a possible Fabric-X deployment scenario, where different combinations of parties operate different smart contracts, each with their own rules, crypto layers or underlying hardware infrastructure.
Fabric-X provides strong sovereignty in smart contract governance and execution (as shown in Figure 2 ) enabling the integration of a range of privacy‑enhancing technologies across the smart contract lifecycle. It is coupled with the Fabric Token SDK, a performance‑optimized tokenization framework implemented using traditional programming languages, that supports multiple levels of transactional privacy in enterprise environments, while enforcing audit‑compliant processing at every stage. Fabric Token SDK has already been adopted by multiple central banks worldwide and includes support for self‑sovereign identity.
A less visible — but increasingly critical — aspect of privacy is cryptographic longevity. The emergence of quantum computing changes the threat model for public‑key cryptography, introducing “harvest‑now, decrypt‑later” risks for systems that are meant to store value and records for decades.
This is why quantum readiness is already supported by Fabric-X privacy frameworks. On one hand, Fabric‑X builds on Fabric’s identity‑centric and crypto‑agile foundations, making it possible to evolve cryptographic primitives over time without redesigning the platform. On the other hand, and equally crucially, Fabric tokenization artifacts (e.g., Fabric Token SDK) extend their privacy and soundness properties post quantum, ensuring assets introduced today, are not threatened by quantum computers in the future. Finally, quantum‑safe cryptographic algorithms transition for digital signatures is explicitly on the Fabric-X roadmap, and active research is ongoing to explore optimal hybrid and post‑quantum signature models for Fabric‑based systems.
____________________________________________________________________________________________________________________________________________
You can find more information about Fabric Token SDK in the associated scientific publication and LFDT Labs repository. _____________________________________________________________________________________________________________________________________________
No digital asset ecosystem can function in isolation. While this is broadly true of distributed systems, it is especially critical for digital asset platforms, where value is only unlocked through transparency and real-time, atomic interoperability across systems.
In practice, banks, financial market infrastructures, custodians, and service providers will operate across multiple platforms built on different technologies, governance models, and regulatory regimes. Assets and currencies must be able to move—or be referenced—across these platforms, often under strict atomicity constraints such as delivery versus payment (DvP) or payment versus payment (PvP). As a result, digital asset platforms must be designed as components of a wider system of systems, not as isolated silos.
Fabric-X addresses this requirement through native support for interoperability and cross-system coordination. It enables smart contracts to incorporate oracle interactions directly within their execution, allowing onchain logic to depend safely on external data and systems. This is made possible by the combination of Fabric-X’s preorder execution model and its flexible programming model. This results in an enhanced version of possible Fabric-X deployment scenarios as shown in Figure 3.
Figure 3. Fabric-X deployment scenario that includes connection with external DLT systems. Interoperation is accomplished either by having the smart contract endorsers being part of these systems, or through them connecting to appropriate (centralized or decentralized) oracle services.
The preorder execution model permits smart contracts to make nondeterministic calls to external systems during endorsement, while Fabric-X’s programming model enables contracts to explicitly encode workflows that span organizations, platforms, and external services. Domain experts can express these workflows in familiar financial terms, which are then implemented as smart contracts that align naturally with existing processes and controls.
Fabric Smart Client and Endorser SDKs are key enablers in this direction, allowing Fabric-X application components (endorsers) to interact with external systems—such as other DLTs, legacy infrastructures, or oracle networks—during transaction execution. This positions Fabric-X as an enabler of seamless, secure coordination across platforms.
This approach contrasts sharply with post-order execution DLTs, which prohibit smart contracts from calling external systems and require developers to strictly separate onchain and offchain logic. Such separation adds complexity and friction to cross-platform workflows, particularly where atomicity and coordination are essential.
By design, Fabric-X is well suited for building integrated oracle solutions that allow endorsers to query, authenticate, and act upon external data in a modular and secure manner. These capabilities form the foundation for advanced cross platform use cases, including secure asset transfers, atomic exchanges, and complex multisystem financial workflows.
Ecosystem scale is ultimately also developer scale.
Digital asset platforms are no longer isolated deployments built for a single application or institution. They increasingly serve as shared foundations for entire ecosystems—spanning markets, jurisdictions, networks, and long-lived applications. In that setting, the ability to leverage the outcomes of the wider development community---across enterprises, startups and open-source communities, reuse existing applications, and maintain compatibility over time is as important as raw ledger performance.
To this end, Fabric-X comes equipped with two architectural properties.
First, Fabric-X has a flexible programming and execution model. Smart contract execution is cleanly separated from consensus and ordering, allowing execution environments to evolve independently from the core ledger machinery. This decoupling makes it possible to introduce new execution models, runtimes, and tooling without destabilizing the underlying system.
Second, Fabric-X is intentionally non-prescriptive about how transactions are assembled. Its execute-order-validate architecture does not mandate a single way of structuring application logic or state transitions. Instead, it allows different programming paradigms—traditional programming languages, domain-specific logic, or virtual-machine based smart contracts—to coexist, as long as they produce deterministic read-write sets.
Together, these properties create architectural "headroom": the ability to integrate new developer ecosystems and execution environments without compromising governance, determinism, or performance.
As proof of this fact, Fabric-X’s roadmap has been enhanced with support for Solidity based smart contracts, with early versions of this feature already in place.
Traditional programming environments benefit from several important advantages. They offer access to hardened, production-grade cryptographic libraries, as well as decades of compiler, runtime, and hardware optimizations that are difficult to replicate in emerging decentralized application (DApp) ecosystems. Moreover, when applications follow a preorder or offchain execution model, there is no intrinsic requirement for deterministic execution across multiple nodes. This removes many of the constraints typically imposed on smart contract development, such as restricted language features, limited libraries, and performance tradeoffs.
By contrast, the Ethereum ecosystem has cultivated a massive, global developer community and a highly mature application development stack. This includes the Solidity programming language, comprehensive testing and debugging frameworks, standardized auditing workflows, and a large body of well-understood smart contract design patterns—particularly for digital assets and onchain financial primitives. In addition, the widespread adoption of the Ethereum Virtual Machine (EVM) across many public blockchains further reinforces this ecosystem advantage. As a result, a large majority of DApp developers are already familiar with Solidity and EVM-compatible tooling, making Ethereum-based development paradigms a natural default despite their inherent execution and determinism constraints.
Enabling Fabric-X to bring the two worlds together offers strong benefits from ecosystem building standpoint. That is, by combining:
institutional developers can innovate faster (i.e., by leveraging different ecosystems’ optimizations, as needed) and sustainably (i.e., without abandoning the operational and compliance properties enterprises require along the way). The resulting capability is illustrated in Figure 4.
Fabric-X (but also Fabric) is extended with two core capabilities:
These capabilities are realized through a new component called fabric-x-evm. At a high level, fabric-x-evm introduces an Ethereum execution environment that is tightly integrated with Fabric-X's transaction flow, without altering Fabric's core architecture. Conceptually, the system consists of:
Seen as a whole, fabric-x-evm acts as a bridge between execution semantics, letting Ethereum contracts live naturally inside a Fabric-X network —without weakening either side's guarantees.
We believe that platforms that scale fastest are those that allow developers to innovate with speed. Clearly, enabling developers to leverage the best of multiple worlds in their applications is a key step in this direction: they can then build on what others have built/hardened over the years. At the same time, EVM-extensions of Fabric-X, allow institutional innovators to continue to innovate in an ecosystem compatible way, while grounding this innovation in Fabric‑X’s accountable, governance-centric, yet highly scalable and interoperable execution model.
____________________________________________________________________________________________________________________________________________
You can find more information about the EVM compatibility layer of Fabric-X here!
___________________________________________________________________________________________________________________________________________
Scaling digital assets is not a single‑axis problem.
It requires platforms that:
Fabric‑X is compelling because it addresses all four dimensions together, while remaining firmly rooted in Hyperledger Fabric’s permissioned, enterprise‑grade philosophy.
With the recent addition of EVM compatibility, Fabric‑X also opens the door to a much broader innovation — allowing regulated digital asset platforms to evolve with the global smart‑contract ecosystem, rather than alongside it.
The next phase of digital assets will be defined not by isolated networks, but by interconnected, developer‑driven ecosystems. Fabric‑X is a clear accelerator in this direction.
How to get involved
We welcome everyone who is interested in Fabric-X to join the community and help us with our plans for the year. You are welcome to join any of the upcoming Fabric community calls and also join the discussions on the Fabric channels on LFDT’s Discord.
AI Disclosure: This post used artificial intelligence tools for research, structural assistance, graphic creation, or grammatical refinement. The final content was reviewed, edited, and validated by human contributors to LF Decentralized Trust to ensure accuracy and alignment with our community standards. We remain committed to transparency in the use of generative technologies within the open source ecosystem.