Update bsip-0040.md
This commit is contained in:
parent
51d46dae43
commit
b5602911ad
1 changed files with 1 additions and 1 deletions
|
@ -46,7 +46,7 @@ Note: The user can still use the active authority just like used to, no change i
|
||||||
|
|
||||||
This BSIP will be split into parts that will be voted on separately (see Milestones section). All of the above keys are possible with Milestone 1. Milestone 2 allows stateful restrictions (e.g. allow market orders up to some amount for every month), Milestone 3 gives finer control of how to combine restrictions and Milestone 4 allows to set a number of allowed executions per authority (introduces an additional on-chain dependency). Milestone 2, 3 and 4 will be put up for voting if Milestone 1 proves successful.
|
This BSIP will be split into parts that will be voted on separately (see Milestones section). All of the above keys are possible with Milestone 1. Milestone 2 allows stateful restrictions (e.g. allow market orders up to some amount for every month), Milestone 3 gives finer control of how to combine restrictions and Milestone 4 allows to set a number of allowed executions per authority (introduces an additional on-chain dependency). Milestone 2, 3 and 4 will be put up for voting if Milestone 1 proves successful.
|
||||||
|
|
||||||
# Rational
|
# Rationale
|
||||||
|
|
||||||
Custom active permission is a list of `custom active authorities`. A `custom active authority` contains an `operation_id`,
|
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 `restrictions` than can be used to restrict arguments.
|
an `authority` (just like with active permission) and `restrictions` than can be used to restrict arguments.
|
||||||
|
|
Loading…
Reference in a new issue