Cryptographic Proof Verification
The ITYLOS laboratory allows you to analyze a verifiable digital proof associated with a capsule. This forensic tool mathematically validates the cryptographic signature and confirms the integrity of our audit registry, without sending your data over the network.
Proof Injector
The system will reconstruct the payload to attest to the authenticity of the destruction event.
Expert Report
How to verify a proof
The forensic process is immediate:
- Download the JSON proof from a capsule’s history.
- Drop the file into the injector or paste its raw content.
- Launch the cryptographic analysis.
- The report will confirm the authenticity or possible alteration of the file.
Technical specification
Cryptographic fingerprint details:
- Signature : Ed25519
- Public key: 32 bytes
- Signature size: 64 bytes
- Type: Detached signature
Independent verification
ITYLOS proofs can be verified without access to the service infrastructure.
Anyone with the JSON file can confirm the authenticity of the signature in a completely autonomous manner.
Why verify a proof?
Independent verification allows confirming:
- That the capsule did exist on our infrastructure
- That the status matches the audit registry
- That the destruction after reading was recorded
- That the document has not been tampered with
Use Cases and Compliance
ITYLOS proofs can be used in several contexts:
- Cryptographic security audit
- Technical investigation and forensics
- Internal compliance (GDPR, ISO)
- Traceability of sensitive operations
Format Open-Source
Compatible with standard libraries:
- libsodium
- TweetNaCl
- PyNaCl
"ed25519_signature": "Lywx..."
}
Frequently Asked Questions
Understanding the technical expertise of digital proofs
Can a proof be verified without using this site?
ITYLOS proofs use a standard Ed25519 signature. They can be verified with any compatible cryptographic library (Python, Go, Node.js), guaranteeing total independence from our platform.
Where are verifications performed?
Can a proof be forged?
Does a proof allow recovering a capsule?
The proof contains only structural metadata and a signed audit log. The client-side encryption architecture guarantees that it can in no way provide access to the original capsule content.