We’re currently integrating the Scale package with SDK v10 as per the migration documentation. For EVM-compatible chains, chain switching in our dApp works as expected using the toggles from the Web3Auth Developer Dashboard.
However, when we enable the Tron Blockchain, we encounter a critical issue:
The UI updates to reflect the Tron network, but the wallet address remains unchanged (it does not switch to a Tron address).
Additionally, other wallet functions stop working after the switch.
Could you help clarify what might be causing this problem? Is there a known limitation or extra configuration required for Tron support in SDK v10? Any guidance would be greatly appreciated.
Thanks for the detailed report! Here’s a summary of your issue for the support team:
Issue Summary
SDK: Web3Auth Plug and Play (PnP) Web SDK
SDK Version: v10.0.5
Platform: Web
Integration Context: Using the Scale package with SDK v10, following migration docs.
Chain Switching: Works for EVM-compatible chains via Web3Auth Developer Dashboard toggles.
Tron Blockchain Issue:
UI updates to Tron, but wallet address does not switch to a Tron address.
Other wallet functions stop working after switching to Tron.
Question: Is there a known limitation or extra configuration required for Tron support in SDK v10?
Next Steps & Suggestions
1. Tron Support in Web3Auth SDK v10
Current State: As of Web3Auth Documentation, Tron is a non-EVM chain and requires a different integration path than EVM chains.
Known Limitation: Chain switching using the EVM-based toggles or Wagmi hooks will not work for Tron, since Tron uses a different address format and provider logic.
Extra Configuration: You need to use the Tron-specific provider and methods as described in the Tron Integration Guide.
2. Action Items
Check Initialization: Are you initializing the Web3Auth SDK with the correct chainNamespace for Tron (CHAIN_NAMESPACE.OTHER)? See Tron Integration Example.
Provider Usage: For Tron, you should use the returned provider with TronWeb or the Web3Auth Tron Plugin, not with EVM libraries like ethers.js or Wagmi.
Switching Between EVM and Tron: If your app supports both, you may need to re-initialize or re-configure the provider when switching between EVM and Tron, since the underlying provider logic is different.
3. Request for Details (if further investigation is needed)
If you need deeper troubleshooting, could you please share:
Your Web3Auth initialization and login code snippets (especially how you handle chain switching and provider instantiation).
Any browser console errors or screenshots after switching to Tron.
Confirmation if you’re using the Web3Auth Tron Plugin or a custom provider setup.
Summary:
Tron support is fundamentally different from EVM chains in Web3Auth. EVM chain switching tools (like Wagmi) do not work for Tron. Please review the Tron-specific integration steps and ensure you are initializing and using the provider as per the docs. If you’re already following these steps, please share your initialization code and any error logs for further analysis.
Let us know if this helps or if you can provide the requested details for deeper troubleshooting!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours
I managed to integrate Tron successfully. However now I encounter another trouble: Tron wallet address is showing EVM address and it does not accept original Tron address but Tron EVM address…
How could I display Tron address instead of Tron EVM address?
How could I Send or Receive or Use Tron address with wallet modal?
Are you trying to display TRON addresses in the Wallet UI or the code?
Via Code we have an example around which you can create a UI yourself to display it. For now, Wallet UI only shows EVM and Solana addresses.