111 lines
3.3 KiB
Markdown
111 lines
3.3 KiB
Markdown
|
# Smart Vault vs MetaMask Smart Accounts Kit - Summary
|
||
|
|
|
||
|
|
**Date**: 2026-01-26
|
||
|
|
**Status**: ✅ **COMPARISON COMPLETE**
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Key Findings
|
||
|
|
|
||
|
|
### Proxmox Smart Vault System
|
||
|
|
|
||
|
|
**Purpose**: Payment rail settlement and compliance system
|
||
|
|
|
||
|
|
**Components**:
|
||
|
|
1. **RailEscrowVault** (`0x609644D9858435f908A5B8528941827dDD13a346`)
|
||
|
|
- Escrows tokens for payment rails (FEDWIRE, SWIFT, SEPA)
|
||
|
|
- Per-trigger escrow tracking
|
||
|
|
- Lock/release functionality
|
||
|
|
|
||
|
|
2. **AccountWalletRegistry** (`0xBeEF0128B7ff030e25beeda6Ff62f02041Dedbd0`)
|
||
|
|
- Maps fiat accounts (IBAN, ABA) to Web3 wallets
|
||
|
|
- Supports MetaMask, Fireblocks, etc.
|
||
|
|
- 1-to-many account-wallet mapping
|
||
|
|
|
||
|
|
3. **SettlementOrchestrator**
|
||
|
|
- Coordinates payment trigger lifecycle
|
||
|
|
- Validates compliance and policies
|
||
|
|
- Manages escrow lock/release
|
||
|
|
|
||
|
|
**Architecture**: Standard EOAs with escrow contracts
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
### MetaMask Smart Accounts Kit
|
||
|
|
|
||
|
|
**Purpose**: Programmable accounts and granular permission sharing
|
||
|
|
|
||
|
|
**Key Features**:
|
||
|
|
- Smart Accounts (ERC-4337 compatible)
|
||
|
|
- Delegation Framework
|
||
|
|
- Advanced Permissions (ERC-7715)
|
||
|
|
- User Operations (batch transactions)
|
||
|
|
- Gas Abstraction
|
||
|
|
|
||
|
|
**Reference**: [MetaMask Smart Accounts Kit](https://docs.metamask.io/smart-accounts-kit#partner-integrations)
|
||
|
|
|
||
|
|
**Architecture**: Smart contract accounts with programmable logic
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Comparison Result
|
||
|
|
|
||
|
|
### They Are Different Systems
|
||
|
|
|
||
|
|
| Aspect | Proxmox Smart Vault | MetaMask Smart Accounts Kit |
|
||
|
|
|--------|---------------------|----------------------------|
|
||
|
|
| **Purpose** | Payment rail settlement | Programmable accounts |
|
||
|
|
| **Account Type** | Standard EOAs | Smart Contract Accounts |
|
||
|
|
| **Use Case** | FEDWIRE, SWIFT, SEPA | dApp interactions |
|
||
|
|
| **Features** | Escrow, Compliance | Delegation, Permissions |
|
||
|
|
|
||
|
|
### They Can Be Complementary
|
||
|
|
|
||
|
|
✅ **Smart Vault**: Handles payment rails
|
||
|
|
✅ **Smart Accounts Kit**: Handles dApp interactions
|
||
|
|
✅ **AccountWalletRegistry**: Can bridge both systems
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Integration Recommendation
|
||
|
|
|
||
|
|
### Hybrid Approach (Recommended)
|
||
|
|
|
||
|
|
1. **Keep Smart Vault**: Continue using RailEscrowVault for payment rails
|
||
|
|
2. **Add Smart Accounts**: Deploy Smart Accounts Kit for dApp interactions
|
||
|
|
3. **Unify Management**: AccountWalletRegistry manages both
|
||
|
|
4. **Flexible Usage**: Users can have both EOA and smart account
|
||
|
|
|
||
|
|
**Benefits**:
|
||
|
|
- ✅ Maintains existing payment rail functionality
|
||
|
|
- ✅ Adds smart account capabilities
|
||
|
|
- ✅ Flexible for different use cases
|
||
|
|
- ✅ Backward compatible
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Files Created
|
||
|
|
|
||
|
|
1. **`docs/SMART_VAULT_VS_METAMASK_SMART_ACCOUNTS_COMPARISON.md`** - Initial comparison
|
||
|
|
2. **`docs/SMART_VAULT_COMPREHENSIVE_COMPARISON.md`** - Comprehensive comparison
|
||
|
|
3. **`docs/SMART_ACCOUNTS_INTEGRATION_ROADMAP.md`** - Integration roadmap
|
||
|
|
4. **`scripts/deploy-smart-accounts-kit.sh`** - Deployment script
|
||
|
|
5. **`smart-accounts-kit-deployment/DEPLOYMENT_GUIDE.md`** - Deployment guide
|
||
|
|
6. **`smart-accounts-kit-deployment/ACCOUNT_WALLET_INTEGRATION.md`** - Integration guide
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Next Steps
|
||
|
|
|
||
|
|
1. **Review Comparison**: Understand differences and opportunities
|
||
|
|
2. **Deploy Smart Accounts Kit**: Deploy to ChainID 138
|
||
|
|
3. **Integrate with AccountWalletRegistry**: Extend existing system
|
||
|
|
4. **Test Integration**: Test all features
|
||
|
|
5. **Deploy to Production**: Deploy after testing
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Status**: ✅ **COMPARISON AND INTEGRATION PLAN COMPLETE**
|
||
|
|
|
||
|
|
**Last Updated**: 2026-01-26
|