feat: migrate tronlink to the hub #1319
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 TronLink into the Hub and aligns its connection, account retrieval, and signing flows with the Hub’s standardized Tron namespace model.
The integration was smooth, and TronLink introduces no feature limitations. All core behaviors—including connection, account handling, and transaction signing—function correctly within the Hub architecture.
Key changes:
No known limitations were identified.
Fixes # (issue)
How did you test this change?
TronLink was tested end-to-end using the Hub integration:
Verified successful connection through the Hub.
Confirmed correct retrieval of Tron accounts and addresses.
Executed signing operations to ensure compatibility with TronLink’s provider.
Verified stability during reconnections and repeated operations.
Test A
Test B
Checklist: