How availproject/bridge-ui works
Component Relationships
• User Interface → Hooks → Stores (State Management)
• Hooks → Services → Blockchain Networks
• API Routes → External Services
• MetaMask Integration ↔ Blockchain Networks
Specific Component Details
Frontend Components:
┌─ UI Layer ─────────────────┐
• Bridge Section │
• Transaction Section │
• Wallet Components │
• Common UI Components │
• ┘
State Management:
┌─ Stores ──────────────────┐
• Wallet Store │
• Transaction Store │
• Common Store │
• Block Info Store │
• ┘
Integration Layer:
┌─ Services ────────────────┐
• API Service │
• Transaction Service │
• Vector Pallet Service │
• ┘
Additional Elements
• Version/environment indicators (test, staging, prod)
• Deployment flow as mentioned in README:
• Test → Preview Domains
• Staging → turing.bridge.avail.so
• Prod → bridge.availproject.org
Technical Stack Indicators
Badges/labels for:
• Next.js
• TypeScript
• Tailwind CSS
• MetaMask
• Ethereum
• Avail Network
Remember to include notes about the different deployment environments and their corresponding domains, as this is crucial for understanding the complete system architecture.