Web3 Policy
What are Web3 policies?
When performing smart contract-related operations using a Web3 wallet, such as token transfers, token approvals, contract authorizations, contract calls, NFT transfers, and NFT authorizations, it is necessary to control which contracts the Web3 wallet can interact with. To ensure security, strict approval control should be implemented through Web3 policies.
The approval process for the Web3 policy is consistent with the description above. The triggering conditions encompass multiple dimensions, which can be combined to fit your business setting.
Initiator
Limit transaction initiators. An initiator can be any team member with the permission to Create Transactions or an API Key. Define transaction initiators through the use of the following options: 1. Any member with the permission or API Key 2. Designate one or more members with the permission or API Keys
Source
Define Web3 wallets to be used for transfers using the following two options: 1. Any, which means transferring assets from any Web3 wallet 2. Designate 1 or more Web3 wallets
Destination
Limit smart contract addresses, and the maximum is 50 addresses per policy.
Priority
Define the priority of policy matching. A larger value indicates a higher priority. When policies conflict, the policy with a larger value takes precedence.
Approval Process
Define the action for duplicate signature tasks through the following options: 1. Reject 2. Enter a set approval process
How to configure Web3 policies?
If you need to add an advanced policy, please contact Safeheron's Support team. The Support team will assist you in configuring an Web3 policy based on the specifics of your business.
🪄 Tips:
You can use the following template to send an email to support@safeheron.com.
Web3 Policy Email Template
Subject
Web3 Policy Request
Content
Team ID: <Your Team ID>
🪄 Tips: You can find your Team ID by navigating to Settingsand click your team name. See below.
Description of Business Setting: <Describe your business settings where you use advanced policies, so that Safeheron's support team can verify whether the policy settings are reasonable and safe>
Examples of policies requested to add:
API Key 1
Any
0x694b...4008 0x795e...F7A6 0x3bF6...3038
100
Node name: Auto Approval Approvers: API Co-Signer Approval Threshold: 1/1
None
None
Member A
Web3 Wallet 1
Any
200
Node name: Finance Approval Approvers: B, C Approval Threshold: 1/2
Node name: Risk Control Approval Approvers: E, F Approval Threshold: 1/2
None
...
...
...
...
...
...
...
Last updated
