{"id":17174,"date":"2014-10-01T22:06:09","date_gmt":"2014-10-01T14:06:09","guid":{"rendered":"https:\/\/www2019.dash.org\/2014\/10\/01\/development-update-october-1-2014\/"},"modified":"2021-09-18T11:40:19","modified_gmt":"2021-09-18T11:40:19","slug":"development-update-october-1-2014","status":"publish","type":"post","link":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/","title":{"rendered":"Development Update – October 1, 2014"},"content":{"rendered":"

Darksend seems to be very stable and now that we\u2019re open source and we\u2019ve passed an audit I think it\u2019s time to work on some other functionality. We\u2019re working out of development plan for the next weeks weeks and here\u2019s what we have so far.<\/p>\n

Masternode Security<\/b><\/h3>\n

There are a few things that are missing in Dash to properly implement\u00a0InstantX<\/a>). One of the greatest objections to InstantX from the Bitcoin community was the possibility to DOS the selected masternodes that are responsible for consensus voting.<\/p>\n

This would stop the consensus voting forcing the network to evaluate transactions using the mining network, bring the first confirmation from 10-20 seconds back to 2.5 minutes. While not a terrible issue, it\u2019s something we can deal with by hiding the masternode identities and using a token based routing system to pass messages back and forth. This will be discussed in great detail in the v2 of the Dash whitepaper.<\/p>\n

To build a network that can withstand attacks, the masternodes must not publish their IPs. To do this we\u2019re going to utilize a new multipath communication technology. This will add another layer of privacy to the system as it will allow users to communicate with the network securely without exposing their IPs and will also hide the identity of the Darksend mixing nodes making it extremely difficult, if not impossible, for third parties to spy on users information.<\/p>\n

It uses multi-path routing so users can send more than one encrypted message using different routes on the mesh network for redundancy. This will allow us quick communication, robustness and anonymous two way communication.<\/p>\n

The diagram below shows the new system in action:<\/p>\n

Enforcement<\/b><\/h3>\n

Currently there is a very basic version of enforcement that is going to be enabled soon.<\/p>\n

The strategy employed by Dash currently to protect masternode payments is definitely not a perfect solution and wasn\u2019t meant to stay in this form forever. While it does make cheating much more difficult, it\u2019s still remains possible.<\/p>\n

The next version of enforcement will be a huge improvement over this current version and will introduce much greater security.<\/p>\n

Masternode Reward Structure<\/b><\/h3>\n

The Dash network relies heavily on the strength of the Masternode network. They are the foundation of our currency in provide great value to the network. Whether it be serving the blocks to a client that is syncing or proving the services such as Darksend and InstantX.<\/p>\n

While writing the whitepaper for InstantX and v2 of Dash, I\u2019ve realized that the network would gain an incredible amount of security by increasing the amount of running Masternodes. When originally envisioned, the target number of masternodes was 2000-3000. I\u2019ve waited some time to see if the amount of active Masternodes will increase alone, but I\u2019m beginning to think some tweaking is in order.<\/p>\n

The number of Masternodes reaches an equilibrium with the price of Dash and the ROI of running a node over a period of time. Currently we have about 900 total Masternodes (some haven\u2019t updated to RC5 yet, but you can see the stats\u00a0here<\/a>), with this amount of nodes each has a ROI of 23%<\/p>\n

It can be calculated with: ((a\/b)*c*d*e)\/1000)
\na is the amount of Masternodes you control
\nb is the total amount of Masternodes
\nc is the amount of blocks per day
\nd is the days in a year
\ne is payment per block won<\/p>\n

So with that in mind the current profitability can be calculated by<\/p>\n

((1\/900.0)*576*365*(5*.20))\/1000 = 0.23 (23% per year ROI in DASH)<\/i><\/p>\n

The reward of 23% can be thought of as the current equilibrium that the network has found. So it is expected that no matter the reward structure, the network will come to rest as this level.<\/p>\n

If our goal is to gain more Masternodes to improve the overall security of the network, I propose increasing the reward structure for Masternodes by 5% every month until the optimal amount of Masternodes is reached. This can be thought of as a type of\u00a0price discovery<\/a>. It’s also worth noting, by adding 5% rewards per month we’ll have a decreasing amount of impact each month thereafter. From 20% to 25% is a 25% change, from 25% to 30% is a 20% change, then 16.6%, 14.2%, 12.5%, etc. This will allow a good deal of reaction time.<\/p>\n

This also means that Dash must be purchased in order to start new Masternodes. This doesn\u2019t include Masternodes selling their existing node\u2019s Dash in order to cash out (that wouldn\u2019t change the Masternode total count). Considering this, we should see very long term steady growth, gain a lot of media attention and gain real-world adoption.<\/p>\n

I believe this update will be great for Dash by increasing the security of InstantX and Darksend, while providing significant growth for Dash. An update like this requires a very solid version of enforcement along with updates to the daemon to tell the pool operators how much Dash is suppose to be paid to the current Masternode operator.<\/p>\n

FAQ:<\/p>\n

Can’t we just decrease the amount required to run a Masternode:\u00a0https:\/\/dashtalk.org\/threads\/development-update-oct-1-2014.2561\/page-4#post-23297<\/a><\/p>\n

PS. Thanks to BabyGiraffe for inspiring this conversation about Masternode Payments.<\/p>\n","protected":false},"excerpt":{"rendered":"

Darksend seems to be very stable and now that we\u2019re open source and we\u2019ve passed an audit I think it\u2019s time to work on some other functionality. We\u2019re working out of development plan for the next weeks weeks and here\u2019s what we have so far.<\/p>\r\n

Masternode Security<\/b><\/h3>\r\n

There are a few things that are missing in Dash to properly implement\u00a0InstantX<\/a>). One of the greatest objections to InstantX from the Bitcoin community was the possibility to DOS the selected masternodes that are responsible for consensus voting.<\/p>\r\n

This would stop the consensus voting forcing the network to evaluate transactions using the mining network, bring the first confirmation from 10-20 seconds back to 2.5 minutes. While not a terrible issue, it\u2019s something we can deal with by hiding the masternode identities and using a token based routing system to pass messages back and forth. This will be discussed in great detail in the v2 of the Dash whitepaper.<\/p>\r\n

To build a network that can withstand attacks, the masternodes must not publish their IPs. To do this we\u2019re going to utilize a new multipath communication technology. This will add another layer of privacy to the system as it will allow users to communicate with the network securely without exposing their IPs and will also hide the identity of the Darksend mixing nodes making it extremely difficult, if not impossible, for third parties to spy on users information.<\/p>\r\n

It uses multi-path routing so users can send more than one encrypted message using different routes on the mesh network for redundancy. This will allow us quick communication, robustness and anonymous two way communication.<\/p>\r\n

The diagram below shows the new system in action:<\/p>\r\n

\"[\u200bIMG]\"<\/p>\r\n

Enforcement<\/b><\/h3>\r\n

Currently there is a very basic version of enforcement that is going to be enabled soon.<\/p>\r\n

The strategy employed by Dash currently to protect masternode payments is definitely not a perfect solution and wasn\u2019t meant to stay in this form forever. While it does make cheating much more difficult, it\u2019s still remains possible.<\/p>\r\n

The next version of enforcement will be a huge improvement over this current version and will introduce much greater security.<\/p>\r\n

Masternode Reward Structure<\/b><\/h3>\r\n

The Dash network relies heavily on the strength of the Masternode network. They are the foundation of our currency in provide great value to the network. Whether it be serving the blocks to a client that is syncing or proving the services such as Darksend and InstantX.<\/p>\r\n

While writing the whitepaper for InstantX and v2 of Dash, I\u2019ve realized that the network would gain an incredible amount of security by increasing the amount of running Masternodes. When originally envisioned, the target number of masternodes was 2000-3000. I\u2019ve waited some time to see if the amount of active Masternodes will increase alone, but I\u2019m beginning to think some tweaking is in order.<\/p>\r\n

The number of Masternodes reaches an equilibrium with the price of Dash and the ROI of running a node over a period of time. Currently we have about 900 total Masternodes (some haven\u2019t updated to RC5 yet, but you can see the stats\u00a0here<\/a>), with this amount of nodes each has a ROI of 23%<\/p>\r\n

It can be calculated with: ((a\/b)*c*d*e)\/1000)
\r\na is the amount of Masternodes you control
\r\nb is the total amount of Masternodes
\r\nc is the amount of blocks per day
\r\nd is the days in a year
\r\ne is payment per block won<\/p>\r\n

So with that in mind the current profitability can be calculated by<\/p>\r\n

((1\/900.0)*576*365*(5*.20))\/1000 = 0.23 (23% per year ROI in DASH)<\/i><\/p>\r\n

The reward of 23% can be thought of as the current equilibrium that the network has found. So it is expected that no matter the reward structure, the network will come to rest as this level.<\/p>\r\n

If our goal is to gain more Masternodes to improve the overall security of the network, I propose increasing the reward structure for Masternodes by 5% every month until the optimal amount of Masternodes is reached. This can be thought of as a type of\u00a0price discovery<\/a>. It’s also worth noting, by adding 5% rewards per month we’ll have a decreasing amount of impact each month thereafter. From 20% to 25% is a 25% change, from 25% to 30% is a 20% change, then 16.6%, 14.2%, 12.5%, etc. This will allow a good deal of reaction time.<\/p>\r\n

This also means that Dash must be purchased in order to start new Masternodes. This doesn\u2019t include Masternodes selling their existing node\u2019s Dash in order to cash out (that wouldn\u2019t change the Masternode total count). Considering this, we should see very long term steady growth, gain a lot of media attention and gain real-world adoption.<\/p>\r\n

I believe this update will be great for Dash by increasing the security of InstantX and Darksend, while providing significant growth for Dash. An update like this requires a very solid version of enforcement along with updates to the daemon to tell the pool operators how much Dash is suppose to be paid to the current Masternode operator.<\/p>\r\n

FAQ:<\/p>\r\n

Can’t we just decrease the amount required to run a Masternode:\u00a0https:\/\/dashtalk.org\/threads\/development-update-oct-1-2014.2561\/page-4#post-23297<\/a><\/p>\r\n

PS. Thanks to BabyGiraffe for inspiring this conversation about Masternode Payments.<\/p>\r\n","protected":false},"author":1,"featured_media":0,"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":[216],"tags":[],"acf":[],"yoast_head":"\nDevelopment Update - October 1, 2014 - Dash<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Development Update - October 1, 2014 - Dash\" \/>\n<meta property=\"og:description\" content=\"Darksend seems to be very stable and now that we\u2019re open source and we\u2019ve passed an audit I think it\u2019s time to work on some other functionality. We\u2019re working out of development plan for the next weeks weeks and here\u2019s what we have so far. Masternode Security There are a few things that are missing in Dash to properly implement\u00a0InstantX). One of the greatest objections to InstantX from the Bitcoin community was the possibility to DOS the selected masternodes that are responsible for consensus voting. This would stop the consensus voting forcing the network to evaluate transactions using the mining network, bring the first confirmation from 10-20 seconds back to 2.5 minutes. While not a terrible issue, it\u2019s something we can deal with by hiding the masternode identities and using a token based routing system to pass messages back and forth. This will be discussed in great detail in the v2 of the Dash whitepaper. To build a network that can withstand attacks, the masternodes must not publish their IPs. To do this we\u2019re going to utilize a new multipath communication technology. This will add another layer of privacy to the system as it will allow users to communicate with the network securely without exposing their IPs and will also hide the identity of the Darksend mixing nodes making it extremely difficult, if not impossible, for third parties to spy on users information. It uses multi-path routing so users can send more than one encrypted message using different routes on the mesh network for redundancy. This will allow us quick communication, robustness and anonymous two way communication. The diagram below shows the new system in action: Enforcement Currently there is a very basic version of enforcement that is going to be enabled soon. The strategy employed by Dash currently to protect masternode payments is definitely not a perfect solution and wasn\u2019t meant to stay in this form forever. While it does make cheating much more difficult, it\u2019s still remains possible. The next version of enforcement will be a huge improvement over this current version and will introduce much greater security. Masternode Reward Structure The Dash network relies heavily on the strength of the Masternode network. They are the foundation of our currency in provide great value to the network. Whether it be serving the blocks to a client that is syncing or proving the services such as Darksend and InstantX. While writing the whitepaper for InstantX and v2 of Dash, I\u2019ve realized that the network would gain an incredible amount of security by increasing the amount of running Masternodes. When originally envisioned, the target number of masternodes was 2000-3000. I\u2019ve waited some time to see if the amount of active Masternodes will increase alone, but I\u2019m beginning to think some tweaking is in order. The number of Masternodes reaches an equilibrium with the price of Dash and the ROI of running a node over a period of time. Currently we have about 900 total Masternodes (some haven\u2019t updated to RC5 yet, but you can see the stats\u00a0here), with this amount of nodes each has a ROI of 23% It can be calculated with: ((a\/b)*c*d*e)\/1000) a is the amount of Masternodes you control b is the total amount of Masternodes c is the amount of blocks per day d is the days in a year e is payment per block won So with that in mind the current profitability can be calculated by ((1\/900.0)*576*365*(5*.20))\/1000 = 0.23 (23% per year ROI in DASH) The reward of 23% can be thought of as the current equilibrium that the network has found. So it is expected that no matter the reward structure, the network will come to rest as this level. If our goal is to gain more Masternodes to improve the overall security of the network, I propose increasing the reward structure for Masternodes by 5% every month until the optimal amount of Masternodes is reached. This can be thought of as a type of\u00a0price discovery. It’s also worth noting, by adding 5% rewards per month we’ll have a decreasing amount of impact each month thereafter. From 20% to 25% is a 25% change, from 25% to 30% is a 20% change, then 16.6%, 14.2%, 12.5%, etc. This will allow a good deal of reaction time. This also means that Dash must be purchased in order to start new Masternodes. This doesn\u2019t include Masternodes selling their existing node\u2019s Dash in order to cash out (that wouldn\u2019t change the Masternode total count). Considering this, we should see very long term steady growth, gain a lot of media attention and gain real-world adoption. I believe this update will be great for Dash by increasing the security of InstantX and Darksend, while providing significant growth for Dash. An update like this requires a very solid version of enforcement along with updates to the daemon to tell the pool operators how much Dash is suppose to be paid to the current Masternode operator. FAQ: Can’t we just decrease the amount required to run a Masternode:\u00a0https:\/\/dashtalk.org\/threads\/development-update-oct-1-2014.2561\/page-4#post-23297 PS. Thanks to BabyGiraffe for inspiring this conversation about Masternode Payments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\" \/>\n<meta property=\"og:site_name\" content=\"Dash\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/DashPay\" \/>\n<meta property=\"article:published_time\" content=\"2014-10-01T14:06:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-09-18T11:40:19+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/media.dash.org\/wp-content\/uploads\/dash_facebook.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"dash\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@dashpay\" \/>\n<meta name=\"twitter:site\" content=\"@dashpay\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"dash\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\"},\"author\":{\"name\":\"dash\",\"@id\":\"https:\/\/www.dash.org\/#\/schema\/person\/49e370ea57b37d1186318dab9e4e6513\"},\"headline\":\"Development Update – October 1, 2014\",\"datePublished\":\"2014-10-01T14:06:09+00:00\",\"dateModified\":\"2021-09-18T11:40:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\"},\"wordCount\":868,\"publisher\":{\"@id\":\"https:\/\/www.dash.org\/#organization\"},\"articleSection\":[\"News\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\",\"url\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\",\"name\":\"Development Update - October 1, 2014 - Dash\",\"isPartOf\":{\"@id\":\"https:\/\/www.dash.org\/#website\"},\"datePublished\":\"2014-10-01T14:06:09+00:00\",\"dateModified\":\"2021-09-18T11:40:19+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.dash.org\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Development Update – October 1, 2014\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dash.org\/#website\",\"url\":\"https:\/\/www.dash.org\/\",\"name\":\"Dash\",\"description\":\"Dash is Digital Cash You Can Spend Anywhere\",\"publisher\":{\"@id\":\"https:\/\/www.dash.org\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dash.org\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.dash.org\/#organization\",\"name\":\"Dash\",\"url\":\"https:\/\/www.dash.org\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dash.org\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/media.dash.org\/wp-content\/uploads\/dash-d.png\",\"contentUrl\":\"https:\/\/media.dash.org\/wp-content\/uploads\/dash-d.png\",\"width\":500,\"height\":500,\"caption\":\"Dash\"},\"image\":{\"@id\":\"https:\/\/www.dash.org\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/DashPay\",\"https:\/\/twitter.com\/dashpay\",\"https:\/\/www.instagram.com\/dashpay\",\"https:\/\/www.linkedin.com\/company\/10424093\",\"https:\/\/www.pinterest.com\/dashdigitalcash\",\"https:\/\/www.youtube.com\/c\/DashOrg\",\"https:\/\/en.wikipedia.org\/wiki\/Dash_cryptocurrency\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dash.org\/#\/schema\/person\/49e370ea57b37d1186318dab9e4e6513\",\"name\":\"dash\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dash.org\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/8aabe262ffeff934a0baa0b4a798992f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/8aabe262ffeff934a0baa0b4a798992f?s=96&d=mm&r=g\",\"caption\":\"dash\"},\"url\":\"https:\/\/www.dash.org\/author\/dash\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Development Update - October 1, 2014 - Dash","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/","og_locale":"en_US","og_type":"article","og_title":"Development Update - October 1, 2014 - Dash","og_description":"Darksend seems to be very stable and now that we\u2019re open source and we\u2019ve passed an audit I think it\u2019s time to work on some other functionality. We\u2019re working out of development plan for the next weeks weeks and here\u2019s what we have so far. Masternode Security There are a few things that are missing in Dash to properly implement\u00a0InstantX). One of the greatest objections to InstantX from the Bitcoin community was the possibility to DOS the selected masternodes that are responsible for consensus voting. This would stop the consensus voting forcing the network to evaluate transactions using the mining network, bring the first confirmation from 10-20 seconds back to 2.5 minutes. While not a terrible issue, it\u2019s something we can deal with by hiding the masternode identities and using a token based routing system to pass messages back and forth. This will be discussed in great detail in the v2 of the Dash whitepaper. To build a network that can withstand attacks, the masternodes must not publish their IPs. To do this we\u2019re going to utilize a new multipath communication technology. This will add another layer of privacy to the system as it will allow users to communicate with the network securely without exposing their IPs and will also hide the identity of the Darksend mixing nodes making it extremely difficult, if not impossible, for third parties to spy on users information. It uses multi-path routing so users can send more than one encrypted message using different routes on the mesh network for redundancy. This will allow us quick communication, robustness and anonymous two way communication. The diagram below shows the new system in action: Enforcement Currently there is a very basic version of enforcement that is going to be enabled soon. The strategy employed by Dash currently to protect masternode payments is definitely not a perfect solution and wasn\u2019t meant to stay in this form forever. While it does make cheating much more difficult, it\u2019s still remains possible. The next version of enforcement will be a huge improvement over this current version and will introduce much greater security. Masternode Reward Structure The Dash network relies heavily on the strength of the Masternode network. They are the foundation of our currency in provide great value to the network. Whether it be serving the blocks to a client that is syncing or proving the services such as Darksend and InstantX. While writing the whitepaper for InstantX and v2 of Dash, I\u2019ve realized that the network would gain an incredible amount of security by increasing the amount of running Masternodes. When originally envisioned, the target number of masternodes was 2000-3000. I\u2019ve waited some time to see if the amount of active Masternodes will increase alone, but I\u2019m beginning to think some tweaking is in order. The number of Masternodes reaches an equilibrium with the price of Dash and the ROI of running a node over a period of time. Currently we have about 900 total Masternodes (some haven\u2019t updated to RC5 yet, but you can see the stats\u00a0here), with this amount of nodes each has a ROI of 23% It can be calculated with: ((a\/b)*c*d*e)\/1000) a is the amount of Masternodes you control b is the total amount of Masternodes c is the amount of blocks per day d is the days in a year e is payment per block won So with that in mind the current profitability can be calculated by ((1\/900.0)*576*365*(5*.20))\/1000 = 0.23 (23% per year ROI in DASH) The reward of 23% can be thought of as the current equilibrium that the network has found. So it is expected that no matter the reward structure, the network will come to rest as this level. If our goal is to gain more Masternodes to improve the overall security of the network, I propose increasing the reward structure for Masternodes by 5% every month until the optimal amount of Masternodes is reached. This can be thought of as a type of\u00a0price discovery. It’s also worth noting, by adding 5% rewards per month we’ll have a decreasing amount of impact each month thereafter. From 20% to 25% is a 25% change, from 25% to 30% is a 20% change, then 16.6%, 14.2%, 12.5%, etc. This will allow a good deal of reaction time. This also means that Dash must be purchased in order to start new Masternodes. This doesn\u2019t include Masternodes selling their existing node\u2019s Dash in order to cash out (that wouldn\u2019t change the Masternode total count). Considering this, we should see very long term steady growth, gain a lot of media attention and gain real-world adoption. I believe this update will be great for Dash by increasing the security of InstantX and Darksend, while providing significant growth for Dash. An update like this requires a very solid version of enforcement along with updates to the daemon to tell the pool operators how much Dash is suppose to be paid to the current Masternode operator. FAQ: Can’t we just decrease the amount required to run a Masternode:\u00a0https:\/\/dashtalk.org\/threads\/development-update-oct-1-2014.2561\/page-4#post-23297 PS. Thanks to BabyGiraffe for inspiring this conversation about Masternode Payments.","og_url":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/","og_site_name":"Dash","article_publisher":"https:\/\/www.facebook.com\/DashPay","article_published_time":"2014-10-01T14:06:09+00:00","article_modified_time":"2021-09-18T11:40:19+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/media.dash.org\/wp-content\/uploads\/dash_facebook.png","type":"image\/png"}],"author":"dash","twitter_card":"summary_large_image","twitter_creator":"@dashpay","twitter_site":"@dashpay","twitter_misc":{"Written by":"dash","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#article","isPartOf":{"@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/"},"author":{"name":"dash","@id":"https:\/\/www.dash.org\/#\/schema\/person\/49e370ea57b37d1186318dab9e4e6513"},"headline":"Development Update – October 1, 2014","datePublished":"2014-10-01T14:06:09+00:00","dateModified":"2021-09-18T11:40:19+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/"},"wordCount":868,"publisher":{"@id":"https:\/\/www.dash.org\/#organization"},"articleSection":["News"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/","url":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/","name":"Development Update - October 1, 2014 - Dash","isPartOf":{"@id":"https:\/\/www.dash.org\/#website"},"datePublished":"2014-10-01T14:06:09+00:00","dateModified":"2021-09-18T11:40:19+00:00","breadcrumb":{"@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dash.org\/news\/development-update-october-1-2014\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dash.org\/news\/development-update-october-1-2014\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.dash.org\/"},{"@type":"ListItem","position":2,"name":"Development Update – October 1, 2014"}]},{"@type":"WebSite","@id":"https:\/\/www.dash.org\/#website","url":"https:\/\/www.dash.org\/","name":"Dash","description":"Dash is Digital Cash You Can Spend Anywhere","publisher":{"@id":"https:\/\/www.dash.org\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dash.org\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.dash.org\/#organization","name":"Dash","url":"https:\/\/www.dash.org\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dash.org\/#\/schema\/logo\/image\/","url":"https:\/\/media.dash.org\/wp-content\/uploads\/dash-d.png","contentUrl":"https:\/\/media.dash.org\/wp-content\/uploads\/dash-d.png","width":500,"height":500,"caption":"Dash"},"image":{"@id":"https:\/\/www.dash.org\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/DashPay","https:\/\/twitter.com\/dashpay","https:\/\/www.instagram.com\/dashpay","https:\/\/www.linkedin.com\/company\/10424093","https:\/\/www.pinterest.com\/dashdigitalcash","https:\/\/www.youtube.com\/c\/DashOrg","https:\/\/en.wikipedia.org\/wiki\/Dash_cryptocurrency"]},{"@type":"Person","@id":"https:\/\/www.dash.org\/#\/schema\/person\/49e370ea57b37d1186318dab9e4e6513","name":"dash","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dash.org\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/8aabe262ffeff934a0baa0b4a798992f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/8aabe262ffeff934a0baa0b4a798992f?s=96&d=mm&r=g","caption":"dash"},"url":"https:\/\/www.dash.org\/author\/dash\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/posts\/17174"}],"collection":[{"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/comments?post=17174"}],"version-history":[{"count":2,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/posts\/17174\/revisions"}],"predecessor-version":[{"id":25269,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/posts\/17174\/revisions\/25269"}],"wp:attachment":[{"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/media?parent=17174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/categories?post=17174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dash.org\/wp-json\/wp\/v2\/tags?post=17174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}