docs: add cross-chain recommendation #1142
Open
+30
−13
Conversation
This file contains 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
✅ Deploy Preview for oasisprotocol-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
rube-de
force-pushed
the
rube/1134-docs-add-recommendation-for-testnet-cross-chain-messaging-development
branch
2 times, most recently
from
885972b to
2aeffcb
Compare
rube-de
force-pushed
the
rube/1134-docs-add-recommendation-for-testnet-cross-chain-messaging-development
branch
from
2aeffcb to
b64cc67
Compare
aefhm
approved these changes
Feb 21, 2025
| @@ -44,32 +44,49 @@ messages, please visit our [Gasless Transactions chapter]. | |||
|
|
|||
| ## Message Bridges | |||
|
|
|||
| You can integrate message bridges into your dApps using one of these three | |||
| You can integrate message bridges into your dApps using one of these four | |||
There was a problem hiding this comment.
Suggested change
| You can integrate message bridges into your dApps using one of these four | |
| You can integrate messaging bridges into your dApps using one of these four |
Comment on lines
+72
to
+75
| **[Hyperlane][hyperlane]**: Due to its permissionless nature, it is easy to use | ||
| with other testnets, and you can easily run your own Relayer. This flexibility | ||
| makes it an ideal choice for hackathons, early-stage development and testing | ||
| environments. |
There was a problem hiding this comment.
Suggested change
| **[Hyperlane][hyperlane]**: Due to its permissionless nature, it is easy to use | |
| with other testnets, and you can easily run your own Relayer. This flexibility | |
| makes it an ideal choice for hackathons, early-stage development and testing | |
| environments. | |
| **[Hyperlane][hyperlane]**: Due to its permissionless nature, Hyperlane integrates well | |
| with other testnets, and you can easily run your own Relayer. Hyperlane's flexibility | |
| is great for hackathons, early-stage development, and testing | |
| environments. |
(Very optional), I went back and forth on wording. 🤔
Comment on lines
+79
to
+82
| **[Router Protocol][router]**: Battle-tested by ecosystem dApps like Neby and | ||
| features the most active token pairs. It provides a highly reliable, | ||
| production-ready solution for cross-chain communication, making it a top | ||
| recommendation for production environments. |
There was a problem hiding this comment.
Suggested change
| **[Router Protocol][router]**: Battle-tested by ecosystem dApps like Neby and | |
| features the most active token pairs. It provides a highly reliable, | |
| production-ready solution for cross-chain communication, making it a top | |
| recommendation for production environments. | |
| **[Router Protocol][router]**: Battle-tested by ecosystem dApps like Neby | |
| features the most active token pairs. Router provides a highly reliable, | |
| solution for cross-chain communication, making it a top recommendation | |
| for production-ready environments. |
Double checking it was just Neby?
matevz
approved these changes
Feb 21, 2025
Comment on lines
+63
to
+66
| | **[OPL SDK]** | SGN (Celer) | Executor (self-hosted or <br/>hosted service by Celer) | SGN Fee: Paid via `msg.value` <br/> Executor Fee: Charged externally (Free on testnet) | | ||
| | **[Celer IM][celer]** | SGN (Celer) | Executor (self-hosted or <br/>hosted service by Celer) | SGN Fee: Paid via `msg.value` <br/> Executor Fee: Charged externally (Free on testnet) | | ||
| | **[Hyperlane][hyperlane]** | Self-hosted or<br/>run by Hyperlane | Self-hosted or <br/>run by Hyperlane | Interchain Gas Payments on origin chain | | ||
| | **[Router Protocol][router]** | Orchestrators (Router Chain) | Relayer (run by 3rd party) | Paid by the approved feepayer on the Routerchain | |
There was a problem hiding this comment.
Should we move the Hyperlane and Router chapters above or is that a separate PR?
There was a problem hiding this comment.
I think this loosely alphabetized? I'm down with recommendation order too.
There was a problem hiding this comment.
yes, right now logic is: OPL-sdk then alphabetical
I can move them in this PR. What would be the recommended order?
- Hyperlane
- Router
- OPL-sdk
- Celer
?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.