# Token Metadata

### HyperCore

Unit tokens are deployed on HyperCore through the [HIP-1](https://hyperliquid.gitbook.io/hyperliquid-docs/hyperliquid-improvement-proposals-hips/hip-1-native-token-standard) native token standard. The Unit HyperCore deployer is a multi-sig user with address `0xF036a5261406a394bd63Eb4dF49C464634a66155`

<table><thead><tr><th width="105.55078125">Name</th><th width="106.56640625">L1 Name</th><th width="142.3046875">Full Name</th><th>Native Chain</th><th>Token ID (Explorer Details)</th></tr></thead><tbody><tr><td>BTC</td><td>UBTC</td><td>Unit Bitcoin</td><td>Bitcoin</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x8f254b963e8468305d409b33aa137c67">0x8f254b963e8468305d409b33aa137c67</a></td></tr><tr><td>ETH</td><td>UETH</td><td>Unit Ethereum</td><td>Ethereum Mainnet</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0xe1edd30daaf5caac3fe63569e24748da">0xe1edd30daaf5caac3fe63569e24748da</a></td></tr><tr><td>SOL</td><td>USOL</td><td>Unit Solana</td><td>Solana Mainnet Beta</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x49b67c39f5566535de22b29b0e51e685">0x49b67c39f5566535de22b29b0e51e685</a></td></tr><tr><td>PUMP</td><td>UPUMP</td><td>Unit Pump Fun</td><td>Solana Mainnet Beta</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x544e60f98a36d7b22c0fb5824b84f795">0x544e60f98a36d7b22c0fb5824b84f795</a></td></tr><tr><td>FARTCOIN</td><td>UFART</td><td>Unit Fartcoin</td><td>Solana Mainnet Beta</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x7650808198966e4285687d3deb556ccc">0x7650808198966e4285687d3deb556ccc</a></td></tr><tr><td>SPXS</td><td>UUUSPX</td><td>Unit SPX6900</td><td>Solana Mainnet Beta</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x2ff71b802a6788a052c7f1a58ec863af">0x2ff71b802a6788a052c7f1a58ec863af</a></td></tr><tr><td>BONK</td><td>UBONK</td><td>Unit Bonk</td><td>Solana Mainnet Beta</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0xb113d34e351cf195733c98442530c099">0xb113d34e351cf195733c98442530c099</a></td></tr><tr><td>XPL</td><td>XPL</td><td>Unit Plasma</td><td>Plasma Mainnet</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x2c54c60600e1d786b2dfc139a38a5a99">0x2c54c60600e1d786b2dfc139a38a5a99</a></td></tr><tr><td>ZEC</td><td>UZEC</td><td>Unit Zcash</td><td>Zcash Mainnet</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x1c994ad3381d31c86c8c2d74ed89a365">0x1c994ad3381d31c86c8c2d74ed89a365</a></td></tr><tr><td>AVAX</td><td>UAVAX</td><td>Unit Avalanche</td><td>Avalanche Mainnet</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x730fc3855fb77d2aa5a19dd7891dbe80">0x730fc3855fb77d2aa5a19dd7891dbe80</a></td></tr><tr><td>VIRTUAL</td><td>UVIRT</td><td>Unit Virtual</td><td>Base Mainnet</td><td><a href="https://app.hyperliquid.xyz/explorer/token/0x85b8124314ae77b78b4b6f20ecd93149">0x85b8124314ae77b78b4b6f20ecd93149</a></td></tr></tbody></table>

### HyperEVM

A subset of Unit tokens are also deployed on the HyperEVM. These tokens are fungible between Hyperliquid's two execution environments. HyperCore <> HyperEVM transfers can be done via the respective token's system address. This feature is enabled by the Hyperliquid protocol, more information can be [found here](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/hypercore-less-than-greater-than-hyperevm-transfers).

**Note: Users should understand this mechanism and its caveats before use.**&#x20;

Due to orderbook constraints, the number of decimals for a given token may vary between the HyperEVM and HyperCore. If you are transferring tokens to the environment in which the token has fewer decimals, it is recommended to only specify up to this amount, as [the non-round amount is burned](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/hyperevm/hypercore-less-than-greater-than-hyperevm-transfers#caveats). This is true for all spot tokens, including HYPE.

HyperEVM contracts are deployed from `0xB4FC973924a91362D301E583E839Cdaf4f19cdF8`. The Unit HyperEVM deployer is controlled via multi-party computation (MPC), requiring key-shares from multiple signers to construct and perform transactions, such as deployments.

<table><thead><tr><th width="128.53515625">Unit Token</th><th>HyperEVM Contract Address</th><th>Explorer Link</th></tr></thead><tbody><tr><td>Bitcoin</td><td><code>0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463</code></td><td><a href="https://hyperevmscan.io/address/0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463">https://hyperevmscan.io/address/0x9FDBdA0A5e284c32744D2f17Ee5c74B284993463</a></td></tr><tr><td>Ethereum</td><td><code>0xBe6727B535545C67d5cAa73dEa54865B92CF7907</code></td><td><a href="https://hyperevmscan.io/address/0xBe6727B535545C67d5cAa73dEa54865B92CF7907">https://hyperevmscan.io/address/0xBe6727B535545C67d5cAa73dEa54865B92CF7907</a></td></tr><tr><td>Solana</td><td><code>0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29</code></td><td><a href="https://hyperevmscan.io/address/0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29">https://hyperevmscan.io/address/0x068f321Fa8Fb9f0D135f290Ef6a3e2813e1c8A29</a></td></tr><tr><td>Pump</td><td><code>0x27eC642013bcB3D80CA3706599D3cdA04F6f4452</code></td><td><a href="https://hyperevmscan.io/address/0x27eC642013bcB3D80CA3706599D3cdA04F6f4452">https://hyperevmscan.io/address/0x27eC642013bcB3D80CA3706599D3cdA04F6f4452</a></td></tr><tr><td>Fartcoin</td><td><code>0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF</code></td><td><a href="https://hyperevmscan.io/address/0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF">https://hyperevmscan.io/address/0x3B4575E689DEd21CAAD31d64C4df1f10F3B2CedF</a></td></tr></tbody></table>


---

# 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.hyperunit.xyz/developers/key-addresses/mainnet/token-metadata.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.