# Exchanges and custodians

> Plan asset identification, deposits, withdrawals, and finality handling against the draft IceRoot integration model.

Source: https://docs.iceroot.com/developers/exchanges/

This is the [draft protocol’s](https://docs.iceroot.com/core/protocol-design/index.md) proposed custody model. Node endpoints and SDK packages must be verified against an actual release before use.

## Identify and credit deposits

Allow-list assets by **AssetID**. Any account can receive an asset, so an unfamiliar balance must not automatically become a credited customer deposit.

The draft offers two account models:

- **Tagged deposits:** one deposit account with a per-customer memo tag.
- **Address pool:** per-customer addresses generated offline, using hardened derivation.

Credit only when the matching transaction is final. In the proposed node API, that means `finalized: true`. Confirmations count progress; they do not replace finality.

Check the network of every address. In the draft, mainnet addresses start with `ice1` and public-testnet addresses with `tice1`.

## Prepare withdrawals

The draft transfer has one memo for the entire transaction. Tagged recipients therefore need separate transactions. Untagged recipients can be batched within the protocol’s recipient limit, proposed as 256.

Read these values from the selected node before signing:

- Account nonce.
- Required fee.
- Public-key registration state.
- Transaction format version.

Preserve integer amounts and asset precision throughout construction, signing, and accounting.

## Integration surfaces

| Proposed service     | Responsibility                                                                               |
| -------------------- | -------------------------------------------------------------------------------------------- |
| Relay REST API       | State, fees, configuration, individual records, broadcast                                    |
| Indexer              | Historical search and saved-event notifications through SSE                                  |
| Mesh gateway         | Data API plus Construction `submit`, `hash`, and `parse`                                     |
| Shared Rust SDK core | Encoding and signing, used from TypeScript through WebAssembly and from Go through a binding |

The proposed Mesh gateway exposes finalized history as its tip. Transaction construction and signing belong to the SDK; the gateway does not offer every Mesh Construction operation.

## Voting and customer funds

The draft’s onboarding guide includes an exchange voting commitment: an exchange commits not to vote with its customers’ ROOT and names any validator it runs. The commitment is a published policy, not a consensus rule. Separately, consensus gives zero vote weight to any account holding more than 5% of ROOT’s supply, so a large custodial or omnibus balance does not automatically become election power just because the exchange controls its keys. That rule does not stop a holder from splitting ROOT across smaller accounts; it makes that a deliberate step. Arrangements with exchanges and custodians are made in writing.

## Custody gateways and releases

An exchange or custodian that issues an IceRoot asset on another chain can run a custody gateway: an ordinary IceRoot account, labeled with its operator’s name, whose holdings are visible. See [Custody gateways](https://docs.iceroot.com/developers/custody-gateways/index.md) for labels and what an operator publishes.

Release announcements, with their checksums and activation heights, are mirrored on [Network status](https://docs.iceroot.com/network/status/index.md).

## What can be tried now

The [explorer API](https://docs.iceroot.com/developers/explorer-api/index.md) provides a read-only view of one relay on the public lab devnet. It is not a source of truth for exchanges or custody. The [wallet provider](https://docs.iceroot.com/developers/wallet-provider/index.md) supports the portal’s devnet signed login. Neither is a deposit-crediting or withdrawal service.
