Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-933

There should always be fresh enough signature of a state

    XMLWordPrintable

Details

    • Story
    • Status: Complete
    • Medium
    • Resolution: Done
    • None
    • 1.6.83
    • None

    Description

      As of now, multi-sigs are created on every Request. But if there are no Requests in a pool, then the state and multi-signatures may become outdated.
      So, a Primary needs to initiate re-signing of the same state periodically to have up-to-date state (for the latest pool ledger).
      It will help to solve two problems:

      • Have up-to-date multi-signature (with the latest timestamp)
      • Have multi-signature for the latest pool ledger (the client can use the latest pool ledger in most of the cases)

      All states (for all ledgers) need to be re-signed periodically.

       

      Acceptance criteria

      • Implement periodic BLS re-signing of all states (for all ledgers). It can be done via existing PrePrepare msg, or via a new message (decide when creating a PoA).
      • Re-sign period needs to be configurable (config file for now). Default is 1 min.
      • It should be possible to disable/enable the feature in config.
      • An INFO level log message is issued which states "Freshness was updated through consensus."

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. INDY-614 As a Indy user I want to know that when I get an answer back from the ledger, it is no more than 60 seconds old

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1911 Send INSTANCE_CHANGE if state doesn't get updated long enough

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1928 As a user of Valdiator Info script, I need to know whether the pool has write consensus and when the state was updated the last time

          • Medium - Has the potential to affect progress.
          • Complete
          relates to

          Bug - A problem which impairs or prevents the functions of the product. INDY-968 The pool state should be updated after any node BLS key changing

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1137 Support GET_REVOC_REG request

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1954 As a user, I need to be able to know what was the last update time of the ledger when querying a txn via GET_TXN request

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-1281 As a Network Maintainer, I need to be able to check whether write works for every txn type without writing garbage to the ledger

          • Medium - Has the potential to affect progress.
          • Complete

          Activity

            People

              VladimirWork Vladimir Shishkin
              ashcherbakov Alexander Shcherbakov
              Alexander Shcherbakov, Lovesh Harchandani, Renata Toktar, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: