Introduction Following community discussion, public postings, and the recent AMA, this proposal outlines the next steps in the GMX bridge selection process and provides further clarity on GSR-related contributions from each bidding party.
This vote is part of a broader bridge initiative and focuses on messaging infrastructure, which will be critical in enabling secure intent-based bridging and communication between GMX deployments on multiple chains.
GMX contributors were authorized to conduct private commercial negotiations on behalf of the DAO, including verifying terms, clarifying Safety Reserve contributions, and ensuring alignment with the DAO’s strategic goals.
Motivation As GMX expands to multi-chain, selecting a secure, composable, and well-aligned messaging bridge partner is a key infrastructural decision. Each protocol’s bid has been evaluated based on technical compliance, contribution to the GMX Strategic Reserve (GSR), and alignment with the DAO’s long-term goals.
The shortlisted candidates Chainlink, LayerZero, and Wormhole - Axelar have been assessed on:
. Technical compliance and maturity of the solution
. Contributions to the GMX Strategic Reserve (GSR)
. Alignment with GMX values
Rationale
The primary focus of this evaluation is on selecting a messaging bridge partner to secure the cross-chain movement of GMX-native assets ($GMX, GMs, GLV), support future chain expansion, and enable composable cross-chain messaging. While GMX initially encouraged proposals combining messaging and low-latency bridging for assets like USDC, ETH, and BTC, we recognize the fast-bridging landscape is evolving rapidly. As such, we have chosen not to lock into a single asset-bridging partner at this time and will continue evaluating the best long-term solution. Future partnerships for low-cost bridging may still be negotiated separately and could involve the chosen messaging provider, though this is not a strict requirement.
On the commercial front, all protocols have offered varying degrees of financial support and conditional contributions to the GMX Strategic Reserve (GSR), with terms kept private to preserve negotiation flexibility. While technical proposals are public, GMX contributors will limit public commentary on financial details, only indicating whether a proposal aligns with baseline expectations. Final agreements will codify all commitments, and any material deviations will require DAO re-approval.
Negotiations & GSR Involvement As noted in the previous update, contributors have been in discussions with potential messaging bridge partners regarding their involvement in supporting the GSR. These negotiations, outlined in the tender process, will be conducted with Labs for the benefit of the DAO, though not all details may be publicly disclosed.
Guidance on GSR Contributions Below is an overview of how each partner proposes to align with the GSR, which is a program designed to create a long term safety and security program for the protocol.
For more Information on the GSR: Proposal to Establish the GMX Safety Reserve (GSR)
Chainlink
- Compliant
- Full coverage of Chainlink products and select global occurrences No token swap proposed
. LayerZero
- Compliant
- Includes proposed GSR support and token swaps under the tender terms
. Wormhole
- Alternatively Compliant
- Proposes a conditional future token swap in place of a direct contribution
Candidate Details & GSR Summary
- Chainlink - The GMX <> Chainlink <> Across proposal presents a hybrid cross-chain solution by integrating Chainlink’s Cross-Chain Interoperability Protocol (CCIP) with Across Protocol’s intents-based bridging, enabling secure, fast, and low-cost asset transfers across chains. Building on GMX’s current use of Chainlink Data Streams, the solution leverages CCIP’s secure messaging, Risk Management Network, and 23+ decentralized node operators alongside Across’s rapid bridging infrastructure, connected through a custom-built intent router built by Chainlink Labs for the GMX DAO. Key use cases include fast deposits/withdrawals and secure transfers of GMX-native assets like GMX and GLV, using the CCIP Cross-Chain Token (CCT) standard. With 28+ audits, minimal trust assumptions, and no development costs for GMX, the system ensures security and cost-efficiency. Transfers are near-instant, with fees as low as 1–3 bps, $0.05 for small transactions, and $0.25 for CCIP CCT transfers—further reduced by potential token issuer subsidies. If approved, implementation will proceed in two phases, beginning with an initial deployment in 2–3 months, followed by broader multi-chain expansion, supporting GMX’s long-term cross-chain ambitions.
More details of the Chainlink proposal can be found here: Bridging & Messaging Partner for GMX - Chainlink
- LayerZero - The GMX x LayerZero proposal introduces LayerZero as GMX’s cross-chain interoperability partner, utilizing its Omnichain Fungible Token (OFT) standard and Decentralized Verifier Network (DVN) to enable secure, low-cost bridging of $GMX and GMX-native assets across 120+ blockchains. Backed by major users like PayPal, BitGo, and Tether, LayerZero secures over $100B+ in assets and offers an immutable, audited protocol with the second-largest bug bounty in crypto. GMX would retain full control over its OFT contracts, fees, and security, with no vendor lock-in and no bridging fees beyond gas costs—e.g., $0.10–$0.30 per transfer (Arbitrum to Optimism). The DVN model allows GMX to run or choose from 40+ verifiers like Google or Axelar, and offers features like lzRead for cross-chain governance, sync pools, and multi-token transfers. With 5–60 second finality, regulatory tools, and support for non-EVM chains like Solana and TON, the proposal outlines a two-phase rollout, starting April 2024. This solution offers GMX a flexible, future-proof, and enterprise-grade pathway to omnichain expansion.
More details of the Layerzero proposal can be found here: Bridging & Messaging Partner for GMX - LayerZero
- Wormhole - Axelar - The Axelar x Wormhole proposal introduces a secure, decentralized, multi-chain bridging solution that combines Native Token Transfers (NTT) for $GMX with intent-based bridging for stablecoins via Wormhole, Mayan, and Squid. The architecture supports unified liquidity, fast transfers, and high security across Arbitrum, Ethereum, BASE, BNB, and other chains, with future expansion to Solana and TON. $GMX transfers follow a burn/mint model with 2-of-2 threshold verification from Axelar and Wormhole, avoiding liquidity fragmentation and ensuring robustness. Wormhole supports 40 chains, and Axelar supports 70 chains, with overlapping support for Ethereum, Arbitrum, BASE, Polygon, and Avalanche. Stablecoin transfers settle in 5–30 seconds with low fees of 1–10 bps, while fixed transaction costs for token transfers range from $0.01–$0.66, depending on the source chain. The system features an NTT manager, redundant transceivers, and fallback mechanisms for resilience. It also enables multi-token bridging, gasless USDC transfers via Circle’s CCTP, and support for assets like $GMX, GLV, USDC, ETH, wBTC, and more. Security is bolstered by Wormhole’s $25M bug bounty, decentralized Guardians like Jump Crypto, and Axelar’s PoS-secured network of 75 validators. This dual-bridge, high-speed, low-cost framework offers GMX a flexible, future-proof, and secure path to omnichain expansion.
More details of the Wormhole - Axelar proposal can be found here: Bridging & Messaging Partner for GMX - Wormhole - Axelar
Select your preferred messaging bridge partner for GMX’s next phase of multichain expansion based on Rank choice voting :
. Chainlink . LayerZero . Wormhole - Axelar . Abstain
We encourage you to consider these details carefully when casting your vote. If you have any further questions, feel free to raise them prior to or during the voting window. Thank you for your ongoing participation in this process.
Off-Chain Vote
Loading…
- Author
0xc3a9…0cDE
- IPFS#bafkreie
- Voting Systemranked-choice
- Start DateApr 05, 2025
- End DateApr 12, 2025
- Total Votes Cast449.11K GMX
- Total Voters320
Discussion
Timeline
- Apr 05, 2025Proposal created
- Apr 05, 2025Proposal vote started
- Apr 12, 2025Proposal vote ended
- Apr 12, 2025Proposal updated