Add tron sign message and txs support for WalletConnect#925
Add tron sign message and txs support for WalletConnect#925
Conversation
Summary of ChangesHello @0xh3rman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly expands the platform's multi-chain capabilities by introducing comprehensive support for the Tron blockchain. It establishes a dedicated Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces support for Tron wallet connect. The changes are comprehensive, touching multiple crates to add Tron to chain configurations, WalletConnect namespaces, and message/transaction signing logic. The core implementation for Tron signing is added in the gem_tron crate.
My main feedback is on a logical issue in the new chain_signer.rs file, where applying a signature to a transaction payload might fail for nested JSON structures. I've provided a detailed comment with a suggested fix for this.
Overall, the changes are well-structured and the addition of Tron support is a great enhancement.
| @@ -0,0 +1,11 @@ | |||
| use sha2::{Digest, Sha256}; | |||
|
|
|||
| pub fn sha256(bytes: &[u8]) -> [u8; 32] { | |||
There was a problem hiding this comment.
can you make this reusable across the app? we use in many places
There was a problem hiding this comment.
so we use gem_hash across the app
| let Some(data) = value.data.as_deref() else { | ||
| return Ok(None); | ||
| }; | ||
| let owner_address = if payload.address.is_empty() { |
There was a problem hiding this comment.
can you create serde desealizer for this in tron? we do this often, easier to mark to decode as TronAddress
| } | ||
|
|
||
| #[derive(Serialize, Debug)] | ||
| pub struct TriggerConstantContractDataRequest { |
There was a problem hiding this comment.
consolidate with TriggerSmartContractData ? are we sure there is no similar models?
| } | ||
|
|
||
| impl TriggerConstantContractResponse { | ||
| pub fn check_error(&self) -> Option<TronRpcError> { |
There was a problem hiding this comment.
we already have this logic?
| Algorand, | ||
| Sui, | ||
| Ton, | ||
| #[serde(rename = "tron")] |
| pub(crate) value: TronContractValue, | ||
| } | ||
|
|
||
| #[derive(Debug, Clone, Serialize, Deserialize)] |
There was a problem hiding this comment.
models seems duplicated and not all values are used.
|
|
||
| fn apply_signature(payload: Value, signature_hex: &str) -> Result<Value, SignerError> { | ||
| let mut payload: TronPayload = serde_json::from_value(payload).map_err(|_| invalid_input("Invalid Tron transaction payload"))?; | ||
| if !payload.transaction.signature.is_empty() { |
There was a problem hiding this comment.
why do you need to check for this?
|
|
||
| fn sign_data(input: &TransactionLoadInput, private_key: &[u8]) -> Result<String, SignerError> { | ||
| let (transaction, metadata) = extract_transaction(input)?; | ||
| if !transaction.signature.is_empty() { |
| visible: true, | ||
| }; | ||
|
|
||
| let response: TriggerConstantContractResponse = self.client.post("/wallet/triggerconstantcontract", &request_payload, None).await?; |
There was a problem hiding this comment.
consolidate with TRC20 estimation? same logic?
|
|
||
| [dependencies] | ||
| sha2 = { workspace = true } | ||
| sha3 = { version = "0.10.8" } |
There was a problem hiding this comment.
let's move sha3 to workspace
Uh oh!
There was an error while loading. Please reload this page.