introduce starknet warp route & infra config example#23
Open
swiiny wants to merge 5 commits intohyperlane-xyz:mainfrom
Open
introduce starknet warp route & infra config example#23swiiny wants to merge 5 commits intohyperlane-xyz:mainfrom
swiiny wants to merge 5 commits intohyperlane-xyz:mainfrom
Conversation
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
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.
Summary
This PR adds a fully runnable Warp‑route example, complete with documentation, scripts, and infra configs, so teams can stand up a Starknet ↔ Gnosis Chiado route with Hyperlane in just a few commands.
Motivation
Until now the repository offered reference contracts but no end‑to‑end guide for deploying and exercising a Warp route.
Teams interested in re‑using the implementation had to piece the flow together from code and scattered notes, costing time (and brain‑cells).
By contributing a ready‑to‑run example we:
shorten the on‑ramp for new integrators,
provide a concrete template they can adapt to their own token,
keep the main repo as the single source of truth for both code and usage.
What’s included