Supported Markets & Leverage

Yamata Perpetuals will launch with a selection of popular crypto asset markets, each quoted against USDC. This section lists the initial supported perpetual markets and their leverage limits, as well as notes on contract specifications. Yamata will continuously expand market offerings, but risk management considerations dictate the maximum leverage for each asset.

Available Perpetual Markets

At launch, Yamata is expected to support the following perpetual futures contracts (all settled in USDC):

Market	Underlying Asset	Description	Max Leverage (Initial)
BTC-PERP	Bitcoin (BTC)	Perpetual swap for BTC price, quoted in USDC. 1 contract = 1 BTC.	50×
ETH-PERP	Ethereum (ETH)	Perpetual swap for ETH price, in USDC. 1 contract = 1 ETH.	50×
ARB-PERP	Arbitrum (ARB)	Perpetual contract for ARB token (Layer2 token) vs USDC.	20×
SOL-PERP	Solana (SOL)	Perpetual contract for SOL vs USDC.	20×
OP-PERP	Optimism (OP)	Perpetual contract for OP token vs USDC.	20×
LINK-PERP	Chainlink (LINK)	Chainlink token perpetual vs USDC.	20×
DOGE-PERP	Dogecoin (DOGE)	Dogecoin perpetual vs USDC.	10×
ADA-PERP	Cardano (ADA)	Cardano token perpetual vs USDC.	10×
MON-PERP	Monad	Monad token perpetual vs USDC.	10×
SOMI-PERP	Somnia	Somnia token perpetual vs USDC.	10×
…	More to come	Yamata will list additional assets based on demand and liquidity.	Varies

Notes:

• The above is an illustrative list. The precise assets at launch may vary. Major large-cap assets like BTC and ETH will definitely be included, with high leverage available. Mid-cap and newer assets (ARB, OP, etc.) are also planned, typically with moderate leverage limits to start.

• Max Leverage means the highest leverage factor allowed when trading that market. 50× implies 2% initial margin requirement; 20× implies 5% margin; 10× implies 10% margin. Yamata sets these limits based on asset volatility and liquidity – more volatile assets have lower max leverage to ensure stability.

Leverage Tiers and Position Size Limits

Yamata employs a tiered leverage system to manage risk for large positions:

• All markets support the maximum leverage for small to medium position sizes. As your position grows in notional value, the effective maximum leverage may be reduced. This is done by increasing margin requirements for larger notional tiers.

• For example, Yamata might allow up to 50× on the first $500k of BTC-PERP position notional. For notional beyond that, the required margin gradually increases (e.g., equivalent to 20× max on notional above $5M, etc.). This means institutional-scale traders can’t take 50× on extremely large positions – they would need to post more collateral proportionally.

• These position tiers ensure that the platform’s exposure is controlled and the insurance fund isn’t at risk from a single huge highly-levered position. The majority of retail traders will not hit these limits, but it’s good to be aware that maximum leverage is a function of position size.

• Yamata will publish a detailed Margin Tier Table for each asset. Typically it looks like: e.g., for BTC-PERP:

  • 0–$1M notional: 50× allowed (2% margin)

  • $1M–$5M: 20× (5% margin)

  • $5M+ : 10× (10% margin), etc. (These are examples; refer to official numbers.)

Contract Specifications

• Contract Size: For linear contracts like BTC-PERP, one contract represents 1 BTC. For some lower-priced assets, Yamata might define 1 contract as a larger unit (e.g., 1000 units of an asset) to avoid overly small price increments. The documentation will clarify per asset if it’s not 1:1.

• Price Increments (Tick Size): Each market has a minimum price increment (tick). For example, BTC-PERP price may tick in 0.5 USDC increments, while something like DOGE-PERP might tick in 0.0001 USDC increments given its lower price. The trading interface enforces these ticks.

• Quantity Increments (Lot Size): Similarly, there may be a minimum trade size. E.g., 0.001 BTC might be the smallest increment for BTC-PERP. These ensure efficient handling and are usually very small to accommodate all trader sizes.

• Funding Interval: Most markets will have funding every hour or every 8 hours. Yamata might set major assets (BTC, ETH) to frequent funding (e.g., 1-hour) for tighter price sync, and alts to a bit longer (e.g., 4-hour or 8-hour) if needed. The current interval and next funding time is displayed per market.

• Index Price Sources: Each perpetual uses an index comprised of prices from reliable exchanges or oracles. Yamata likely sources from top exchanges (Coinbase, Binance, etc.) or decentralized oracles for each asset to compute the index. This guards against anomalies on any single venue.

• Settlement Asset: All listed contracts settle in USDC (as a stablecoin, effectively pegged to USD). There are no inverse contracts (which would settle in the crypto itself) in Yamata’s Perps – this simplifies multi-collateral and risk management.

Adding New Markets

Yamata’s goal is to unify “every market, one platform.” New perpetual markets will be added over time, including possibly:

• Additional large-cap coins (LTC, XRP, etc if not at launch).

• Promising mid-cap and DeFi tokens.

• Possibly indices or sector baskets in the future.

• Community-voted listings based on demand.

When new markets are added:

• They may start with conservative leverage (e.g., 10×) and then increase as liquidity grows.

• Announcements will be made, and documentation updated with the contract specs.

• Ensure you familiarize with any unique aspects of the new contract (some might have different funding mechanics or higher volatility).

Multi-Chain Support and Markets

At launch, Yamata Perps operate on the Monad chain (an EVM Layer-1 optimized for trading). However, Yamata will expand to multiple chains (Somnia, Sonic, MegaETH and more). Cross-chain support means you could trade, for instance, BTC-PERP from Ethereum or Base – the backend handles the bridging of liquidity.

The list of markets remains the same across chains, although certain collaterals or features might be chain-specific. Yamata’s account abstraction will make using multiple chains seamless in the UI.