3.3 KiB
3.3 KiB
Rollback Procedures - Smart Accounts
Date: 2026-01-26
Network: ChainID 138 (SMOM-DBIS-138)
Overview
This guide explains rollback procedures for Smart Accounts deployments and upgrades.
Rollback Scenarios
Scenario 1: Contract Deployment Issues
Symptoms:
- Contracts deployed incorrectly
- Functionality not working
- Security concerns
Rollback:
- Pause New Contracts: Pause affected contracts if possible
- Revert to Previous: Use previous contract versions
- Update Configuration: Update config to point to previous contracts
- Verify: Test that rollback works
- Investigate: Identify and fix issues
Scenario 2: Configuration Issues
Symptoms:
- Configuration errors
- Wrong addresses
- Incorrect settings
Rollback:
- Restore Backup: Restore previous configuration
./backups/recover-smart-accounts-config.sh <timestamp> - Restart Services: Restart affected services
- Verify: Test functionality
- Fix: Correct configuration issues
Scenario 3: SDK Upgrade Issues
Symptoms:
- SDK version incompatible
- Breaking changes
- Functionality broken
Rollback:
- Downgrade SDK: Install previous version
npm install @metamask/smart-accounts-kit@<previous-version> - Update Code: Revert code changes if needed
- Test: Verify functionality
- Fix: Address compatibility issues
Rollback Checklist
Pre-Rollback
- Identify issue
- Assess impact
- Locate backup/previous version
- Prepare rollback plan
- Notify team
Rollback
- Pause affected systems
- Restore previous version
- Update configuration
- Restart services
- Verify functionality
Post-Rollback
- Monitor for issues
- Verify all features work
- Document rollback
- Investigate root cause
- Plan fix
Backup Locations
Configuration Backups
Location: backups/
Files:
smart-accounts-config_<timestamp>.jsonmonitoring-config_<timestamp>.json
Restore:
./backups/recover-smart-accounts-config.sh <timestamp>
Contract Backups
Location: Block explorer (immutable)
Information:
- Previous contract addresses
- Previous deployment transactions
- Previous contract code
Emergency Procedures
Critical Issues
Immediate Actions:
- Pause Contracts: Pause if pause function available
- Disable Features: Disable affected features
- Notify Users: Communicate issue
- Investigate: Identify root cause
- Fix: Implement fix
- Test: Test fix thoroughly
- Deploy: Deploy fix
Communication
- Notify stakeholders immediately
- Provide status updates
- Document all actions
- Post-mortem after resolution
Prevention
Best Practices
- Test Thoroughly: Test before deployment
- Staged Rollout: Deploy gradually
- Monitor Closely: Watch for issues
- Keep Backups: Regular backups
- Document Changes: Document all changes
Testing
- Test on testnet first
- Test with small user group
- Monitor metrics
- Watch for errors
Resources
Last Updated: 2026-01-26