> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hedera.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain.
> Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names.
> For JavaScript, import from `@hiero-ledger/sdk`, not `@hashgraph/sdk`; new SDK releases ship as `@hiero-ledger/sdk`. The Java SDK keeps the `com.hedera.hashgraph:sdk` Maven coordinates. Verify the exact import against the docs.
> Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural.
> Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case.
> For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias".

# Creating Issues

> Report a documentation problem or suggest new content by opening an issue in the hedera-docs GitHub repository, step by step.

If you've identified a problem in the documentation or have a suggestion for additional content, you can submit an issue. Follow these steps:

1. **Navigate to the Repository:** Visit the [`hedera-docs`](https://github.com/hashgraph/hedera-docs) GitHub repository.
2. **Open the Issues Tab:** Find the "Issues" tab near the top of the repository page, next to "Code" and "Pull Requests". Click on it.
3. **Create a New Issue:** Click the "New Issue" button to open a form where you can detail the problem or suggestion.
4. **Fill Out the Form:** Give your issue a title and a detailed description. Be as clear and concise as possible to ensure we fully understand the issue. If applicable, include screenshots or code snippets.
5. **Submit the Issue:** After filling out the issue, click the "Submit new issue" button. We'll review your issue and take appropriate action.