# Hedera (HBAR and HTS tokens)

Webapp 2.0 supports Hedera: the native **HBAR** cryptocurrency and **Hedera Token Service (HTS)** tokens (fungible tokens and NFTs). Creating accounts, sending, receiving, and staking all follow the generic [Operator](/helpcenter2/for-operators/operators-overview.md) and [Administrator](/helpcenter2/overview.md) guides. The Hedera-specific points are below.

## Token association

On Hedera, an account can only hold or receive a token it has been **associated** with. An account that isn't associated with a token **can't receive it**, and a transfer of that token to it will fail. For the token accounts Webapp 2.0 manages this is handled for you, so the account is ready to receive. You mainly need to be aware of it when sending to an **external** address that hasn't associated the token.

> **Note:** Addresses given as an **EVM-compatible alias** are associated automatically on the first transfer, so they don't need a separate association step.

## Fees: always in HBAR, sometimes with custom fees

The Hedera **network fee** for any transaction is paid in **HBAR** by the sender. So **every Hedera account needs a small HBAR balance to transact**, including HTS token accounts. A token account with no HBAR can't cover the fee to send.

On top of the network fee, an individual HTS token can carry **custom fees** set by its issuer. These may be charged in HBAR or in the token itself, and the issuer decides whether the **sender or the receiver** pays. When they apply, the [send screen](/helpcenter2/for-operators/sending-assets.md) itemises the network fee and any custom fees separately, and indicates who pays, so you see the full cost before approving.

## Sending to an unprepared recipient

Because of association, an HTS send can be rejected if the recipient isn't ready for that token; on-chain this surfaces as a *token not associated to account* error. Some accounts are also configured to require the **receiver to sign** incoming transfers; a standard transfer to such an account will fail until that's satisfied. If a send is flagged, resolve it with the recipient (for example, have them associate the token) before retrying.

## Staking HBAR: liquid, whole-balance

Hedera staking is unusual in two ways, both reflected in the generic [Staking](/helpcenter2/for-operators/staking.md) section:

* it stakes the account's **entire HBAR balance** (you don't choose an amount); and
* it's **liquid**, with **no lock-up and no unbonding delay**, so staked HBAR stays available.

You stake to a Hedera **node** or delegate to a Hedera **account**. Rewards begin accruing after roughly 24 hours.

> **Warning:** Collect rewards within 365 days. Only the most recent 365 days of rewards can be collected; Webapp 2.0 warns you as rewards approach that limit. Rewards are also paid out automatically when a qualifying transaction occurs on the account.

## Addresses and accounts

Hedera addresses are shown in standard format (`shard.realm.num`, e.g. `0.0.12345`) and, where applicable, as an EVM-compatible alias. HTS token accounts can be organised under a parent HBAR account, shown on the account page so you can move between a token account and its HBAR parent. See [Finding accounts & checking balances](/helpcenter2/for-operators/finding-accounts-and-checking-balances.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.enterprise.ledger.com/helpcenter2/network-specific-guidance/hedera-hbar-and-hts-tokens.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.