From e749319cace5ed0d43f8ce4abfcb2c8003a13527 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Fri, 10 Aug 2018 22:42:02 +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 096a005..ddabb8d 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -222,7 +222,7 @@ Adding a custom active authority means increased effort for the backend, and wit - 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 (i.e. `date_to - max(now, date_from)`) -- `update_custom_active_authority`: Base fee similar to `account_update` plus dynamic one for any duration changes, no payback if duration in decreased. +- `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` This logic forces the user to think about the desired duration and enforces to put it rather too short than too long.