Documentation Index
Fetch the complete documentation index at: https://docs.xentfi.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Why Asset Recovery?
🚨 Emergency Response
Quickly secure funds when a wallet is compromised or keys are lost
⚡ One-Click Recovery
Single operation to move all assets from source to destination wallet
🔒 Secure Transfer
All transfers are secure, audited, and require proper authentication
📊 Audit Trail
Complete record of recovery operations for compliance
🌐 Multi-Asset
Recover all supported assets across multiple blockchains
🎯 Precision Control
Recover specific assets or entire wallet contents
When to Use Asset Recovery
Emergency Scenarios
| Scenario | Action | Priority |
|---|---|---|
| Private key compromised | Immediate recovery to safe wallet | Critical |
| Team member departure | Recover assets from their wallets | High |
| Suspicious activity | Move funds to secure location | Critical |
| Wallet sunsetting | Consolidate before deactivation | Medium |
| Security audit | Temporary fund relocation | Low |
Recovery Triggers
Prerequisites
Before performing asset recovery, ensure:- ✅ You have a destination wallet (safe wallet) configured
- ✅ You have proper authentication (API key with recovery permissions)
- ✅ The source wallet is accessible (even if compromised)
- ✅ You understand which assets will be recovered
- ✅ You have notified relevant stakeholders
Recovery Process
Performing Asset Recovery
Recover All Assets
Recover Specific Assets
Dry Run Recovery (Simulation)
Recovery Status
Status Tracking
| Status | Description | Next Action |
|---|---|---|
pending | Recovery initiated, waiting | Monitor progress |
processing | Transfers in progress | Wait for completion |
completed | All assets recovered | Verify destination |
partial | Some assets recovered | Retry failed assets |
failed | Recovery failed | Investigate and retry |
Check Recovery Status
Recovery Best Practices
- Designate safe wallets - Configure dedicated safe wallets before emergencies
- Test recovery process - Perform dry runs regularly
- Document procedures - Create runbooks for recovery scenarios
- Limit permissions - Restrict recovery to authorized personnel only
- Audit regularly - Review recovery logs for suspicious activity
- Notify stakeholders - Alert team when recovery is initiated
Security Considerations
| Risk | Mitigation |
|---|---|
| Unauthorized recovery | Multi-signature approval for recovery |
| Wrong destination wallet | Wallet address whitelisting |
| Partial recovery | Automatic retry for failed transfers |
| Gas price spikes | Configurable gas limits |
| Network congestion | Queue and retry mechanism |
Recovery Configuration
Safe Wallet Setup
Approval Workflow
Webhook Events
| Event | Trigger | Payload contains |
|---|---|---|
recovery.started | Recovery initiated | Recovery ID, source, destination |
recovery.asset.completed | Asset transferred | Asset details, transaction hash |
recovery.asset.failed | Transfer failed | Asset, error reason |
recovery.completed | All assets recovered | Summary of transfers |
recovery.failed | Recovery failed | Error details |
Troubleshooting
Insufficient gas for recovery
Insufficient gas for recovery
Solution: Ensure source wallet has enough native tokens (ETH, MATIC, etc.) for gas fees. Add gas funds if needed.
Recovery stuck in processing
Recovery stuck in processing
Possible causes:
- Network congestion
- Gas price too low
- Destination wallet issues
Partial recovery only
Partial recovery only
Solution:
- Check which assets failed
- Verify destination supports those assets
- Retry failed assets individually
Pricing
| Feature | Starter | Professional | Business | Enterprise |
|---|---|---|---|---|
| Asset recovery | ❌ | ✅ | ✅ | ✅ |
| Dry run simulation | ❌ | ✅ | ✅ | ✅ |
| Approval workflow | ❌ | ❌ | ✅ | ✅ |
| Priority execution | ❌ | ❌ | ✅ | ✅ |
| Recovery webhooks | ❌ | ✅ | ✅ | ✅ |
Related Products
Master Wallets
Source and destination wallet management
Security
Security best practices
Webhooks
Recovery event notifications

