Skip to content

Create msig_erc20_fee_permission.md #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Create msig_erc20_fee_permission.md #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions msig_contract_deployment/msig_erc20_fee_permission.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
<h1>Multisig to set up the "fee" permission for account eosio.erc2o</h1>

**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