You are ready to build. We are here to help. This is your central resource for understanding and integrating Fattoreum. Whether you need a high-level architecture guide or a specific API endpoint, you will find it here.
Your first five minutes to your first attestation. Follow a simple path to submit data, retrieve evidence, and run independent verification checks.
The complete, detailed reference for API endpoints, including request parameters, response payloads, and integration examples.
Dive deeper into the why behind Fattoreum, including hashing models, signature semantics, and anchoring policy behavior.
Canonical exact-content integrity uses SHA-384. SHA-256 values are retained only for internal bundle/journal/artifact checks and compact anchor commitments.
Integrity Check, Signed Attestation, and Signed Manifest Lane differences.
Fattoreum keeps deterministic cryptographic integrity separate from probabilistic similarity signals.
Canonical SHA-384 is deterministic and authoritative for exact-match verification.
SimHash (`simhash_64`) is probabilistic decision support for minor edits and closely related text.
Optional OCR-based anti-evasion signal includes confidence metadata and is never exact textual equivalence.
Similarity does not prove intent, plagiarism, fraud, copying, or misconduct. Human review is required.
Practical examples for securing CI/CD workflows, validating financial documents, and handling records-sensitive operations with clear evidence trails.