No more guessing. No more gut feelings. When a student submits a .solus file, you get a cryptographic certificate showing every keystroke, every paste, and the exact order events happened — signed and tamper-evident.
The student writes in Solus and clicks "Submit." The .solus file is sealed with their ECDSA-P256 key and sent to your class dashboard. You get a notification.
The submission appears in your class list with a status badge — VALID, PARTIAL, TAMPERED, or PENDING. Click to open the full certificate view.
See the essay text alongside the verification report: keystroke count, paste events, human-origin percentage, timestamp chain, and 14-point check results.
Leave inline comments and a grade. Export the entire class's results to CSV for your LMS. The certificate stays attached to the submission record permanently.
Every .solus file embeds a cryptographic certificate with objective, machine-verifiable facts.
The total number of keystrokes, with a signed hash of the full timing log. You see the count; the log proves it's authentic.
Every paste event is logged with its content hash and character count. Pasted text is quarantined, not blocked — you see exactly what was pasted.
Calculated from the ratio of typed characters to total characters. A document with 3,000 typed chars and 200 pasted chars scores 94% human-origin.
Start time, end time, and a chain of intermediate hashes proving the document was written continuously — not assembled from fragments.
The ECDSA-P256 public key used to sign the document, tied to the student's Solus account. Proves which account produced the file.
From magic prefix to cryptographic signature, 14 independent checks confirm the document is authentic and unmodified since submission.
The certificate is cryptographically signed — it can't be selectively altered. If the signature verifies, the data is authentic. If the student claims their low keystroke count or high paste count is a bug, you can ask them to demonstrate the bug occurring in a new document. Solus logs are deterministic: a document written by a human will always produce a plausible keystroke pattern. A low-keystroke document with high paste volume is what it looks like.
Yes. The public verifier at verify.soluseditor.com (or the Verify page on this site) lets anyone drag and drop a .solus file to run a full 14-point check — no account required. The verification runs entirely in your browser using the SubtleCrypto API. Nothing is uploaded.
PARTIAL means the document passed most checks but not all. The most common causes: (1) the document contains a significant amount of pasted content — more than the class policy allows; (2) the signing key checks pass but the optional chain check is absent (older document format); (3) the human-origin score is below 80%. PARTIAL is not automatically a violation — it's a flag that warrants a conversation. You see exactly which checks failed, so you can judge in context.
No. Solus works offline for writing and local saving. The keystroke signing is entirely local — it uses the device's cryptographic hardware, not a server. Students only need internet to submit to your class dashboard. They can write offline and submit later.
Yes. Students can open the local verifier in Solus to see their own certificate before submitting. This is intentional — we believe transparency builds trust. Students know exactly what you'll see. There are no surprises.
Document content is encrypted with AES-256-GCM. X Point's servers never see the plaintext of essays. You (the teacher) can decrypt and read the essay through your dashboard because you hold the class decryption key. But X Point cannot read your students' essays — only you can.
Apply for institutional access and we'll set up your first class within 48 hours.