No announcement yet.

DAPS Technology Update

  • Filter
  • Time
  • Show
Clear All
new posts

  • DAPS Technology Update

    DAPS Technology Update

    Since the news release of DAPS having Bulletproofs, we had lots of conversations over the last few months – of blending the best of Monero and PIVX.

    What this meant in the early days was that we used some of their libraries and concepts.

    What does this mean today, has anything changed?
    The short answer to this is yes.

    What has changed?

    Just before we went into the code audit, we removed the last remnants of anything Monero related in our repositories.

    This means that not only do we have no dependencies on anything Monero related, but it also means that the RingCT, Ring Signature and Bulletproof implementation we have is 100% ours.

    Is this a good thing?

    Of course, it is. It means a few things:

    1. We have our own unique implementation.
    2. We absolutely have to have it audited anyway because it may have issues that have not been seen before. Hence making the audit even more important.
    3. There have been some comments made online by folk who have said “Monero already paid to have that code audited, perhaps DAPS should pay Monero”, guess what, NOPE! 😝
    4. We do not need to accredit Monero in our repo at mainnet because we do not rely on them at all.

    There will undoubtedly be a few questions that come up at this point.

    For example:

    1. Why do this? Why not just use Monero code?
    2. So if Monero has a vulnerability in their code, does this mean we won’t have it?
    3. But Monero is good at what they do, what makes you think our developers did a good job?

    So let’s answer these questions:

    1. It’s both a simple and complex answer at the same time. The simple reason is that it’s easier to maintain a single code base with relations to a single other repo (in this case PIVX) than to have to manage changes and improvements in 2 separate repos and then to have to attempt to integrate them and all the issues that can come of it. DAPS and Monero use different elliptic curves so we had to go custom.
    2. Correct!
    3. Because we have already tested it in 2 separate beta tests and it worked exactly as expected each time! That, plus the auditors will let us know if there are any issues with it.

    So to wrap it up DAPS code no longer has any dependencies or references to Monero.

    Our developers are amazing! 🙌
    Last edited by DAPS User; 3 September 2019, 11:04 AM.