How warden-protocol/wardenprotocol works
Main Components
a. Core Protocol Layer:
• Warden Chain (Cosmos SDK-based blockchain)
• Smart Contract Layer (including EVM compatibility)
• Protocol Modules (x/warden, x/act, x/async, x/gmp)
b. Client Applications:
• SpaceWard (Web Interface)
• Automated Orders System
• CLI Tools (wardend, wardenkms)
c. Development & Integration:
• API Layer (REST/gRPC)
• Client SDKs (wardenjs, go-client)
• Smart Contract Integration
Architectural Layers
┌─ Application Layer ─────────────────────┐
• SpaceWard UI | Automated Orders | Tools │
• Integration Layer ────────────────────┐│
• WardenJS SDK | Go Client | REST/gRPC ││
• Protocol Core ─────────────────────┐ ││
• Modules | Smart Contracts | Chain │ ││
• Infrastructure ──────────────────┐ │ ││
• Cosmos SDK | Tendermint | EVM │ │ ││
• ┘─┘─┘┘
Key Relationships to Highlight
a. Module Interactions:
• GMP (General Message Passing) interactions
• Smart contract integration points
b. Client-Protocol Communication:
• API endpoints and SDK connections
• Authentication and signature flows
• Precompile interfaces
Implementation Details
Use these symbols:
• Hexagons for modules
• Rectangles for applications
• Diamonds for decision points
Additional Elements
Include:
• Version information
• Protocol boundaries
• External service connections
• Monitoring points
• Error handling paths
Notes
Annotations for:
• Critical paths
• Security considerations
• Scaling points
• Future expansion areas
This architectural representation will serve as a crucial reference for understanding the system's structure and interactions, facilitating both development and maintenance activities.