{"id":106813,"date":"2023-05-15T14:08:24","date_gmt":"2023-05-15T14:08:24","guid":{"rendered":"https:\/\/wp.dash.org\/?p=106813"},"modified":"2023-05-15T15:35:58","modified_gmt":"2023-05-15T15:35:58","slug":"dash-core-group-release-announcement-dash-platform-v0-24-on-testnet","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/blog\/dash-core-group-release-announcement-dash-platform-v0-24-on-testnet\/","title":{"rendered":"Dash Core Group Release Announcement: Dash Platform v0.24 on Testnet"},"content":{"rendered":"
Release Highlights include: Identity v2 improvements, Headers first synchronization in JavaScript SDK, Porting DPP to Rust, a New Fee System, Same-block execution, Dashmate Improvements, Protocol Version Signaling, Decentralized API with HTTPS, Dash Network Deploy Tool updates<\/span><\/i><\/p>\n Dash Core Group is pleased to announce the release of Dash Platform v0.24 on testnet. <\/span>The primary focus of this version was the introduction of the Rust port for the Dash Platform Protocol, which was originally implemented in JavaScript. Another major improvement is an implementation of same-block execution approach for Platform chain. This allows block commitment and signing within a single block, an improvement over the previous two-block system.<\/span><\/p>\n This version also includes two groundbreaking features to the blockchain industry: total balance verification and fee refunds. The total balance verification protects against inflationary bugs and attacks. It ensures that the total amount of Dash on Platform is always equals to the amount brought in minus the amount withdrawn. With this release, we’re also introducing an update to our state transition fee system, dividing fees into storage and processing components. Furthermore the implementation of decentralized identities on Dash Platform has seen numerous enhancements allowing more fine grained requests, lower storage and processing costs.\u00a0<\/span><\/p>\n As with our previous updates, v0.24 brings many other technical improvements. These touch on dependencies and Platform components such as the Dash Network Deploy tool, Tenderdash, Dashmate, GroveDB, and the JavaScript SDK. We would like to mention that the release notes for this update also encompass changes from Platform v0.23. Although it was never formally announced or launched on the testnet, its developments have been integrated into v0.24.<\/span><\/p>\n While this release of the Platform remains in the beta stage, the first component, Dashmate, is now fully prepared for mainnet nodes deployment. We recommend utilizing Dashmate to configure your first Evonet masternode.<\/span><\/p>\n We encourage you to follow our <\/span>Dash Platform Product Review<\/span><\/a> right after the v0.24 testnet deployment. It summarizes the whole increment provided with that version and brings some use cases that are covered with these improvements.<\/span><\/p>\n Version 0.24 was a massive undertaking that we are all very proud of. For the last two or so months we got to a point where adding more people would not have sped up development. This is why we started parallel work on version 0.25. The most major difference between v0.24 and v0.25 is a rewrite of the block execution logic from Javascript to Rust. Having one part of the project in Javascript (Block Executor) and other parts in Rust (Protocol – Drive – GroveDB \u2026) required an adapter called the Protocol WASM bindings. This adaptor was often a source of issues and was very time-consuming.\u00a0<\/span><\/p>\n Having the main Platform Application logic all in Rust is a major simplification of the application architecture and will accelerate the development pace going forward. It will also greatly reduce memory overhead and speed up state transition block processing allowing more transactions per second. We are confident that while this approach might have added more development work in the short term, the benefits will allow us to reach a stable Mainnet faster.<\/span><\/p>\n After this 0.24 release, our goal is to get a beta release of v0.25 out for internal and external developers to test and work on as soon as possible. This is why we are splitting the next release into three phases: v0.25.0-beta.1, v0.25.0-beta.2 and finally renaming it to v1.0.0-rc.1.<\/span><\/p>\n The first phase is estimated to be complete in approximately a week with a deliverable of a version to an open Devnet that we will make public, giving external developers the choice to try out this nightly version. Doing this is necessary to preserve our main testnet for testing the actual release upgrade process.<\/span><\/p>\n Here is a non-exhaustive list of more notable features that will be present in our Beta-1, all features in this list are <\/span>done and in testing<\/b> unless otherwise stated.<\/span><\/p>\n In the second phase we will be reorganizing into two platform teams, one will be actively testing finished components while the other will be working on the following final features. These features are generally for items that are less important for developers but needed for the mainnet release, these are:<\/span><\/p>\n To recap here is the updated rough timeline:<\/span><\/p>\n v0.25-beta.1 – Estimated 22th May Open Devnet – Start of testing phase.<\/span><\/p>\n v0.25-beta.2 – Mid June Testnet – Second period testing phase.<\/span><\/p>\n V1.0-RC-1 – Mid July testing phase over – Release candidate<\/span><\/p>\n Platform v0.24 introduces several breaking changes which make previous Platform data invalid. Platform state data has hence been wiped. On the other hand, there have been no changes to the Dash Core Payment chain, ensuring the preservation of all historical payment transactions and blocks.<\/span><\/p>\n Please join us with testing the platform version v0.24 and <\/span>setup your node<\/span><\/a> for testnet. To update your existing node please <\/span>update the distribution package and reset platform data<\/span><\/a>.<\/span><\/p>\n We would like to thank all developers, testers, masternode owners and community participants who have made this release possible.<\/span><\/p>\n Follow the Dash blog and social media channels (especially <\/span>Youtube<\/span><\/a>) for more announcements and updates and as usual – your thoughts, feedback and suggestions are greatly appreciated.<\/span><\/p>\n Please note that the Dash Platform repository has been moved to the <\/span>dashpay GitHub organization<\/span><\/a>. All development and pull request activity can now be found at <\/span>https:\/\/github.com\/dashpay\/platform<\/span><\/a>.\u00a0<\/span><\/p>\n Authors:<\/span><\/p>\n Ivan Shumkov, Lead Platform Software Engineer<\/span><\/p>\n Samuel Westrich, Chief Technology Officer<\/span><\/p>\n ThePhez, Head of Documentation<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"Release Highlights include: Identity v2 improvements, Headers first synchronization in JavaScript SDK, Porting DPP to Rust, a New Fee System, Same-block execution, Dashmate Improvements, Protocol Version Signaling, Decentralized API with HTTPS, Dash Network Deploy Tool updates Dash Core Group is pleased to announce the release of Dash Platform v0.24 on testnet. The primary focus of…","protected":false},"author":66,"featured_media":106816,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[290],"tags":[],"class_list":["post-106813","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"yoast_head":"\nRelease Highlights<\/span><\/b><\/h1>\n
\n
\n
\n
What\u2019s next?<\/span><\/h1>\n
\n
\n
\n
\n
Deployment and Testing<\/span><\/h1>\n
Release Notes<\/span><\/h1>\n
\n