Versions Compared

Old Version 8

changes.mady.by.user Vadim Reutskiy

Saved on

compared with

New Version 9

changes.mady.by.user Vadim Reutskiy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use case title
[FR0108] Changing list of signatories for the  multimulti-signature account
Preconditions
  • The user has permissions to change the list of signatories to the required account
  • The user has generated key pair for adding it as /deleting a signatory to the /from the selected account

Use case flow

  1. The user prepares the instruction of adding/deleting signatories for sending
  2. The user sends the instruction to the Iroha peer (<<include>> FR0100)
  3. The user receives the response from the Iroha peer
Postconditions
  • List of signatories for the selected account was changed correspondingly
Alternative flowN/A
Exception flow
  • On step 2, if the signatory with the current key pair is exists in the list of signatories in the target account, the Iroha peer will return "already added" error status; use case flow stops.


Use case title
[FR0109] Signing multi-signature instruction
Preconditions
  • There is a multi-signature account in the Iroha network
  • The user has access to the one or many key pairs for the multi-signature account
  • The current amount of signatures to the multi-signature instruction is lower than a current quorum value

Use case flow

  1. The user obtains the current list of pending instructions (<<include>> FR0203)
  2. The user finds information required instruction that can be signed by his/her signatures
  3. The user signs required instruction using the available key pair by calling the corresponding method from CLI or client SDK
  4. The user sends signed instructions to the Iroha peer (<<include>> FR0100)
Postconditions
  • Amount of signatures in the signed instruction increased by 1 signature
  • Signed instruction disappears from the list of pending instructions for the current user's account
Alternative flow
  • On step 2 the user can select more than one instruction, all of them can be sent on step 4 as a separate requests
  • On step 3 the user can sign the instruction by more than one signature, and all of them can be sent as a single request per single instruction on step 4
Exception flow
  • On step 1, in case of the empty list of pending instructions, the Iroha peer will return corresponding status and the use case flow stops
  • Status
    colourYellow
    titleTBD
     On On step 3, if the user uses key pair, which was already used for signing the instruction, the CLI/SDK will return corresponding error status; use case flow stops if there are no more available key pairs. 
    Status
    colourYellow
    titleTBD
     (define, will it be available to do on the client-side?)


Use case title
[FR0110] Changing the conditions for the multi-signature account
Preconditions
  • The user has permissions to change the conditions for the target multi-signature account

Use case flow

  1. The user requests the list of currently configured conditions for the target multi-signature account
  2. The user prepared the instruction with the list of conditions to be added/removed
  3. The user sends the prepared instruction to the Iroha peer (<<include>> FR0100)
  4. The Iroha peer sends the response to the user
Postconditions
  • The list of conditions for the target multi-signature account was changed correspondingly
Alternative flow
Exception flow


Acquiring data from the Iroha network by queries

...

Use case title
[FR0203] Acquiring a list of pending multi-signature instructions
Preconditions
  • The user has permissions to request the list of pending instructions

Use case flow

  1. The user prepares query for requesting the list of pending instructions
  2. The user sends the query to the Iroha peer (<<include>> FR0200)
  3. The user receives the list of currently pending multi-signature instructions  
    Status
    colourYellow
    titleTBD
     (should the Iroha expose all pending instructions, or we need to add the account ID / public key to request?)
Postconditions
  • The user have the list of currently pending instructions
Alternative flowN/A
Exception flow
  • On step 3, if there are no currently pending instruction, the Iroha peer will return "empty response" status


Use case title
[FR0204] Acquiring a list of current conditions for a multi-signature account
Preconditions
  • The user has permissions to request a list of conditions to the target multi-signature account

Use case flow

  1. The user prepares query for requesting a list of currently configured conditions of signing for the target multi-signature account
  2. The user sends the query to the Iroha peer (<<include>> FR0200)
  3. The user receives the list of currently configured conditions of signing for the target multi-signature account
Postconditions
  • The user received the list of conditions for the target account
Alternative flowN/A
Exception flow
  • On step 3, if there are no currently configured conditions, the Iroha peer will return "empty response" status
  • On step 3, if the account is not multi-signature, the Iroha peer will return "not applicable" status

Non-functional requirements

...