Integrate BACKBEAT SDK and resolve KACHING license validation

Major integrations and fixes:
- Added BACKBEAT SDK integration for P2P operation timing
- Implemented beat-aware status tracking for distributed operations
- Added Docker secrets support for secure license management
- Resolved KACHING license validation via HTTPS/TLS
- Updated docker-compose configuration for clean stack deployment
- Disabled rollback policies to prevent deployment failures
- Added license credential storage (CHORUS-DEV-MULTI-001)

Technical improvements:
- BACKBEAT P2P operation tracking with phase management
- Enhanced configuration system with file-based secrets
- Improved error handling for license validation
- Clean separation of KACHING and CHORUS deployment stacks

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
anthonyrawlins
2025-09-06 07:56:26 +10:00
parent 543ab216f9
commit 9bdcbe0447
4730 changed files with 1480093 additions and 1916 deletions

View File

@@ -46,7 +46,7 @@ The main orchestrator that coordinates between all storage layers:
### 2. Encrypted Storage (`encrypted_storage.go`)
Role-based encrypted storage with enterprise-grade security:
- **Per-role encryption** using the existing BZZZ crypto system
- **Per-role encryption** using the existing CHORUS crypto system
- **Key rotation** with automatic re-encryption
- **Access control validation** with audit logging
- **Encryption metrics** tracking for performance monitoring
@@ -184,16 +184,16 @@ type ContextStoreOptions struct {
- **Timeout values**: Set appropriate timeouts for your network
- **Background intervals**: Balance between performance and resource usage
## Integration with BZZZ Systems
## Integration with CHORUS Systems
### DHT Integration
The distributed storage layer integrates seamlessly with the existing BZZZ DHT system:
The distributed storage layer integrates seamlessly with the existing CHORUS DHT system:
- Uses existing node discovery and communication protocols
- Leverages consistent hashing algorithms
- Integrates with leader election for coordination
### Crypto Integration
The encryption layer uses the existing BZZZ crypto system:
The encryption layer uses the existing CHORUS crypto system:
- Role-based key management
- Shamir's Secret Sharing for key distribution
- Age encryption for data protection