agorise/bsips
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update bsip-0040.md

Browse source
This commit is contained in:
Stefan Schießl 2018-08-12 20:45:24 +02:00 committed by GitHub
parent e749319cac
commit 51d46dae43
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
bsip-0040.md
View file

@ -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: 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: - `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 - 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)`) (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) - `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` - `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. 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. 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 # Discussion