feat: research bridge/messaging protocol options for source-chain pro… - #164
Open
yahia008 wants to merge 1 commit into
Open
feat: research bridge/messaging protocol options for source-chain pro…#164yahia008 wants to merge 1 commit into
yahia008 wants to merge 1 commit into
Conversation
…of delivery Compares Axelar, LayerZero, Chainlink CCIP, Wormhole, and Hyperlane as candidate protocols for delivering source-chain transaction proofs to the Soroban intent_settlement contract on Stellar. Key findings: - Axelar: live Stellar Mainnet (Feb 2026), GMP + ITS, official Stellar docs - LayerZero: live Stellar Soroban, DVN model, OApp/OFT standards; KelpDAO $292M exploit (Apr 2026) due to single-DVN config — multi-DVN is mandatory - Chainlink CCIP: announced for Stellar but not yet live; 10-20min latency exceeds current fill window; best for high-value fills once live - Wormhole: no Stellar integration found; not viable today - Hyperlane: no Stellar integration found; monitor for permissionless deploy Recommendation: Axelar as primary path (only production-ready option with official Stellar docs); LayerZero as fallback with mandatory multi-DVN config; CCIP for high-value fills once live on Stellar. Covers cost (~$0.05-$0.50/msg for Axelar+LZ), latency (1-2min fits the 5min fill window), trust assumptions, and security incident history. Cross-references the Stellar oracle spike for a full picture of proof delivery options. Closes stellar-vortex-protocol#128
|
@yahia008 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title:
feat: research bridge/messaging protocol options for source-chain
proof delivery
Body:
Summary
Closes #128
Research spike comparing general-purpose cross-chain messaging
protocols as candidate paths for delivering source-chain transaction
proofs to the Soroban
intent_settlementcontract on Stellar.Complements the Stellar-oracle spike — both documents should be read
together before finalizing the interface design.
What's in this PR
docs/bridge-protocol-comparison.md— full comparison of Axelar,LayerZero, Chainlink CCIP, Wormhole, and Hyperlane covering:
Wormhole $326M exploit)
Recommendation (TL;DR)
Testing
Documentation-only PR — no contract code changes, no build or test
impact.
Cross-references
issue