Skip to content

Release/3.0.0 - #68

Closed
taran-a wants to merge 5 commits into
mainfrom
release/3.0.0
Closed

Release/3.0.0#68
taran-a wants to merge 5 commits into
mainfrom
release/3.0.0

Conversation

@taran-a

@taran-a taran-a commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Explanation

Tron package release v1.33.2

  • This package was migrated from snap-tron-wallet. See the source repository for the original changelog. (#45)
  • Changed the package license from dual MIT-0/Apache-2.0 licensing to a single MIT license. (#50)

References

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

@taran-a
taran-a requested review from a team as code owners July 29, 2026 15:49
@taran-a
taran-a temporarily deployed to default-branch July 29, 2026 15:49 — with GitHub Actions Inactive
@taran-a
taran-a temporarily deployed to default-branch July 29, 2026 15:50 — with GitHub Actions Inactive
@metamask-ci

metamask-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown

✅ No changelog changes needed.

@taran-a

taran-a commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

@metamaskbot publish-preview

@taran-a taran-a closed this Jul 29, 2026
@taran-a
taran-a deleted the release/3.0.0 branch July 29, 2026 16:20
jeremytsng pushed a commit that referenced this pull request Aug 5, 2026
chore: add in memory cache to NetworkService
jeremytsng pushed a commit that referenced this pull request Aug 5, 2026
## Explanation
Adds Wallet Standard-style client request RPCs for validating
destination addresses and send amounts, backed by a new
TransactionService.createValidatedSendTransaction flow that supports
slip44/native, classic, and SEP-41 transfers.

Pre-requirement (require below PRs to be merged):
- [ ] #69 
- [ ] #68 
- [ ] #67   

<!--
Thanks for your contribution! Take a moment to answer these questions so
that reviewers have the information they need to properly understand
your changes:

* What is the current state of things and why does it need to change?
* What is the solution your changes offer and how does it work?
* Are there any changes whose purpose might not obvious to those
unfamiliar with the domain?
* If your primary goal was to update one package but you found you had
to update another one along the way, why did you do so?
* If you had to upgrade a dependency, why did you do so?
-->

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## 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](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant