Skip to main content
Accounts are the central starting point when interacting with the Hedera network and using Consensus Node services. A Hedera account is an entity, a distinct object type, stored in the ledger, that holds tokens. Accounts can hold the native Hedera fungible token (HBAR), custom fungible, and custom non-fungible tokens (NFTs) created on the Hedera network. The Hedera native token HBAR (ℏ) is a utility token primarily used to pay for transactions and query fees when interacting with the network. The HBAR symbol is represented as “ℏ.” Applications may reference HBAR as the token denomination; however, the network returns information in tinybars (tℏ), a denomination of HBAR. 100,000,000 tℏ are equivalent to 1 ℏ. This includes things like transaction fees or accounts HBAR balances. You interact with the network by submitting transactions that modify the ledger’s state or submitting query requests that read data from the ledger. Most transactions and queries have a transaction fee that is charged in HBAR. Unlike custom tokens users create on the Hedera network, no token ID represents the native HBAR token.

Account Creation

Auto Account Creation

Account Properties

​
FAQs

A Hedera account is a unique entity in the Hedera Network that can hold tokens. These can be Hedera’s native fungible token (HBAR), custom fungible, or non-fungible tokens (NFTs).
New accounts are created by submitting a transaction to the network and paying the transaction fee. You’ll need access to an existing account with sufficient HBAR to cover this fee. If you don’t have access to an existing account, you can use a supported wallet, visit the Hedera Developer Portal, or use the “Auto Account Creation” feature for applications.
Auto Account Creation allows applications to generate free user accounts instantly, even without an internet connection, by creating an account alias.
A hollow account is created when value is transferred to an EVM Address from Public Key via Auto Account Creation without a corresponding key on file. It has an account number and an EVM address but no account key. It can receive tokens but cannot send tokens or modify account properties until the matching ECDSA key is added, completing the account. This is the standard onboarding path for EVM-wallet users.