elaraSign
BUILDContent Provenance Standard
"Transparency is not optional"
âŗ Checking forensic status...đŧī¸ Image Signing
Embeds provenance metadata (EXIF/PNG) + sidecar JSON. Survives basic editing (Paint, rename). Screenshot = re-encode = metadata lost (keep sidecar).
Drop image here
PNG, JPG, WebP, GIF, TIFF âĸ Max 50MB
đŦ Video Signing
Creates sidecar JSON with content hash and metadata. Video file unchanged (sidecar approach for lossless compatibility).
Drop video here
MP4, WebM, MOV âĸ Max 500MB
đĩ Audio Signing
Creates sidecar JSON with content hash and metadata. Audio file unchanged (sidecar approach for format compatibility).
Drop audio here
WAV, MP3, FLAC, OGG âĸ Max 100MB
đ Document Signing
Embeds metadata in PDF properties. Creates sidecar for verification.
Drop PDF here
PDF only âĸ Max 50MB
đ Verify Any File
Check if a file has elaraSign provenance embedded, or validate against a sidecar JSON.
Drop file here
Images, PDFs, Audio, or Video files
đ Optional: Validate Against Sidecar
Drop sidecar JSON here
Validates file against provenance data
âšī¸ About elaraSign
Understanding the content hash system and multi-layer verification.
đ Content Hash System
Every file gets a unique cryptographic fingerprint using SHA-256:
- Content Hash: Full SHA-256 of the raw file bytes (no truncation)
- Metadata Hash: Full SHA-256 of the JSON metadata (no truncation)
- 64-bit Timestamp: Millisecond precision, future-proof until year 292 billion
This ensures tamper-proof provenance - any change to the file breaks the signature.
đ¯ Multi-Location Redundancy (Images)
Images embed signatures in 5 locations for maximum crop resistance:
Even aggressive cropping leaves at least one signature intact!
đ Sidecar Validation
Upload a sidecar JSON file to verify any image matches its provenance:
- Checks content hash against the file
- Validates metadata integrity
- Confirms generation method and timestamp
Perfect for verifying downloaded content or shared files.
đ PDF Digital Signatures
PDFs get industry-standard PKCS#7 signatures that Adobe recognizes:
- Visible signatures in Adobe Reader
- Green checkmarks from online validators
- Legal validity for documents
Combines elaraSign metadata with standard digital certificates.
đ Verification Layers
Files are checked through multiple verification layers:
- Billboard: Human-readable metadata (EXIF/PNG chunks)
- DNA: Hidden steganographic signatures (LSB pixels)
- The Spread: DCT watermark (survives JPEG compression)
Each layer provides different resilience to processing and editing.
⥠Admin Panel
Forensic decryption for legal accountability. Master key required.
đ Forensic Decryption
Upload a signed image to decrypt embedded accountability data:
Drop signed image here
PNG, JPG, WebP, GIF, TIFF âĸ Max 50MB
đ What Gets Decrypted
- Timestamp: Exact signing time (millisecond precision)
- User Fingerprint: SHA-256 hash prefix for user lookup
- IP Address: IPv4 address of the signer
- Platform: Which service generated the signature
This data is encrypted with the master key and embedded in pixel data. Only the key holder can decrypt it.
â ī¸ Legal Use Only
Forensic decryption should only be used in response to valid legal requests from authorities. Misuse violates user privacy.