Skip to content

chore(release): update changelog and bump version to 0.25.7#1507

Closed
shumkov wants to merge 1 commit into
masterfrom
release_0.25.7
Closed

chore(release): update changelog and bump version to 0.25.7#1507
shumkov wants to merge 1 commit into
masterfrom
release_0.25.7

Conversation

@shumkov

@shumkov shumkov commented Oct 18, 2023

Copy link
Copy Markdown
Collaborator

Issue being fixed or feature implemented

Release new Dash Platform version

What was done?

  • Updated changelog
  • Bumped packages version

How Has This Been Tested?

None

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@shumkov shumkov added this to the v0.25.x milestone Oct 18, 2023
@shumkov shumkov closed this Oct 18, 2023
@shumkov
shumkov deleted the release_0.25.7 branch October 18, 2023 16:24
bfoss765 added a commit to bfoss765/platform that referenced this pull request Jul 12, 2026
…ed scan persists CoinJoin spends (dashpay#1507)

The interim `debit_router_omitted_asset_lock_spends` ran at step 4b right
after broadcast and did a bare in-memory `utxos.remove()` +
`update_balance()` with no changeset queued. Because it stripped the
spent CoinJoin/DashPay UTXO before dash-spv's async scan, the router-
fixed `check_core_transaction` found no UTXO, emitted no TransactionRecord
for that account, so `derive_spent_utxos` saw empty `input_details` and
the deletion was never persisted — the dashpay#1507 balance re-inflates on the
next restart.

Now that the rust-dashcore router fix is vendored (CoinJoin +
DashpayReceivingFunds + DashpayExternalAccount in
`get_relevant_account_types(AssetLock)`), the normal pipeline debits and
persists these spends: the scan produces a record whose `input_details`
cover the spent outpoints, flowing through
`WalletEvent::TransactionDetected` -> `core_bridge::derive_spent_utxos`
-> the persister, surviving restart. Remove the mitigation and its call
site.

Replace the now-moot `broadcast_mitigation_and_router_fix_do_not_double_debit`
test with `router_fix_records_spent_coinjoin_input_for_persistence`, which
asserts the router-fixed scan emits a CoinJoin record whose input_details
resolve to the spent outpoint (the exact data the persister deletes by) —
directly covering the persistence gap the reviewer flagged. Existing
`router_fix_debits_coinjoin_asset_lock_spend_on_rescan` continues to cover
the in-memory debit + no-reinflation on rescan.

Co-Authored-By: Claude Fable 5 <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.

1 participant