From 4349e8da45d71bbb0688dfeefc1d9b255e9ef5ec Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Sun, 29 Jul 2018 00:22:22 +0200 Subject: [PATCH] Update bsip-0040.md --- bsip-0040.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bsip-0040.md b/bsip-0040.md index 6c31e69..b87b5ce 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -179,7 +179,7 @@ Notes: The implementation must not differentiate on which operation the custom a We propose do split the implmentation into two milestones: 1. Implementation of basic functionaliy to allow custom active permissions and authorities, including `any`, `none`, `lt, le, gt, ge` and `length` `asserts`. If deemed necessary by developpers, reduce to only allow one key or one account for every `custom active authority` -2. Evaluation of stateful and more sophisticated asserts in terms of performance and if positive, implementation of `limit`, `limit_monthly` and `contains_only` `asserts` +2. Evaluation of stateful asserts `limit`, `limit_monthly` and more sophisticated assert `contains_only` in terms of performance. If positively evaluated, implement This approach allows as well to add other asserts at a later stage (with a new BSIP).