Wallet Strategy Engine

​

Introduction

ChainUp Custody’s wallet strategy engine enables customers to easily establish a robust and personalized risk control strategy. It allows for the effortless configuration and management of strategies based on business needs. By collaborating with your team, it facilitates governance of the security environment, mitigates human errors, prevents collusion by internal and external parties, and fulfills internal risk control requirements.

The wallet strategy engine of ChainUp Custody controls the core risk scenarios under the wallet, comprising two types of strategies: basic strategy and advanced strategy. Once the approval strategy is set, any transfer and approval will be enforced according to the rules, eliminating the possibility of bypassing or tampering.

​

Basic Strategy

The basic strategy is the initial internal control solution for wallets. In the absence of advanced strategies, it serves as a fallback for all risk scenarios, ensuring that all critical operations are always subject to approval control by the basic strategy. This eliminates human errors and guards against collusion by internal and external parties.

If users have not configured any advanced strategies, all risk scenarios (such as transfer transactions, Web3 Transactions, Whitlist management, strategy management, etc.) will be controlled by the basic strategy.

​

You can define the following parameters for the basic strayegy:

The triggered actions by the strategy ：

• Orders that match the basic strategy require approval through the user-defined approval process to be granted.

Explanation of Approval Nodes

Approval Node Type	Node Approvers	Number of Nodes	Number of Approvers
Approval	All Wallet Members	9 nodes, reorderable	20 people
Approval and Sign	Members with Wallet Private Key Permissions, including owners, admins	1 node, final node, not reorderable	20 people

​

Advanced Strategy

The advanced strategy allows users to easily configure control policies for each wallet, including transfer transaction control strategiess, transaction type configuration, approval roles, and approval workflows. Once the policy is established, no operation will be executed without approval, thereby protecting digital assets from internal threats.

You can define the following parameters for the Transfer Transactions Advanced Strategy:

Strategy Name: Name the transfer strategy for easy identification.

Strategy Trigger Conditions:

• Transaction Source: Specific wallet members or API.

• Transaction Assets: Specific currencies and NFTs, clearly defining the scope of assets protected by the strategy.

• Transfer Limit: Quantity or value of assets.

You can define the following parameters for the Web3 Transactions Advanced Strategy:

Strategy Name: Name the transfer strategy for easy identification.

Strategy Trigger Conditions:

• Transaction Source: Specific wallet members or API.

• Transaction Contract: Specific or any contract address.

Strategy Trigger Actions:

• Option 1: Transactions that match the strategy require approval. By setting the approver and approval threshold, ensure that transfers undergo the appropriate approval process.

Explanation of Approval Nodes

Approval Node Type	Node Approvers	Number of Nodes	Number of Approvers
Approval	All Wallet Members	9 nodes, reorderable	20 people
Approval and Sign	Members with Wallet Private Key Permissions, including owners, admins	1 node, final node, not reorderable	20 people

• Option 2: Orders that match this strategy will be automatically rejected, allowing for restrictions on specific transfer initiations to prevent internal malfeasance.