mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 04:22:55 +01:00
f0009acfae
## Issue being fixed or feature implemented Platform and research team have requested this change. ## What was done? `quorum info` was updated with the introduction of new field `previousConsecutiveDKGFailures` that be returned only for rotated LLMQs. This field will hold the number of previously consecutive failed DGKs for the corresponding quorumIndex before the currently active one. Note: If no previously commitments were found then 0 will be returned for `previousConsecutiveDKGFailures`. Example: - DKG `A` was successful - DKG `B` failed - DKG `C` failed - DKG `D` was successful - DKG `E` was successful - `previousConsecutiveDKGFailures` = 0 when requesting for quorum `A` (because `A` is the first ever created quorum for that quorumIndex) - `previousConsecutiveDKGFailures` = 2 when requesting for quorum `D` - `previousConsecutiveDKGFailures` = 0 when requesting for quorum `E` ## How Has This Been Tested? ## Breaking Changes ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [x] I have made corresponding changes to the documentation **For repository code-owners and collaborators only** - [x] I have assigned this pull request to a milestone Co-authored-by: thephez <thephez@users.noreply.github.com>
5 lines
365 B
Markdown
5 lines
365 B
Markdown
Updated RPCs
|
|
--------
|
|
|
|
- `quorum info`: The new `previousConsecutiveDKGFailures` field will be returned for rotated LLMQs. This field will hold the number of previous consecutive DKG failures for the corresponding quorumIndex before the currently active one. Note: If no previous commitments were found then 0 will be returned for `previousConsecutiveDKGFailures`.
|