• We’re currently experiencing issues
  • Server
    Service Layer Dependency Conflict and Replay-Protection Sensitivity Regression

    The following remediation steps have been deployed and are currently under observation: Service Layer Decoupling: We have refactored the internal provider architecture, moving away from constructor-based injection to a Lazy Retrieval pattern using Container.get() within method execution scopes. Deployment of Whale Leniency Logic: Introduced a context-aware validation layer in the Analysis Worker. Whales (users with >= 5,000 VOT3 power or VIP status) are now evaluated via a specialized heuristic path: Visual Leniency: Permits Near Match, document layouts (likely recurring merchant templates) while maintaining a hard-block on exact bit-level duplicates (distance: 0). Dynamic OCR Thresholding: Increased the similarity rejection threshold from 0.85 to 0.98 for high-tier users. This allows receipts with similar structural data but different line items to pass validation. Frontend Performance & UX Hardening: Asset Modernization: Optimized Largest Contentful Paint (LCP) by migrating all brand assets (logos) to the WebP format, reducing payload size. PWA Manifest Refresh: Synchronized high-resolution icon sets ( logofbg.png ) for improved mobile/standalone experience. UI Asynchrony Protection: Implemented a Pre-flight Skeleton State in the SubmissionBox . This prevents Ghost Clicks by strictly locking the UI until the useDailyLimit hook has fully synchronized with the B3TR Reward Pool state (< 500 B3TR hard-block).

    Monitoring·
    Ongoing for 2 weeks
    ·Affects Server

    System status

    Mobile Apps

    Server