给 EOSLaoMao 投票，请认准我们的主网节点ID：eoslaomaocom
Following the BankofStaked project, which brings convenience to the community, the EOSLaoMao team now adds a tool to the community in terms of account security – the EOS Security Guardian. Let’s introduce EOS Security Guardian to you.
We observed that in the community, users have a variety of questions and appeals when transferring token:
"How can other permissions be used in addition to the delegating vote?"
“Can't a token transfer have a more personalized design?”
“When I am sensible, I just want to charge myself up to 100 grapefruit games every day!”
“Community account funds are frequently stolen. Is there no way to limit the amount of funds transferred?”
“Can I set the daily transfer limit amount when I transfer the money? Can I set different transfer amounts for different accounts, for example, I want to transfer only a large amount of funds to my mom’s account?”
"How can I remind me not to continue to transfer money to an account that has been blacked out by the community?"
and many more.
These are the common concerns and ideas that everyone has when transferring token. If you want to know more about the transfer rights (functions) on EOS, you can refer to the following three articles from EOS blockgenic:
EOS Permission Management,
EOS Accounts and Permissions Visualized,
EOS Accounts: How They Work and How To Get One
Now EOS users generally use active permissions for daily transfers. In case the user's active key is stolen or leaked, the token in the account can theoretically be transferred away. The EOS Security Guardian can achieve the goal of reducing the risk of user assets by making reasonable settings on the account permissions. In terms of deployment, after the user deployed the EOS Security Guardian:
Safetransfer and safedelegate can be used with safeperm without the use of risky active and owner permissions to reduce the frequency of use of high privilege such as active and owner;
Safetransfer can set a single transfer limit and a maximum transfer limit within a certain time range.
We encourage users who have deployed EOS Security Guardian to use the low-permission (safeperm) key for daily secure transfer operations. Even if the key is compromised or stolen, the hacker will not be able to transfer more than the user-set transfer within a certain period of time. The upper limit of EOS, thus achieving the purpose of reducing the risk of funds.
The EOS Security Guardian currently consists of two main functions - a safe delegate function (safedelegate) and a safe transfer function (safetransfer).
Among them, the security delegate function can reduce the risk of the user being transferred in the delegate process to zero.
The secure transfer function allows users to customize the following three types of usage scenarios.
The first category is the transfer cap function. The user can set the upper limit of the single transfer (cap_tx) and the total transfer limit (cap_total) within a certain time range (duration).
For example, if there are 1000 EOS in my account, I want to limit the account to a maximum of 500 EOS per week. I only need to set the EOS Security Guardian's transfer limit to 7 days, and the transfer limit does not exceed 500 EOS to achieve the above limit.
In addition, I can also set a single maximum amount. For example, if I set it to 10 EOS, then every time I use the safe transfer function, I will automatically check if the transfer is beyond 10 EOS. Once exceeded, the transfer will be automatically suspended.
Therefore, with the transfer limit function, users can flexibly limit the total amount of funds transferred per unit time, thus strengthening the financial security of the account.
The second category is the whitelist feature. The setting parameters for this function are similar to the transfer restrictions above, the only difference being that these settings only apply to specific accounts. This feature provides the flexibility to meet the need to send large amounts of money to a dedicated account. For example, in the setting of global transfer limit, I can only transfer 500 EOS in a week, but today I need to transfer 600 EOS to long-term cooperative business partners. I only need to add the partner's collection account to the whitelist, and set a total limit of more than 600 EOS for this account, you can transfer 600 EOS to this account, and it will not affect the setting of other accounts. The transfer limit for 500 EOS.
The third category is the blacklist function. Some accounts are best not to trade with them, such as accounts that are added to the blacklist by ECAF, or other accounts that users find suspicious. To avoid making transfers to these accounts, users can add such accounts to the blacklist. If the user accidentally initiates a transfer to the blacklist account via the secure transfer function, the EOS Security Guardian automatically suspends the transfer operation before calling the transfer interface of the system contract.
The above is the main function of EOS Security Guardian. Whether it is transfer restriction function, whitelist function or blacklist function, users can update the settings at any time (requires active permission for update settings). This flexible operation can make more users different. Better protect your assets in the case.
See the GitHub content for details.
If you have any questions, please join the EOS Security Guardian telegram group to communicate with us.
We sincerely hope that EOS Security Guard can protect the security of EOS accounts.
BP节点账号：eoslaomaocom
CPU&NET 资源租赁：BankofStaked
币乎：EOSLaoMao
Telegram: EOSLaoMao
Twitter：EOSLaoMao
GitHub: EOSLaoMao
Steemit: EOSLaoMao
