feat: migrate brave to the hub #1304
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 migrates Brave to the Hub architecture, updating its connection flow and internal integrations to align with the Hub’s standardized capability model. The migration was straightforward, and no limitations were identified.
Key changes:
No known limitations were found.
Fixes # (issue)
How did you test this change?
I tested Brave end-to-end under the Hub-managed environment:
Verified Brave connects successfully through the Hub.
Confirmed address retrieval and account updates behave as expected.
Ensured signing and other wallet interactions work correctly.
Test A
Test B
Checklist: