Integration Patterns
Integration Patterns Overview
This section covers common patterns and best practices for integrating Ika dWallet functionality into your Move contracts.
Available Patterns
| Pattern | Description | Use Case |
|---|---|---|
| Shared dWallet Contracts | Contract-owned dWallets that sign without user interaction | DAOs, treasuries, automated systems |
| Presign Pool Management | Maintain a pool of presigns for continuous operation | Any contract that signs frequently |
Pattern Overview
Shared dWallet for Smart Contracts
The most common pattern for Move integration. The contract owns a shared dWallet and controls signing through its business logic.
Key characteristics:
- Contract holds the
DWalletCap - Uses public user share (shared mode)
- Network can sign without user interaction
- Access control through contract logic
Presign Pool Management
Presigns are consumed during signing, so you need to maintain a pool for continuous operation.
Key characteristics:
- Store multiple presigns
- Replenish after each signature
- Auto-replenish when pool gets low
Combining Patterns
Most real-world contracts combine multiple patterns:
Quick Reference
Essential Structure
Essential Helper Functions
Next Steps
- Learn about Shared dWallet Contracts for DAO and treasury use cases
- See Presign Pool Management for continuous signing operations