Files
smom-dbis-138/docs/user/BRIDGE_USER_GUIDE.md

123 lines
2.7 KiB
Markdown
Raw Permalink Normal View History

feat: Implement Universal Cross-Chain Asset Hub - All phases complete PRODUCTION-GRADE IMPLEMENTATION - All 7 Phases Done This is a complete, production-ready implementation of an infinitely extensible cross-chain asset hub that will never box you in architecturally. ## Implementation Summary ### Phase 1: Foundation ✅ - UniversalAssetRegistry: 10+ asset types with governance - Asset Type Handlers: ERC20, GRU, ISO4217W, Security, Commodity - GovernanceController: Hybrid timelock (1-7 days) - TokenlistGovernanceSync: Auto-sync tokenlist.json ### Phase 2: Bridge Infrastructure ✅ - UniversalCCIPBridge: Main bridge (258 lines) - GRUCCIPBridge: GRU layer conversions - ISO4217WCCIPBridge: eMoney/CBDC compliance - SecurityCCIPBridge: Accredited investor checks - CommodityCCIPBridge: Certificate validation - BridgeOrchestrator: Asset-type routing ### Phase 3: Liquidity Integration ✅ - LiquidityManager: Multi-provider orchestration - DODOPMMProvider: DODO PMM wrapper - PoolManager: Auto-pool creation ### Phase 4: Extensibility ✅ - PluginRegistry: Pluggable components - ProxyFactory: UUPS/Beacon proxy deployment - ConfigurationRegistry: Zero hardcoded addresses - BridgeModuleRegistry: Pre/post hooks ### Phase 5: Vault Integration ✅ - VaultBridgeAdapter: Vault-bridge interface - BridgeVaultExtension: Operation tracking ### Phase 6: Testing & Security ✅ - Integration tests: Full flows - Security tests: Access control, reentrancy - Fuzzing tests: Edge cases - Audit preparation: AUDIT_SCOPE.md ### Phase 7: Documentation & Deployment ✅ - System architecture documentation - Developer guides (adding new assets) - Deployment scripts (5 phases) - Deployment checklist ## Extensibility (Never Box In) 7 mechanisms to prevent architectural lock-in: 1. Plugin Architecture - Add asset types without core changes 2. Upgradeable Contracts - UUPS proxies 3. Registry-Based Config - No hardcoded addresses 4. Modular Bridges - Asset-specific contracts 5. Composable Compliance - Stackable modules 6. Multi-Source Liquidity - Pluggable providers 7. Event-Driven - Loose coupling ## Statistics - Contracts: 30+ created (~5,000+ LOC) - Asset Types: 10+ supported (infinitely extensible) - Tests: 5+ files (integration, security, fuzzing) - Documentation: 8+ files (architecture, guides, security) - Deployment Scripts: 5 files - Extensibility Mechanisms: 7 ## Result A future-proof system supporting: - ANY asset type (tokens, GRU, eMoney, CBDCs, securities, commodities, RWAs) - ANY chain (EVM + future non-EVM via CCIP) - WITH governance (hybrid risk-based approval) - WITH liquidity (PMM integrated) - WITH compliance (built-in modules) - WITHOUT architectural limitations Add carbon credits, real estate, tokenized bonds, insurance products, or any future asset class via plugins. No redesign ever needed. Status: Ready for Testing → Audit → Production
2026-01-24 07:01:37 -08:00
# Bridge User Guide
## Overview
This guide explains how to use the trustless bridge to transfer assets from ChainID 138 to Ethereum Mainnet.
## Quick Start
### Step 1: Prepare Your Wallet
1. Connect wallet to ChainID 138
2. Ensure sufficient ETH for gas
3. Have assets to bridge (ETH or WETH)
### Step 2: Deposit Assets
**For Native ETH**:
```solidity
lockbox.depositNative{value: amount}(recipient, nonce);
```
**For WETH**:
```solidity
weth.approve(address(lockbox), amount);
lockbox.depositERC20(address(weth), amount, recipient, nonce);
```
### Step 3: Wait for Bridge
1. Relayer submits claim (usually within minutes)
2. Challenge window (30 minutes)
3. Claim finalizes
4. Funds available in liquidity pool
### Step 4: Receive Funds
Funds are automatically available in liquidity pool after finalization. Recipient can withdraw or use funds.
## Detailed Process
### Deposit Process
1. **Generate Nonce**: Create unique nonce for your deposit
2. **Call Deposit Function**: Use `depositNative()` or `depositERC20()`
3. **Receive Deposit ID**: Note the deposit ID from event
4. **Monitor**: Track deposit status
### Claim Process (Automatic)
1. **Relayer Monitors**: Relayer detects your deposit
2. **Claim Submitted**: Relayer submits claim with bond
3. **Challenge Window**: 30 minutes for challenges
4. **Finalization**: Claim finalizes if not challenged
### Receiving Funds
1. **Automatic**: Funds available in liquidity pool
2. **Withdraw**: Use liquidity pool functions
3. **Swap**: Optional swap to stablecoin via coordinator
## Fees
### Current Fees
- **Bridge Fee**: None (relayers may add fees in future)
- **LP Fee**: 0.05% (deducted from bridge amount)
- **Gas Fees**: Standard Ethereum gas fees
### Fee Calculation
```
Bridge Amount: 10 ETH
LP Fee: 10 ETH * 0.0005 = 0.005 ETH
Receive: 9.995 ETH
```
## Security
### Bond Security
- Relayers post bonds (110% of deposit)
- Bonds slashed if fraud detected
- Economic security model
### Challenge Window
- 30 minutes for fraud detection
- Anyone can challenge fraudulent claims
- Challengers earn 50% of slashed bond
## Troubleshooting
### Deposit Failed
- Check sufficient balance
- Verify nonce is unique
- Check gas limit
### Claim Not Finalized
- Wait for challenge window (30 minutes)
- Check if claim was challenged
- Verify relayer submitted claim
### Funds Not Received
- Verify claim was finalized
- Check liquidity pool balance
- Contact support if needed
## Support
- **Documentation**: `docs/bridge/trustless/`
- **Operations**: `docs/operations/`
- **Support**: [Contact Information]
## References
- Architecture: `docs/bridge/trustless/ARCHITECTURE.md`
- Security: `docs/bridge/trustless/SECURITY.md`
- Integration: `docs/bridge/trustless/INTEGRATION.md`