feat: migrate leap cosmos to the hub #1322
Open
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 integrates Leap (Cosmos) into the Hub and aligns its behavior with the Cosmos namespace and capability model.
Leap provides stable Cosmos functionality, but has an important limitation related to auto-connect. Aside from these constraint, all other features (connection, account retrieval, signing) work correctly.
Implementation notes / limitations
Leap is only available on Chromium-based browsers
(e.g., Chrome, Brave, Edge).
It is not supported on Firefox or Safari.
Leap does not support eager-connect for Cosmos.
A manual connection interaction is required for each session.
The wallet provides no API to silently restore state, so auto-connect must remain disabled.
Other Features
All other Leap Cosmos features work as expected:
No additional limitations were observed.
Fixes # (issue)
How did you test this change?
Leap was tested under the Hub integration across supported environments:
Verified successful manual connection.
Confirmed correct Cosmos account retrieval and chain info.
Performed signing operations to validate compatibility.
Test A
Test B
Checklist: