Verification &
Proof of Work
We do not issue completion certificates. We generate a cryptographically verifiable log of problem-solving history.
1. Computation vs. Attendance
Traditional credentials verify that a student was present (latency) or memorized a fact (storage). Mentrast verifies computation. We measure your ability to synthesize new logic in real-time.
- Video Completion Rate
- Multiple Choice Quizzes
- Attendance Logs
- + Unit Test Passage
- + Semantic Logic Derivation
- + Time-Bounded Problem Solving
2. The Ledger Mechanism
Every solved problem generates a "Proof Block". This block is hashed and chained to your previous history. This ensures that your mastery curve is visible and tamper-proof.
{
"id": "block_0x8f2a...",
"timestamp": "2024-11-02T14:22:01Z",
"challenge": {
"type": "SYSTEM_DESIGN",
"topic": "Distributed Consensus",
"complexity": "HARD"
},
"submission": {
"hash": "0x7d3e91...",
"time_to_solve": "42m 12s",
"attempts": 3
},
"verification": {
"status": "PASS",
"validator": "grok_v3_logic_core"
},
"prev_hash": "block_0x1b9c..."
}
3. Anti-Gaming Logic
Semantic Variation
No two users receive the exact same prompt. The exact parameters of a problem are generated at runtime, preventing "answer key" sharing.
Keystroke Dynamics
The system monitors input velocity. "Copy-paste" events of large code blocks trigger a validation flag requiring explanation.
Socratic Interrogation
Solving the problem is not enough. The Mentor Engine may interrupt to ask *why* you chose a specific implementation.
4. Verification Modes
Returns binary VERIFIED / NOT FOUND status.
5. Retention & Privacy
- - Proof hashes stored permanently.
- - Raw telemetry retained 90 days.
- - User owns cryptographic keys.