v1.5.5

Argos 1.5.5 improves recovery reliability and protects sensitive recovery state.

Upgrading from an older release

Older workspaces without the new private-storage protections cannot be resumed or automatically migrated. Argos preserves them and uses a new default directory (workspace-v2 in the desktop app; argos_data_v2 in the CLI). Use your original seed, wallet file, or spending keys to start a fresh scan in a genuinely new data-directory path.

Before recovering funds again, reconcile every previously broadcast transaction using trusted evidence. Keep the entire old directory, journals, saved transaction bytes, and original recovery material until the funds and transactions are independently settled. Changing permissions or adding markers does not migrate old recovery state.

Fixes

• Resume authenticated wallet-file scans using the original wallet file and encryption password, without requiring a seed. Pasted Sapling-key scans can also resume using the same keys in their original order.
• Keep recovery dialogs inside the window with scrolling and reachable controls. Fix narrow-window address matching and conditional fields that could remain visible.
• Retry the specific canceled-connection error that could terminate compact-block recovery scans.
• Honor argos-gui --verbose --scan-batch-size 100; the GUI previously ignored these options and continued using 1,000-block batches. The effective batch size is logged at startup.
• Refuse incompatible destinations and memos before resuming; prevent duplicate resume submissions and release temporary wallet reviews after each attempt.
• Strengthen private recovery storage, wallet-file review binding, and secret cleanup across Windows, macOS, and Linux.
• Harden account-gap and mixed seed/standalone-key database rebuilds, including interrupted rebuilds and Windows file-sharing conflicts.
• Add regression coverage for Sprout execution-time re-verification and recovery-source identity checks.