In a recent tweet, Dash announced another development update that the team has been working on.
The announcement read:
“Introducing Long Living Masternode Quorums! Just another step in the
$Dash Evolution Revolution!”
The Alexander Block, Core Developer at Dash elaborated in detail about ‘Long Living Masternode Quorums’ or LLMQs on Dash’s official blog.
The developer stated that the project is currently under development. The community will see some impacts in the future on some Evolution and non-Evolution topics and features.
Alexander said, the current Quorum [collection of entities that are able to vote on something] system utilized by the team poses difficulties and limitations and cannot be used in particular use cases. In order to eliminate the drawback of the present system, the team devised LLMQs as a solution. The LLMQs are long living and it increases the use of only certain required resources like CPU, RAM, network on its members and avoids increasing the load on the entire network.
Furthermore, he said that the Quorum is built beforehand and reused for a certain period of time instead of selecting a new Quorum when the demand arrives. He stated:
“The reason for this is that an LLMQ performs M-of-N threshold signing sessions to gain majority consensus when decisions need to be made. The new M-of-N scheme requires executing a trustless and distributed key generation (DKG) protocol before actual signing/voting can happen. Since this DKG protocol is quite resource-intensive, we do it in advance and then reuse the keys for multiple signing sessions.”
In contrast to the existing system, the LLMQs only require the members of Quorums to perform propagations and validation of votes and the final result is propagated to the remaining portions of the network only after a certain amount of votes are collected. He added:
“Since the final result is the outcome of a BLS based M-of-N threshold signing session, it’s just a single BLS signature. Propagating only this single signature in the network requires a lot less CPU, RAM, and network bandwidth resources.”
The LLMQs will occur in different sizes and longevity which will be supported fully, he explained. The type will be selected depending on the use case. The best example of the use case of LLMQs is Dash’s InstaSend.
Subscribe to AMBCrypto’s Newsletter
Ripple official claims that in time banks will adopt cryptocurrencies but before that it will be small companies
Ripple to lay xCurrent base in India? Industry player talks about partnership
Litecoin [LTC/USD] Technical Analysis: Bear’s hunger for bulls reflected in price trend
Winklevoss Twins launch new app; say they are “at home” with the crypto-winter
Ethereum’s [ETH] Vitalik Buterin talks about non-financial applications of blockchain in a tweetstorm
BREAKING: Ripple class-action lawsuit rolls ahead; plaintiffs place new demand
XRP to $589 proponent and rumored Ripple insider Bearableguy123 resurfaces: Can 1635x growth occur in 28 days?
Bitcoin [BTC] futures on Nasdaq confirmed by company executive; to be launched in first half of 2019
Ripple CEO responds to NYSE Chairman’s comment on digital assets
XRP twitter army blocked by Dogecoin [DOGE] creator after facing backlash to his comment on Ripple
XRP ecosystem blooms as the year ends; Ripple, r3 leave animosity behind and more
Bitcoin Cash [BCH] ABC to be delisted from all exchanges, says Bitcoin SV [BSV]’s Calvin Ayre
Cardano [ADA] creates record by becoming 4th biggest loser in terms of trading price against all-time high
Tron [TRX]’s weekly report: New multi-signature wallet underway, Accelerator program gains momentum