This file has been truncated. show original
# How to create a new pool with IBC assets
Osmosis is a automated market maker blockchain. This means any IBC-enabled zone can add its token as an asset to be traded on Osmosis AMM completely permissionlessly. Because Osmosis is fundamentally designed as an IBC-native AMM that trades IBC tokens, rather than tokens issued on the Osmosis zone, there are additional nuances to understand and steps to be taken in order to ensure your asset is supported by Osmosis.
This document lays out the prerequisites and the process process that's needed to ensure that your token meets the interchain UX standards set by Osmosis.
1. Zone must have IBC token transferred enabled (ICS20 standard).
2. Assets to be traded should be a fungible `sdk.Coins` asset.
3. Highly reliable, highly available altruistic (as in relay tx fees paid on behalf of user) relayer service.
4. Highly reliable, highly available, and scalable RPC/REST endpoint infrastructure.
### 0. Enabling IBC transfers
Because only IBC assets that have been transferred to Osmosis can be traded on Osmosis, the native chain of the asset must have IBC transfers enabled. Cosmos defines the fungible IBC token transfer standard in [ICS20](https://github.com/cosmos/ibc/tree/master/spec/app/ics-020-fungible-token-transfer) specification.
At this time, only chains using Cosmos-SDK v0.40+ (aka Stargate) can support IBC transfers.
Note that IBC transfers can be enabled via:
1. as part of a software upgrade, or