FundingPips is facing renewed questions over its economic-calendar accuracy after a trader alleged that a news event appeared to have finished before its restricted trading window actually ended, resulting in an account breach. Separately, a security review of proposed Monero wallet code identified a potential background-synchronisation problem, while Vultisig is investigating an Android bug that prevents certain users from swapping tokens through its two-device Secure Vault configuration.
The three developments, reported between October 29 and 30, concern different aspects of cryptocurrency and trading infrastructure. FundingPips’ case raises questions about how proprietary trading firms communicate restrictions and enforce account rules. The Monero finding concerns wallet recovery and blockchain synchronisation, while the Vultisig issue highlights a failure affecting multi-device transaction signing.
None of the reports establishes a widespread compromise or confirmed loss of cryptocurrency. However, they highlight how inaccurate platform information, proposed software changes and wallet-specific failures can create financial or operational consequences for customers.
FundingPips Faces Complaints Over Economic Calendar and News Restrictions
FundingPips is facing multiple customer complaints alleging that changes to the duration of economic-calendar events were not displayed consistently, potentially leaving traders unaware that their positions remained within a restricted news-trading window.
The latest complaint was published on October 29 by French reviewer Damien JUGE on Trustpilot. The trader alleged that an event on FundingPips’ official economic calendar initially appeared to have finished, only for its duration to be extended or displayed differently approximately 35 minutes later.
JUGE said the discrepancy created confusion over the permitted trading period and contributed to an account breach. FundingPips publicly responded to the complaint, confirming that the account had been suspended for violating its FundingPips Zero news-trading restrictions.
The company identified the relevant restricted event as running from 10:30 PM to 11:05 PM Dubai time. According to its response, the trader held a position during that period, which resulted in the account violation.
The company’s explanation establishes its position on the account closure, but it does not independently resolve the central calendar-display allegation. The available complaint does not include archived screenshots or timestamped records establishing precisely what duration the dashboard displayed when the trader made the trading decision.
The October 29 complaint was not isolated. On October 28, another reviewer, Harman Sidhu, reported an account breach involving a position opened at 6:44 PM UK time after an event displayed at 6:30 PM. A separate reviewer, Jovica S, alleged that delayed updates to event durations resulted in two funded-account closures.
These remain customer allegations rather than independently verified cases of incorrect enforcement. Nevertheless, the similarity between the complaints raises a specific operational question: whether traders were consistently shown the actual duration of restricted speeches and the corresponding trading window before making decisions.
FundingPips’ published FundingPips Zero rules distinguish between scheduled high-impact news releases and speeches. For scheduled releases, the restriction applies from 10 minutes before the event until 10 minutes afterward. For high-impact speeches, the restricted period starts 10 minutes before the speech and continues until 10 minutes after it actually ends.
Consequently, a speech lasting 35 minutes can legitimately produce a longer restricted period than an ordinary scheduled announcement. FundingPips also identifies its dashboard economic calendar as the official source for determining which events are restricted.
The distinction makes the accuracy of the calendar particularly important. If an event’s actual end time changes, traders need to know whether the dashboard updates that information immediately and whether previously displayed completion times remain visible or are replaced retrospectively.
FundingPips has faced other customer disputes involving account terminations, device identification and payout eligibility. Dave Finances previously examined complaints concerning FundingPips’ post-evaluation verification procedures, highlighting how enforcement decisions can become contentious when traders receive explanations after completing paid evaluations.
Monero Review Identifies Potential Background-Sync Cache Failure
Monero’s wallet software is facing a separate security review after an independent assessment identified a potential problem in proposed changes intended to correct inaccurate restore-height estimates when a wallet is created without access to a daemon.
The finding appeared in xmrack review #1406, published on October 29 at 23:06 UTC. It examined Monero pull request #11640, which proposes rechecking blockchain restore heights that were estimated using the local system clock when no daemon was available.
Wallet restore height determines how far back the software must scan the blockchain to identify transactions belonging to an account. An estimate that is too high can cause the wallet to skip blocks containing relevant transactions, potentially leaving the displayed balance incomplete.
The proposed change attempts to correct this by checking the estimated height against the blockchain reported by the connected daemon. If the estimated height exceeds the daemon’s current and target heights, the wallet can lower its starting point and scan additional blocks.
However, reviewers identified a potential interaction with BackgroundSyncReusePassword. If the restore-height adjustment occurs while background synchronisation is running, the wallet can clear information stored in its background cache. When synchronisation stops, the wallet may reject the cached results because the stored refresh-height settings no longer match.
The consequence, under the specific conditions described by the reviewers, could be the loss of information about outputs discovered during background scanning and associated spending records. The wallet could consequently display an incorrect balance or transaction history until the user performs a manual blockchain rescan.
The trigger is relatively narrow. It involves a wallet created while its daemon was unavailable, an estimated restore height above the connected chain’s height, and background synchronisation started before a successful normal refresh. The review classified the finding as low severity.
Importantly, pull request #11640 remained open and unmerged at the time of the review. The finding therefore concerns proposed code rather than an established regression affecting released Monero wallets.
The pull request also provides important context. Its author reported functional testing on regtest, including a scenario where an offline-created wallet previously displayed a zero balance despite having received mining rewards. The proposed change corrected that test case. Subsequent discussion clarified that the issue is primarily relevant to regtest configurations and unusual offline-creation circumstances, rather than a demonstrated loss of funds on Monero’s main network.
The review therefore identifies a potential cache-handling weakness in the proposed correction, not evidence that Monero’s cryptographic security or live-network transaction records have been compromised.
Vultisig Investigates Android Swap Failure on Two-Device Secure Vault
Vultisig is investigating a separate Android wallet problem after a user reported being unable to complete swaps from USDC to CAKE on the BNB Smart Chain when using its two-device Secure Vault configuration.
The issue was opened in the project’s public Android GitHub repository on October 30 at 09:57 UTC. The report concerns application version 1.0.123 and describes a failure affecting the BSC.USDC-to-BSC.CAKE trading pair.
According to the reproduction steps, the problem occurs when users configure a Secure Vault using two Android devices and attempt the specified swap. The transaction fails during the process, preventing completion. However, the same token pair reportedly works when using Fast Vault.
The distinction is important because it narrows the investigation toward the Secure Vault’s multi-device signing and coordination process rather than establishing a general problem with the swap route or the underlying tokens.
Vultisig’s issue description specifically asks developers to investigate differences between the Secure Vault and Fast Vault transaction flows, identify why multi-signature coordination fails and correct the signing logic without changing unrelated swap pairs or the working Fast Vault functionality.
The project marked the issue as high priority, although that classification reflects its internal development prioritisation rather than an assessment of financial losses or security severity.
No root cause has been established, and the report does not demonstrate that customer funds were stolen or that other networks and trading pairs are affected. The available evidence also does not establish whether the failure originates in transaction construction, signature coordination or another component of the Android application.
Platform Reliability and Transparent Enforcement Remain Key Issues
The three developments highlight different risks that can emerge when customers depend on software to manage trading restrictions, wallet balances and cryptocurrency transactions.
For FundingPips, the central issue is whether traders can rely on the economic calendar when the company uses it as the official reference for enforcing restrictions that can result in immediate account termination. The firm has explained why it considered the October 29 position a violation, but archived calendar displays and event timestamps would be needed to establish whether the customer received accurate information before the breach.
For Monero, the review demonstrates why software corrections need to be evaluated against different wallet configurations, not simply the scenario they were designed to address. A change intended to prevent skipped blockchain transactions should not inadvertently invalidate data collected during background synchronisation. The open pull request and its associated review discussion will determine whether maintainers modify the implementation before merging it.
For Vultisig, the difference between Secure Vault and Fast Vault performance makes the multi-device signing process the main area to watch. A successful swap through one configuration does not establish that the other is functioning correctly, particularly when transaction approval and signing involve additional coordination between devices.
The next developments worth monitoring are FundingPips’ response to questions about calendar-update timing, the outcome of Monero pull request #11640 and whether Vultisig can reproduce and resolve the Android swap failure. Until further evidence emerges, the FundingPips allegations remain disputed, the Monero finding remains limited to proposed code, and the Vultisig issue remains an unresolved user-reported software bug.
Together, the cases reinforce an important point for retail traders and cryptocurrency users: platform reliability is not limited to whether an exchange or wallet remains online. Accurate information, predictable enforcement and dependable transaction processing are equally important to customers who rely on these services to manage their money.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574