{"id":14153,"date":"2018-05-17T00:00:00","date_gmt":"2018-05-16T16:00:00","guid":{"rendered":"https:\/\/www2019.dash.org\/2018\/05\/17\/observations-of-the-dash-treasury-dao\/"},"modified":"2021-09-18T11:37:22","modified_gmt":"2021-09-18T11:37:22","slug":"observations","status":"publish","type":"post","link":"https:\/\/wp.dash.org\/news\/observations\/","title":{"rendered":"Observations of the Dash Treasury DAO"},"content":{"rendered":"
This post considers DASH\u2019s treasury model and history of proposal voting. Relevant data and R code are in\u00a0this github repository<\/a>.<\/p>\n This post is structured as follows:<\/p>\n DASH was I think the first cryptocurrency to award a portion of the block reward to a fund which is administered by a Decentralized Autonomous Organization (DAO) for the purpose of developing and promoting the project. There are other projects that have a built-in funding mechanism, I\u2019ve written about some of them\u00a0here as part of a larger piece on governance<\/a>.<\/p>\n Masternode Operators (MNOs) are key actors in the Dash network. Dash Masternodes (MNs) provide certain services (InstantSend<\/em>\u00a0and\u00a0PrivateSend<\/em>) to users, receive 45% of the block reward, and collectively control the project\u2019s development fund through voting. A MNO can operate multiple MNs.<\/p>\n Each month, DASH dispenses 10% of the block rewards for that \u2026.<\/p>\n\n
The Dash\u00a0Treasury<\/h4>\n