Hyperledger Cacti’s Stellar connector brings Soroban smart-contract operations into a framework designed to coordinate work across different distributed ledger technologies (DLTs). Its documented initial scope covers deploying, initializing, managing, and executing Soroban contracts; the announcement also describes bridging assets between Soroban and Hyperledger Besu. Cheesecake Labs contributed the connector with the Cacti community. A Besu bridge prototype and scenarios such as Brazil’s DREX are examples, not evidence of production deployments.
What is the Stellar connector for Hyperledger Cacti?
Hyperledger Cacti is a modular interoperability framework for applications that need to work with more than one ledger. Its connectors encapsulate ledger-specific communication and operations—such as connecting to nodes, retrieving data, deploying smart contracts, and submitting transactions—so an application can coordinate across networks without requiring them to share a protocol or governance model. Cheesecake Labs’ technical article and its connector announcement describe that role and the initial Stellar integration.
As an Amazon Associate I earn from qualifying purchases.
The Stellar connector is the Cacti component that provides this ledger-specific interface for Stellar. Its first documented focus is Soroban, Stellar’s smart-contract platform. The goal is not to make Stellar and other networks identical, but to give Cacti applications a way to invoke supported Stellar capabilities as part of a wider cross-ledger workflow.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What does the Stellar connector support?
The initial version described by Cheesecake Labs supports Soroban contract operations through Cacti. The technical article says applications can deploy, initialize, manage, and execute Soroban smart contracts, and identifies Stellar Plus, an open-source JavaScript library, as a library used during development. The announcement specifically describes asset bridging between Stellar Soroban and Hyperledger Besu.
#1 Best Overall
- Documented initial scope: Soroban smart-contract lifecycle and execution operations exposed through the connector.
- Announced interoperability direction: bridging assets between Soroban and Hyperledger Besu through Cacti.
- Not established by these sources: quantified throughput or latency, production adoption, security audit results, or the current package version and ledger-version compatibility.
That boundary matters: a connector that exposes contract operations is a building block for cross-ledger applications, not by itself proof that a particular asset transfer is live, audited, or deployed in production.
How does Hyperledger Cacti connect Stellar to other blockchains?
Cacti’s connector model gives an application a ledger-specific route into each participating network. The application can use the relevant connector to perform supported operations on that ledger, then coordinate a workflow involving another connector. For the Stellar integration, that means invoking Soroban capabilities from a Cacti application while another connector handles its own network’s operations. The design provides an interoperability layer; it does not remove the need to define how a cross-network workflow handles asset representation, settlement, failure, or trust.
Stellar and Hyperledger Besu
The announcement identifies asset bridging between Soroban and Besu as an initial interoperability use case. Separately, contributor Fabricius Zatti described adapting a Cacti SATP CBDC example, implementing Stellar smart contracts, and demonstrating a Stellar–Besu bridge prototype. In his June 27, 2024 contributor account, he said the demo was not yet in the Cacti repository and that the team planned to polish it and add it as an example. That is historical prototype evidence, not confirmation that the example was later released or that a production bridge is operating.
Illustrative scenarios are not deployments
The technical article offers Brazil’s Real Digital/DREX as a possible scenario: a representation on a Besu-based network could be bridged to Stellar. It also discusses potential Stellar DeFi applications that use price feeds from Ethereum-based markets or connect liquidity pools across networks. These are illustrative possibilities, not evidence that DREX uses the connector, that such feeds are operational, or that the described pool connections are live.
Can Stellar Soroban smart contracts interact with Hyperledger Besu?
The connector’s announced scope and the contributor’s historical prototype both point to Soroban–Besu interoperability. The intended interaction is coordinated across ledger-specific components: Cacti applications can use the Stellar connector for Soroban operations and a Besu connector for Besu-side work. The contributor account documents a prototype, but the available sources do not establish a production deployment, current operational status, or a completed, generally available bridge implementation.
Cross-ledger asset movement also requires a defined exchange and settlement design; having connectors for both networks does not alone specify those guarantees. The technical article discusses Delivery Versus Payment (DVP) and Hash Time-Locked Contracts (HTLCs) as directions for secure asset exchange development, rather than confirming that these mechanisms shipped.
What is the status of classic Stellar transactions and planned exchange features?
The 2024 announcement said support for Stellar classic transactions was planned. The technical article also described continued development around DVP use cases and HTLCs. The sources available here do not verify whether classic transaction support or those exchange mechanisms have since shipped. Nor do they establish the connector’s current package version, supported ledger versions, or release-specific compatibility. The 2025 Cacti annual review confirms community collaboration and refers to Cacti releases v2.0.0 and v2.1.0, while noting artifact publishing was on hold during an organizational migration; it does not settle those connector-specific status questions.
Recommended Free Tools
How was the Stellar connector developed and tested?
In his contributor account, Fabricius Zatti says Cacti community member Peter Somogyvari prepared a connector skeleton based on an existing connector, after which Zatti implemented Stellar-specific operations with community support. Zatti said the initial version was completed in a couple of weeks; that is his account of this project’s development, not a general development estimate or independently measured benchmark.
Best Value
The same account describes a standalone test-ledger tool that provisions a fresh Docker-based local environment with Horizon API, Soroban RPC, and Friendbot. It can also be used independently for local development. A September 4, 2024 Linux Foundation webinar listing includes the test ledger and demonstration among its topics. These sources describe a development and demonstration setup, not a published performance evaluation or security audit.
What Cheesecake Labs contributed
Cheesecake Labs contributed implementation work in collaboration with the Cacti community. The contributor account credits engineer Fabricius Zatti and community contributor Peter Somogyvari with the collaborative development. The 2025 Cacti annual review also records the collaboration. This supports describing Cheesecake Labs as a contributor; it does not by itself establish that the company maintains every later release or that a particular deployment is supported by it.
What to verify before building with the connector
Because the cited material does not establish current connector-specific release and deployment details, teams evaluating it should verify those details against the project’s current artifacts and documentation before committing to an implementation. In particular, confirm:
Quick Recap
- Which connector release and Cacti version are available, and whether required artifacts are publishable.
- Which Stellar network and ledger versions, Soroban operations, and transaction types that release supports.
- Whether the intended Besu workflow is an available example, a prototype, or custom application work.
- How the proposed design handles authorization, asset representation, settlement, failures, and recovery across ledgers.
- What security review and operational monitoring are required for the deployment; the cited sources report no audit findings.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
