[ulissesferreira]

Explanation

Adds support for signing VoteWitnessContract and AccountPermissionUpdateContract transactions.

The sign flow deserializes and rebuilds transactions before signing. TronWeb 6.1.0 does not support these contract types in its deserializer, so signing failed with WalletSignTransactionError: trasaction ... not supported. This upgrades TronWeb to 6.5.1, which includes deserializers for both contract types.

It also regenerates the local TronWeb patch against 6.5.1 with only the two changes the Snap still needs:

• Preserve provider URLs as passed in, including trailing slashes used by Infura.
• Allow self-sends (TRX and TRC-10) by removing TronWeb's client-side same-account validation.

TronWeb 6.5.1 depends on axios@1.18.0, which is flagged for known CVEs, so the existing axios@1.12.2 resolution is extended to resolve axios@1.18.0 to the already-used axios@1.20.0.

Adds regression coverage for trailing-slash provider URLs and for deserializing and rebuilding both newly supported contract types.

References

Ticket: WPN-2455

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	tronweb@​6.1.0 ⏵ 6.5.1	+1			+3

View full report

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Priority	Alert  (click "▶" to expand/collapse)	Action
	Potential code anomaly (AI signal): npm tronweb is 62.0% likely to have a medium risk anomaly Notes: This module is not overtly malicious by itself; it contains no explicit exfiltration, command execution, or credential handling. However, it is a high-privilege plugin installer that executes plugin constructors and dynamically overwrites TronWeb component methods (or extends the public API) using plugin-controlled code. While it blocks a limited set of protected modules and signing/private-key related methods, it does not sandbox or authenticate plugins, leaving meaningful supply-chain risk: a malicious or compromised plugin could tamper with non-protected TronWeb behaviors that execute during normal use. Confidence: 0.62 Severity: 0.68 From: packages/tron-wallet-snap/package.json → npm/tronweb@6.5.1 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/tronweb@6.5.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Warn

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[stanleyyconsensys]

LGTM

small question, we need to path tron web, becoz we wanna unblock self send, and sth abt the host ?

[ulissesferreira]

LGTM

small question, we need to path tron web, becoz we wanna unblock self send, and sth abt the host ?

Yes, precisely, patching Tronweb is done for:

• Avoid Tronweb's corruption of Infura base URLs
• Allow self-send