IBEx.Fi Recovery Flow

1. Enable Recovery Flow
🔒
Create Recovery Operation
POST /v1.1/safes/operations
ENABLE_RECOVERY + personal data
🔐
Sign Operation
PUT /v1.1/safes/operations
navigator.credentials.get()
User signs with passkey
✍️
Finalize Activation
PUT /v1.1/safes/operations
Submit credential
Safe
Wait for Execution
Bundler submits to blockchain
Operation status: EXECUTED
Recovery enabled
2. Check Recovery Status Flow
📊
Get Recovery Status
GET /v1.1/recovery/status/{safeAddress}
Returns recovery status
Safe
Recovery Status
recoveryEnabled, pending, executed
canExecute, executeAfter
3. Cancel Recovery Flow
❌
Create Cancel Operation
POST /v1.1/safes/operations
CANCEL_RECOVERY
🔐
Sign Operation
PUT /v1.1/safes/operations
navigator.credentials.get()
User signs with passkey
✍️
Finalize Cancellation
PUT /v1.1/safes/operations
Submit credential
Safe
Wait for Execution
Bundler submits to blockchain
Operation status: EXECUTED
Recovery cancelled

📋 Data to Store

  • userOpHash : Operation hash for tracking
  • recoveryEnabled : Whether recovery is enabled
  • recoveryAddress : Guardian address (if enabled)
  • delay : Recovery delay in seconds
  • canExecute : Whether recovery can be executed
  • executeAfter : Timestamp when recovery can be executed
  • pending : Array of pending recovery operations
  • executed : Array of executed recovery operations

🔧 Endpoints

⚙️ Technical Details

  • Recovery module via Safe module pattern
  • Personal data stored securely
  • ERC-4337 Account Abstraction
  • Gasless transactions (bundler/paymaster)
  • Recovery delay: 1 day (86400 seconds)
  • Status tracking: CREATED → SIGNED → EXECUTED → CONFIRMED
← Back to Recovery Guide