Dash Platform has never been that close to the release! In this wrap-up, we will provide an overview of the latest developments and updates to the Dash Platform, highlighting the progress.
Watch the video or check the short summary below!
Dashmate stabilization
What We Planned
- Testing Dashmate in progress
- Dashmate E2E tests in progress
- Dashmate debian package for arm64 done
- Remove Docker dependencies from debian package done
- Warning to open Dashmate package for Mac done
- Generate random RPC user and password on
dashmate setup
done - Can't find begoo/index with
yarn dashmate setup
done - Reward shares can be negative during HP masternode registration done
- When submit the form with BLS private key and reward share, it accepts invalid BLS key done
What Is Done
- Invalid protx register command in output of
dashmate setup
done - Dashmate status shows empty masternode status done
- Select number of masternodes during local setup freezes done
- Error form ZeroSSL during IP address verification done
- Dashmate for Windows doesn't handle paths properly done
- Provide helpful information if Docker or Docker Compose v2 is not installed done
- The Docker socket not found error using Docker Desktop done
- Dashmate local setup ends up with deadline exceeded error done
- Multiple Dashmate group reset command issues done
v0.24 deployment
What We Planned
- Update deployment tool to deploy with dashmate version and branch done
- Platform v0.24-dev deployment and testing on devnet done
- Handle double init chain call in Drive done
- Handle duplicated masternode keys on testnet done
- Platform v0.24-dev deployment to testnet in progress
- Failed recovering or verifying threshold signature: threshold block signature is invalid in progress
- Compare js-dpp and wasm-dpp tests done
- createdAt != updatedAt on document create done
v0.25 Development
What Is Done
- Masternode Identities in review done
- Persist ephemeral state in testing done
- Completely clean DPP serialization and deserialization done
- We used Proc Macros (very clean code)
- Implemented a Proc Macro for signable bytes done
- Initialize chain on same state transition done
- Validator set update on init chain done
- Heavy tests for masternode list updates done
- EDDSA-Hash160 key type done
- System Key Purpose type done
- Non unique keys full support (public key hashes, script hashes) done
- v0.24 backports (Up till Friday) done
Deployment - Phase 1 (Dashmate Local)
- Successfully deployed to Dashmate
- Currently on height 7000 + with absolutely no errors
- Multiple Validator Set Rotations have happened
- Will try to run for two more weeks to see masternode payouts
Deployment - Phase 2 (Devnet)
- Multiple deployments in progress Goal: Test Platform activation when core transitions from v19 to v20
- Deployment 1 (failed): 1 wrong parameter Fixed
- Deployment 2 & 3: Failed because of issue in RPC Core client (both times some optional fields were not allowed to be empty) Fixed
- Deployment 4 and more in progress
What Is Left
- Fix queries / SDK.
- Validation costs
- Just in time atomic state transition payments
- Finalization of withdrawals
- Versioning in progress
- A lot of Testing
Core Team
V19 Core Upgrade Status
- Hard Fork signalling began
- ~17.5% Miner signaling
- Masternodes ~65% updated
- Earliest Possible Activation May 13th -> May 20th
Core Status - Current Development
- V19.0.1 Expected
- V20 On Chain CLSigs / Quorum Selection based on CLSigs in progress / partial devnet testing
- Implementation /backporting of GUIX; replacement for gitian in progress
- Enhanced Hard Fork Implementation in progress
- Asset Locks devnet testing
- Masternode Reward Location Reallocation in progress
- Merged PRs: 5334, 5336, 5338, 5339, 5346, 5341, 5340, 5255, 5348, 5351 done
Top comments (0)