Dash Platform v1.7.0, supporting Dash Core v22.0, is Officially Released!

splawik21

splawik21

Yeah, it's me....
Staff member
Dash Core Group
Foundation Member
Dash Support Group

Dash Platform v1.7.0​


We are happy to announce the release of the Dash Platform v1.7.0 🎉
This is a mandatory release.

AMD64/x86 (linux):
Code: 
wget https://github.com/dashpay/platform/releases/download/v1.7.0/dashmate_1.7.0.b265bb81c-1_amd64.deb
sudo apt update
sudo apt install ./dashmate_1.7.0.b265bb81c-1_amd64.deb
dashmate update && dashmate restart --safe
dashmate status

ARM64 (linux):
Code: 
wget https://github.com/dashpay/platform/releases/download/v1.7.0/dashmate_1.7.0.b265bb81c-1_arm64.deb
sudo apt update
sudo apt install ./dashmate_1.7.0.b265bb81c-1_arm64.deb
dashmate update && dashmate restart --safe
dashmate status

Features​

  • sdk: ban addresses failed in sdk (#2351)

Bug Fixes​

  • drive: security vulnerability in hashbrown (#2375)
  • sdk: create channel error due to empty address (#2317)

Build System​

  • explicitly require tonic v1.12.3 (#2357)

Continuous Integration​

  • remove manage runs workflow (#2325)
  • replace actions/upload-artifact@v3 with actions/upload-artifact@v4 (#2359)

Miscellaneous Chores​

Code Refactoring​

  • sdk: unify state transition processing (#2338)
  • sdk: separate dash core client error

âš  BREAKING CHANGES​

  • sdk: AddressList.available removed
  • sdk: you need to use Waitable to call wait_for_response()
  • sdk: changed multiple args of functions in state transition broadcast logic
  • sdk: From<Uri> for Address replaced with TryFrom<Uri> for Address
  • sdk: From<&str> for AddressList replaced with FromStr for AddressList
  • sdk: FromIterator<Uri> for AddressList replaced with FromIterator<Address> for AddressList
  • sdk: LowLevelDashCoreClient now returns DashCoreError instead of ContextProviderError.
  • sdk: Added ContextProviderError: DashCoreError variant
  • sdk: dash_sdk::Error::CoreClientError now uses DashCoreError instead of dashcore_rpc::Error.
 
From QE :

Knipsel.JPG


Knipsel.JPG
 
To all Evonode operators :

Looks like the idea is now that we will go with Platform v1.7.0 after all. But please wait with updating to Platform v1.7.0 untill we are in new Platform epoch 12 (15th of December 2024, 11:00 AM).

@tfoto no problem, we just need to make sure not every Evonode operator update to v1.7.0 right away. The rest of us need to wait for next epoch, so the hard fork that was accidentally left in v1.7.0 (and will do nothing) can be re-used for a tokens feature.
 
Last edited:
Tenderdash Docker Status │ running ║
║ Tenderdash Service Status │ syncing ║
║ Drive Docker Status │ running ║
║ Drive Service Status │ up

its ok?
 
tfoto said:
Tenderdash Docker Status │ running ║
║ Tenderdash Service Status │ syncing ║
║ Drive Docker Status │ running ║
║ Drive Service Status │ up

its ok?
Click to expand...
dashmate status (Platform Blockheight)
compare with : https://platform-explorer.com/blocks

Currently we are on Platform block 86119
Maybe your Evonode is still syncing to that block ? Check if it is stuck in status 'syncing' (you will have a problem then)

This is what it should look like with command dashmate status platform :

Knipsel.JPG

(Platform v1.6.2)
 
Last edited:
Epoch 12 has started, update your Evonodes to the current version.
 
tfoto said:
what happened to blockchain? the blocks are moving very quickly..
Click to expand...
We had a problem with Platform withdrawals not getting picked up for the last few days.
So i ran a strategy test / stress test to generate a lot of state transitions to move things along and to make sure withdrawals got through this time.
Quantum Explorer is not sure if there is an issue worth fixing or not, so we will check if withdrawals will get picked up on their own tomorrow (without any help from us).

This is the result of the strategy test of almost two hours :

Knipsel.JPG

Source : https://platform-explorer.com/

All pending withdrawals (some 800 dash) got processed.

Also when Core v22 activate in a few weeks / month, the Platform withdrawals will get processed by a quorum every hour.
So that should hopefully improve things as well, with regards to Platform withdrawals.

By the way, there will be a Platform v1.7.1 out soon, because there is an issue with voting on contested usernames by mno's right now.
mno's may want to keep an eye on it.
 
Last edited:
Update from Quantum:

Masternode voting on the Platform chain (for usernames) turned out to be broken in Protocol Version 6 (Version 1.6.x onwards). Currently voting does not work on an Evonode or Masternode if you have voted over 24 times. It was a small oversight where we would validate against the Owner Identity instead of the Voting Identity for protection against replay attacks. We are releasing an upgrade to Version 1.7.1 that fixes this issue.We have decided to make this an emergency upgrade, that means that Evonodes/Masternodes that have not upgraded by the end of the epoch (around the 24th of December) will stall.Quick cheatsheet (coming from 1.7.0):

AMD64/x86 (linux):

Code: 
wget https://github.com/dashpay/platform/releases/download/v1.7.1/dashmate_1.7.1.fc7d994b8-1_amd64.deb
sudo apt update
sudo apt install ./dashmate_1.7.1.fc7d994b8-1_amd64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

ARM64 (linux):
Code: 
wget https://github.com/dashpay/platform/releases/download/v1.7.1/dashmate_1.7.1.fc7d994b8-1_arm64.deb
sudo apt update
sudo apt install ./dashmate_1.7.1.fc7d994b8-1_arm64.deb
dashmate stop --platform
dashmate update
dashmate start --platform

If you are upgrading from 1.6.x you should also do
Code: 
dashmate restart --safe
 
You must log in or register to reply here.
Back
Top