-
Notifications
You must be signed in to change notification settings - Fork 169
feat: enable Starknet wallet & message ID parsing on UI #505
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
return ( | ||
<StarknetConfig chains={[sepolia]} provider={publicProvider()} explorer={voyager}> | ||
<StarknetConfig | ||
chains={chains} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hyperlane packages update needed? if you visit the preview the UI will break since the context expects at least one chain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, that is why I put do not merge label. There should be a preceding PR to Registry to add at least one starknet chain. Will include it in the PR desc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At least one chain needed for the wallet context
This enables users to connect Starknet wallets and parse Hyperlane message IDs
Important: Merging available after adding at lease one starknet chain to registry!