Dash Platform v5.0.0-rc.6

The sixth release candidate of Dash Platform 5.0.

No protocol change. Nodes can move from rc.5 at their own pace.

Highlights

• Evonode service updates after Dash Core V24. Once Core's V24 deployment is active, Core refuses an evonode ProUpServTx below version 3. The Platform wallet now builds version 3 as soon as the SPV client sees V24 (a version-4 coinbase in the masternode list diffs, or a version-3 list entry), and returns a retryable error while it cannot tell yet. Wallet apps that update or unban evonodes through the Swift or Kotlin SDK should ship a build with this release before V24 activates. The V24 signal comes from the coinbase that SPV peers serve with masternode list diffs and is not yet verified against the block; a verified signal follows in a later release.
• Clearer refusal for transitions that are not active yet. A state transition whose type or version is not active at the current protocol version is now refused with a StateTransitionNotActiveError consensus error (still free), instead of an internal error.
• DAPI Core-call limit holds. rs-dapi keeps its Core RPC slot until Core answers, so Core-backed endpoints can no longer pile up leftover calls.
• SDK. Document writes persist the owner balance their proof carries.
• Dependencies. GroveDB 6.1.1 (debugger-only change), plus security updates to h2, rustls, quinn-proto, crossbeam-epoch, rust_decimal and several npm packages. The rust-dashcore pin moves to the 5.0 integration branch's a40daba7.

Upgrading

• From rc.5: update dashmate and restart Platform. Core does not need a restart.
• From rc.4 or earlier: follow the rc.5 notes first.

Full changelog: https://github.com/dashpay/platform/blob/v5.0.0-rc.6/CHANGELOG.md