Introduction to transaction policies
Learn about off-chain and on-chain transaction policies in Cobo Portal, automating transaction handling.
Understanding transaction policies
Each organization manages a list of off-chain and/or on-chain transaction policies. When a transaction is initiated, it undergoes a matching process against the ordered policies in the list. If a matching policy is identified, the corresponding approval action will be automatically executed.
Transaction policies in Cobo Portal come in two main types:
- On-chain transaction policies
- Off-chain transaction policies
On-chain transaction policies
On-chain transaction policies are governed by smart contracts on the blockchain networks and are specifically designed for Smart Contract Wallets. These policies provide:
- Delegate management for single-signature operations
- Token approval controls
- Token transfer controls
- Custom contract call controls
Once created, modifications to on-chain transaction policies require multi-signature confirmation from Safe signers.
Off-chain transaction policies
Off-chain transaction policies are managed by Cobo Portal’s backend system. They offer:
- Flexibility: Easy to modify and update as needed
- Compatibility: Works with multiple wallet types
- Immediate effect: Changes take effect instantly without blockchain transactions
Off-chain transaction policies include the following types:
Policy Type | Main Purpose | Key Controls |
---|---|---|
Token transfer | Control token movements and limits | • Initiators • Amounts • Receiving addresses • Token types |
Contract call | Manage smart contract interactions | • Initiators • Token approvals • Token transfers • Contract addresses, methods, and parameters |
Message signing | Control transaction signing | • Initiators • Message types • Safe message signing controls |
Emergency policy | Immediate risk control for contingency | Enforcing auto rejection or auto quorum for all transactions |
Smart Contract Wallet policy guide
Smart Contract Wallets can use both on-chain and off-chain transaction policies. Here’s when to use each:
Use on-chain transaction policies when:
- Setting up delegate permissions that need to be enforced at the smart contract level
- Implementing permanent or long-term rules that shouldn’t be easily changed
- Configuring rules that must be executed on-chain for security
- Changes require multi-signature approval from Safe signers
Use off-chain transaction policies when:
- Need quick policy updates without requiring multi-sig approval
- Want additional control layers beyond on-chain rules
- Managing temporary or frequently changing rules
- Controlling specific transaction initiators or API access
For maximum security, you can combine both:
- Use on-chain transaction policies for core security rules
- Add off-chain transaction policies for flexible, day-to-day control
Setting up transaction policies
For detailed setup instructions, see:
- On-chain transaction policies:
- Off-chain transaction policies:
Was this page helpful?