Update bsip-0040.md
This commit is contained in:
parent
6a00164534
commit
5dcf316a63
1 changed files with 2 additions and 2 deletions
|
@ -158,10 +158,10 @@ When a signed transaction arrives and before the backend evaluates if all necess
|
|||
- iterate over `required accounts`
|
||||
- iterate over all `operations` (child operations of proposal are not included) within the transactions that require the active authority of this account
|
||||
- iterate the `custom_active_authorities` of this account, and if it matches, remember that and continue with next `operation`
|
||||
- if a `custom active authority` match was found for every operation in the loop, behave as if the `active authority` of this account is present for the correspoding operations
|
||||
- if a `custom active authority` match was found for every operation in the loop, behave as if the `active authority` of this account is present for the corresponding operations
|
||||
|
||||
Note:
|
||||
- A `custom_active_authority` can only grant the `active authority` of the corresponding account for the matching operation, nothing more
|
||||
- A `custom_active_authority` can only grant the `active authority` of the required account of the corresponding operation, nothing more
|
||||
- The actual active authority of a required account can still be given as before, existing behavior is not to be changed
|
||||
- This for illustration, not actual implementation instructions
|
||||
|
||||
|
|
Loading…
Reference in a new issue