Skip to content

Conversation

@arlert-armin
Copy link
Contributor

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:

  • Added TronLink provider support within the Hub.
  • Implemented full Tron namespace compatibility (connection, account retrieval, signing).
  • Ensured provider detection and routing align with existing Hub infrastructure.

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:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • Implemented a user interface (UI) change, referencing our Figma design to ensure pixel-perfect precision.

@arlert-armin arlert-armin force-pushed the feat/rf-2762-migrate-bitget-to-the-hub branch from 9e8a869 to 4e9c5d7 Compare November 29, 2025 11:44
@arlert-armin arlert-armin force-pushed the feat/rf-2762-migrate-bitget-to-the-hub branch 4 times, most recently from a82b776 to e2a40ef Compare November 30, 2025 06:22
Base automatically changed from feat/rf-2762-migrate-bitget-to-the-hub to next November 30, 2025 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants