Skip to content

Fix sync progress on rescan - #14

Merged
QuantumExplorer merged 1 commit into
developfrom
fix/sync-progress-again
Nov 27, 2018
Merged

Fix sync progress on rescan#14
QuantumExplorer merged 1 commit into
developfrom
fix/sync-progress-again

Conversation

@podkovyrin

Copy link
Copy Markdown
Contributor

We had to stop progress indicator before because notifications were not reliable (probably) but DashSync seems to send them right.

@QuantumExplorer
QuantumExplorer merged commit 6509ce0 into develop Nov 27, 2018
@podkovyrin
podkovyrin deleted the fix/sync-progress-again branch December 5, 2018 12:24
llbartekll added a commit that referenced this pull request Apr 9, 2026
Brings DASHSYNC_MIGRATION.md in line with what's actually shipped:

- Add "Where we are" entries for #5 wallet balance (commits
  2b447fc, f1b481b, 7c00be4) and #11 SPV chain sync via
  M5 + M6 (3cf5962 + 86ed727).
- Update #14 wipe entry to mention the post-#5 SPV stop +
  clearBalance calls.
- Flip Status column for rows #5 and #11 from `—` to `🌗 Flipped`.
- Update file paths and storage notes in rows #5/#6/#7/#11 to
  reflect the actual code locations and migration story.
- Drop the Core Data → SwiftData migrator from Hard Blockers.
  After the #5 work landed, the migrator turned out unnecessary:
  chain-derived data (UTXOs, tx history, masternode list, sync
  state) is re-derivable via SPV resync from SwiftDashSDK's own
  on-disk chain data. User-entered metadata (tx categories, tax
  categories, gift card receipts, address labels) was never in
  DashSync's Core Data — it lives in dashwallet's own SQLite via
  TransactionMetadataDAOImpl and AddressUserInfo, keyed by txHash
  / address, so it stays attached after resync automatically.
- Rewrite the "Storage migration" section with the corrected
  picture (no migrator required).
- Rework the "Recommended order" wave structure: the chain +
  balance push (Wave 2 now) ran ahead of DashPay/Platform work
  because the storage groundwork was unblocked. Tx history (Wave
  4 now) is the next big wave and follows the same shape as #5.

No code changes — doc only.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants