GLP and GM Token Composition Standard

introduction

LIQUIDITY TOKEN BASKET SPECIFICATION

What the GLP and GM Token Composition Standard Defines

The canonical standard for the asset baskets, target weights, and mint/redeem logic backing GMX's GLP and GM liquidity provider tokens.

The GLP and GM Token Composition Standard is the core specification defining the multi-asset baskets that collateralize GMX's liquidity provider tokens. For GLP, the standard enumerates the basket of blue-chip assets—typically stablecoins, ETH, and BTC—along with their target weightings, which are governed by the DAO. For GM tokens, the standard defines a market-specific composition where a single GM token is backed by a basket of assets configured for that particular trading pool. This specification is the foundational reference for any protocol integrating GMX's liquidity tokens, as it dictates the exact assets a user holds exposure to when minting and the assets they receive upon redemption.

Operationally, the standard governs the mint and burn (redeem) interfaces, including the logic that determines which underlying asset a user provides or receives based on the current basket composition and target weights. It specifies the rebalancing mechanics that allow the vault to maintain target allocations, creating arbitrage incentives for minters and redeemers. A critical technical detail is the fee accrual mechanism: the standard defines how trading and borrowing fees are continuously reinvested into the basket, increasing the value of each token share without requiring a separate claim transaction. This auto-compounding behavior is a key integration consideration for yield aggregators and money markets, which must account for a token's value increasing against its underlying components.

For builders and risk teams, this standard is the authoritative source for understanding composition risk. A yield aggregator building a GLP wrapper must model how a user's deposit is routed to a specific asset and how a withdrawal might be fulfilled by a different asset, creating a taxable event or unwanted portfolio drift. A money market accepting GM tokens as collateral must monitor the health and liquidity of every asset in that specific GM pool's basket, as a depeg or oracle failure in one component can directly impair the collateral's value. Chainscore Labs helps integration teams audit their composition against this standard, verify correct mint/redeem handling, and build monitoring for the rebalancing and fee-accrual dynamics that define the token's behavior.

LIQUIDITY TOKEN BASKET STANDARD

GLP and GM Token Composition: Quick Facts

Key facts about the asset composition, rebalancing logic, and redemption behavior of GLP and GM tokens for integrators and risk teams.

Area	What changes	Who is affected	Action
Basket Composition	GLP and GM tokens represent a basket of assets with target weights. The composition and weights are governed by the DAO and can change via GIP.	Yield aggregators, money markets, bridges, liquidity providers	Monitor governance proposals for asset additions, removals, or weight changes. Verify against canonical source.
Mint/Redeem Interface	Users mint GLP/GM by depositing any whitelisted basket asset and burn to redeem any asset. The protocol may adjust redemption assets based on current vault weightings.	Wallets, exchanges, DeFi protocols integrating mint/burn functions	Implement logic to handle dynamic redemption paths. Review the Vault Architecture and Asset Listing Standard.
Rebalancing Logic	The vault's target weights create arbitrage incentives for external actors to rebalance. The protocol itself does not perform active rebalancing trades.	Arbitrageurs, traders, liquidity providers	Model the impact of weight divergence on GLP/GM price and redemption value. Do not assume static backing.
Fee Accrual	A portion of trading, borrowing, and liquidation fees are distributed to GLP/GM stakers, increasing the token's value relative to its basket.	Yield aggregators, dashboards, stakers	Account for fee accrual in NAV calculations. Reference the Fee Calculation and Distribution Module Standard.
Oracle Dependency	The value of the GLP/GM basket depends on the protocol's oracle aggregation for each constituent asset. Oracle failure or manipulation for any asset impacts the token's price.	Lending protocols using GLP/GM as collateral, bridges, risk teams	Assess oracle risk for each basket asset. Review the Oracle Aggregation and Pricing Interface Standard.
Composability Risks	Protocols integrating GLP/GM inherit the vault's asset exposure, oracle dependencies, and governance risks. A change in composition or a vault exploit directly affects downstream integrations.	Yield aggregators, money markets, leveraged vaults	Conduct a full integration risk assessment. Monitor the Incidents and Security Advisories group for vault-related events.
Multi-Chain Deployment	GLP/GM contracts exist on multiple chains. Composition, weights, and deployed assets may differ between deployments.	Cross-chain bridges, multi-chain DeFi protocols	Verify the specific basket composition and contract addresses for each chain. Consult the Multi-Chain Deployment and Contract Address Standard.

technical-context

LIQUIDITY TOKEN COMPOSITION

Basket Construction and Rebalancing Mechanics

How the GLP and GM token baskets are constructed, how target weights are set, and how rebalancing mechanics affect mints, redemptions, and composability risk.

The GLP and GM tokens are not static baskets; their composition is governed by a target-weight system that defines the ideal proportion of each asset backing the liquidity pool. For GLP, the basket typically includes a mix of stablecoins and blue-chip volatile assets like BTC and ETH, with weights set by GMX governance to balance liquidity depth against volatility exposure. GM tokens, introduced in GMX V2, isolate liquidity per market, meaning each GM pool (e.g., GM-BTC-USD) is backed by a single asset or a tightly constrained set, simplifying redemption logic but fragmenting liquidity across markets. The target weights are the primary lever for controlling vault risk and directly influence the mint/redeem interface behavior.

Rebalancing is not an active, forced process executed by the protocol. Instead, it is incentive-driven and occurs organically through arbitrage during minting and redemption. When the actual composition of a GLP pool diverges from its target weights—for example, holding too much ETH relative to USDC after a price rally—the mint and redeem pricing adjusts to make the overweight asset cheaper to redeem and the underweight asset more expensive to mint. This creates a profit opportunity for arbitrageurs who restore balance by minting with the underweight asset or redeeming for the overweight one. The getMintAmount and getRedeemAmount functions in the Vault contract encode this dynamic pricing, using the current pool composition relative to targets to calculate fees or discounts that drive rebalancing.

For integrators, this mechanic introduces a critical operational risk: the composition of a GLP or GM token at the time of minting is not guaranteed at the time of redemption. A yield aggregator that deposits USDC into GLP may later redeem a basket with a higher proportion of ETH if rebalancing has occurred, exposing users to unintended asset risk. Money markets accepting GLP as collateral must model this composition drift and apply appropriate haircuts. Bridges wrapping GLP for cross-chain use must handle the asynchronous redemption of a potentially shifted basket. Chainscore Labs reviews integration architectures to ensure they correctly model the getMintAmount and getRedeemAmount dynamics, validate composition assumptions against governance-controlled target weights, and build monitoring for significant weight divergences that could signal elevated redemption risk.

IMPACT ANALYSIS

Who Is Affected by the Composition Standard

Yield Aggregators

Protocols that auto-compound or optimize yields on GLP and GM tokens must model the underlying basket composition to manage risk. Changes to target weights or rebalancing logic directly affect the volatility profile of the LP token.

Action Items:

Recalculate expected returns and drawdown models when composition parameters change.
Monitor mint/redeem fees and adjust vault strategies to avoid unprofitable cycles.
Verify that your vault's slippage tolerance accounts for the liquidity depth of the underlying basket assets.

Chainscore Labs can review your yield strategy's dependency on GLP/GM composition assumptions and model the impact of parameter changes before they reach on-chain voting.

implementation-impact

GLP AND GM COMPOSITION

Integration Impact and Key Considerations

The GLP and GM token composition standard defines the basket of assets backing GMX's liquidity tokens. Integrators must understand target weights, rebalancing logic, and redemption behavior to manage risk and ensure correct accounting.

Redemption Behavior and Liquidity Risk

GLP and GM tokens do not redeem for a fixed basket; they redeem for the vault's current asset composition. During high volatility or skewed market conditions, a redemption may return a disproportionate amount of a volatile or illiquid asset. Yield aggregators and money markets must model worst-case redemption scenarios, not just the target weights, to avoid unexpected portfolio drift or withdrawal failures.

Target Weight vs. Actual Composition Drift

The standard defines target weights, but actual vault composition drifts with trader PnL and market movements. Integrators must monitor the delta between target and actual weights. A large deviation signals that rebalancing is required and that minting or redeeming will have a different asset impact than expected. Build dashboards that track this drift as a key operational metric.

Mint/Redeem Interface and Slippage Controls

The mint and redeem functions accept parameters to control the acceptable asset composition. Integrators must implement strict slippage checks based on the current vault composition to prevent sandwich attacks or unfavorable execution. Wallets and aggregators should surface the expected asset breakdown to users before they sign, not just a single token amount.

Fee Accrual and Accounting Complexity

GLP and GM tokens auto-compound trading fees and liquidation gains directly into the token's redeemable value. This means the token balance in a wallet does not increase; the value per token does. Accounting systems, tax tools, and portfolio trackers must calculate cost basis using a share-based approach, not a simple balance change, to correctly report gains and losses.

Cross-Chain Composition Differences

GMX deploys GLP and GM pools on multiple chains (Arbitrum, Avalanche). Each pool has a distinct asset composition and risk profile. A bridge or yield aggregator must never assume fungibility between pools on different networks. Treat each chain's liquidity token as a separate asset with its own composition standard, oracle set, and risk parameters.

Oracle Dependency Inherited by Integrators

The vault's asset valuation for mint and redeem pricing relies entirely on Chainlink oracles. Any protocol that uses GLP or GM as collateral inherits this oracle dependency. A stale or manipulated oracle price directly impacts the token's mint/redeem rate. Integrators must monitor GMX's oracle heartbeat and deviation thresholds as part of their own risk control framework.

GLP AND GM TOKEN COMPOSITION STANDARD

Composition and Integration Risk Matrix

Evaluates the technical risks and operational impacts for protocols integrating GLP and GM liquidity tokens, based on the asset backing, rebalancing logic, and redemption interfaces defined in the standard.

Area	Failure Mode	Severity	Affected Integrators	Mitigation / Action
Asset Basket Drift	Target weights diverge significantly from actual vault composition due to market volatility or failed rebalancing, causing GLP/GM to not track the intended index.	High	Yield aggregators, money markets, structured products	Monitor vault composition on-chain against stated target weights. Model worst-case redemption scenarios where the basket is concentrated in a depreciating asset.
Rebalancing Front-running	Automated rebalancing transactions create predictable on-chain activity, allowing MEV searchers to extract value at the expense of GLP/GM holders.	Medium	Vault share token holders, arbitrageurs	Analyze rebalancing keeper mempool behavior. Integrators should account for potential NAV erosion between rebalance events when pricing GLP/GM as collateral.
Redemption Queue Congestion	High redemption demand for a specific asset in the basket exceeds available liquidity, delaying withdrawals and forcing partial redemptions in other assets.	High	Bridges, lending protocols, leveraged vaults	Implement circuit breakers or slippage limits on GLP/GM redemptions. Do not assume instant 1:1 redeemability for any single constituent asset.
Stablecoin Depeg Contamination	A stablecoin in the basket (e.g., USDC, DAI) loses its peg, causing GLP/GM NAV to drop and potentially triggering cascading liquidations in lending markets using it as collateral.	Critical	Lending protocols, CDP platforms, treasury managers	Stress test GLP/GM collateral value under constituent depeg scenarios. Set conservative Loan-to-Value (LTV) ratios that account for the worst-performing basket asset.
Mint/Redeem Interface Change	An upgrade to the Vault contract alters the mint or redeem function signatures, fees, or asset acceptance logic, breaking downstream integrations.	High	All integrators	Monitor GIPs and on-chain governance for vault upgrade proposals. Verify contract interfaces against the canonical ABI before each deployment. Chainscore Labs can perform an upgrade readiness review.
Oracle Dependency Cascade	GLP/GM pricing relies on the GMX Oracle Aggregation Standard. A failure or manipulation of a constituent asset's price feed corrupts the NAV calculation.	Critical	Oracles, pricing engines, liquidators	Do not blindly consume a derived GLP/GM price. Independently verify the aggregate oracle logic and monitor heartbeat and deviation for each basket asset's feed.
Cross-Chain Composition Divergence	GLP/GM on different chains have different basket compositions and risk profiles, but are treated as fungible or equivalent by bridges or yield aggregators.	High	Cross-chain bridges, multi-chain yield optimizers	Treat GLP/GM as distinct, chain-specific assets. Verify composition and risk parameters for each chain deployment. Never assume a unified cross-chain price.
Fee Accrual Opacity	Integrators incorrectly calculate the value of accrued fees within GLP/GM, leading to mispricing in secondary markets or incorrect reward distribution.	Medium	Wallets, portfolio trackers, reward distributors	Use the canonical Fee Calculation Standard to model fee accrual. Validate on-chain that claimed rewards match expected values before distribution to users.

GLP AND GM TOKEN COMPOSITION

Integration Readiness Checklist

A technical checklist for protocols integrating GLP or GM liquidity tokens. Each item identifies a critical integration assumption, the risk it mitigates, and the signal that confirms readiness before deployment.

What to check: Confirm the current basket of assets backing GLP or the specific GM pool you are integrating. Validate the target weight for each asset against the canonical Vault contract's getTokenWeights or equivalent read function.

Why it matters: The composition directly determines the token's risk profile. A yield aggregator or money market that accepts GLP as collateral inherits the volatility and correlation risk of every underlying asset. An incorrect assumption about composition can lead to mispriced risk and bad debt.

Readiness signal: Your integration logic dynamically fetches token weights on-chain and can gracefully handle the addition or removal of assets via governance. Hardcoded asset lists in your codebase are a red flag.

resource-links

GMX LIQUIDITY TOKEN COMPOSITION REFERENCES

Canonical Resources and References

Use these resources to verify the current GLP basket, GM market-token composition, mint and redeem behavior, governance changes, and implementation assumptions before integrating GMX liquidity tokens.

GMX Official Documentation

Start with the official GMX documentation when validating GLP and GM token mechanics. For GLP, teams should confirm the supported assets, target weights, fee behavior, and redemption constraints for the relevant network. For GM tokens in GMX V2, review how each market token represents liquidity in a specific market with long-token and short-token pool exposure rather than a single protocol-wide basket. Integrators should treat the docs as an orientation layer, then verify live parameters and contracts before pricing, lending against, bridging, or auto-compounding these assets.

EXPLORE

GMX V1 Contracts Repository

The gmx-contracts repository is the primary source for reviewing the V1 architecture that underpins GLP integrations. Security reviewers and protocol engineers should inspect vault, router, reward, and liquidity-related contract logic rather than relying only on frontend assumptions. For GLP-backed strategies, confirm how minting, burning, asset accounting, fees, and manager permissions are implemented on the target deployment. Any money market, vault, or bridge accepting GLP should map its risk controls to the actual contract behavior, including pause paths, privileged roles, and reward-accounting dependencies.

EXPLORE

GMX V2 Synthetics Repository

The gmx-synthetics repository is the key implementation reference for GMX V2 market tokens and isolated market liquidity. GM token integrations should review datastore keys, market configuration, deposit and withdrawal flows, oracle validation, callback behavior, and market-token accounting directly in the codebase. Unlike GLP, GM exposure is market-specific, so a token’s risk depends on that market’s long token, short token, open interest, borrowing configuration, price impact settings, and oracle inputs. Builders should pin audited commit references internally and re-check repository changes before supporting new markets.

EXPLORE

GMX Governance Forum

The GMX governance forum is the operational reference for proposed changes that can affect GLP and GM composition, including market listings, parameter updates, fee changes, oracle changes, and liquidity migration plans. Risk teams should monitor forum proposals before they become active because composition risk can change without a token interface change. For each proposal, identify whether it affects asset eligibility, target exposure, redemption liquidity, market caps, borrowing fees, open interest limits, or treasury-controlled settings. Integrators should maintain an internal review process for governance posts that touch accepted collateral or vault-token valuation.

EXPLORE

GMX Snapshot Space

Snapshot voting is an important signal source for GMX governance decisions, even when execution details may occur through separate operational or on-chain steps. Teams integrating GLP or GM tokens should monitor Snapshot proposals for composition-impacting changes and distinguish signaling outcomes from deployed contract changes. A passed vote should not be treated as live implementation until canonical contracts, parameters, and frontend or documentation updates are verified. For production systems, connect governance monitoring to risk limits so lending caps, vault allocations, and supported-market lists can be adjusted before material exposure changes.

EXPLORE

GMX Stats and Live Market Monitoring

GMX Stats is useful for observing live protocol conditions that affect liquidity-token risk, including market activity, pool utilization, open interest, fees, and network-specific behavior. It should not replace contract-level verification, but it helps risk teams detect when GLP or GM exposure is becoming concentrated, when redemption pressure is increasing, or when a specific market is operating near configured limits. Protocols using GLP or GM as collateral should combine stats monitoring with on-chain reads, oracle health checks, and governance alerts before changing collateral factors or strategy allocations.

EXPLORE

Chains We Build On

Looking to build on a specific blockchain?

We build smart contracts, DeFi applications, wallets, tokenization platforms, and blockchain infrastructure across the major ecosystems teams choose today. That includes Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Solana, Sui, Aptos, Hedera, Stellar, and NEAR, with support for additional EVM and non-EVM networks based on your product requirements.

Learn More

EVM ecosystems

Ethereum
Arbitrum
Optimism
Polygon
Avalanche
Cronos

Non-EVM ecosystems

Solana
Sui
Aptos
Hedera
Stellar
NEAR

Additional ecosystems

Polkadot
Cosmos
TON
Cardano
Algorand
Tempo

Also available for Base, appchains, custom EVM networks, and cross-chain product architecture.

GLP AND GM COMPOSITION FAQ

Frequently Asked Questions

Common questions from integrators, risk teams, and protocol architects about the asset basket backing GLP and GM tokens, redemption behavior, and composition risks.

GLP and GM tokens represent a pro-rata claim on a basket of assets held in the GMX Vault. The composition is not fixed; it is governed by target weights set through GMX governance.

What to check:

The canonical list of whitelisted assets and their current target weights, which are published in the GMX documentation and verifiable via governance proposals.
The actual vault balances versus target weights, which can diverge due to market movements and mint/burn activity.

Why it matters:

The basket composition directly affects the risk profile of holding the token. A concentration in volatile or correlated assets increases drawdown risk for liquidity providers.
Yield aggregators and money markets that accept GLP/GM as collateral must model the worst-case value of the underlying basket, not just the token's market price.

Signal to monitor:

Governance proposals that adjust target weights, add new assets, or delist existing ones. A change in composition can alter the risk and return profile overnight.

Trusted by Industry Leaders

Delivering blockchain solutions for 5+ years.

We have partnered with 50+ leading DeFi protocols, NFT ecosystems, and fintech innovators to build secure, scalable, and capital-efficient blockchain products.

Selected Partners & Clients

“I've been working with Chainscore Labs for last 3+ years, they've consistently delivered with strong ownership across multiple projects. The team is reliable and detail-oriented.”

Lee Erswell

CEO, Telos Foundation

how to get started

How to get started?

If you're looking for blockchain integration, ChainScore Labs has 5+ years of experience helping teams build and integrate exchanges, wallets, smart contracts, tokenization solutions, and protocol-connected products, we can help you choose the right path, integrate securely, and get to production faster. Our team consists of experienced blockchain developers and architects who can help you with your blockchain integration needs.

Exploration & Strategy

Define your product goals and choose the right blockchain architecture for your use case.

Architecture & Design

Design the smart contracts, tokenomics, and security parameters of your system.

Development & Integration

Build and integrate with wallets, oracles, and front-end dApps for a seamless experience.

Security & Launch

Comprehensive audits followed by a risk-managed mainnet deployment to protect your users.

Learn More

Explore More Solutions

Discover our
blockchain development services.

We build production-grade blockchain solutions for top-tier projects across DeFi and Web3.

Book a Call

DeFi Protocol Development

End-to-end development of custom DeFi protocols including core smart contracts and system architecture.

DEX & Exchange Development

Building high-performance decentralized exchanges with optimized liquidity and advanced trading logic.

Lending & Borrowing Platforms

Scalable credit markets and money protocols built for production-grade liquidity and security.

What the GLP and GM Token Composition Standard Defines

GLP and GM Token Composition: Quick Facts

Basket Construction and Rebalancing Mechanics

Who Is Affected by the Composition Standard

Yield Aggregators

Integration Impact and Key Considerations

Redemption Behavior and Liquidity Risk

Target Weight vs. Actual Composition Drift

Mint/Redeem Interface and Slippage Controls

Fee Accrual and Accounting Complexity

Cross-Chain Composition Differences

Oracle Dependency Inherited by Integrators

Composition and Integration Risk Matrix

Integration Readiness Checklist

Canonical Resources and References

GMX Official Documentation

GMX V1 Contracts Repository

GMX V2 Synthetics Repository

GMX Governance Forum

GMX Snapshot Space

GMX Stats and Live Market Monitoring

Looking to build on a specific blockchain?

Frequently Asked Questions

Delivering blockchain solutions for 5+ years.

How to get started?

Exploration & Strategy

Architecture & Design

Development & Integration

Security & Launch

Discover our blockchain development services.

DeFi Protocol Development

DEX & Exchange Development

Lending & Borrowing Platforms

Need a blockchain engineering team?

Discover our
blockchain development services.