How bordalix/helm-wallet works
Main Components Identification
The system should be represented with these key components:
a) Frontend Layer (React Application)
• User Interface Components (/src/components)
• Screen Flows (/src/screens)
• Provider Components (/src/providers)
b) Core Business Logic Layer (/src/lib)
• Wallet Management
• Transaction Processing
• Cryptographic Operations
• Network Communications
c) External Services
• Boltz Exchange Integration
• Lightning Network Interface
• Liquid Network Interface
• Explorer Services
┌─ User Interface Layer ─────────────────────┐
• (React Components, Screens, UI Logic) │
• Application State Layer ──────────────────┤
• (Providers: wallet.tsx, config.tsx, etc.) │
• Business Logic Layer ────────────────────┬┤
• ┌─ Wallet Core ─┐ ┌─ Network ─┐ ┌─ Crypto ┐│
• wallet.ts │ │ boltz.ts │ │blinder.ts││
• transactions.ts│ │ lnurl.ts │ │signer.ts ││
• ┘ └──────────┘ └──────────┘│
• External Services Layer ─────────────────┬┤
• ┌─ Boltz Exchange ─┐ ┌─ Lightning Network ┐│
• ┘ └──────────────────┘ │
• ┘
Key Relationships to Highlight
• Data flow between UI components and providers
• Communication between business logic and external services
• Wallet interactions with Boltz Exchange
• Lightning payment routing through Boltz
Technical Details
Annotations for:
• React/TypeScript as the frontend framework
• Liquid Network as the underlying blockchain
• Lightning Network compatibility through Boltz
• Local storage and encryption mechanisms
• Transaction fee structure
Implementation Notes
• Clear separation between UI components (/src/components) and business logic (/src/lib)
• Flow from user input through to blockchain transactions
• Role of providers in managing application state
• Demonstrate how the wallet maintains its simple UX while handling complex operations
Additional Elements
• Component types and their relationships
• Important configuration points