• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Development Update, Whitepaper and Other News

eduffield

Core Developer
Hello Everyone,

We just wanted to give everyone an update on the project and what we are focusing on right now. Currently the team is working on many different projects for development, marketing and outreach. We’ve made some great progress with marketing & outreach, we’ll have more about that in the coming weeks/months. We know it’s been quiet for a couple weeks and there’s good reason for that.

Development Update - v0.12.0.0

  • Udjin has merged all upstream changes from Bitcoin 10 into the project. This means we’ll support much faster syncing via headers-first blocks and various other changes to the core software.
  • I’ve been working on re-implementing the Masternode Broadcast/Pinging classes to be much easier to read and more efficient. This will allow us to finally use inventory messages for updates to the Masternode network, reducing bandwidth by as much as 80%!
  • The code is getting very close to the point where we will no longer require the reference node. The reference node was created in order to solve a problem dash has had since the beginning, unfair masternode payments. With the reference node, the network has round robin masternode payments, but this node is centralized and our goal is to decentralize all components of the network. In the v0.12.0.0 version, we’re going to run the network in a hybrid state where the reference node can be turned off and the network will enforce masternode payments in a round-robin fashion just like it does now, except with no centralization. This hybrid state will allow us to still use the reference node as a backup if needed.
  • Udjin has been working on improved language support for the the Darksend process, which means users mixing coins in other languages will no longer see english errors messages.

Mobile Wallets Capable of DS and IX

  • We’re happy to announce that we have developers working on Darksend/InstantX implementations for mobile. This is very exciting because it will allow person-2-person instant transfer of value just like cash in a completely decentralized way, involving no third party. This is important because it brings us very close to our goal of providing a real medium of digital cash.
  • We also want to take the opportunity to welcome our new developer QuantumExplorer who is handling the development of our iPhone wallet.

Decentralized Cryptocurrency Management Proposal
  • We’ve been working on a plan for months now to fully decentralize the projects funding and management going forward. This is a brand new concept in crypto and goes beyond the foundation model. We’re very excited, as we believe it solves some long standing issues that Bitcoin and other crypto-currencies have faced. We’ll be releasing a detailed whitepaper about this concept on Wednesday this week.

Dash Whitepaper V1
  • The old whitepaper was very out of date, we’ve updated it and detailed all technology that we’re using within Dash. Click here to read the new whitepaper!
 
Page 5 of the white paper still shows DRK in the last column where it says "Dash Required"

Thanks for all your hard work

edit: also page 12 & 13
 
phwarr awesome read- amazing as usual Evan, keep up the great work.....one step closer and closer!
 
Thanks Evan for the update. Sounds like the development is on a very good way. it's also nice to see updated white paper.
 
Hello Everyone,

We just wanted to give everyone an update on the project and what we are focusing on right now. Currently the team is working on many different projects for development, marketing and outreach. We’ve made some great progress with marketing & outreach, we’ll have more about that in the coming weeks/months. We know it’s been quiet for a couple weeks and there’s good reason for that.

Development Update - v0.12.0.0

  • Udjin has merged all upstream changes from Bitcoin 10 into the project. This means we’ll support much faster syncing via headers-first blocks and various other changes to the core software.
  • I’ve been working on re-implementing the Masternode Broadcast/Pinging classes to be much easier to read and more efficient. This will allow us to finally use inventory messages for updates to the Masternode network, reducing bandwidth by as much as 80%!
  • The code is getting very close to the point where we will no longer require the reference node. The reference node was created in order to solve a problem dash has had since the beginning, unfair masternode payments. With the reference node, the network has round robin masternode payments, but this node is centralized and our goal is to decentralize all components of the network. In the v0.12.0.0 version, we’re going to run the network in a hybrid state where the reference node can be turned off and the network will enforce masternode payments in a round-robin fashion just like it does now, except with no centralization. This hybrid state will allow us to still use the reference node as a backup if needed.
  • Udjin has been working on improved language support for the the Darksend process, which means users mixing coins in other languages will no longer see english errors messages.

Mobile Wallets Capable of DS and IX

  • We’re happy to announce that we have developers working on Darksend/InstantX implementations for mobile. This is very exciting because it will allow person-2-person instant transfer of value just like cash in a completely decentralized way, involving no third party. This is important because it brings us very close to our goal of providing a real medium of digital cash.
  • We also want to take the opportunity to welcome our new developer QuantumExplorer who is handling the development of our iPhone wallet.

Decentralized Cryptocurrency Management Proposal
  • We’ve been working on a plan for months now to fully decentralize the projects funding and management going forward. This is a brand new concept in crypto and goes beyond the foundation model. We’re very excited, as we believe it solves some long standing issues that Bitcoin and other crypto-currencies have faced. We’ll be releasing a detailed whitepaper about this concept on Wednesday this week.

Dash Whitepaper V1
  • The old whitepaper was very out of date, we’ve updated it and detailed all technology that we’re using within Dash. Click here to read the new whitepaper!
Hi eduffield,
Can you draw some points about the future solution for the unfair masternode rewarding? I think the hashrate of Dash is actually very poor and does not have any sense as securing the network. Does have the coin any chance of overpass the POW concept in near future?
Thanks
 
Feedback for the Dash v1 white paper:
1) The first graph should state Bitcoin clearly (eg: "Figure 1: Bitcoin Full nodes in the spring of 2014")
2) There is a random word, "coin" just before section 2.1.
3) Should change "doesn’t" to "does not". (no contractions)
4) Should elaborate "AAPL". For example, "if AAPL is" should change to "if Apple Stock (AAPL) is".
5) "Upon starting a Masternode" should have a comma. "Upon starting, a Masternode".
6) "To pay the Masternodes this interface" should have a comma. "To pay the Masternodes, this interface".
7) "it’s" should just be "it is". (s/it's/it is/g')
8) Fix extra spacing in "approach , denominations". (to "approach, denominations")
9) Add Bitcoin to "Figure 2: An example Coinjoin transaction with 2 users [11][12]" (example:" Figure 2: An example Bitcoin Coinjoin transaction with 2 users [11][12]")
10) Add Bitcoin to "of Coinjoin, it’s possible". (to "of Bitcoin Coinjoin, it’s possible")
11) Add Bitcoin to "Figure 3: Forward Change Linking" (to "Figure 3: Example of Bitcoin Forward Change Linking")
12) Decimal amounts should always have leading zero. ('.7BTC' should be '0.7BTC') This should be changed in the graphic(s) as well.
13) "Figure 4: Through Change Linking" should have Bitcoin added (example: "Figure 4: Through Change Linking of Bitcoin")
14) Need to explain "DOS". This "3.3 Improved Privacy and DOS resistance" should be changed to "3.3 Improved Privacy and Denial of service (DOS) resistance"
15) There should be a ":" colon following this text, "as follows" should be "as follows:".
16) Should a table caption be a sentence? "Table 3. The probability of follow a Darksend transaction on the network given the attacker controls N Nodes." should be "Table 3. Probability of follow a Darksend transaction on the network given the attacker controls N Nodes".
17. Add date to "(5.3 million at the time of writing)". For example, "(5.3 million at the time of writing, April 2015)".
18. Change "can’t" to "cannot".
19. Should explain acronyms CPU and GPU. For example, "Central Processing Unit (CPU)" and "Graphics Processing Unit (GPU)".
20. Add page header/footers. (with page number and something like "Dash Whitepaper (v1)") Probably add link to official site for the whitepaper.
21. Add p2p after the first use of "peer-to-peer". (to "peer-to-peer (p2p)")
22. Add graph of the estimated number of Masternodes, showing growth over time.
23. Sometimes there is a space between the quantity of DASH and the word DASH. (example: "1000 DASH") It should be consistent throughout. Either "1000 DASH" or "1000DASH".
24. Change heading from "5.1 x11" to "5.1 x11 hashing algorithm".
25. Should have info regarding where code is located (https://github.com/dashpay/dash) and mention that it is completely open source.
26. Should there be mention of the Foundation?

Most of these are minor edits, but they detract the reader.
 
Last edited by a moderator:
And Evan has killed the arguments of trolls on BCT once again. I wonder what the trolls will rage about again.

Good job Evan and Dashteam. Can't wait for 0.12!
 
Back
Top