littleshop/ROADMAP.md

LittleShop Development Roadmap

Executive Summary

This roadmap outlines the development priorities and strategic direction for LittleShop, a privacy-focused e-commerce platform with multi-cryptocurrency payment support. The roadmap prioritizes critical security fixes, production readiness, feature enhancements, and long-term scalability.

Last Updated: September 19, 2025 Version: 1.1.0 Status: Active Development

---

🚨 Phase 1: Critical Security Fixes (IMMEDIATE - September 2025)

HIGH Priority Security Vulnerabilities

1. ❗ Certificate Validation Bypass [CRITICAL]

• Location: LittleShop/Services/BTCPayServerService.cs:32-35
• Severity: HIGH
• Impact: Enables man-in-the-middle attacks on payment processing
• Fix Applied:
  • ✅ Removed unsafe certificate validation bypass
  • ✅ Implemented environment-specific configuration
  • ✅ Added explicit Development-only bypass with warning logs
• Timeline: Immediate - Before any production deployment
• Status: 🟢 COMPLETE (September 19, 2025)

2. ❗ Overly Permissive CORS Policy [HIGH]

• Location: LittleShop/Program.cs:139-148
• Severity: HIGH
• Impact: Enables Cross-Site Request Forgery (CSRF) attacks on admin panel
• Fix Applied:
  • ✅ Replaced AllowAnyOrigin() with specific trusted origins
  • ✅ Implemented anti-CSRF tokens on all state-changing endpoints
  • ✅ Created separate CORS policies for Development/Production/API
• Timeline: Immediate - Before production deployment
• Status: 🟢 COMPLETE (September 19, 2025)

Additional Security Hardening

3. ⚠️ CSRF Protection Implementation

• ✅ Added [ValidateAntiForgeryToken] to all Admin controllers
• ✅ Protected all POST/PUT/DELETE actions (10 controllers)
• Timeline: Week 1
• Status: 🟢 COMPLETE (September 19, 2025)

4. ⚠️ Environment-Specific Configuration

• ✅ Created appsettings.Development.json with dev-specific settings
• ✅ Created appsettings.Production.json template
• ✅ Configured environment-based CORS and SSL settings
• Timeline: Week 1
• Status: 🟢 COMPLETE (September 19, 2025)

---

📋 Phase 2: Production Readiness (Q4 2025 - October-December)

Testing & Quality Assurance

1. Test Coverage Improvement

• Current: 59% pass rate (24/41 tests)
• Target: 90% pass rate with comprehensive coverage
• Tasks:
  • Fix service registration in integration tests
  • Align test expectations with soft delete behavior
  • Standardize authentication configuration in tests
  • Add payment workflow integration tests
• Timeline: October 2025
• Status: 🟡 IN PROGRESS

2. E2E Testing Implementation

• Implement Playwright E2E tests for critical user journeys
• Test payment workflows with BTCPay Server sandbox
• Validate Telegram bot integration flows
• Timeline: October 2025
• Status: 🔴 PENDING

Infrastructure & Deployment

3. Docker Production Configuration

• Optimize Docker image size
• Implement health checks
• Add container orchestration support (Docker Swarm/K8s ready)
• Timeline: November 2025
• Status: 🟡 PARTIALLY COMPLETE

4. Monitoring & Observability

• Implement application performance monitoring (APM)
• Add distributed tracing for payment flows
• Set up alerting for critical errors
• Create operational dashboards
• Timeline: November 2025
• Status: 🔴 PENDING

5. Backup & Disaster Recovery

• Automated database backups
• Point-in-time recovery capability
• Disaster recovery documentation
• Timeline: December 2025
• Status: 🔴 PENDING

---

🚀 Phase 3: Feature Enhancements (Q4 2025 - Q1 2026)

Security & Privacy Features

1. 🔒 TeleBot Channel Lock & PIN Protection [HIGH PRIORITY]

• Status: 📋 Documented - Ready for Implementation
• Priority: HIGH - Privacy & Security Enhancement
• Location: docs/CHANNEL_LOCK_DESIGN.md
• Description: Complete channel lock system with 4-digit PIN protection
• Features:
  • Single security gate protecting all bot functionality
  • 4-digit PIN with PBKDF2 hashing (100,000 iterations)
  • Auto-lock modes (Manual, On Main Menu, Inactivity, On Exit, Always)
  • Brute force protection (3 attempts → 5 min lockout)
  • Screenshot-safe locked state (no data visible)
  • Backward compatible (Guest mode for users without PIN)
• Benefits:
  • ✅ Enterprise-grade privacy protection
  • ✅ Shared device safety
  • ✅ Mobile banking UX pattern
  • ✅ GDPR compliance enhancement
  • ✅ Zero data loss (preserved during lock)
• Implementation Estimate: 2-3 hours core + 1-2 hours UX polish
• Timeline: October 2025
• Success Metrics:
  • 60% user adoption within 30 days
  • < 0.1% lockout rate

  • 90% user satisfaction

• Future Enhancements:
  • Biometric unlock (Telegram WebApp API)
  • 2FA/TOTP support
  • Hardware security key integration
  • Zero-knowledge encryption

Shipping & Logistics

2. Royal Mail Integration

• API integration for label generation
• Tracking number management
• Automated shipping calculations
• International shipping support
• Timeline: January 2026
• Status: 🔴 PLANNED

3. Multi-Carrier Support

• Abstract shipping provider interface
• Support for DHL, FedEx, UPS
• Shipping rule engine
• Timeline: February 2026
• Status: 🔴 PLANNED

Communication & Notifications

4. Email Notification System

• Order confirmation emails
• Shipping notifications
• Payment status updates
• Admin alerts for critical events
• Timeline: January 2026
• Status: 🔴 PLANNED

5. Enhanced Telegram Bot Features

• Rich media product browsing
• Voice message support
• Automated customer support responses
• Multi-language support
• Timeline: March 2026
• Status: 🔴 PLANNED

Analytics & Reporting

6. Advanced Analytics Dashboard

• Sales trends and forecasting
• Customer behavior analytics
• Product performance metrics
• Cryptocurrency payment analytics
• Timeline: February 2026
• Status: 🔴 PLANNED

7. Financial Reporting

• Automated tax calculations
• Multi-currency reconciliation
• Export to accounting software
• Timeline: March 2026
• Status: 🔴 PLANNED

---

🏗️ Phase 4: Scale & Optimization (Q2 2026 - April-June)

Performance Optimization

1. Caching Strategy

• Implement Redis for session management
• Product catalog caching
• API response caching
• Database query optimization
• Timeline: April 2026
• Status: 🔴 PLANNED

2. Database Scaling

• Migration from SQLite to PostgreSQL
• Read replica configuration
• Database partitioning strategy
• Timeline: May 2026
• Status: 🔴 PLANNED

Advanced Features

3. Inventory Management System

• Real-time stock tracking
• Low stock alerts
• Automatic reorder points
• Supplier management
• Timeline: April 2026
• Status: 🔴 PLANNED

4. Multi-Tenant Support

• White-label capability
• Tenant isolation
• Custom domains per tenant
• Timeline: June 2026
• Status: 🔴 PLANNED

5. AI-Powered Features

• Product recommendation engine
• Chatbot customer support
• Fraud detection system
• Price optimization
• Timeline: June 2026
• Status: 🔴 PLANNED

---

📊 Success Metrics

Security Metrics

• ✅ Zero critical vulnerabilities in production
• ✅ 100% HTTPS/TLS enforcement
• ✅ Regular security audits passed

Performance Metrics

• ✅ < 200ms API response time (p95)
• ✅ 99.9% uptime SLA
• ✅ < 3s page load time

Quality Metrics

• ✅ > 90% test coverage
• ✅ < 1% error rate in production
• ✅ Zero data breaches

Business Metrics

• ✅ Support for 10+ cryptocurrencies
• ✅ < 5 minute order processing time
• ✅ > 95% payment success rate

---

🔄 Version History

v1.1.0 (September 19, 2025) - Security Fixes Complete

• ✅ Fixed certificate validation bypass vulnerability
• ✅ Implemented environment-specific SSL configuration
• ✅ Fixed overly permissive CORS policies
• ✅ Added CSRF protection to all admin controllers
• ✅ Created development and production configuration files
• Impact: All critical security vulnerabilities from Phase 1 resolved

v1.0.0 (September 19, 2025)

• Initial roadmap creation
• Identified critical security vulnerabilities
• Defined four development phases
• Established success metrics

---

📝 Notes

Dependencies

• BTCPay Server v2.0+ for payment processing
• .NET 9.0 for application runtime
• Docker for containerization
• Telegram Bot API for messaging integration

Risk Factors

1. Security: Certificate validation bypass must be fixed before production
2. Compliance: Ensure GDPR compliance for EU operations
3. Scalability: SQLite limitations for high-volume transactions
4. Integration: BTCPay Server API changes may impact payment flow

Contact

For questions about this roadmap, please contact the SilverLabs DevTeam at dev@silverlabs.uk

---

Status Legend

• 🔴 PENDING - Not started
• 🟡 IN PROGRESS - Active development
• 🟢 COMPLETE - Finished and tested
• ⏸️ ON HOLD - Temporarily paused
• ❌ CANCELLED - No longer planned