You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have deployed TRC20 token on the tron mainnet using TransparentUpgradeableProxy (v4/v5), but I don't see any Read/Write as proxy buttons on the Contract tab.
Here are the steps I took:
have deployed the implementation contract
have deployed the proxy contract (implementation address has been passed as a construct parameter)
have verified the implementation contract
have verified the proxy contract
have sent a request via "Update Proxy Contract's Implementation address button" in "Contact Us" section
Have I done something wrong or should I just wait for my request to be fulfilled?
Additionaly I have researched examples of other TRC20 tokens implemented via proxy pattern and have found that there is a direct link to the token page from the proxy contract in the "Overview" section, for example:
There is no such link in my proxy contract, have I missed something?
The text was updated successfully, but these errors were encountered:
razorbohan
changed the title
TRC20 Proxy contract doesn't have Read/Write as proxy buttons
TRC20 Proxy contract doesn't have "Read/Write as proxy" buttons
Aug 1, 2024
Hi!
I have deployed TRC20 token on the tron mainnet using TransparentUpgradeableProxy (v4/v5), but I don't see any Read/Write as proxy buttons on the Contract tab.
Here are the steps I took:
Proxy: TDFLhfVG74ZXqbN2U7TyYyLNo2kEUz1uYv
Implementation: TYTx7u3u6o55Tc7tncr2Ykr3NQD2qqTn1d
Have I done something wrong or should I just wait for my request to be fulfilled?
Additionaly I have researched examples of other TRC20 tokens implemented via proxy pattern and have found that there is a direct link to the token page from the proxy contract in the "Overview" section, for example:
There is no such link in my proxy contract, have I missed something?
The text was updated successfully, but these errors were encountered: