Skip to content

Dash Platform v5.0.0-rc.5

Pre-release
Pre-release

Choose a tag to compare

View all tags
@shumkov shumkov released this 19 Oct 14:43
v5.0.0-rc.5
8fccc88
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The fifth release candidate of Dash Platform 5.0.

rc.5 does not change consensus or the protocol. Nodes can move from rc.4 at their own pace, and a network can run a mix of the two.

Highlights

  • Fewer extra consensus rounds. Drive now sends ChainLocks to Dash Core with the block hash in the order Core expects. Before, a validator whose Core had not yet seen a ChainLock could have it refused as an invalid signature and reject a valid proposal, costing the network an extra round. This affected every earlier release, including 4.1.
  • Core v24 masternodes in the Platform wallet. The wallet builds version-3 ProUpServTx for masternodes on Dash Core v24.
  • DashPay rescans resume after a restart. The Platform wallet persists how far it has rescanned DashPay contacts, so a relaunch continues instead of rewinding again. Stored wallet data is kept (the Room migration is additive), but apps must be rebuilt against the new SDK: two FFI structs grew, compiled Kotlin/Java code that constructs WalletEntity or DashpayContactRequestEntity must be recompiled, and Rust users get a new PlatformWalletInfo field and new enum variants.
  • SDK proof checks. Queries without a limit (votes, proposers, token distributions, groups) are now verified against the page Drive actually proves, and contested DPNS names are read as the bare labels Drive returns.

Upgrading

  • From rc.4: update dashmate and restart Platform. Core does not need a restart.
  • From rc.3 or 4.1.x: follow the rc.4 notes.

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

Assets 19
Loading