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

Search results

  1. K

    Distributed platform storage (avoids High Performance nodes)

    ZK rollups are specific to transactions. As I understand it, it is a Layer 2 solution that batches transactions in a Merkle tree and stores the batch with the root hash in a Layer 1 smart contract. The smart contract verifies the snark proof submitted with a batch before accepting and updating...
  2. K

    Should Platform run on all nodes or should Platform run only on High Performance nodes ?

    I don't know. Maybe the spam filter, because at the same time I was also banned from posting. The administrator promptly restored my privilege to post when I contacted him, but could not restore the thread. It is somewhat surprising that a spam filter can retroactively delete a thread.
  3. K

    Distributed platform storage (avoids High Performance nodes)

    As mentioned in GroveDB documentation, the details are explained in this paper Database Outsourcing with Hierarchical Authenticated Data Structures
  4. K

    Should Platform run on all nodes or should Platform run only on High Performance nodes ?

    The forum thread about Proof-of-Useful Work, which retains the key benefits of PoW while consuming energy in a more sustainable way, was somehow deleted. The administrator of the forum was unable to restore the post when I asked him to. At that time, I took a snapshot of the thread, which you...
  5. K

    Distributed platform storage (avoids High Performance nodes)

    Thank you very much for the answer, I appreciate it. I still think the solution is doable, but before I ask any more questions, I should really look at the code now. I do not want to take up any more of your time so don't feel obligated to reply. What I will look at in the code is how the...
  6. K

    Distributed platform storage (avoids High Performance nodes)

    This is true, but should be solved by: (a) caching (b) high frequency applications can directly contact MNs in their subset (avoiding the additional hop)
  7. K

    Distributed platform storage (avoids High Performance nodes)

    Let me try to give some additional explanation of the proposed solution to make it more understandable and add some additional thoughts on the subject. The goal is to split the platform data between the masternodes, so that each masternode does not need to store the whole platform state, but...
  8. K

    Distributed platform storage (avoids High Performance nodes)

    Thank you for taking the time to respond. You make a heroic effort to respond to all the posts that are thrown at you. My hat is off to you. I also apologize for being so late in replying, but I have had to meet my work commitments which have taken up all my time lately. After reading your...
  9. K

    Distributed platform storage (avoids High Performance nodes)

    There is an ongoing discussion about the introduction of a High Performance masternode (HPMN) type with strengthened hardware resources with the goal of reducing data platform fees. Three options are proposed by Dash Core Group in the Introductory presentation on High Performance Masternodes...
Back
Top