Update bsip-0040.md
This commit is contained in:
parent
5ebcbb6f99
commit
a82530729e
1 changed files with 1 additions and 1 deletions
|
@ -37,7 +37,7 @@ The above list of named keys is nothing that is known to the backend as the back
|
|||
# Rational
|
||||
|
||||
The description here is more on a superficial level and no recommendation how it can best be implemented.
|
||||
Custom active permission is a list of custom active authorities. A `custom active authorities` contains an `operation_id`, an `authority` (just like with active permission) and a list of `assert`s than can be used to restricted arguments. When a transaction is signed with such an authority the backend checks if the contained operation has a corresponding custom active authority entry and if so acts as if the active authority of the corresponding account is given. It also checks if the arguments are in the allowed range.
|
||||
Custom active permission is a list of custom active authorities. A `custom active authority` contains an `operation_id`, an `authority` (just like with active permission) and a list of `assert`s than can be used to restricted arguments. When a transaction is signed with such an authority the backend checks if the contained operation has a corresponding custom active authority entry and if so acts as if the active authority of the corresponding account is given. It also checks if the arguments are in the allowed range.
|
||||
|
||||
A Custom Active Permission looks like follows (in JSON for clarification, backend serializes and stores in a different way):
|
||||
```
|
||||
|
|
Loading…
Reference in a new issue