# Fees and limits

> The numbers that constrain a transfer on USD Network.

| Limit | Value |
| --- | --- |
| Transfer fee | 0.01 USD₮ |
| Amount precision | 6 decimals (1 unit = 0.000001 USD₮) |
| Smallest transfer | 0.000001 USD₮ |
| Memo length | 140 characters |
| Transfers per block | Up to 500 |
| Heartbeat interval | One empty block an hour when idle |
| Faucet (testnet) | 100 USD₮ per address per 24 hours, one request per IP per minute |
| New read passes checked | 120 a minute per IP, 30 a minute per address (a pass is checked once, then reused) |
| Balance proofs | 20 a minute per IP, 10 a minute per address |
| Transfers submitted | 120 a minute per IP |
| Deposit checks (`POST /bridge/check`) | 20 a minute per IP |

Over a limit, the API answers `429` with a `retry-after` header in seconds. Public reads (`/stats`, `/blocks`, `/txs`, `/block/:height`, `/bridge`, `/checkpoint`, proofs) are served from the edge cache for a few seconds, so polling them is cheap and needs no limit.

## Amounts

Amounts are sent and returned as decimal strings, such as `"12.5"` or `"0.000001"`, never as floating-point numbers. Internally, balances are integers of the smallest unit, so there is no rounding.

## Nonces

Each transfer must carry the sender's current nonce, which starts at 0 and increases by one with every sealed transfer. A transfer with any other nonce is rejected with status `409`, and the error tells you the expected nonce. Read the current nonce from `GET /address/:address` with a [read pass](/build/api#confidential-reads).

## Memos

A memo is optional free text, up to 140 characters, included in the signed message and stored with the transfer. Like the rest of a transfer it is [confidential](/wallet/confidential), but anyone you share a receipt with sees it, and USD.NET can see it. Do not put personal data in it.
