Dev Release 77

Greeting BlockDAG Community,

Thorough Testing and Exciting Developments: New Features

• Push Notifications
• Upon the completion of a mining session, the backend triggers a notification event for the user using a push notification service (Firebase Cloud Messaging). The notification payload includes session details and prompts the user to re-engage with the application.
• This real-time notification mechanism enhances user engagement by reducing latency in communication and encouraging immediate user action.
• New Status in Referral Module
• The backend updates the referral module schema to include new fields for 'Active,' 'Inactive,' and 'Pending' statuses. Each status is assigned based on user activity and registration status, queried and updated through optimized database operations.
• Enables more granular tracking and management of user referrals, improving user engagement strategies and platform transparency.
• VoIP Number Blocking Service
• Implemented a backend service that utilizes an IP geolocation API to determine the physical location of the phone number's registration. VoIP numbers identified as non-compliant with physical location requirements are automatically blocked through an API call to the platform's blacklist database.
• Enhances platform integrity by preventing fraudulent activities and ensuring fair participation, supported by automated verification and blocking mechanisms.

Pagination in Referral Module

• Implemented server-side pagination using a combination of SQL queries with LIMIT and OFFSET clauses. The backend retrieves referral data in chunks defined by pagination parameters, improving query efficiency and reducing load times.
• Enhances usability by allowing users to navigate through large datasets of referral records seamlessly, supported by efficient data retrieval and display mechanisms.
  
  FAQ Addition for Referral Status
• Integrated a structured FAQ database schema within the application backend, associating each FAQ entry with specific referral status queries. The frontend fetches and displays relevant FAQ entries dynamically based on user queries or navigation within the referral module.
• Provides users with immediate access to contextual help, improving user understanding and reducing support queries related to referral status definitions.
   
• Referral Module Filtering
• Implemented a frontend filtering mechanism using an API requests. Users can select filter criteria (e.g., Active, Inactive, Pending) triggering API calls to fetch and display filtered referral data from the backend database.
• Empowers users with the ability to customize views based on specific referral status criteria, enhancing user experience and facilitating efficient referral management.
  
  Leaderboard Optimization
• Refactored database indexing and query optimization strategies using database management system (DBMS)-specific techniques (e.g., index optimization, query plan analysis). Implemented caching mechanisms to store frequently accessed leaderboard data in memory for rapid retrieval.
• Significantly improves leaderboard performance by reducing query execution times and enhancing scalability, ensuring responsive and accurate leaderboard updates.
  
  Internet Connectivity Check
• Implemented a background service or periodic task within the application that sends HTTP requests to a predefined endpoint (e.g., Google DNS or a dedicated server). Monitors network connectivity status based on server response codes (e.g., 200 OK), triggering automatic reconnection attempts upon detection of network restoration.
• Ensures uninterrupted application functionality during intermittent network disruptions, enhancing user experience by maintaining seamless operation and data integrity.
  
  Session Management
• Enhanced session management logic in backend APIs and client-side application frameworks. Sessions are terminated immediately upon receiving deactivation or deletion requests from users, triggering cleanup of session data and associated resources.
• Improves application security by promptly terminating inactive sessions, reducing the risk of unauthorized access and enhancing overall system resource management.

As we have been rigorously testing the BlockDAG X1 Miner application before its official release. During our final round of testing, we identified an issue related to the FCM (Firebase Cloud Messaging) token.

Details on the FCM Token Issue:
The FCM token is a unique identifier used by Firebase Cloud Messaging to send notifications to a specific device. It is crucial for ensuring that users receive timely notifications related to their mining sessions, referrals, and other updates. The issue we encountered involved the improper registration and update of the FCM token, which could potentially lead to users not receiving critical notifications.

Resolution:
Upon identifying the issue, our team conducted a thorough investigation to understand the root cause and the scenarios in which the problem occurred. We have since implemented a fix to ensure the correct handling of FCM tokens, ensuring that all notifications are reliably delivered to our users.

Current Status:
We are now in the process of extensive testing to verify that the implemented fix resolves the issue without affecting any existing functionality. Our goal is to ensure that the application remains stable, secure, and fully functional for all users.

Next Steps:
As we are done with functionalities and features, so we are about to rollout the new update for our BlockDAG X1 app on Apple store and Amazon Store. Be ready to unlock new features in our BlockDAG X1 app.