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

# Accept and hold USDh

> What a wallet, exchange, payment app or treasury needs to know to support USDh.

**Supporting USDh takes the same work as supporting USDC.** This page covers the few details that are specific to USDh.

## The basics

| | |
| - | - |
| Address | `0xbcFC42391e55484129191eDfcC766a2c6F9eb503` on Ethereum mainnet (chain ID 1) |
| Symbol and name | `USDh` |
| Decimals | 6. One USDh is `1000000` base units |
| Interface | Standard ERC-20 (`transfer`, `approve`, `transferFrom`, `balanceOf`, `totalSupply`) |
| Burn | Holders can destroy their own USDh with `burn`. This does not pay anything out. Only Mint Users redeem for dollars |

## Approvals without gas (EIP-2612)

USDh supports `permit`. A user signs an approval off-chain, and your contract submits it together with the action that uses it. The user pays no gas for the approval.

| Signing domain field | Value |
| - | - |
| `name` | `USDh` |
| `version` | `1` |
| `chainId` | `1` |
| `verifyingContract` | `0xbcFC42391e55484129191eDfcC766a2c6F9eb503` |

## Transfers without gas (EIP-3009)

USDh supports `transferWithAuthorization` and `receiveWithAuthorization`, the same functions USDC uses. A user signs a transfer, and anyone can submit it on their behalf.

* Each authorization uses a random 32-byte `nonce` and a time window (`validAfter`, `validBefore`).
* Use `receiveWithAuthorization` when a contract receives the funds. It only accepts the call from the receiver, which stops someone else from front-running it.
* Contract wallets such as Safes can sign, through EIP-1271.
* An unused authorization can be cancelled with `cancelAuthorization`.

## Before you go live

**1. Use the proxy address**

Check it against [Contracts](https://docs.hamilton.xyz/for-developers/contract-addresses.md). Never use the implementation address.

**2. Read decimals from the contract**

Do not assume 6.

**3. Handle a paused system and a frozen address**

Both make transfers fail. Your app should show a clear message, not break. See [Handle pauses, freezes and limits](https://docs.hamilton.xyz/for-developers/errors-and-limits.md).

**4. Watch for scheduled changes**

Every change to USDh is scheduled on the timelock 48 hours before it can take effect. Watch for `CallScheduled` events on the [timelock](https://etherscan.io/address/0x9461ffd88ec07884338c7a2db648d4d82f0a98d3).

*Last updated: 17 November 2026*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.