01
Download Writer and check your setup.
Writer accompanies your writing session in the selected app. Review the recorded activity and link it to your finished file when the session ends. You can then share the signed record.
02
Verify in your browser.
Local verification requires JavaScript, WebCrypto with Ed25519, and a secure environment using HTTPS or localhost. Recipients do not need the Writer app for this check. Test the actual browser with the synthetic example; a product name alone does not establish version, configuration or cryptographic support.
03
Three files with different roles.
Select a ExtraProof PDF or JSON record as evidence. The comparison file is the separately bound submission version. Verify compares its bytes without analysing its text.
- ExtraProof PDF: up to 32 MiB.
- Creation Record as JSON: up to 16 MiB.
- File for comparison: up to 64 MiB.
- An ordinary PDF without the designated ExtraProof attachment is not a verifiable ExtraProof record.
04
The boundary of PDF verification.
The browser extracts the uniquely indexed humanproof-certificate.json attachment, checks its SHA-256, then verifies the record’s signature and event chain. It does not verify visible PDF content or the PDF/CMS signature. A positive record result therefore does not confirm the entire PDF presentation. The native app checks the PDF signature separately.
05
Working offline and resolving problems.
Prepare the required verification environment and all files before losing the connection. Offline reading of information pages does not replace this trial. Keep the bound version unchanged. If a file does not match or cannot be verified, note the browser or app version, error message and file format for follow-up.
