{"id":109726,"date":"2024-07-29T17:16:48","date_gmt":"2024-07-29T17:16:48","guid":{"rendered":"https:\/\/wp.dash.org\/?p=109726"},"modified":"2024-07-29T17:43:14","modified_gmt":"2024-07-29T17:43:14","slug":"dash-evolution-v1-0-0-release-announcement","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/dash-evolution-v1-0-0-release-announcement\/","title":{"rendered":"Dash Evolution v1.0.0 Release Announcement"},"content":{"rendered":"
Today I am very pleased to announce the release of Dash Evolution v1.0.0 and mark the turning of a new page in our project\u2019s history. This release has been a culmination of a great many efforts over many years.<\/span><\/p>\n Today\u2019s release supports most of the core functionalities that we wanted for v1.0.0. It is occurring under an accelerated release schedule, and as such some features that we originally envisioned at release did not make it in. Most notably, balance withdrawals will not be active until the code is fully reviewed and tested, something we have not yet had time for. This had been previously communicated with the voting network that approved this plan. We estimate at this point that the next release enabling withdrawals will come out the Monday following the first distribution of credits which should be 9.125 days after activation.<\/span><\/p>\n Features that are supported in v1.0.0 include:<\/span><\/p>\n While the system has proven to be very secure thanks to innovations such as GroveDB sum trees and an acceptable amount of testing, the testing phase was cut slightly short for the purpose of getting a release out faster. It is expected that some issues may arise, mainly as a result of the differences between a smaller, DCG-controlled network (testnet) and a fully decentralized, global network, with more nodes than are used on a testnet, as well as some additional related nuances. To be clear this means that there is a likelihood of a chain stall on Mainnet in the first few months, but a close to non-existent chance of an attack that would cause money to be lost.<\/span><\/p>\n In addition, since we were testing up till the date of release we uncovered a few issues that might warrant a patch update within the upcoming weeks.<\/span><\/p>\n We have decided to release Dashpay and Dash Platform Name Service in v1.0.0, two features that inspired the idea of creating Dash Evolution. That means that as soon as Platform activates, you will be able to get your Dash username.<\/span><\/p>\n In order to prevent early adopters of DPNS to capture all popular names, such as Coca-Cola, for the purpose of reselling at a higher value later, we have introduced a \u201ccontested usernames\u201d system. A Dash username that contains only letters, 0s, 1s and hyphens is considered a contested username. In order to get a contested username, a user must submit to register a username and pay a 0.2 Dash fee. The fee does not guarantee that the user is awarded the name, but it allows them to try to get it. A two-week voting phase will then start where masternodes vote on who, if anyone, the name will be awarded to. Other contenders for the same username can only join in the first week of voting. Masternodes and Evonodes are both able to vote and each vote is weighted based on their collateral. Masternodes are weighted 1 for 1000 Dash, and Evonodes are weighted 4 for 4000 Dash. They can also vote to lock a name so that it is not awarded at all. Locked names will be unlockable for a higher fee in a future version of Evolution. It is expected that unless a user can prove that they are, for example, the actual Coca-Cola company, names like that should be withheld from being awarded until Coca-Cola actually comes around to get the name.<\/span><\/p>\n Sam, Slim-Shady, Coca-Cola, only1<\/span><\/p>\n Examples of names that are not contested:<\/span><\/p>\n Trekkie123, LEET02, T2T4, only2<\/span><\/p>\n 0s and 1s are included in the contested usernames as all usernames have a normalized version to prevent phishing. For example: the usernames \u201clemon\u201d and \u201c1emon\u201d can be made to look alike in certain fonts, which can be used for a phishing attack. A user that gets the username lemon makes it impossible for another user to get the username 1emon.<\/span><\/p>\n What are the minimal\/recommended specifications for an Evonode?<\/b><\/p>\n <\/p>\n <\/p>\n We strongly recommend at least 4 CPUs or vCPUs at release. While it is possible that Evonode operators could get by with only 2 CPUs and 8GB of Ram, such a configuration will only work with light usage of Platform and you might see yourself missing a few payments if the chain gets any significant usage. If your configuration allows for easy updating we recommend starting with the recommended settings at release, then adjusting downwards or upwards depending on usage.<\/span><\/p>\n Documentation is provided here: <\/span>https:\/\/docs.dash.org\/en\/stable\/docs\/user\/masternodes\/setup-evonode.html<\/span><\/a><\/p>\n We will also provide a tutorial for upgrading from an existing Core node in the next 24 hours.<\/span><\/p>\nFeatures<\/span><\/h1>\n
\n
\n
\n
Stability<\/span><\/h1>\n
Dashpay and DPNS<\/span><\/h1>\n
\n<\/span>Examples of names that would be contested:<\/span><\/p>\nMinimal requirements<\/span><\/h1>\n
\n\n
\n <\/td>\n Minimal at release<\/span><\/td>\n Recommended<\/span><\/td>\n<\/tr>\n \n CPU<\/span><\/td>\n 4 CPU<\/span><\/td>\n 4 CPU<\/span><\/td>\n<\/tr>\n \n RAM<\/span><\/td>\n 8 GB<\/span><\/td>\n 16 GB<\/span><\/td>\n<\/tr>\n \n Storage<\/span><\/td>\n 130 GB<\/span><\/td>\n 200 GB<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Installation<\/span><\/h1>\n