Java SDK for interacting with the Hedera API
Switch branches/tags
Nothing to show
Clone or download
Latest commit 9d2b942 Oct 21, 2018

Hedera Java SDK

CircleCI Discord

The Java SDK for interacting with Hedera Hashgraph: the official distributed consensus platform built using the hashgraph consensus algorithm for fast, fair and secure transactions. Hedera enables and empowers developers to build an entirely new class of decentralized applications.

Version is 0.1.0

The Hedera Java SDK uses semantic versioning.

Features supported include:

  • Micro-payments between two Accounts
  • Storing files to Hedera
  • Creating Solidity Smart Contracts
  • Executing Smart Contracts

Environment Set-up


  • JDK: 10.0.x

  • Maven: 3.5.x

    To check the versions of these products from CLI use:

    Java: java -version

    Maven: mvn --version


Maven Installation MAC

  • Open terminal

  • Complete the commands below in your terminal

>brew update
>brew install maven
   ==> Downloading
   ==> Downloading from
       ######################################################################## 100.0%
>which mvn
>mvn -v
   Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T13:33:14-05:00)
   Maven home: /usr/local/Cellar/maven/3.5.4/libexec
   Java version: 10.0.2, vendor: Oracle Corporation, runtime: 
   Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"

From Eclipse or IntelliJ:

  • Right click on pom.xml
  • Run As -> Maven Install

From CLI:

$> mvn install

Note that the .proto files are compiled with Maven, so the project may initially look full of errors, this is normal.

If there are still some project issues, try a Maven project update and project clean followed by a Maven install.

Running the examples

A is provided, copy the file to and update with your account details, the details of the node you want to communicate to, and your private/public keys (as hex strings).

This file is ignored by git so all changes will remain local.

Example location within this repo

There is a main Demo file in each of the three main example folders:

These Demo files contain working examples of account, file and smart-contract APIs. As such they provide a good starting point for developers who wish to familiarise themselves with the Hedera SDK for Java.


Javadocs are generated automatically as part of the Maven build (if run from Eclipse, make sure your JAVA HOME is set otherwise the build will fail).

They are generated as a JAR file which is compiled into the target/ folder.

Building a simple test with the Hedera SDK for Java

Code snippets used in this document are excerpt from the full examples included in this repo. Those examples can be found here in their entirety.

Prerequisites for using the SDK

Access to the Hedera mainnet or a Hedera testnet

In order to be able to use the Hedera SDK for Java you must have access to a testnet or to the Hedera mainnet. Access to mainnet and testnets are currently restricted.

Temporary testnets (or "Flashnets") may become available for specific events and engagements such as hackathons.

To get access to any Hedera network you must first create a Hedera Profile in the Hedera Portal, then enter an access or promo code that was received from the Hedera team.

Addresses of testnet nodes

After you join a network through the Hedera Portal, you will be provided information required connect to that network, specifically:

  • IP address and/or DNS name – providing IP connectivity to that node
  • Port number – The specific port on the node to which queries and transactions must be sent
  • Account ID – the Hedera account number associated with the node. This is required in order to issue transactions and queries. It determines the account to which node-fees will be paid. Hedera account IDs are made up of three int64 numbers separated by colons (e.g. 0:0:3) The three numbers represent Shard-number, Realm-number and Account-number respectively. Shards and Realms are not yet in use, so you should expect Account IDs to start with two zeros for the present time.

NOTE: This information should be added to your file (see above) if you wish to run the example code provided.

Public/Private Key Pairs

Hedera accounts must be associated with cryptographic keys. ED25519 key pairs can be generated using the Hedera Keygen utility. A complete explanation of the key generation process is documented in the readme file in that repo. A minimal version of that process will be shown below.

NOTE: This information should be added to your file (see above) if you wish to run the example code provided.

Using the Hedera SDK for Java

The following steps describe some first steps using the SDK:

  1. Generate a Key Pair
  2. Create a new java project
  3. Create a Hedera account
  4. Retrieve the balance of a Hedera account
  5. Transfer hbars between Hedera accounts

Generating a Key Pair

Download the sdk-keygen-jar to a folder in your development environment.

Open that folder using terminal and execute the following command to generate a public/private key pair based on a system-generated random seed:

java -jar sdk-keygen-1.0.jar
Example Output
Your key pair is:
Public key:
Secret key:
Recovery word list:
[ink, enable, opaque, clap, make, toe, brine, tundra, cater, Joe, small, run, Seoul, grand, atom, crush, circus, abbey, vacuum, whim, hollow, afar]

Copy this information into a safe place as you will need these keys below.

Should you wish to specify your own seed, please refer to the Hedera KeyGen readme file.

Create a new Java project

Open your IDE of choice (Eclipse, IntelliJ, VSCode...)

Once the maven install has been completed, you should be able to locate a new jar-file sdk-0.1.0.jar within the hedera-sdk-java/target/ folder.

Once you have added that jar file to your project, you should be able to import classes from the SDK for use within your application.

Create a Hedera account

In the interest of clarity, these examples assume a sunny-day scenario and do not include exception-handling logic. Refer to the main examples folder for more resilient code.

This is the definition of the simple version of the create method in the HederaAccount class:

public HederaTransactionResult create(long shardNum,
                                      long realmNum,
                                      byte[] publicKey,
                                      KeyType keyType,
                                      long initialBalance,
                                      HederaAccountCreateDefaults defaults
                                      throws InterruptedException

The purpose of each of the parameters is as follows:

shardNum - the shard number for the new account. Note that this is not currently used, and should be set to 0 at present.

realmNum - the realm number for the new account. Note that this is not currently used, and should be set to 0 at present.

publicKey - the public key for the new account. This should be set to the Public Key generated using the Hedera Key Generation Tool (see above).

keyType - The type of cryptographic key used by this account. In future, a variety of standards will be supported; at present only ED25519 keys are supported.

initialBalance - A Hedera account must contain hbars on creation. This parameter describes that opening balance in TinyBars. Note: 100,000,000 TinyBars is equivalent to 1 hbar.

defaults - The Hedera SDK for Java makes extensive use of defaults parameters to maximise reuse and readability. These defaults help new developers to get started without the need to understand all of the necessary parameters in detail. Once you are familiar with basic functionality of each method, additional behaviour can be unlocked by modifying these defaults.

Using HederaAccount.create

Utility functions have been provided within the examples. The first of these that we should use configures default settings for all transactions and queries.

Note: For these example steps to function as expected, you must have updated the file as described above. The pubkey + privkey and payingAccount... parameters are used to determine the account from which hbars are transferred.

// setup a set of defaults for query and transactions
HederaTransactionAndQueryDefaults txQueryDefaults = new HederaTransactionAndQueryDefaults();
txQueryDefaults = ExampleUtilities.getTxQueryDefaults();

In order to create a Hedera account, an initial balance must be transferred into the new account from an existing account. The package retrieves details of the "source" or paying account from the file.

A HederaAccount variable must be defined and associated with the txQueryDefaults we just created.

HederaAccount account1 = new HederaAccount();

// setup transaction/query defaults (durations, etc...)
account1.txQueryDefaults = txQueryDefaults;

To keep things simple in this example, a cryptographic record of the transaction is not required. In the following code-snippet, a new cryptographic private/public key pair is generated for the new account, specifying a KeyType of ED25519. This is equivalent to generating a key pair using the Hedera Key Generation utility. It is worth making a note of those public and private keys.

account1.txQueryDefaults.generateRecord = false;
HederaCryptoKeyPair account1Key = new HederaCryptoKeyPair(KeyType.ED25519);

Now that everything is set up correctly, the following statement should create a Hedera account by transferring 100,000 TinyBars from the paying account defined in into the new account.

account1 = AccountCreate.create(account1, account1Key, 100000);

Retrieve the balance of a Hedera account

Assuming that you have completed the steps above, the following statement will retrieve the balance of the account by querying the network.

long balance1 = account1.getBalance();

Transfer hbars between Hedera accounts

To transfer hbars from one account to another, a second account is required. The following code snippet replicates the steps undertaken above to create a second account, and assumes that this code will be added to the steps above.

HederaAccount account2 = new HederaAccount();

// setup transaction/query defaults (durations, etc...)
account2.txQueryDefaults = txQueryDefaults;

account2.txQueryDefaults.generateRecord = false;
HederaCryptoKeyPair account2Key = new HederaCryptoKeyPair(KeyType.ED25519);

account2 = AccountCreate.create(account2, account1Key, 100000);

At this stage, two accounts: account1 and account2 – each holding 100,000 TinyBars – have been created.

In the supplied examples, the txQueryDefaults object contains details of the original paying account used to fund the opening of both accounts; these defaults were read from the file.

In order to transfer TinyBars from account1 to account2 we must override that behaviour. This code snippet sets the default paying account to account1.

account1.txQueryDefaults.payingAccountID = account1.getHederaAccountID();
account1.txQueryDefaults.payingKeyPair = account1Key;

To send the transfer transaction to Hedera, transferring 10,000 TinyBars from account1 to account2 the following code should be used:

AccountSend.send(account1, account2, 10000);

To verify that account1 now contains 90,000 TinyBars and account2 contains 110,000 TinyBars the following instructions should suffice.

long balance1 = account1.getBalance();
long balance2 = account2.getBalance();

Note: In the event you're not waiting for consensus on the transfer transaction, it's possible that the balances will initially show no change. Adding a small delay between the transfer and the balance queries will ensure the correct values are returned. Ideally, you would ask for a receipt and check transaction status following the transfer transaction before querying the updated balances. This is shown in the examples contained within the SDK.

More information

To learn more about Hedera visit The Hedera Site.

If you want to contribute please review the Contributing Guide.

Need help?


Copyright (c) 2018-present, Hedera Hashgraph LLC.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.