# Zama Token

The Zama protocol uses to $ZAMA token as its utility token to pay for protocol operations such as decryptions. It is implemented as an ERC20 on Ethereum, and exposed on other chains as a LayerZero OFT.

## Contract information

| Resource              | Link                                                                                                                  |
| --------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Deployed addresses    | [Addresses directory](/protocol/protocol-apps/addresses.md)                                                           |
| ZamaERC20 source      | [ZamaERC20.sol](https://github.com/zama-ai/protocol-apps/blob/main/contracts/token/contracts/ZamaERC20.sol)           |
| ZamaOFT source        | [ZamaOFT.sol](https://github.com/zama-ai/protocol-apps/blob/main/contracts/token/contracts/ZamaOFT.sol)               |
| ZamaOFTAdapter source | [ZamaOFTAdapter.sol](https://github.com/zama-ai/protocol-apps/blob/main/contracts/token/contracts/ZamaOFTAdapter.sol) |

The primary token contract is the Zama ERC20 deployed on Ethereum. It is made available on other chains via LayerZero, as implemented via the OFT adapter on Ethereum and OFT contracts on each destination chain.

## Structure

{% @mermaid/diagram content="flowchart
subgraph Ethereum
Protocol-DAO
ZAMA-ERC20
ZAMA-OFTAdapter

```
    Protocol-DAO -- admin role --> ZAMA-ERC20
    Protocol-DAO -- owner + delegate --> ZAMA-OFTAdapter
    ZAMA-ERC20 -. locks .- ZAMA-OFTAdapter
end

subgraph Gateway
    Gateway-Multisig
    ZAMA-OFT-GW

    Gateway-Multisig -- owner + delegate --> ZAMA-OFT-GW
end

subgraph BNB Smart Chain
    BNB-Multisig
    ZAMA-OFT-BNB

    BNB-Multisig -- owner + delegate --> ZAMA-OFT-BNB
end

subgraph HyperEVM
    HyperEVM-Multisig
    ZAMA-OFT-HYPEREVM

    HyperEVM-Multisig -- owner + delegate --> ZAMA-OFT-HYPEREVM
end

subgraph Solana
    Solana-Multisig
    ZAMA-OFT-SOL

    Solana-Multisig -- owner + delegate --> ZAMA-OFT-SOL
end

ZAMA-OFTAdapter <-. linked (via LayerZero) .-> ZAMA-OFT-GW
ZAMA-OFTAdapter <-. linked (via LayerZero) .-> ZAMA-OFT-BNB
ZAMA-OFTAdapter <-. linked (via LayerZero) .-> ZAMA-OFT-HYPEREVM
ZAMA-OFTAdapter <-. linked (via LayerZero) .-> ZAMA-OFT-SOL" %}
```

Ownership of each OFT contract is detailed in [Governance](/protocol/protocol-apps/governance/governance.md).

### Solana

On Solana, the token (SPL) and the bridge logic are split into different accounts. The token logic (used by exchanges and wallets) corresponds to the mint address, while the bridging logic and the LayerZero specific configuration are mainly inside the program and store addresses.

All Solana OFT addresses can be found in the [Solana mainnet addresses](/protocol/protocol-apps/addresses/mainnet/solana.md).

### Hyperliquid

The Hyperliquid bridge is a "double bridge": Ethereum <> HyperEVM <> HyperCore.

The HyperEVM OFT contract is linked to a [HIP-1](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-1-native-token-standard) token instance on HyperCore.

The HIP-1 details are the following:

| HIP-1 metadata | Value                              |
| -------------- | ---------------------------------- |
| name           | ZAMA                               |
| szDecimals     | 2                                  |
| weiDecimals    | 8                                  |
| index          | 433                                |
| tokenId        | 0x93be47677e2dc084333dc6b59ac5672c |
| fullName       | Zama                               |

To streamline the double-bridging process, a composer contract is deployed on HyperEVM (leveraging the [lzCompose](https://docs.layerzero.network/v2/developers/evm/composer/overview) pattern). This allows users to bridge in a single step directly from Ethereum to HyperCore, by sending tokens to the composer contract on HyperEVM with correct lzCompose options. This is abstracted away via the dedicated bridge frontend (see [Bridges](#bridges)).

{% hint style="warning" %}
Before bridging to HyperCore, users should ensure they have activated their account on HyperCore as a prerequisite. This could be done for instance via the [Hyperliquid UI](https://app.hyperliquid.xyz/trade) and depositing 10 USDC to their address via the official Arbitrum bridge. Another method is by letting another already active account send them 1 USDC via the Hyperliquid UI (be aware that this amount will be burned).
{% endhint %}

All HyperEVM contract addresses (OFT + composer) can be found in the [HyperEVM mainnet addresses](/protocol/protocol-apps/addresses/mainnet/hyper_evm.md).

## Bridges

The [Zama bridge](https://bridge.zama.org/) is available as a LayerZero frontend to bridge $ZAMA between the chains on which it is deployed, including Ethereum and the Gateway.

The bridge may also be used to bridge ETH from Arbitrum One to the Gateway, to pay for gas fees on the latter.

### $ZAMA bridges

* Main bridge: <https://bridge.zama.org/> (using Superbridge)
  * Ethereum <> Gateway
  * Ethereum <> BSC
  * Ethereum <> Solana
* HyperLiquid bridge: [https://stargate.finance/](https://stargate.finance/?srcChain=ethereum\&srcToken=0xA12CC123ba206d4031D1c7f6223D1C2Ec249f4f3\&dstChain=hypercore\&dstToken=0x93be47677e2dc084333dc6b59ac5672c) (using Stargate)
  * Ethereum -> HyperCore
  * HyperCore -> HyperEVM
  * Ethereum <> HyperEVM

### $ETH bridges

* Main bridge: <https://bridge.zama.org/> (using Superbridge)
  * Arbitrum One <> Gateway
* Arbitrum One bridge: [https://portal.arbitrum.io/bridge](https://portal.arbitrum.io/bridge?destinationChain=arbitrum-one\&sanitized=true\&sourceChain=ethereum)
  * Ethereum <> Arbitrum One


---

# 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://docs.zama.org/protocol/protocol-apps/zama-token.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.