Cosmos vs. Hyperledger Besu

Selecting the right digital ledger technology platform is a key decision point in institutional DLT projects because the chosen infrastructure has to satisfy engineering, operational, and regulatory requirements at the same time. Two popular choices are Hyperledger Besu and Cosmos. Hyperledger Besu is an Ethereum client built to run as a public Ethereum node or as a permissioned enterprise network. Cosmos provides a customizable stack for building independent digital ledgers that interoperate natively across networks.

This article compares the two across architecture, performance, compliance posture, and production history to help you assess which platform aligns with your use case.

Cosmos and Hyperledger Besu at a glance

Hyperledger Besu and Cosmos are enterprise blockchain platforms with distinct design principles.

Hyperledger Besu is an Ethereum client written in Java, designed to support both public Ethereum networks and permissioned enterprise deployments. It implements the Ethereum specification and runs Solidity smart contracts, with several consensus algorithms available for permissioned use. Because Besu inherits Ethereum's account model, EVM execution layer, and gas-based fee structure, it integrates cleanly with the wider Ethereum tooling ecosystem.

Cosmos, on the other hand, is a full-stack technology framework for building sovereign digital ledgers. It lets teams design every layer of their ledger, from consensus to fee models to security, around their own requirements. Networks built on it can communicate and interoperate with a vast ecosystem of ledgers, including other Cosmos chains, EVM-compatible chains, Hyperledger Besu, and Solana, through the Inter-Blockchain Communication (IBC) protocol, which ships natively with the stack, and they can be deployed in private, consortium, public, or public-permissioned configurations, depending on what the business requires.

The two frameworks also differ on their level of customizability and their approach to interoperability. Besu is based on the Ethereum specification, which gives it immediate compatibility with established Ethereum tooling and the EVM execution model, an account-based ledger structure, and a gas-based fee system with it. To interoperate beyond its own network, a Besu deployment generally relies on third-party bridges or external services. Cosmos provides built-in interoperability, allowing connections to any blockchain or external system that supports signing, and the Cosmos SDK delivers a high level of flexibility. It allows teams to define their network structure, consensus parameters, fee models, features, and governance policies. It also allows you to run a full EVM to access the Ethereum blockchain, tooling, and applications.

What is Hyperledger Besu

Hyperledger Besu is an Ethereum client hosted by LF Decentralized Trust, the umbrella organization that now houses what was formerly the Hyperledger project family. Originally developed by Consensys and donated to Hyperledger in 2019, Besu is written in Java and implements the full Ethereum specification, which means it can run as a node on public Ethereum networks or be deployed as a permissioned enterprise network where every participant is a known entity.

Ethereum compatibility and EVM-based architecture

Besu's most defining property is its tight alignment with the Ethereum ecosystem. It runs the Ethereum Virtual Machine, supports Solidity smart contracts, and exposes the standard JSON-RPC interface, which gives enterprise teams direct access to the same tooling, wallets, and developer libraries the wider Ethereum community uses. Existing Ethereum applications can typically be redeployed onto a Besu network with some modification.

Consensus options for permissioned networks

Besu ships with several consensus algorithms intended for permissioned use. The most common are IBFT 2.0 and QBFT, both Byzantine fault-tolerant protocols designed for known validator sets, and Clique, a proof-of-authority algorithm for simpler deployments where a small set of authorized signers takes turns producing blocks. Each option offers a different balance of finality guarantees, throughput, and operational complexity, and the choice has direct implications for how the network handles validator faults and recovery.

Privacy and permissioning

Hyperledger Besu's approach to privacy is execution-layer focused: rather than embedding privacy logic natively into the node, Besu exposes its EVM implementation as a reusable runtime that higher-level privacy frameworks can consume. Paladin, an application-layer privacy framework that handles off-chain coordination, including proof generation, endorsement workflows, and private state management, uses Besu's EVM as the execution engine for its Pente privacy group component. Besu handles deterministic EVM execution while Paladin owns the privacy coordination layer above it. Besu therefore functions as a stateless, embeddable execution engine within a broader privacy stack, rather than as a self-contained privacy solution.

What is Cosmos

Cosmos is a technology stack for building digital ledger solutions with native interoperability. It's a strong fit for organizations that need their infrastructure to interoperate with other systems and connect to a wider set of ledgers and blockchains, while keeping a high degree of operational and regulatory control over the network itself. The stack supports both public deployments and private enterprise configurations, covering consortia, multi-party public and private networks, and setups operated by a small set of administrators.

Modular architecture and flexible SDK

The Cosmos SDK is a modular framework that enables teams to build custom blockchains tailored to a specific business use case. Each network operates independently and defines its own security guarantees, operator structure, privacy parameters, and interoperability scope. That independence is what makes the stack practical for institutions that need a ledger configured specifically to their own compliance and security requirements.

Consensus mechanism: CometBFT consensus engine

The Cosmos stack uses CometBFT, a Byzantine fault-tolerant consensus engine that delivers immediate finality. Once a block is committed by the validator set, it is final, and no reorganization or rollback occurs under normal operating conditions. This matters for settlement workflows, where downstream processes can begin as soon as the block is final. CometBFT-based ledgers reliably reach 2,000+ transactions per second in production conditions, and have been optimized to clear 10,000+ TPS under load, as demonstrated by Crypto.com's Cronos chain.

Interoperability: Inter-Blockchain Communication Protocol

IBC is the interoperability framework that lets digital ledgers connect directly to exchange messages and assets through peer-to-peer connections. The protocol currently connects more than 150 production ledgers.

Differences in modularity and consensus between Hyperledger Besu and Cosmos

The underlying architectural question is how each platform handles transaction processing, smart contract execution, and finality. The answers shape everything from settlement guarantees to how the network is integrated with existing systems.

Modularity and customization approaches

Both platforms expose customization surfaces to the teams that deploy them, but the surfaces work differently:

• Besu: A plugin API lets developers extend node behavior with custom data exporters, telemetry, and transaction validation logic, and the network operator can choose between consensus algorithms (IBFT 2.0, QBFT, Clique) at network creation. The underlying architecture itself is fixed to the Ethereum specification.
• Cosmos: The Cosmos SDK ships with a set of base modules for common digital ledger functions, including token issuance, and teams can add plug-and-play modules to fit a specific use case. Consensus parameters, fee models, account models, and module composition are all configurable from the ground up.

Smart contract execution

Besu runs the Ethereum Virtual Machine natively and executes Solidity and Vyper smart contracts in-process. This gives Besu deployments direct compatibility with the Ethereum tooling ecosystem, including wallets, libraries, developer frameworks, and the JSON-RPC interface. The execution model is the one defined by the Ethereum specification, which means smart contracts inherit Ethereum's account model and gas-based fee mechanics.

Cosmos takes a different starting point. Cosmos SDK modules are written in Go and compile directly into the chain binary, which gives teams native module-level control over transaction handling, state, and business logic. For teams that need Ethereum compatibility specifically, Cosmos EVM provides a full EVM implementation on top of the SDK, enabling Solidity support and allowing the same chain to run both Cosmos-native modules and Ethereum-compatible smart contracts in the same network. This full EVM integration includes support for custom precompiled contracts (precompiles) that expose module-specific functionality, allowing for custom configurable logic and seamless interaction between EVM contracts and native Cosmos modules.

Hyperledger Besu versus Cosmos performance comparison

Performance numbers for both Cosmos and Besu vary significantly based on consensus algorithm, network topology, and transaction complexity. The following sections compare throughput, finality, and cost structure under representative production configurations.

Throughput under production conditions

Cosmos-based digital ledgers demonstrate stable 2,000+ transactions per second (TPS) in standard configurations. Ledgers that optimize their configurations can achieve 10,000+ TPS in production, as demonstrated on Crypto.com's Cronos chain.

Besu's throughput depends on which consensus algorithm is in use. Permissioned deployments running QBFT or IBFT 2.0 typically operate in the high hundreds to low thousands of TPS range in optimized configurations, with public benchmarks varying widely by hardware and network setup. Operators running Besu in permissioned mode generally have to balance finality time, validator count, and block size to land on the throughput they need.

Cosmos Performance Metrics

Cosmos stack release family R2026.1

• Year: 2026
• TPS: 2,000 (sustained)
• Conditions: 5-validator, 32-CPU network using Cosmos ledger release family 2026.1

Cronos Proof of Stake

• Year: 2025
• TPS: 10,000 (peak, not sustained)
• Conditions: 100 validator network

Hyperledger Besu Performance Metrics

LF Decentralized Trust QBFT wiki

• Year: 2024
• TPS: 645–1,200
• Conditions: Up to 2 validators, Caliper "open" test

ConsenSys Besu benchmark suite

• Year: 2024
• TPS: 200–800
• Conditions: QBFT, contract-complexity dependent; 2–4s latency

Note: This chart presents performance after the Ethereum merge in September 2022.

Transaction finality time and settlement speed

CometBFT's immediate finality means Cosmos chains confirm transactions in under a second. Settlement workflows that depend on certainty at the moment of execution can proceed immediately.

Besu's finality model depends on the consensus algorithm chosen. QBFT and IBFT 2.0 deliver single-block finality similar to Cosmos, while Clique (proof-of-authority) requires confirmation depth and offers probabilistic finality. In practice, this means a Besu deployment's finality characteristics are set at network creation and locked in for the life of the network unless the operator migrates to a different consensus algorithm.

Transaction cost structures

Neither platform charges protocol-level transaction fees the way public Ethereum does, but the fee-model architecture differs in ways that matter operationally. Cosmos chains can be configured with a wide range of fee models, including zero fees, custom fee tokens, sponsored transactions, and revenue-generating fee structures for payment networks. Besu inherits Ethereum's gas-based fee mechanics, and while gas prices can be set to zero in a permissioned deployment, gas accounting itself stays in place and block gas limits still apply. Custom fee tokens and non-gas-based fee structures require working around the EVM's gas accounting, which adds engineering effort and operational complexity.

Interoperability and cross-chain connectivity

Enterprise blockchain deployments connect to other ledgers, existing financial systems, or external networks at some point in their lifecycle. Cosmos and Besu take different approaches to that requirement, with implications for time-to-integration, vendor footprint, and operational dependencies.

Hyperledger Besu and cross-network patterns

Besu does provide a native interoperability framework. A Besu network can communicate with other networks through third-party interoperability protocols such as Chainlink CCIP, LayerZero, or Wormhole. Each of these introduces additional counterparty risk, vendor dependencies, and trust assumptions. For institutions evaluating cross-network requirements at procurement time, this is a material difference between the platforms.

IBC Protocol for multi-ledger communication

The Inter-Blockchain Communication Protocol is the native interoperability framework for Cosmos-based ledgers. It allows networks to communicate point-to-point through self-hosted infrastructure. The protocol supports arbitrary message passing in addition to standard asset transfers, which makes it possible to build cross-ledger contract calls, coordinated workflows, and conditional settlement patterns across independent networks, allowing for the creation of complex cross-system and cross-ledger workflows. Ledgers that use IBC retain their cybersecurity profiles. IBC allows ledgers to connect to other ledgers, external systems that support signing, such as servers, and external rails, such as payment rails.

Integration with existing financial infrastructure

Cosmos's IBC has been extended to connect with Ethereum, Ethereum Layer 2s, Solana, and other blockchains, and can also be used to connect to any non-blockchain system that supports signing. Besu integrations with existing financial infrastructure typically rely on the Ethereum tooling ecosystem (Web3 libraries, standard JSON-RPC interfaces, custom middleware) along with the services described above for any cross-network connectivity needs.

Compliance and access control for permissioned deployments

Compliance is often the primary gating factor for institutional blockchain adoption. Both Cosmos and Besu support permissioned configurations, with different mechanisms for managing identity, access, and data privacy.

Participant permissioning and identity management

• Besu: Permissioning can be configured at both the node and account level, with rules expressed either through local configuration files or through on-chain smart contracts. The choice between these approaches affects how dynamic the permission set is and where the source of truth for participant identity lives. Besu does not ship a dedicated identity management layer of its own, so identity controls typically integrate with external systems the institution already runs.
• Cosmos: Administrative permissioning controls allow system operators to select network validators and participants, with the rules expressed through SDK modules that the operator configures. The model is customizable to the institution's specific compliance, security, and operational requirements, and can be extended to integrate with existing KYC and identity providers.

Data privacy and residency controls

Hyperledger Besu's approach to data residency and enterprise privacy controls has shifted to an app-layer model, with privacy logic handled by frameworks like Paladin rather than natively within the node. For enterprise access controls, Besu retains node-level and account-level permissioning. Cosmos handles privacy primarily at the application layer through encrypted payloads (store ciphertext on-chain with off-chain key management) and zero-knowledge proof integrations that allow verification of state changes without revealing underlying data.

Regulatory alignment considerations

KYC, AML, sanctions screening, and other regulatory controls require deliberate setup on both platforms. Both have been deployed in regulated environments, and the implementation work for compliance integration is driven primarily by the institution's existing systems and the regulator's specific requirements, with the platform choice being a smaller factor.

Production track record and institutional adoption

Both frameworks have substantive production footprints, with different ecosystem profiles.

Hyperledger Besu enterprise implementations

Besu has been deployed in production across CBDC programs and capital markets initiatives. Nigeria's eNaira, the first African CBDC, launched on Besu in October 2021 and continues to process retail payments. The mBridge cross-border CBDC project, which connects central banks in Hong Kong, Thailand, China, and the UAE, is built on Besu. Bank Indonesia has tested Besu as one of the underlying platforms for its Digital Rupiah program.

The Hyperledger Besu Financial Services Working Group, launched in March 2024, brings together institutional members including DTCC (which chairs the group), Citi, Banco Central do Brasil, Santander, Visa, Mastercard, Japan Securities Clearing Corporation, Accenture, and ConsenSys to coordinate Besu adoption across financial services use cases.

Cosmos ecosystem deployments

The Cosmos stack powers more than 150 production blockchains, including networks handling significant transaction volumes and asset values. Financial services implementations include cross-border payment infrastructure, stablecoin platforms, and tokenization networks. Named adopters include Progmat/Datachain for cross-border payments, Ondo Chain for tokenization, and Figure for HELOC lending.

Support ecosystem and developer resources

Building and maintaining production systems takes more than the core platform itself. Tooling, talent availability, and support options matter for long-term viability.

Both platforms maintain comprehensive documentation. Besu's documentation is hosted by LF Decentralized Trust at besu.hyperledger.org, and smart contract teams can draw on the wider Ethereum tooling ecosystem (Solidity, Hardhat, Foundry, Web3 libraries, MetaMask, and standard wallets) for application development. Cosmos publishes detailed documentation, with continuous development and maintenance from the primary development team, Cosmos Labs, and supported by active community contributions and an open-source tooling ecosystem.

For enterprise support, Cosmos provides professional services including implementation support, custom development, and ongoing maintenance. Besu enterprise support is available through several vendors, including Consensys (the team that originally developed Besu) and Kaleido, which offers managed Besu networks as a service.

Institutional use cases for Hyperledger Besu versus Cosmos

The right platform depends on the specific requirements, constraints, and existing technology investments of the institution.

For payments and cross-border settlements, Cosmos's fast transaction processing, native interoperability, and configurable security model make it well-suited for multi-ledger payment networks spanning organizations or jurisdictions. For asset tokenization, IBC allows tokenized assets to move across ledgers natively, important for assets that move across multiple venues. Cosmos has demonstrated 10,000+ TPS in optimized production environments, which gives high-throughput regulated use cases such as Figure's HELOC lending platform substantial transaction headroom.

Stablecoin infrastructure benefits from high throughput, configurable compliance controls, and the ability to design reserve attestation mechanisms into the chain itself. Production stablecoin platforms run on Cosmos-based chains today. Capital markets applications prioritize settlement speed, auditability, and integration with established market infrastructure, and both Cosmos and Besu have relevant implementations in this space.

Besu's strongest fit is in use cases where teams want to build on the Ethereum specification and inherit its tooling ecosystem. This includes CBDC programs, tokenized securities issuance, and permissioned consortium networks that benefit from Solidity-based smart contracts and standard Ethereum developer workflows. Cross-network interoperability beyond the Besu deployment itself generally requires an additional service, which can limit the applicability of Besu in situations where interoperability is a going concern.

Getting started with enterprise blockchain on Cosmos

For institutions evaluating Cosmos for an enterprise deployment, we provide professional services to shorten the path from evaluation to production. Engagements draw on a stack that has been production-proven since 2019 across more than 150 independent networks, with scoping, design, and implementation work led by Cosmos Labs, the development and growth team behind Cosmos and the Cosmos stack, which provides blockchain advisory services to institutions and governments.

Get started with Cosmos

Frequently Asked Questions

Is Hyperledger Besu still relevant for enterprise blockchain projects?

Yes. Besu has substantive enterprise adoption, particularly in CBDC programs (Nigeria's eNaira, mBridge, and the Bank Indonesia Digital Rupiah testing) and tokenized securities. Active development continues under LF Decentralized Trust, and the project's Financial Services Working Group includes DTCC, Citi, Banco Central do Brasil, Santander, Visa, and Mastercard among its institutional members. Enterprise support is available through vendors including ConsenSys and Kaleido.

Can Cosmos be used for private or permissioned enterprise blockchains?

Yes. Cosmos supports configurable validator sets, account-level permissioning, and application-layer access controls, which can be combined to build fully permissioned enterprise or consortium networks.

How do Cosmos and Hyperledger Besu compare to R3 Corda and Hyperledger Fabric?

All four platforms serve enterprise blockchain use cases with different design priorities. R3 Corda focuses on bilateral agreements between known parties with a UTXO-style transaction model. Hyperledger Fabric provides permissioned consortium networks with channels for private data. Cosmos offers a customizable stack for building independent networks with native interoperability via IBC. Besu emphasizes direct compatibility with the Ethereum specification and tooling ecosystem for both public and permissioned deployments.

What programming languages does each platform support?

Besu is written in Java, and applications running on a Besu network use Solidity or Vyper for smart contracts, along with the standard Ethereum tooling stack (Hardhat, Foundry, Web3 libraries) for development. The Cosmos SDK is written in Go, which is also the primary language for building custom modules. For teams with existing Ethereum codebases or Solidity expertise, Cosmos EVM provides Solidity support on top of the SDK, letting the same chain run Go-based modules and Solidity contracts together.

How long does it typically take to deploy a production network on Cosmos or Hyperledger Besu?

Timelines vary significantly depending on use-case complexity, compliance requirements, and integration scope. The bulk of any production timeline is spent on integration with existing systems, compliance testing, regulatory approval, and stakeholder alignment. These institution-side factors set the schedule, regardless of which platform is chosen.