The Web3 Policy Engine lets you create custom transaction policies tailored to meet your specific operational needs. Separate policy engines are available for web3 transactions and web3 messages.
The policies are defined on an “IF, THEN” basis, allowing you to:
Define conditions for applying a transaction rule, including the source wallet or address group (excluded for messages) and the user initiating the transaction
Define the outcomes if the conditions are met, such as the required consensus and who can sign the transaction.
Without a custom policy, the default rule governs web3 transaction execution and message signing are governed by the default rule. This rule applies to all transactions unless a custom rule specifies otherwise. Custom rules are evaluated sequentially, from top to bottom. You can configure the priority of each rule when editing conditions. If a rule’s conditions are met, the rule’s outcomes will be used for approval and signing.
In Coinbase Prime, open Settings.
Navigate to the Web3 Settings.
In the Policy Engine tab, you'll find sections for Web3 Transactions and Web3 Messages.
Select Manage.
Select Add Rule and fill out the required conditions and outcomes.
Click Add.
Repeat for additional rules as needed.
Drag and drop policies in the required order. Note: custom rules are enforced from top to bottom when executing a transaction.
Click Review Changes and verify with your Yubikey.
The new policy will be live once your General Consensus is met.
In Coinbase Prime, open Settings.
Navigate to the Web3 Settings.
In the Policy Engine tab, you'll find sections for Web3 Transactions and Web3 Messages.
Select Manage.
Select the pencil icon next to the policy you want to change.
Edit the details or select delete rule.
Repeat for additional changes as needed.
Drag and drop policies in the required order. Note: custom rules are enforced from top to bottom when executing a transaction.
Click Review Changes and verify with your Yubikey.
The new policy will be live once your General Consensus is met.