From 436cafe28e4c59e1d29ef7dfc3dc8e6158f30f9f Mon Sep 17 00:00:00 2001 From: Kayan <37097018+taokayan@users.noreply.github.com> Date: Fri, 24 Nov 2023 18:25:56 +0800 Subject: [PATCH] Create msig_erc20_fee_permission.md --- .../msig_erc20_fee_permission.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 msig_contract_deployment/msig_erc20_fee_permission.md diff --git a/msig_contract_deployment/msig_erc20_fee_permission.md b/msig_contract_deployment/msig_erc20_fee_permission.md new file mode 100644 index 0000000..cffb772 --- /dev/null +++ b/msig_contract_deployment/msig_erc20_fee_permission.md @@ -0,0 +1,16 @@ +

Multisig to set up the "fee" permission for account eosio.erc2o

+ +**Background** + +As the ERC20 token bridge will be supporting more tokens, we need an efficient way to control the bridging fee (ingress fee & egress fee) to ensure the fee can always able to cover the gas cost and the CPU cost introduced by the bridge transactions. + +In this multisig proposal, we propose a special "fee" permission (under "active" permissoin) allow ENF to act on the following actions in account eosio.erc2o: + - eosio.erc2o::setegressfee + - eosio.erc2o::setingressfee + - eosio.erc2o::withdrawfee + +**list of actions**: + - Action 1: create the new permission "fee" in account eosio.erc2o, whose parent permission is "active". This permission will be satisfied by enf@active + - Action 2: set "fee" as permission for eosio.erc2o::setegressfee + - Action 3: set "fee" as permission for eosio.erc2o::setingressfee + - Action 4: set "fee" as permission for eosio.erc2o::withdrawfee