2.3 KiB
2.3 KiB
Upgrade Procedures - Smart Accounts
Date: 2026-01-26
Network: ChainID 138 (SMOM-DBIS-138)
Overview
This guide explains upgrade procedures for Smart Accounts contracts and configuration.
Contract Upgrades
AccountWalletRegistryExtended
Upgrade Type: Proxy pattern (if using upgradeable proxy)
Procedure:
- Deploy new implementation
- Propose upgrade via governance
- Wait for approval
- Execute upgrade
- Verify functionality
Rollback:
- Keep previous implementation
- Can rollback if issues occur
Configuration Upgrades
Smart Accounts Kit SDK
Upgrade Steps:
- Update package.json
- Run
npm install - Update configuration if needed
- Test new version
- Deploy to production
Version Compatibility:
- Check SDK changelog
- Review breaking changes
- Update code if needed
Feature Upgrades
Adding New Features
Process:
- Deploy new contracts
- Update configuration
- Update documentation
- Test thoroughly
- Deploy to production
Enabling Features
Example: Enable gas abstraction
- Deploy Paymaster contract
- Update configuration
- Update SDK configuration
- Test gas abstraction
- Enable for users
Upgrade Checklist
Pre-Upgrade
- Review upgrade notes
- Backup current configuration
- Test on testnet
- Prepare rollback plan
Upgrade
- Deploy new contracts
- Update configuration
- Update SDK
- Test functionality
- Monitor for issues
Post-Upgrade
- Verify all features work
- Monitor metrics
- Check error logs
- Update documentation
Rollback Procedures
Contract Rollback
- Identify issue
- Pause new implementation
- Rollback to previous version
- Verify rollback success
- Investigate issue
Configuration Rollback
- Restore previous configuration
- Restart services
- Verify functionality
- Investigate issue
Best Practices
1. Staged Rollout
- Deploy to testnet first
- Deploy to staging
- Deploy to production gradually
2. Monitoring
- Monitor during upgrade
- Watch for errors
- Track metrics
3. Communication
- Notify users of upgrades
- Document changes
- Provide support
Resources
Last Updated: 2026-01-26