> ## 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".

# Token Management with Hedera Token Service

> The native HBAR token cannot be burned. Learn how EVM developers use the HTS system contract at 0x167 and a supply key to mint and burn custom tokens.

## Overview

Ethereum supports native ETH burning via mechanisms like [EIP-1559](https://ethereum.github.io/abm1559/notebooks/eip1559.html), but Hedera takes a different approach. The native HBAR token cannot be burned. Instead, developers can use the Hedera Token Service (HTS) to create and manage custom tokens with built-in minting and burning capabilities.

### Key Features for EVM Developers

* **Supply Key**
  * Controls minting and burning of tokens.
  * Must be securely managed to prevent unauthorized actions.
* **HTS System Contract**
  * System contract functions accessible via reserved address `0x167`.
  * Enable token creation, minting, and burning directly from Solidity contracts.
* **Access Control**
  * Only addresses authorized by the supply key can mint or burn tokens.
  * Multi-signature (multi-sig) or threshold key configurations can enhance security.

***

### Minting and Burning Tokens with HTS

* **Minting Tokens**: Introduce new tokens for incentives, rewards, or liquidity.
* **Burning Tokens**: Remove tokens to increase scarcity or meet regulatory requirements.

#### Code Example: HTS Mint/Burn

```solidity wrap theme={null}
// SPDX-License-Identifier: Apache-2.0
pragma solidity ^0.8.0;

interface HederaTokenService {
    function createFungibleToken(
        address treasury,
        uint64 initialSupply,
        string memory tokenName,
        string memory tokenSymbol,
        uint32 decimals
    ) external returns (address tokenAddress);

    function mintToken(address token, int64 amount, bytes[] calldata metadata) external returns (int64 newTotalSupply);

    function burnToken(address token, int64 amount, bytes[] calldata metadata) external returns (int64 newTotalSupply);
}

contract TokenManager {
    HederaTokenService constant hts = HederaTokenService(0x167);
    address public token;

    constructor(address treasury) {
        // Create a fungible token with an initial supply of 1,000 units
        // Token parameters: name = "MyHederaToken", symbol = "MHT", decimals = 8
        token = hts.createFungibleToken(treasury, 1000, "MyHederaToken", "MHT", 8);
    }

    // Mint additional tokens. Ensure that msg.sender holds the supply key or is authorized.
    function mintMoreTokens(int64 amount) external {
        // Metadata array left empty, but can be used for NFT-like functionality or extra data
        hts.mintToken(token, amount, new bytes[](0));
    }

    // Burn existing tokens. Ensure the caller is authorized via supply key management.
    function burnSomeTokens(int64 amount) external {
        hts.burnToken(token, amount, new bytes[](0));
    }
}
```

**Important Notes**

* Ensure the caller holds the supply key.
* Associate the treasury account with the token for successful operations.
* Minting and burning fail without proper key authorization.

***

## Additional Resources

* [**Access HTS Tokens Through the EVM**](/evm/hedera-services/hybrid/erc-compatibility)
* [**HTS System Contract Functions**](https://github.com/hiero-ledger/hiero-contracts/tree/main/contracts/token-service)