npm / @metamask/tron-wallet-snap
@metamask/tron-wallet-snap
What changed in @metamask/tron-wallet-snap 15 to 16, from its official release notes, upgrade guides and advisories. Also covers @metamask/bitcoin-wallet-snap, @metamask/solana-wallet-snap. Sources checked 2026-10-19.
3 breaking2 new APIs and options3 behavior and defaults3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@metamask/tron-wallet-snap 165 changes
Breaking changes 1
Soroban RPC TRY_AGAIN_LATER now fails transaction submission instead of being treated as success.
Behavior and default changes 1
Allows up to a 100% network-fee increase after confirmation and shows the latest fee estimate on the confirmation dialog.
Fixes and other changes 3
Security alerts use generic copy instead of the Blockaid description.
Transaction rebuilding after txBadSeq preserves sorobanData, allowing SEP-41 sends to retry successfully.
The catalog hot-reloads during account sync when its last sync has expired, so newly listed SEP-41 tokens can appear without waiting for the hourly cron.
@metamask/tron-wallet-snap 156 changes
Breaking changes 2
Now fetches live assets from the chain through the Snap's Solana RPC clients instead of returning persisted state.
Now fetches live balances from the chain through the Snap's Solana RPC clients instead of returning persisted state.
New APIs and options 2
The unified swap/bridge flow accepts optional sourceAssetId and destAssetId request options to classify transaction_type; classification is carried through to Transaction Finalized.
Transaction lifecycle events now emit transaction_type, allowing transaction flows to be attributed.
Behavior and default changes 2
Estimated changes from the previous scan remain visible while a confirmation re-scans, rather than being replaced by a loading skeleton.
A “Checking for security issues” banner appears while the transaction scan is in progress.