# Bridge provider for $Fluid Multi-Chain Deployment

- Space: [Instadapp](https://snapshot.box/s:instadapp-gov.eth.md)
- Author: 0x4604E3bFbaCcB317a6FfEde8Bf24105F476A7329
- State: Closed
- Voting type: Single choice
- Start: 2025-05-11 22:06 UTC
- End: 2025-05-14 22:06 UTC
- Votes: 8
- Discussion: https://gov.fluid.io/t/fluid-multi-chain-deployment-evaluating-bridge-solutions/1418
- Open in Snapshot: https://snapshot.box/#/s:instadapp-gov.eth/proposal/0x6c87affd22907d68074cafc89648cedfee624b4639a16eb83c6095c228e23680

## Results

- Native bridges: 0 voting power, 0.0%
- LayerZero: 0 voting power, 0.0%
- Socket: 0 voting power, 0.0%
- Axelar: 0 voting power, 0.0%
- Wormhole: 0 voting power, 0.0%
- Chainlink: 5,316,317.89 voting power, 100.0%

## Proposal

# Summary
This proposal seeks community support to select a bridge provider for the $Fluid multi-chain deployment.

# Proposal
As we prepare to deploy our token across multiple networks, we must choose a bridging solution that ensures:

- Security: Avoiding exploits and ensuring robust verification models.
- Cost Efficiency: Reducing gas fees and transaction costs.
- Decentralization: Minimizing trust assumptions and avoiding central points of failure.
- Liquidity Management: Maintaining token supply consistency across networks.
- User Experience: Enabling fast, seamless transactions without complexity.

The forum discussion evaluates native bridges and third-party solutions (LayerZero, Socket, Axelar, Wormhole, CL CCIP) to help determine the best approach.

# Conclusion
This proposal will choose the bridge provider for the $Fluid multi-chain deployment.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

