arrow_drop_down

RVA Wallet Changelog

This page summarises public changes to RVA Wallet, with a focus on security, reliability and compliance, without exposing sensitive internal details.

Applies to: RVA Wallet iOS & Android apps and wallet backend services

Quick Links

* High level changes only. Internal details and security-sensitive information are not published.

Release 2025.3

November 2025

Security updateComplianceStability

Security hardening and reliability improvements following independent security review. Recommended for all users.

Security & privacy

  • Strengthened protection against use of the wallet on compromised devices by tightening checks around device integrity.
  • Improved safeguards on network connections, reducing the risk of data interception on untrusted networks.
  • Refined internal handling of sensitive events to minimize data logging in line with best practice.

Features & UX

  • Clarified on-screen messages related to security prompts and transaction confirmations.
  • Polished visual elements in the portfolio and transaction history views.

Performance & reliability

  • Optimised background processes for transaction monitoring to reduce delays under high load.
  • Improved timeouts and retries for network calls, resulting in more stable behaviour on slow connections.

Integrations & compliance

  • Verified compatibility with the latest requirements of major app stores and key service providers.

Release 2025.2

September 2025

FeaturesUXIntegrations

Introduces UX refinements for portfolio management and updates to third party integrations for buy/sell flows.

Security & privacy

  • Added clearer messaging when users leave the app interface to complete a transaction with third-party providers.
  • Fine-tuned privacy settings to ensure analytics remain strictly opt-in and anonymised.

Features & UX

  • Enhanced portfolio dashboard visibility for overall holdings.
  • Refined search and filtering in token and transaction lists.

Performance & reliability

  • Improved responsiveness in portfolio view by optimising balance and price refreshes.
  • Reduced temporary 'cannot fetch data' messages by smoothing out connectivity handling.

Integrations & compliance

  • Updated configuration for buy/sell flows to align with partner changes.
  • Adjusted market data display to remain consistent with upstream providers.

Release 2025.1

June 2025

LaunchStabilityUX

The initial public version of RVA Wallet, focused on stability, usability and establishing the core non-custodial architecture.

Security & privacy

  • Tightened login and recovery flows to reduce risk on shared devices.
  • Added reinforced messaging about secure storage of the Secret Recovery Phrase.

Features & UX

  • Improved first-time user onboarding with clearer non-custodial explanations.
  • Streamlined navigation between wallet, portfolio and settings.

Performance & reliability

  • Fixed rare crash scenarios discovered during beta.
  • Reduced load times for transaction history and balances.

Integrations & compliance

  • Verified third-party service integrations for production loads.
  • Ensured app store listings and privacy disclosures reflect live implementation.

Earlier Releases

Pre-2025

Earlier releases – Initial public releases and internal hardening

Before the public launch, earlier releases focused on establishing the core non-custodial architecture, building multi-network support, laying down monitoring foundations, and running internal security reviews.

* Detailed internal release notes for these versions are maintained for audit purposes but are not published to avoid exposing sensitive implementation details.

About this changelog

This changelog is intentionally high level. It is designed to give users, partners and regulators a clear view of how RVA Wallet evolves over time, without sharing information that could meaningfully assist malicious actors.

Security Redaction Notice

For security reasons, we do not publish:

  • Internal system names, infrastructure details or environment configuration.

  • Exact technical descriptions of security vulnerabilities or check locations.

  • Credentials, keys, identifiers or anything targeting the platform.

More detailed documentation is available to regulators and key partners under appropriate confidentiality arrangements.