From 1d0a341e61afd80ff757d6c3be6744de2ae9a88c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Fri, 10 Aug 2018 14:08:02 +0200 Subject: [PATCH] Update bsip-0040.md --- bsip-0040.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bsip-0040.md b/bsip-0040.md index 69fb79a..096a005 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -46,8 +46,6 @@ 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. -Note: The impact of Milestone 4 is explained in its own section to not hinder the reading flow - # Rational Custom active permission is a list of `custom active authorities`. A `custom active authority` contains an `operation_id`, @@ -62,6 +60,8 @@ account of the transaction if all its belonging operations have at least one pos All descriptions in this section are on a pseudo/prosa level and no recommendation how it can best be implemented or serialized. They are meant to facilitate the understanding. If anything in the looping process or order of evaluation is unsuitable for actual implementation, changes can be made accordingly as long the same functionality is achieved. +Note: The impact of Milestone 4 is explained in its own subsection to not hinder the reading flow + ### Custom active permission and custom active authority A `custom active permission` contains a list of `custom active authorities` and looks like follows (in JSON-like/pseudo for clarification):