Develop correctness-check logic for node selection

[c0d3sw0t]

Extracted from documentation: T3-InfoSec/t3-memassist#10

---

What is the Problem or Limitation?

The application must validate user selections while they navigate the tree-based structure. A correctness-check system is necessary to compare the selected node with the predefined answer at each step. Without this logic, the app cannot guide users effectively through the learning process or provide immediate feedback on their selections. This could hinder the memorization workflow and reduce user engagement.

---

Describe the Solution You Would Like

The correctness-check logic for node selection should follow these core principles:

1. Validation Using Hash Comparisons

   • Each node answer will have a pre-generated hash. When a user selects a node, the selected answer’s hash should be compared with the correct one stored at that level.
   • The comparison must be instantaneous to provide real-time feedback, ensuring smooth interaction between the user and the app.

2. Feedback Mechanism Based on Results

   • Correct Selection:
     • Display positive feedback (e.g., “Correct! Moving to the next card.”).
     • Increment the user's progress score and navigate to the next relevant node or level.

3. Security and Data Integrity

   • Store all correct answer hashes securely in encrypted storage to prevent tampering.
   • Ensure that node validation logic occurs on the device, without transmitting sensitive data externally to maintain user privacy.

4. Performance Considerations

   • Optimize the correctness-check logic to run efficiently, even in deeper parts of the tree with multiple nodes. Avoid delays that might disrupt the user experience by implementing asynchronous operations where needed.

5. Resilience and Error Handling

   • If the hash comparison fails due to data corruption or unexpected errors, display a clear error message and offer a fallback option to restart the selection process.
   • Implement logging and analytics to track the frequency of errors and ensure continuous improvements in the logic.

---

Additional Considerations

• User Insights: Provide summarized reports showing the user’s success rate and areas where they struggled the most, helping them focus on weak points.