Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. GitHub Wiki
  3. cacti

cacti

Apache-2.0TypeScriptv2.1.0-alpha.1

A pluggable interoperability framework for linking heterogeneous blockchain and distributed ledger networks to run cross-network transactions.

Visit WebsiteGitHubGitHub
390 stars352 forks0 contributors

What is cacti?

Hyperledger Cacti is a modular interoperability framework designed to enable transactions across different distributed ledger technologies (DLTs) without requiring a central settlement chain. It solves blockchain fragmentation by allowing networks to share data, exchange assets atomically, and manage identities across boundaries while preserving security, privacy, and governance autonomy. The project results from merging Hyperledger Cactus and Weaver Lab into a unified codebase under the Hyperledger Foundation.

Target Audience

Blockchain developers and architects building cross-network applications on heterogeneous DLTs like Hyperledger Fabric and Besu. Enterprises and consortia needing to integrate multiple blockchain networks for asset transfers, data sharing, or identity management without sacrificing autonomy.

Value Proposition

Developers choose Cacti for its pluggable architecture that supports multiple interoperability protocols and modules, allowing customization based on specific design and trust assumptions. It uniquely avoids forcing networks into a single chain, offering both Node Server (Cactus legacy) and Relay (Weaver legacy) modes for cross-network transaction orchestration.

Overview

Hyperledger Cacti is a new approach to the blockchain interoperability problem

Use Cases

Best For

  • Building cross-network applications that execute transactions spanning multiple blockchain networks like Fabric and Besu.
  • Enabling atomic transfer of digital assets between heterogeneous distributed ledger technologies without a central settlement chain.
  • Managing identities across different DLT networks while maintaining self-sovereignty and governance autonomy.
  • Sharing ledger data between isolated blockchain networks to prevent ecosystem fragmentation.
  • Selecting and configuring interoperability protocols based on specific design and trust assumptions for custom solutions.
  • Integrating legacy Cactus and Weaver systems under a unified framework with shared CI/CD pipelines and documentation.

Not Ideal For

  • Teams needing simple, drop-in interoperability solutions without extensive configuration and setup.
  • Projects operating exclusively on a single distributed ledger technology with no cross-network requirements.
  • Startups or small teams with limited development resources looking for a mature, stable interoperability framework.

Pros & Cons

Pros

Pluggable Architecture

Supports multiple interoperability protocols and modules that can be selected and configured based on design and trust assumptions, enabling custom solutions for cross-network transactions as highlighted in the Key Features.

Cross-Network Orchestration

Enables distributed applications on ledgers like Fabric and Besu to execute transactions spanning network boundaries without a central settlement chain, illustrated in the transaction orchestration modes diagram.

Unified Legacy Integration

Integrates legacy Cactus and Weaver systems under a common namespace with shared CI/CD pipelines and documentation, facilitating seamless upgrades and a consolidated codebase from the merger.

Atomic Asset Exchange

Facilitates atomic transfer of digital assets between heterogeneous blockchain networks, core to preventing ecosystem fragmentation and enabling secure cross-chain workflows per the project scope.

Cons

Complex Setup and Maintenance

The modular architecture and ongoing 'Cacti cleanup' initiative indicate that deployment and configuration require significant expertise, and the codebase may have unstable or deprecated components needing attention.

Documentation and Onboarding Challenges

The README highlights efforts to improve documentation and onboarding, suggesting current resources are insufficient, making it difficult for new users to get started quickly without deep diving into legacy systems.

Performance and Overhead Considerations

Orchestrating transactions across multiple networks through pluggable modules can introduce latency and performance overhead, which might not be suitable for high-frequency or real-time transaction environments.

Frequently Asked Questions

Quick Stats

Stars390
Forks352
Contributors0
Open Issues153
Last commit1 day ago
CreatedSince 2019

Tags

#hacktoberfest#fabric#distributed-ledger-technology#blockchain-interoperability#cross-chain

Links & Resources

Website

Included in

GitHub Wiki442
Auto-fetched 5 hours ago

Related Projects

guavaguava

Google core libraries for Java

Stars51,497
Forks11,146
Last commit19 hours ago
HystrixHystrix

Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.

Stars24,459
Forks4,698
Last commit5 months ago
hhvmhhvm

A virtual machine for executing programs written in Hack.

Stars18,629
Forks3,073
Last commit5 days ago
foundationdbfoundationdb

FoundationDB - the open source, distributed, transactional key-value store

Stars16,327
Forks1,497
Last commit19 hours ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub