Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
52/100 average clarity
61Strong · 80–100
359Adequate · 60–79
549Thin · 40–59
197Opaque · 0–39
33security candidates with opaque commit messaging
This commit fixes a bug in how Taproot (a modern Bitcoin-style transaction format) inputs were being built. Previously, the 'sequence number'—a field that controls things like time-locks and replacement rules—was being dropped for Taproot …
Missing nSequence preservation for Taproot key-path inputsBehavioral divergence between Taproot and other input types in the same switchPotential for unintended transaction semantics (RBF, timelocks) due to default sequence value
This commit changes how Stack Wallet picks and updates Bitcoin receiving addresses. It makes the wallet rotate (advance to a fresh address) not just on its main address type, but also on other supported address types when they have transac…
Address rotation logic added for non-main derivation pathsView-only Taproot wallet explicitly rejected in Buy flow to avoid deriving addresses without private key materialNew test coverage for address reuse and rotation across BIP44/BIP84/BIP86 paths
This change fixes how Stack Wallet picks a Bitcoin receiving address when a user buys crypto through Simplex. Previously, the app could generate a fresh address every time instead of reusing the same one, which could cause funds sent to an…
Address reuse / derivation index stability for fiat-to-crypto buy flowRace-condition protection via mutex for address generationRemoval of direct Isar query from UI layer in favor of wallet abstraction
This commit adds automated integration and widget tests for the 'Buy' form's 'Choose from Stack' feature in a cryptocurrency wallet app. It does not change production code, fix bugs, or alter security behavior. It only verifies that the ex…
This commit fixes a privacy and usability bug in Stack Wallet. Previously, when the wallet refreshed its transaction history, it only checked whether the main receiving address (for example, a Taproot address) had been used. If you had gen…
This update fixes how Stack Wallet detects Bitcoin transactions that have disappeared from the memory pool (unconfirmed transactions). Previously, the wallet only recognized a specific error message format used by some server software. Now…
Error-handling robustness improvementData consistency fix for local transaction databaseServer-backend compatibility broadening
This is a large build-system refactor for a cryptocurrency wallet app. It replaces an older manual native-library build process with a new 'dnix' system that can either build libraries from source or download verified prebuilt binaries. Th…
Build system refactor only: no application runtime code changedNew verification step check_native_overrides.dart added to CI and local configure flowPrebuilt binaries are now verified against package dnix.lock hashes instead of app-level manifest URLs
This is a large merge commit that rewrites how the wallet connects to Electrum servers. The main security-relevant changes are: each wallet now owns its own Electrum connection instead of sharing one global client; the app learns to rememb…
Per-wallet Electrum connection ownership replaces shared singleton, reducing cross-wallet state contaminationTrusted TLS certificate pinning per node (host/port/SSL) addedCertificate approval UI with SHA-256 fingerprint display and forget action
This is a large refactor of how the Stack Wallet app connects to Electrum servers. Previously, all wallets of the same coin shared one global Electrum connection, which could leak wallet activity across wallets and made it hard to cleanly …
Shared Electrum client manager removed; per-wallet client isolation addedTLS certificate pinning/trust-on-first-use support added for Electrum nodesPer-request timeouts added instead of single global timeout
This commit only rewords comments and a test name. It changes the phrase 'approval pins the certificate' to 'approval accepts the certificate' and clarifies that only untrusted certificates reach the custom check. There is no code behavior…
This commit is purely a code-formatting cleanup in a single Dart file. It rewraps a few lines of navigation and theme code to match the project's style guide. There are no functional changes, no bug fixes, and no security relevance.
This is a large merge commit that refactors how transaction fees are calculated and displayed across Stack Wallet's send screens. It replaces duplicated fee-calculation code in many send views with a shared set of providers and helper widg…
Refactor of transaction-fee estimation logic across send flowsRemoval of duplicated fee-calculation code and session cachesIntroduction of shared fee providers and reusable UI helpers
This is a large code refactor that moves fee-calculation logic out of individual send screens into shared providers and helper classes. The goal is to make the send fee UI behave consistently across mobile, desktop, token, and Solana token…
Refactor of transaction fee estimation and selection UI across all send flowsConsolidation of wallet-specific fee logic (Cryptonote priorities, Firo Spark/public/OP_RETURN, Solana token fallback, Ethereum custom EIP-1559) into shared providersRemoval of per-view fee caches and timers; replacement with shared debounce/focus-loss retry logic
This commit adds a new feature to Stack Wallet that lets Monero (XMR) users cryptographically sign messages with their wallet address and verify signatures from others. It is a routine feature addition, not a security fix or vulnerability …
This commit adds a new feature to Stack Wallet that lets Monero wallet users cryptographically sign messages with their wallet keys and verify signatures from others. It is a routine feature implementation, not a security fix. There is no …
Feature addition, not a patch or fixView-only wallets are explicitly blocked from signingEmpty signature result from underlying library is treated as failure
This commit fixes a bug where Stack Wallet could not clean up old unconfirmed transactions when connected to electrs servers. The wallet checks whether a transaction still exists on the server; it previously only recognized ElectrumX/Fulcr…
Error-message parsing used for transaction lifecycle decisionWallet state desynchronization due to backend-specific error handlingRBF/replaced transaction cleanup failure
This commit fixes a user-interface bug in Stack Wallet's Solana token-add flow. Previously, when a user created a new Solana wallet while trying to add a Solana token, the wallet picker could see the newly created wallet in the database be…
No cryptographic or signing code changedNo network or RPC behavior changedNo authentication, authorization, or permission logic changed
This commit fixes a UI crash in Stack Wallet that could occur when adding an Ethereum token right after creating a new Ethereum wallet. The problem was a timing mismatch: the new wallet's basic info was saved to the database before the wal…
Crash/DoS in wallet picker UI due to inconsistent wallet registration stateRace condition between database persistence and in-memory provider registrationUI state derived from one provider (all wallet info) without checking another provider (registered wallets)
This commit only reformats Dart code to match the project's current Dart SDK style rules. It changes whitespace, line breaks, and import grouping in two wallet-related UI files. There are no functional changes, no security fixes, and no be…
This commit fixes a UI bug in Stack Wallet's Ethereum token-add flow. During wallet creation, the app briefly knew about a new Ethereum wallet before the wallet was fully registered, causing the token picker to show an empty or broken list…
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedfeat: add epicbox server management uiby sneurlax · fd2df8fd · Feb 3, 2026 · 6 filesMessage 57 · ThinInformational 19Details
Commit message · sneurlax
feat: add epicbox server management ui
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit adds a new user-interface feature for managing 'Epic Box' servers in the Stack Wallet desktop app. It lets users add, edit, test, and connect to custom Epic Cash (EPIC) relay servers. The change is a feature addition, not a documented security fix. There are no obvious remote-code-execution or data-theft bugs visible in the diff, but it does introduce network calls to user-supplied hosts and stores custom server entries, which could in principle be abused by a malicious server or a social-engineering attack if input validation or TLS handling elsewhere is weak.
AI review queuedfeat: use stored epicbox config when availableby sneurlax · 18310165 · Feb 3, 2026 · 1 fileMessage 57 · ThinInformational 16Details
Commit message · sneurlax
feat: use stored epicbox config when available
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100
This commit changes how the Epic Cash wallet picks its Epicbox server configuration. Previously it always used a hardcoded default server. Now it first tries to read a user-stored configuration from secure device storage and only falls back to the default if none exists or it cannot be parsed. The change is a feature improvement, not a direct security fix, but it reduces reliance on a single hardcoded server.
AI review queuedelectrumx disable acceptUnverifiedby julian · f55bc21a · Feb 2, 2026 · 2 filesMessage 35 · OpaqueModerate 66Details
Commit message · julian
electrumx disable acceptUnverified
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 66/100
This commit changes two places in a cryptocurrency wallet app where it connects to ElectrumX servers. Previously, one connection accepted unverified TLS/SSL certificates (acceptUnverified: true), which could let a malicious server impersonate a legitimate one. The patch disables that behavior (acceptUnverified: false) and also explicitly disables it in a connection-check helper. In plain terms, the wallet will now refuse to trust servers that cannot prove their identity with a valid certificate, reducing the risk of man-in-the-middle attacks.
AI review queueduse const http constructorby julian · bdb1d418 · Jan 30, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · julian
use const http constructor
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a tiny code-quality change that replaces a regular HTTP client instance with a constant one. It does not fix a security bug and does not change what the app does or how it connects to the internet.
AI review queuedfix db transactionby julian · 3af79fdb · Jan 30, 2026 · 1 fileMessage 28 · OpaqueLow 29Details
Commit message · julian
fix db transaction
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 29/100
This commit fixes a database cleanup routine that deletes a wallet's blockchain data (transactions, addresses, and unspent coins). Previously, the code counted records outside of the write transaction, then opened a transaction to delete them. If data changed between the count and the deletion, the loop logic could behave incorrectly. The fix moves the counts inside the same write transaction and increases the batch size from 50 to 100. There is no claim in the commit that this is a security fix, and no public references tie it to an incident.
AI review queuedat least log wallet delete errorsby julian · ab2bb49d · Jan 30, 2026 · 1 fileMessage 45 · ThinInformational 18Details
Commit message · julian
at least log wallet delete errors
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This commit adds error logging when deleting a wallet fails, and makes minor code cleanups. It does not fix the underlying deletion failure or change how the app behaves when an error occurs. The user still sees the same result, but developers now get a log entry to help diagnose problems.
AI review queuedcode style/formattingby julian · e226ff32 · Jan 30, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · julian
code style/formatting
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is purely a code-style and formatting cleanup. It extracts two long user-facing text strings into named constants and adjusts indentation to match the project's formatting rules. There is no change to app behavior, security logic, or user-visible wording.
AI review queuedfix state errorby julian · 46efac2c · Jan 30, 2026 · 1 fileMessage 28 · OpaqueInformational 16Details
Commit message · julian
fix state error
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 16/100
This is a small UI stability fix in a Dart/Flutter transaction list screen. It checks whether the widget is still on screen before calling setState after an asynchronous data update, preventing a common Flutter runtime error when a user navigates away before the update arrives. There is no indication this affects funds, keys, network traffic, or app permissions.
AI review queuedoptimise spark spendsby Julian · 316e6273 · Jan 30, 2026 · 1 fileMessage 28 · OpaqueLow 28Details
Commit message · Julian
optimise spark spends
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 28/100
This commit optimizes how the wallet prepares private Spark coin spends. It adds a check that throws an error if no spendable coins exist, and it changes the code to only fetch data for the specific coin groups the user actually owns, rather than scanning every group ID from 1 up to the latest one. This is a performance and robustness improvement, not a clear security fix, though it may reduce exposure to certain failure modes.
AI review queuedfix spark isolate initby julian · 4faa2624 · Jan 27, 2026 · 1 fileMessage 28 · OpaqueLow 29Details
Commit message · julian
fix spark isolate init
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 29/100
This commit fixes a race condition in how a background worker (called an 'isolate') for the Spark privacy feature is initialized. Previously, if two parts of the app tried to start the isolate at nearly the same time, both could try to create it, which could waste resources, cause errors, or leave the wallet in an inconsistent state. The fix uses a one-time 'Completer' so that any concurrent callers wait for the first initialization to finish instead of spawning duplicate isolates.
AI review queuedfix epic gecko nameby julian · e0413aa2 · Jan 27, 2026 · 1 fileMessage 28 · OpaqueInformational 19Details
Commit message · julian
fix epic gecko name
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 19/100
This commit fixes a lookup in the Stack Wallet app so it can find the Epic Cash cryptocurrency when its display name is 'Epic Private Internet Cash'. Without this change, the app might fail to recognize or handle Epic Cash correctly when that specific name is used. There is no direct evidence this is a security vulnerability.
AI review queuedadd option to choose between spark and transparent addresses during swap when selecting choose from stack to fill in an addressby julian · 6e981ef0 · Jan 27, 2026 · 9 filesMessage 50 · ThinInformational 19Details
Commit message · julian
add option to choose between spark and transparent addresses during swap when selecting choose from stack to fill in an address
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit updates the wallet's exchange and buy flows so that when a user picks one of their own wallets to receive a swap, they can now choose between a private 'Spark' address and a regular 'Transparent' address for Firo. Previously the app only offered one default address type. The change is a user-facing feature improvement, not a security fix, and the diff does not show any vulnerability being patched.
AI review queuedenable firo masternodes uiby julian · 824795ae · Jan 26, 2026 · 2 filesMessage 35 · OpaqueInformational 17Details
Commit message · julian
enable firo masternodes ui
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 17/100
This commit simply turns on an existing user-interface menu option for Firo masternodes in the Stack Wallet app. It uncomments two previously disabled UI blocks so that Firo wallet users can navigate to the masternodes screen. There is no code change to security logic, cryptography, networking, or data handling in the diff itself.
AI review queuedFix IP and port serialization in Firo masternode transactions.by cassandras-lies · d3eb10a3 · Jan 26, 2026 · 1 fileMessage 50 · ThinModerate 56Details
Commit message · cassandras-lies
Fix IP and port serialization in Firo masternode transactions.
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 56/100
This commit fixes how IP addresses and port numbers are packed into Firo masternode registration transactions in the Stack Wallet mobile/desktop wallet. The previous code reversed the IP octets and used little-endian byte order for the port, which would produce an incorrectly formatted network message. The patch now keeps IP octets in normal order and writes the port in network (big-endian) byte order, matching standard Firo protocol expectations. It also rejects port 0 as invalid. A wallet using the old code would likely create masternode transactions that other Firo nodes could not correctly interpret, leading to registration failures or misdirected masternode announcements.
AI review queuedthis shouldn't affect anything too negativelyby julian · e8cb0218 · Jan 24, 2026 · 1 fileMessage 45 · ThinLow 30Details
Commit message · julian
this shouldn't affect anything too negatively
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 30/100
This small change adds a safety check before updating Epic Cash wallet configuration. Previously, the app would try to update configuration even if the wallet object didn't exist, which could cause a crash. Now it skips the update if the wallet is missing. This is a defensive bug-fix that likely prevents a runtime error rather than a security vulnerability.
AI review queuedfix a couple issuesby Julian · 3c809bb0 · Jan 23, 2026 · 2 filesMessage 28 · OpaqueLow 34Details
Commit message · Julian
fix a couple issues
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes how the Epic Cash wallet is initialized and opened. It removes a dedicated wallet-open method, moves the open-wallet call into the general init flow, and switches the wallet-recovery call to be awaited properly. The changes look like bug fixes to wallet lifecycle handling rather than an obvious security patch, but the commit message gives no details and there are no external references.
AI review queuedformattingby Julian · ee522c38 · Jan 23, 2026 · 2 filesMessage 0 · OpaqueInformational 15Details
Commit message · Julian
formatting
0/100 · OpaqueMessage clarity
! Very short subject! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit only reformats Dart code—breaking a long return-type line and collapsing some function-call arguments onto single lines. There are no functional changes, no bug fixes, and no security alterations.
AI review queuedopenWallet exampleby Julian · 3e27a371 · Jan 23, 2026 · 2 filesMessage 18 · OpaqueInformational 15Details
Commit message · Julian
openWallet example
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit updates the Epic Cash wallet integration so that opening a wallet now requires an extra configuration value (epicboxConfig) and returns a wrapped wallet object instead of a plain string. It appears to be a routine API/example update with no obvious security relevance.
AI review queuedfix(epic): fix wallet opening and handling, add open, remove ensureWalletOpenby sneurlax · ed18ba26 · Jan 23, 2026 · 1 fileMessage 62 · AdequateLow 34Details
Commit message · sneurlax
fix(epic): fix wallet opening and handling, add open, remove ensureWalletOpen
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit restructures how the Epic Cash wallet is opened in the Stack Wallet mobile app. It replaces an automatic 'open if needed' helper with a single explicit open() step that must be called first. The change also makes wallet recovery and re-initialization close the old wallet handle before creating a new one, and it starts the Epic Box listener in more places. The commit looks like a bug-fix/refactoring change rather than a clear security patch, but it removes a pattern where wallet operations could silently re-load the wallet on demand, which could have helped avoid inconsistent or duplicate wallet states.
AI review queuedfix(epic): adjust exit behaviorby sneurlax · b1162d20 · Jan 23, 2026 · 1 fileMessage 57 · ThinLow 34Details
Commit message · sneurlax
fix(epic): adjust exit behavior
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes how Stack Wallet's Epic Cash wallet shuts down and restarts its background listener. The old code forcibly closed the wallet object on every exit, which could leave the listener in a broken or stale state. The new code keeps the wallet object alive, stops only the listener, and ensures the listener is restarted when the wallet is reopened. This is a reliability fix that may also prevent bugs where the wallet appears online but cannot receive transactions.
AI review queueddisplay sol memo in guiby julian · 860ac3d8 · Jan 20, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · julian
display sol memo in gui
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a user-interface feature that displays Solana transaction memos in the wallet app. It reads existing on-chain memo data and shows it to the user, but does not change how transactions are created, signed, or validated. There is no security-relevant change visible in the code.
AI review queuedrefactor amount formatter to handle unified eth/sol contractsby julian · 00be7286 · Jan 20, 2026 · 16 filesMessage 50 · ThinLow 26Details
Commit message · julian
refactor amount formatter to handle unified eth/sol contracts
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100
This commit is a code cleanup that merges two separate ways of handling Ethereum and Solana token amounts into one shared path. It does not appear to fix an active security bug, but it removes duplicated logic that could previously have led to inconsistent token display or parsing. The change is mostly internal refactoring across wallet balance and transaction screens.
AI review queuedsol transaction parsing and gui updatesby julian · 71d4348d · Jan 20, 2026 · 7 filesMessage 45 · ThinInformational 24Details
Commit message · julian
sol transaction parsing and gui updates
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100
This commit updates how Stack Wallet parses and displays Solana (SOL) and Solana token (SPL) transactions. It changes the code that reads transaction data from the Solana blockchain so it looks at the actual 'transfer' instructions inside each transaction rather than guessing sender/receiver from account key order. It also adds Solana-specific support to several user-interface screens that previously only handled Ethereum tokens. There is no clear security fix or vulnerability being patched; it reads as a feature/bug-fix update for Solana transaction handling.
AI review queuedfix linux app idby julian · 0b2b797e · Jan 20, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · julian
fix linux app id
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a one-line build script fix that ensures the Linux app identifier is correctly substituted during packaging. It is not a security fix and does not change any runtime code that handles money, passwords, or network traffic.
AI review queuedfix sol token sends with ATAby julian · e112cdf0 · Jan 20, 2026 · 5 filesMessage 45 · ThinLow 42Details
Commit message · julian
fix sol token sends with ATA
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 42/100
This commit fixes how Stack Wallet sends Solana tokens. Previously, the app required the recipient to already have a token account (ATA) set up, and it could fail or send funds incorrectly if that account didn't exist. The update makes the wallet automatically create the recipient's token account during the transaction if needed, and it cleans up how token details are passed around. There is no clear security bug being patched, but the change touches code that handles real money transfers, so mistakes here could cause lost funds or failed transactions.