Description
Add Tron as a supported network on Noblocks. Tron will appear in the list of available networks alongside the existing networks (Base, BNB Smart Chain, Arbitrum One, Starknet, Polygon, Lisk, Ethereum, Celo, Scroll), and users will be able to transact on Tron just like they can on the other supported networks.
The major changes for Tron are complex and involve integrating Tron as a tier-two network (non-EVM, similar to Starknet). This includes Privy support for Tron, Tron wallet creation and management (including wallet preview), Tron in the network list, and Tron in transaction history. The team should review the existing Starknet implementation as a reference for how Tron should be integrated, since neither is an EVM chain.
User Story
As a Noblocks user,
I want to see Tron in the list of supported networks and transact on it,
So that I can use Noblocks to transact on the Tron network just like I do on the other supported networks.
Acceptance Criteria
-
GIVEN a user opens the network selector
WHEN they view the list of available networks
THEN Tron is displayed in the list with its name and logo.
-
GIVEN a user selects Tron from the network selector
WHEN the selection is made
THEN the active network switches to Tron and the UI reflects Tron as the selected network.
-
GIVEN a user is on Noblocks with Privy
WHEN they use Tron
THEN Privy supports Tron, including wallet creation and management for Tron.
-
GIVEN a user has a Tron wallet on Noblocks
WHEN they view their wallet
THEN the wallet preview is displayed correctly for Tron, in the same way as for other supported networks.
-
GIVEN Tron is the selected network
WHEN the user views their wallet balance and supported tokens
THEN the balance and tokens shown correspond to the Tron network.
-
GIVEN Tron is the selected network
WHEN the user initiates a transaction (swap/off-ramp, transfer)
THEN the transaction can be created, reviewed, confirmed, processed, and completed on Tron in the same way as on other supported networks.
-
GIVEN a user completes a transaction on Tron
WHEN they view the transaction confirmation
THEN the transaction details (amount, recipient, network, explorer link) reflect Tron correctly.
-
GIVEN a user views their transaction history
WHEN they look at past transactions
THEN Tron transactions appear in the history in the same way Starknet transactions currently do.
Tech Details
- Integrate Tron as a tier-two (non-EVM) network on Noblocks, following the existing Starknet implementation as a reference.
- Add Tron support to Privy for wallet creation and management.
- Implement Tron wallet preview in the same pattern as other supported networks.
- Add Tron to the list of supported networks in the network configuration, including Tron's logo, name, and required network metadata.
- Add support for Tron-compatible tokens used on Noblocks (e.g., USDT on Tron).
- Ensure Tron transaction creation, signing, and submission work end-to-end.
- Add Tron transactions to the transaction history view, in the same way as Starknet.
- Link transaction confirmations to the appropriate Tron block explorer.
Notes/Assumptions
- Tron is a tier-two (non-EVM) network for Noblocks; the team should reference the Starknet implementation as the closest existing pattern.
- Tron will be treated as a first-class network on Noblocks, with the same user-facing flows as the other supported networks.
- The tokens supported on Tron will follow the same set Noblocks already supports on other networks where applicable.
- Privy must support Tron in order for wallet creation and management to work end-to-end.
Open Questions
- What is the current state of Privy's Tron support, and what (if any) configuration or upgrade is required?
- Which tokens on Tron will be supported at launch?
- Which Tron block explorer will be used for transaction links?
- Are there any aspects of the Starknet implementation that should explicitly not be replicated for Tron?
- Are there Tron-specific UX considerations (e.g., address format, fee model) that need to be reflected in the wallet preview or transaction flows?
Description
Add Tron as a supported network on Noblocks. Tron will appear in the list of available networks alongside the existing networks (Base, BNB Smart Chain, Arbitrum One, Starknet, Polygon, Lisk, Ethereum, Celo, Scroll), and users will be able to transact on Tron just like they can on the other supported networks.
The major changes for Tron are complex and involve integrating Tron as a tier-two network (non-EVM, similar to Starknet). This includes Privy support for Tron, Tron wallet creation and management (including wallet preview), Tron in the network list, and Tron in transaction history. The team should review the existing Starknet implementation as a reference for how Tron should be integrated, since neither is an EVM chain.
User Story
As a Noblocks user,
I want to see Tron in the list of supported networks and transact on it,
So that I can use Noblocks to transact on the Tron network just like I do on the other supported networks.
Acceptance Criteria
GIVEN a user opens the network selector
WHEN they view the list of available networks
THEN Tron is displayed in the list with its name and logo.
GIVEN a user selects Tron from the network selector
WHEN the selection is made
THEN the active network switches to Tron and the UI reflects Tron as the selected network.
GIVEN a user is on Noblocks with Privy
WHEN they use Tron
THEN Privy supports Tron, including wallet creation and management for Tron.
GIVEN a user has a Tron wallet on Noblocks
WHEN they view their wallet
THEN the wallet preview is displayed correctly for Tron, in the same way as for other supported networks.
GIVEN Tron is the selected network
WHEN the user views their wallet balance and supported tokens
THEN the balance and tokens shown correspond to the Tron network.
GIVEN Tron is the selected network
WHEN the user initiates a transaction (swap/off-ramp, transfer)
THEN the transaction can be created, reviewed, confirmed, processed, and completed on Tron in the same way as on other supported networks.
GIVEN a user completes a transaction on Tron
WHEN they view the transaction confirmation
THEN the transaction details (amount, recipient, network, explorer link) reflect Tron correctly.
GIVEN a user views their transaction history
WHEN they look at past transactions
THEN Tron transactions appear in the history in the same way Starknet transactions currently do.
Tech Details
Notes/Assumptions
Open Questions