Practical overview
When it fits
Use it when a C++ application needs to interact with a Hiero network and you want the repository's documented build presets, examples, and test workflow.
Who it is for
- C++ developers building applications that create or manage on-ledger assets.
- Teams building client software that interacts with smart contracts or Hedera services.
Documented uses
- Create or update on-ledger assets through a C++ application.
- Build client software that interacts with smart contracts on a Hiero network.
- Compile the SDK and run its examples or documented test suites.
Requirements & limits
The repository is public and identifies the project license as Apache-2.0.
- The project is built with CMake 3.15 or later and uses CMake Presets with vcpkg-based dependencies.
- Build prerequisites vary across macOS, Linux, and Windows; Windows additionally calls for Visual Studio 2022, Perl, and NASM.
- Integration tests need a running Hiero network; the README describes Solo for local development and testing.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build the SDK with a documented CMake preset
Clone the repository, initialize its vcpkg submodule, and build the SDK for a documented platform.
Before you start
- C++17 toolchain.
- CMake 3.15 or later and Ninja.
- macOS and Linux: pkg-config; Linux instructions also list zip, unzip, and linux-libc-dev.
- Windows: Visual Studio 2022 with the Desktop development with C++ workload, Perl and NASM on PATH; use the x64 Native Tools Command Prompt.
Steps
Clone https://github.com/hiero-ledger/hiero-sdk-cpp and change into the repository directory.
Run the command below to initialize the vcpkg submodule.
git submodule update --initConfigure and build with the matching preset:
linux-x64-release,windows-x64-release,macos-x64-release, ormacos-arm64-release.
Expected outcome
A release build configured for one of the listed platform presets.
Guide limitations
- The listed presets cover Linux x64, Windows x64, macOS Intel x64, and macOS Apple Silicon arm64.
- The repository documents build steps; this guidance does not indicate that they were executed.
Configure and launch a documented SDK example
Set environment values and run an example executable from a build or release-artifact directory.
Before you start
- A built SDK with examples enabled, or release artifacts containing examples.
- An operator account ID, its DER-encoded hex private key, and a network name (
mainnet,testnet, orpreviewnet). - A passphrase only if using mnemonic-based key generation.
Steps
Create a
.envfile in the project root withOPERATOR_ID,OPERATOR_KEY, andHIERO_NETWORK; addPASSPHRASEif applicable.Run the example executable from the project root using the documented platform-specific examples path.
For release artifacts, navigate to the appropriate architecture directory and copy
.envinto the examples directory before running the selected example.
Expected outcome
The selected SDK example is launched with the configured account and network environment values.
Guide limitations
- The README uses a placeholder for the example name and does not identify a particular example's behavior.
- For batch execution, the documented scripts require updating
EXECUTABLES_DIRECTORYto the build output folder.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- hiero-ledger/hiero-sdk-cpp · Official homepage title · retained in its source language

