From 51d46dae435fbf8bb2dbdf029cec186f0ac7d285 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Sun, 12 Aug 2018 20:45:24 +0200 Subject: [PATCH] Update bsip-0040.md --- bsip-0040.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/bsip-0040.md b/bsip-0040.md index ddabb8d..77a2c9f 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -220,7 +220,7 @@ If the `custom active authority` does not get replenished by the user within one Adding a custom active authority means increased effort for the backend, and with a stateful one also the need for more storage. Proposed transaction fees: - `install_custom_active_authority`: Normal accounts can only create custom active authoritites with a duration of maximum 1 year, LTM can do any duration. Two options come to mind: - A fixed high fee independent of authorities content - - Tied to the duration and complexity of the custom active authority. Transaction fee is then `fee = flat_fee + basic_fee * duration` where `basic_fee` is calculated according to complexity (e.g. size of authority, number of restrictions and etc.). Fee is capped at 1 year for LTM, `duration` refers to the time that is still left, not the actual duration + - Tied to the duration and complexity of the custom active authority. Transaction fee is then `fee = flat_fee + basic_fee * duration` where `basic_fee` is calculated according to complexity (e.g. size of authority, number of restrictions and etc.). The period `duration` refers to the time that is still left, not the set duration (i.e. `date_to - max(now, date_from)`) - `update_custom_active_authority`: Base fee similar to `account_update` plus dynamic one for any duration increase, no payback if duration in decreased (increase/decrease is evaluated on both interval ends separately) - `delete_custom_active_authority`: Cheap similar to `limit_order_cancel` @@ -229,7 +229,8 @@ This logic forces the user to think about the desired duration and enforces to p If a custom active is expired, or considered to be too short, extending it is easily doable. After expired, the custom active becomes disabled and can still be enabled again with a new period, paying the fee for that new period. -Note: For Milestone 4 the install fee would be dependent on the number of executions if no time period is set. +Note: +- For Milestone 4 the install fee would be dependent on the number of executions if no time period is set. # Discussion