Policy Examples

This page provides practical examples of policy configurations for common organizational scenarios. Use these as templates and adapt them to your specific requirements.

These examples are ordered from least restrictive to most restrictive rules. Remember that rule order matters - the first matching rule is applied.

Liquid Fund Policy

An active trading policy for a liquid fund managing dynamic positions and frequent transactions, using maximum thresholds. Use Case: A $10M liquid fund executing high-frequency DeFi strategies with risk management controls and position limits.

1. Auto-approve trading operations up to $250,000 during business hours
   - Amount: <= $250,000 USD
   - Action Type: Swap, Bridge
   - Destination: Verified DEX List
   - Initiator: Trading Team
   - Time: Business Hours (9 AM - 6 PM EST)
   - Action: Auto-Approve
   - Reason: Enable efficient trading execution within defined limits

2. Require Fund Manager approval for weekend trades up to $50,000
   - Amount: <= $50,000 USD
   - Action Type: Swap, Bridge
   - Time: Saturday-Sunday
   - Action: Require 1 Approval
   - Approvers: Fund Manager
   - Reason: Weekend risk oversight for smaller trades

3. Require Fund Manager approval for large positions up to $1,000,000
   # This applies if not auto-approved by rule 1 (e.g. >$250k or outside business hours/DEX list)
   # or if a weekend trade is >$50k (not caught by rule 2)
   - Amount: <= $1,000,000 USD
   - Action Type: Swap, Stake, Bridge
   - Action: Require 1 Approval
   - Approvers: Fund Manager
   - Reason: Position size management for amounts up to $1M

4. Auto-approve staking in blue-chip protocols up to $500,000
   - Amount: <= $500,000 USD
   - Action Type: Stake, Unstake
   - Destination: Blue-chip Protocols (Lido, Aave, Compound)
   - Action: Auto-Approve
   - Reason: Low-risk yield generation up to a limit

5. Require Risk Manager approval for new asset exposure up to $10,000
   - Assets: Not in Approved Asset List
   - Amount: <= $10,000 USD
   - Action: Require 1 Approval
   - Approvers: Risk Manager
   - Reason: Portfolio risk assessment for small new asset exposures

6. Block interactions with unverified protocols
   # This rule is not primarily amount-based but destination-based
   - Action Type: Stake, Token Approval, Smart Contract Call
   - Destination: Not in Verified DeFi List
   - Action: Block
   - Reason: Smart contract risk management

7. Block governance token transfers
   # This rule is asset and action-type based
   - Assets: Governance Tokens
   - Action Type: Transfer
   - Action: Block
   - Reason: Maintain voting power and strategic positions

8. Default: Require trading team lead approval for other operations
   # Catches transactions not fitting above, like smaller new asset exposures > $10k before they get blocked by rule 9, or other unclassified operations
   - Conditions: Any
   - Action: Require 1 Approval
   - Approvers: Trading Team Lead
   - Reason: General oversight for operations not specifically covered

9. Default: Block transactions exceeding defined limits or otherwise not specified
   # Catches any transaction > $1,000,000 if not otherwise handled, or other non-compliant actions
   - Conditions: Any
   - Action: Block
   - Reason: Transaction exceeds maximum approved limit ($1M) or fails other policy criteria

Treasury Management Policy

A sophisticated policy for managing corporate treasury operations with strict financial controls, using maximum thresholds. Use Case: A $50M company treasury managing cash flow, investments, and strategic reserves with CFO oversight and board governance.

1. Auto-approve routine operational expenses up to $10,000
   - Amount: <= $10,000 USD
   - Action Type: Transfer
   - Destination: Address Book Only
   - Initiator: Treasury Team
   - Action: Auto-Approve
   - Reason: Daily operational efficiency for small, known expenses

2. Require Treasury team approval for operational transfers up to $50,000
   - Amount: <= $50,000 USD
   - Action Type: Transfer
   - Destination: Address Book Only
   - Action: Require 1 Approval
   - Approvers: Treasury Team
   - Reason: Operational expense control for medium, known expenses (up to $50k)

3. Require Finance Admin approval for medium transfers up to $500,000
   - Amount: <= $500,000 USD
   - Action Type: Transfer
   - Action: Require 1 Approval
   - Approvers: Finance Admins
   - Reason: Executive oversight by Finance Admins for significant transfer amounts (up to $500k)

4. Require CFO + 2 Board Members for large investments/interactions up to $2,000,000
   - Amount: <= $2,000,000 USD
   - Action Type: Stake, Bridge, Smart Contract Call # And large transfers not caught by rule 3
   - Action: Require 3 Approvals
   - Approvers: CFO (required) + 2 Board Members
   - Reason: Investment committee oversight for major capital movements (up to $2M)

5. Block all DeFi interactions except approved protocols
   # This rule is not primarily amount-based but destination-based for specific actions
   - Action Type: Stake, Swap, Token Approval, Smart Contract Call
   - Destination: Not in Verified DeFi List
   - Action: Block
   - Reason: Risk management and compliance

6. Default: Require Finance Admin approval for unspecified actions
   # Catches transactions or actions not fitting other rules but within overall limits
   - Conditions: Any
   - Action: Require 1 Approval
   - Approvers: Finance Admins
   - Reason: Finance Admin oversight for any operation not explicitly defined

7. Default: Block transactions exceeding overall limits or policy
   # Catches any transaction > $2,000,000 or other non-compliant actions
   - Conditions: Any
   - Action: Block
   - Reason: Board resolution required for major capital movements beyond $2M or policy violation

Basic Multisig Policy

A conservative policy for small teams using a multisig wallet, defining maximums for approvals. Use Case: A 5-person startup with a 3-of-5 multisig wallet managing company funds, paying vendors, and handling routine operations.

1. Auto-approve small operational expenses to known destinations
   - Amount: <= $5,000 USD
   - Destination: Address Book Only
   - Action: Auto-Approve
   - Reason: Routine vendor payments, salaries up to $5k

2. Require 1 Founder approval for very small payments to new destinations
   - Amount: <= $1,000 USD
   - Destination: Not in Address Book
   - Action: Require 1 Approval
   - Approvers: Any Founder
   - Reason: Controlled low-value payments to unverified addresses (up to $1k)

3. Block other payments to unverified destinations
   # This rule applies if Destination is Not in Address Book AND Amount is effectively > $1,000
   # (because Rule 2 would have caught it if Amount was <= $1,000)
   - Destination: Not in Address Book
   - Action: Block
   - Reason: Prevent payments to unverified addresses above $1,000

4. Require 2 Founders approval for medium expenses
   # Applies if not auto-approved (e.g. >$5k, or <=$5k but Not AddrBook and not blocked by Rule 3)
   # Effectively covers amounts up to $25,000 that pass prior rules.
   - Amount: <= $25,000 USD
   - Action: Require 2 Approvals
   - Approvers: Any 2 Founders
   - Reason: Standard expense approval for amounts up to $25,000

5. Require 3 Founders approval for large expenses
   # Applies for amounts effectively >$25k up to $100k, if not blocked by Rule 3
   - Amount: <= $100,000 USD
   - Action: Require 3 Approvals
   - Approvers: Any 3 Founders
   - Reason: Major expense oversight for amounts up to $100,000

6. Default: Block transactions exceeding defined limits or otherwise not specified
   # Catches anything not matched above (e.g., amounts > $100,000, or other unclassified scenarios)
   - Conditions: Any
   - Action: Block
   - Reason: Transaction exceeds maximum approved limit ($100k) or requires board meeting.

Best Practice Recommendations

Start Restrictive

Begin with overly restrictive policies and gradually relax them based on operational needs.

Layer Security

Use multiple overlapping rules rather than relying on a single comprehensive rule.

Regular Reviews

Schedule monthly policy reviews to ensure rules remain appropriate for your operations.

Document Rationale

Maintain clear documentation explaining why each rule exists and when it should be modified.

Ready to implement these examples? Start with our policy editing guide to create your custom rules.

Welcome

Configuration

SDK

Policy Examples

Policy Examples

Liquid Fund Policy

Treasury Management Policy

Basic Multisig Policy

Best Practice Recommendations

Start Restrictive

Layer Security

Regular Reviews

Document Rationale

​Policy Examples

​Liquid Fund Policy

​Treasury Management Policy

​Basic Multisig Policy

​Best Practice Recommendations

Start Restrictive

Layer Security

Regular Reviews

Document Rationale

Policy Examples

Liquid Fund Policy

Treasury Management Policy

Basic Multisig Policy

Best Practice Recommendations