{"id":17171,"date":"2014-10-16T15:19:39","date_gmt":"2014-10-16T07:19:39","guid":{"rendered":"https:\/\/www2019.dash.org\/2014\/10\/16\/onyx-10-15-16-release-now-available\/"},"modified":"2021-09-18T11:40:19","modified_gmt":"2021-09-18T11:40:19","slug":"onyx-release-now-available","status":"publish","type":"post","link":"https:\/\/www.dash.org\/news\/onyx-release-now-available\/","title":{"rendered":"Onyx (10.15.16) Release Now Available"},"content":{"rendered":"

ATTENTION: POOL OPERATORS<\/strong><\/p>\n

This update includes a fork, all daemons and stratum deployments must update their code to pay the correct masternodes and correct reward amounts.<\/p>\n

Software Updates:<\/strong><\/em><\/p>\n

Stratum Users:
\nhttps:\/\/github.com\/darkcoin\/darkcoin-stratum\/commit\/4abf08bd0d3de7fae2311f54edb8a5f86f9ab39a<\/del><\/a><\/p>\n

NOMP Users:
\nhttps:\/\/github.com\/darkcoin\/node-stratum-pool\/commit\/e598fb0b6b643191304b257e0d8b0f47f8a5d34a<\/del><\/a><\/p>\n

P2Pool Users:
\nhttps:\/\/github.com\/darkcoin\/p2pool-DASH\/commit\/98a77c90d5dc460695cab71daed8d8aaab955289<\/del><\/a><\/p>\n

***EDIT (12\/19\/14): Outdated links have been removed. Please update to the most current version from the Downloads page or GitHub repository.***<\/em><\/span><\/p>\n

Deployment Schedule:<\/strong><\/p>\n

Immediately: Enforcement will be turned off, allowing for pools to update their software without risk of orphaned blocks<\/p>\n

Oct 23, 2014: Rewards will step up to 25%. Dash users are encouraged to contact pools that have not updated and politely ask them to update.<\/p>\n

Nov 14, 2014: Enforcement will be turned on, any pools that have not update will have their blocks rejected.<\/p>\n

Who Needs To Update?<\/strong><\/p>\n

All Dash users must update their clients.<\/p>\n

What\u2019s New?<\/strong><\/p>\n

Part of securing the Dash network is creating a strong and healthy network of full nodes to back it up. These nodes provide many tasks for users such as propagating messages, syncing clients and mixing users funds via Darksend.<\/p>\n

To make the network resistant to attack we required these nodes to hold 1000DASH (these coins are held in a completely trustless way in cold storage in most cases, so they can\u2019t be stolen). In return for holding the coins and running the node, these users are paid 20% of the block reward.<\/p>\n

Security for Darksend and InstantX is provided by selecting masternodes deterministically from the total set, then using multiple of these nodes to make decisions. Vastly greater security becomes possible when you add more nodes due to the cost associated with controlling a majority of said nodes. For statistical analysis of this please checkout the InstantX whitepaper<\/a> .<\/p>\n

Increasing Rewards Schedule<\/strong><\/p>\n

With this release we will progressively change the reward to incentivize the creation of more masternodes, this should strengthen the network and protect it from sybil attacks making it more expensive for attackers to control an important portion of the nodes.<\/p>\n

This is also key for instant transaction confirmations to be a reality, the network needs to be robust enough to handle a large amount of transactions as we strive for adoption on real world applications. The features that give value to Dash need to be protected as that is what will ensure the long term success of the project for the benefit of all Dash supporters, current and those that will join DASH in the future.<\/p>\n

*Currently there are 900 active masternodes. Numbers are expected to increase as profitability rises.
\n** ROI calculation is ((1\/t)*b*(r*s)*365)\/1000<\/p>\n

Where:
\nt = Total number of masternodes
\nb = Blocks per day on average (576 for Dash)
\nr = Average reward per block
\ns = Masternode mining share<\/p>\n

Steady Payments and Proof-of-Service<\/strong><\/p>\n

Another issue in the past has been the volatility in return due to the random nature of masternode payments. This is being dealt with by creating an algorithm to pay the masternodes evenly. Each masternode can expect a payment every N blocks with a variance of about 10%.<\/p>\n

Also included in this release is a framework that we can build a true proof-of-service platform on. This means only masternodes actually providing services will be paid for those services.<\/p>\n

To only pay active masternodes, pay masternodes evenly and ensure that all pools pay the correct node and amount we\u2019ve introduced a new type of node, the reference node. This node has a special key that allows it to tell the network which nodes get paid, on which blocks in the future. Anyone on the network can verify these nodes are doing their job (i.e. not tampering with the results) by running the code and comparing the payee\u2019s due to the deterministic algorithm used. In case of DDOS or a service failure, the network default to paying random masternodes as it does now.<\/p>\n

This setup is non-exploitable and will serve as a mechanism of enforcement till we can revisit this in the future. A better future solution would be an in-blockchain voting mechanism like RC3 or a second blockchain updated by the miners that stores the masternode list.<\/p>\n

Masternode Setup<\/strong><\/p>\n

Flare\u2019s Trustless Masternode Hosting Service:
\nhttps:\/\/dashtalk.org\/threads\/service-masternode-hosting-service.2648\/<\/a><\/p>\n

Yidakee\u2019s Service:
\nhttps:\/\/dashtalk.org\/threads\/yi\u2026tup-services-ghostplayer-on-bitcointalk.1633\/<\/a><\/p>\n

MangledBlue\u2019s Service:
\nhttps:\/\/dashtalk.org\/threads\/services-mn-shared-admin.2678\/<\/a><\/p>\n

How To Guide:
\nhttps:\/\/dashtalk.org\/threads\/taos-masternode-setup-guide-for-dummies.2680\/<\/a><\/p>\n

How To Guide 2:
\nhttps:\/\/dashtalk.org\/threads\/remote-masternode-guide-updated.410\/<\/a><\/p>\n

Just for fun:<\/p>\n