How timewave-computer/valence-protocol works
Main Components
a. Core Protocol Components:
• Authorization System (/contracts/authorization)
• Processor System (/contracts/processor)
• Program Registry (/contracts/program-registry)
• Program Manager (/program-manager)
• Base Account System (/contracts/accounts/base_account)
b. Library Components:
• Multiple DEX Integration Libraries (Astroport, Osmosis)
• IBC Transfer Libraries (Generic and Neutron)
• Utility Libraries (Splitter, Forwarder)
c. Cross-Chain Infrastructure:
• Domain Connectors (Cosmos, EVM)
• Bridge Systems
• IBC/ICQ Components
[User/Developer Interface Layer]
[Program Management Layer]
[Core Protocol Layer]
[Library Layer]
[Cross-Chain Infrastructure Layer]
[Blockchain Networks Layer]
Key Relationships to Highlight
• Bidirectional flows between Program Manager and Authorization/Processor components
• How Libraries interface with the Core Protocol
• Demonstrate cross-chain message flow through IBC/Bridge components
• How different blockchain networks connect through the infrastructure layer
Component Details
Core Protocol:
┌─ Program Manager ─────┐
• Config Management │
• Program Migration │
• Domain Connectors │
• ┘
┌─ Authorization ──────┐
• User Actions │
• Owner Actions │
• Domain Management │
• ┘
┌─ Processor ─────────┐
• Queue Management │
• Callbacks │
• State Management │
• ┘
Implementation Notes
• Maintain clear separation between different protocol layers
• Version/status indicators for components under development
• Notes for planned future integrations (e.g., SVM support)
• Trust-minimized execution environment
• Cross-chain capabilities
• Resource model architecture
• Multi-party program support
• Domain-specific co-processor compilation
This system design should be implemented as a living document, updated as new features are added or architecture changes are made to the protocol.