Application Development on HashSphere

This page will highlight the main differences developers should consider when developing HashSphere applications vs Hedera mainnet applications.

This section highlights the key similarities and differences developers should consider when building applications for a private HashSphere environment versus the public Hedera mainnet.

While HashSpheres run the same core technology stack as the Hedera mainnet and testnet, the private, permissioned nature of a HashSphere introduces unique environmental and operational considerations. However, the fundamental development patterns and core APIs remain consistent.

---

Core API Consistency

Your core developer experience remains largely unchanged. The primary Hedera APIs function the same way on HashSphere as they do on the public networks. You can and should continue to use the main Hedera documentation as your primary reference.

Key services that remain consistent include:

• HAPI: The core ledger APIs for the Hedera Consensus, Token, File, and Crypto Services.

• Hedera Smart Contract Service (HSCS): The APIs for deploying and interacting with EVM-compatible smart contracts.

• Mirror Node: The REST APIs for querying historical data and the gRPC subscriptions for receiving real-time event streams.

---

Guides

• Development Environments

  • Choose a development environment for fast iteration and testing.

• SDK Client Configuration

  • Configure an SDK client to connect to a private HashSphere network.

• Application Design Considerations

  • Understand the primary design differences between public and private networks.