Repository navigation
A patch release for the 5.0 line. It makes the JavaScript SDK sync block headers on the real Dash chain again, lets dashmate build local networks on Dash Core 24, and brings several wallet and SDK fixes from the 5.1 line.
Highlights
- JavaScript wallets sync block headers again. A fresh wallet in the JS SDK (
dash8.0.2 and earlier) failed header sync on mainnet at block 25 and on testnet at block 41, because header difficulty was not checked the way Dash Core checks it. It now is. A header-sync error no longer crashes the process or hides its real cause. - dashmate sets up local networks on Dash Core 24.
dashmate setup localworks with a Dash Core 24 image again.
Bug fixes
- Platform wallet:
- A coin whose transaction is confirmed (or InstantSend-locked) is restored as confirmed, instead of staying unconfirmed forever.
- The change of an asset lock resumed after a restart now reaches the app's database when the lock is confirmed.
- Concurrent shielded syncs no longer duplicate note commitments, and zero-amount shielded spends are refused before any notes are reserved.
- Resuming asset locks through the FFI no longer risks a stack overflow.
- SDK:
- Compacted address balances are queried correctly when the recent proof has no boundary.
- wasm DAPI requests use the right path, and wasm-sdk builds without its default features.
- dashmate:
ssl obtainwaits for the previous container to be removed.
Breaking change (FFI only)
UtxoRestoreEntryFFI gains two fields (152 → 160 bytes on 64-bit). The Swift package and the JNI crate in this repository are built against the matching header; an out-of-tree C consumer of this struct must be rebuilt. No stored data changes.
Full changelog: https://github.com/dashpay/platform/blob/v5.0.3/CHANGELOG.md