Mayaprotocol
Mayaprotocol: assets for MAYAChain swaps
MAYAChain, the cross-chain liquidity network within Maya Protocol, connects listed assets through pools that share CACAO. Its documented pool list covers Bitcoin, Ethereum, Arbitrum, Dash, Kujira, THORChain, Radix and Zcash. Swaps require the relevant pools to have left the bootstrap phase, and ZEC support is limited to transparent addresses.
- last updated
Jump to a topic
Documented swap assets by network
Maya Protocol’s Getting Started guide identifies the following pools as active. Availability for a particular swap also depends on the pools’ operating state and the selected interface’s support for the route.
| Network | Assets in the documented active-pool list |
|---|---|
| Bitcoin |
Native BTC:
BTC.BTC
|
| Ethereum |
ETH and the Ethereum tokens USDC, USDT, WBTC and DAI:
ETH.ETH
,
ETH.USDC
,
ETH.USDT
,
ETH.WBTC
and
ETH.DAI
|
| Arbitrum |
ARB and the Arbitrum tokens USDC, USDT and DAI:
ARB.ARB
,
ARB.USDC
,
ARB.USDT
and
ARB.DAI
|
| Dash |
Native DASH:
DASH.DASH
|
| Kujira |
KUJI and USK:
KUJI.KUJI
and
KUJI.USK
|
| THORChain |
RUNE:
THOR.RUNE
|
| Radix |
Native XRD:
XRD.XRD
|
| Zcash |
Native ZEC:
ZEC.ZEC
. Transparent addresses only.
|
Chain support and pool eligibility
A supported blockchain can contain many more tokens than MAYAChain has tradable pools for. The eligibility requirement applies to the individual asset.
- Asset listing
- The Swappers guide describes depositing a new asset to place it in the listing queue. That deposit doesn’t immediately enable swaps: the pool must be added to the network and move beyond bootstrap.
- Staged pools
-
The Getting Started guide separates its active-pool list from staged listings, including
ETH.PEPEand additional Arbitrum tokens. A staged listing doesn’t establish that an asset is available for trading. - Interface support
- Maya Protocol provides backend infrastructure. A wallet or frontend must support the chains and assets involved to expose a usable swap route. An interface’s broader asset catalogue can extend beyond MAYAChain’s own pool coverage.
The network is part of the asset’s identity
- ETH.USDC and ARB.USDC
- These entries identify USDC on Ethereum and USDC on Arbitrum respectively. The chain prefix distinguishes their pools, so selecting USDC also requires selecting its network. A listing on one network doesn’t establish availability on another.
- BTC.BTC and ETH.WBTC
-
BTC.BTCidentifies native Bitcoin, whileETH.WBTCidentifies WBTC as an Ethereum token. MAYAChain doesn’t require assets to be wrapped or pegged as part of its native swap mechanism, but its supported pools can include an already wrapped token such as WBTC. Those entries retain their different asset forms and networks.
CACAO connects the pools without a separate purchase
Each external-asset pool pairs its asset with CACAO. This common settlement asset links the pools without requiring a dedicated pool for every possible asset pair. For swaps between two listed external assets, MAYAChain handles the exchange through CACAO internally.
Swappers don’t need to acquire or handle CACAO first for ordinary supported-asset swaps. CACAO can also be a swap destination. Other transaction types may require CACAO fees.
Swap costs still apply
The Swappers guide identifies an outbound network fee and price slippage as swap costs. It describes the network fee as dynamic, based on recent gas prices. Trade size relative to pool depth affects slippage, so an asset’s presence in the pool list doesn’t establish a fixed exchange cost or received amount.