Stack Wallet

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.

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.

This commit fixes how Stack Wallet classifies Firo Spark addresses. Before the fix, the wallet likely treated Spark addresses as a different, possibly unsupported address type because it didn't have a dedicated check. The fix adds a method that first checks if an address is a Spark address and, if so, returns the correct type; otherwise it falls back to the existing logic. This is a correctness fix that could prevent user-facing errors or misrouting of transactions involving Spark addresses.

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.

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.

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.

This commit replaces a very weak Epic Cash address check with a proper synchronous validation call. Previously, the app considered any string containing an '@' symbol to be a valid Epicbox address, and any non-empty string longer than 10 characters to be valid otherwise. That could have allowed users to send funds to malformed or attacker-controlled addresses. The patch now delegates validation to the underlying Epic Cash library, which should reject invalid addresses correctly.

This commit rewrites how the Epic Cash wallet stores and uses its configuration. Previously, the app saved a full JSON node/wallet configuration in secure storage and reused it later. Now it only stores a simple 'true' flag there and rebuilds the configuration fresh each time from the currently selected node. The change also removes iOS-specific path rewriting that happened when reading the stored config. The commit message is jokey ('fix epic lmao config'), so the security intent is unclear, but the change could fix a bug where stale or incorrect node settings were reused after the user changed nodes.

We cannot evaluate this commit. The actual code changes (diff) were not provided, and there are no verified public references. The title mentions fixing an 'Epic listener issue' in a cryptocurrency plugin, but without seeing what changed, we cannot tell whether this is a routine bug fix or something with security implications.

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.

This commit only updates a reference (likely a Git submodule pointer) to a plugin called flutter_libepiccash. No actual code changes are shown, and there is no description of any security fix. On its own, this commit does not demonstrate any vulnerability or security improvement.

This commit changes how an Epic Cash cryptocurrency wallet is deleted. Previously, the delete command was called directly on an open wallet object. Now the code first closes the wallet, then calls a static delete method that only needs the wallet's configuration string. This looks like a routine cleanup to avoid deleting a wallet that is still open, which could prevent crashes or incomplete deletion. There is no clear security vulnerability visible in the diff itself.

This commit is a code cleanup/refactor for the Epic Cash wallet integration. It replaces direct use of a specific library object with a generic 'dynamic object' wrapper and changes how the wallet is passed around. There is no clear security bug introduced or fixed in the visible diff. The change removes storing a raw wallet handle in secure storage, which could be a minor hardening improvement, but the commit message does not frame it as a security fix.

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.

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.

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.

This is a one-line change to a plugin called flutter_libepiccash, which handles Epic Cash cryptocurrency operations in Stack Wallet. The commit title says it 'updates' a worker, but the actual code change is not visible because the diff was not provided. Without seeing what was changed, it is impossible to tell whether this fixes a security problem, a stability bug, or something routine.

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.

This is a one-line change inside the Epic Cash cryptocurrency plugin that the developer describes as fixing a 'shared static worker.' Without seeing the actual code change, it is impossible to tell whether this is a routine bug fix or a security-sensitive correction. The phrase suggests a static/shared resource may have been handled incorrectly, which can sometimes lead to crashes or race conditions, but no security impact is confirmed by the materials.

This is a one-line change to Epic Cash cryptocurrency plugin code, described as fixing return types and response handling. Without seeing the actual code change, we cannot determine whether this is a routine bug fix or something with security consequences. The description does not mention security.

This commit updates how the Epic Cash wallet in Stack Wallet talks to its underlying Rust library (flutter_libepiccash). It moves some configuration data (epicboxConfig) into wallet load/create calls and removes it from individual transaction/address calls, matching a new library API. It also replaces a real address-validation check with a very simple length check, which could let users paste in malformed or wrong addresses. The change looks like a compatibility/refactoring patch rather than a deliberate security fix, but the weaker address check is a small security regression.

This commit refactors how the Epic Cash wallet in Stack Wallet talks to its underlying Rust library. Instead of repeatedly reading a wallet handle from secure storage and passing it to a global library interface, it now keeps an in-memory wallet object (an 'EpicWallet') and runs operations on that object, often inside a separate worker isolate. The change also adds explicit wallet-close calls on shutdown. The overall direction improves isolation and cleanup, but the commit is described as a work-in-progress ('TODO: test more'), so it may not be a complete or fully tested security fix.

This commit adds a mutex (a simple locking mechanism) around the Epic Cash wallet's openWallet function to prevent multiple operations from running on it at the same time. Without the lock, concurrent calls could potentially corrupt wallet state or cause crashes. The change is very small and the actual code diff was not available, so the exact risk is hard to judge.

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.

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.