Dev Release 60

Greetings BlockDAG Community,

We are excited to announce a work progress in the BlockDAG Explorer! Our team has successfully started fetching all the events from our backend services to display them on the frontend, providing a comprehensive and detailed view of blockchain activities. This improvement aligns our explorer users to have access to rich and timely data.
Similar to other blockchain explorer in the market, which provides extensive data on transactions, contracts, blocks, and more, our enhanced explorer will offer a wealth of information fetched directly from our backend. This will greatly improve the user experience by offering a more detailed and accessible overview of the blockchain's activity.

Data Fetching Methods and Types
To achieve this, we have integrated several methods to fetch various types of data from our backend. Here's a breakdown of the data types and methods used:
 

1. Blocks Data

• Method: getBlocks
• Description: Fetches the latest blocks, including details such as block height, timestamp, number of transactions, miner information, and block rewards.
• Example: This block details page will provide an overview of each block's contents and metrics.

1. Initialize an empty list to store block details.

2. Send a request to the backend service to retrieve block data.

3. For each block in the response:

  a. Extract block height, timestamp, number of transactions, miner information, and reward.

  b. Create a block object with the extracted details.

  c. Append the block object to the list.

4. Return the list of block objects.

2. Transactions Data

• Method: getTransactions
• Description: Retrieves all transactions within a specified block or across the entire blockchain, including transaction hash, sender, receiver, value, gas used, and status.
• Example: This transaction page provides list and details, showing every transaction's specifics.

1. Initialize an empty list to store transaction details.

2. Send a request to the backend service to retrieve transaction data.

3. For each transaction in the response:

  a. Extract transaction hash, sender, receiver, value, gas used, and status.

  b. Create a transaction object with the extracted details.

  c. Append the transaction object to the list.

4. Return the list of transaction objects.

3. Events/Logs Data

• Method: getLogs
• Description: Gathers event logs from smart contracts, including event names, parameters, and transaction hashes.
• Example: This event logs section provides detailing every emitted event from smart contract interactions.

1. Initialize an empty list to store log details.

2. Send a request to the backend service to retrieve log data.

3. For each log entry in the response:

  a. Extract event name, parameters, and transaction hash.

  b. Create a log object with the extracted details.

  c. Append the log object to the list.

4. Return the list of log objects.
 

4. Account/Address Data

• Method: getAccountInfo
• Description: Provides information on individual addresses, including balance, transaction history, and associated smart contracts.
• Example: The address details page, offering insights into an address’s activity and holdings.

1. Initialize an empty dictionary to store account details.

2. Send a request to the backend service to retrieve account data for a specific address.

3. Extract balance, transaction history, and associated smart contracts from the response.

4. Populate the dictionary with the extracted details.

5. Return the dictionary containing the account information.

Next Steps
Our team is fully aligned on this initiative, ensuring that every member understands the importance and scope of these enhancements. We have established clear milestones and checkpoints to guarantee a smooth and timely implementation.
Here are the few planned next steps:

1. Testing and Validation: Conduct thorough testing to ensure data accuracy and reliability.
2. Frontend Integration: Seamlessly integrate the fetched data into the explorer’s user interface.
3. User Feedback: Collect and incorporate feedback from our community to refine and improve the features.
4. Continuous Improvement: Regularly update and enhance the data fetching mechanisms to keep up with blockchain changes and user needs.
    

Conclusion
We believe this enhancement will greatly benefit our users, providing deeper insights and a more engaging experience on the BlockDAG Explorer. By aligning closely with the standards, we aim to deliver a familiar yet powerful tool for blockchain exploration.
Stay tuned for more updates!

Today marks the second day of our bug bounty program, and we are pleased to report that we've received several valuable bug submissions. Our dedicated mobile development team is rigorously working to address these issues, ensuring the X1 Miner app delivers the best possible experience for our users.

Bug Reports and Fixes
Over the past two days, we have received a variety of bug reports, ranging from minor UI inconsistencies to more complex performance issues. Here are some of the key areas we are focusing on:

User Interface (UI) Enhancements

• Issue: Some users reported inconsistencies in the UI elements across different device models and screen sizes.
• Action: Our team is standardizing UI components to ensure a consistent look and feel across all devices.
  
  Performance Optimization
• Issue: A few users experienced lag and slow response times during intensive mining operations.
• Action: We are optimizing the app's performance to handle higher loads more efficiently, reducing lag and improving responsiveness.
  
  Stability and Crash Fixes
• Issue: There were instances of the app crashing under certain conditions, particularly during background operations.
• Action: Our developers are investigating the root causes of these crashes and implementing fixes to enhance the app's stability.
  
  Feature Improvements
• Issue: Users suggested improvements to some of the app’s features, such as more detailed mining statistics and enhanced notification settings.
• Action: We are incorporating this feedback to refine and expand the app's feature set, making it more user-friendly and informative.
   

Our mobile development team is working around the clock to address the reported issues. We have set up a streamlined process for prioritizing and resolving bugs, ensuring that critical issues are addressed first while also planning for the implementation of user-suggested enhancements.
Steps Taken by Our Team:

1. Daily Stand-ups: Our team conducts daily stand-up meetings to discuss progress, prioritize tasks, and allocate resources effectively.
2. Collaborative Debugging: Developers are working collaboratively, leveraging their collective expertise to debug and fix reported issues swiftly.
3. User Testing: We are conducting extensive user testing to validate the fixes and ensure that new updates do not introduce additional problems.
4. Continuous Feedback Loop: We maintain an open feedback loop with our users, acknowledging their reports and providing updates on the status of their submissions
    

Conclusion & Road Ahead
Our team is fully dedicated to ensuring that the X1 Miner application meets the highest standards of quality and performance. Once everything is complete we look forward to submit the applications soon on stores.