Blockchain Transaction Details¶
Overview¶
Each registered evidence document has an associated blockchain transaction. The portal provides a detailed view of the on-chain record for full transparency and independent auditability.
Transaction Sequence¶
The video below, illustrates the transaction sequence:
1- The LLIMAGER app produces a DMG forensic image of a mac computer.
2- Along with the DMG image and other logs, the LLIMAGER app generates a tamper-evident PDF acquisition log with a QR code
3- The QR code is scanned using the LLIMAGER Companion app.
4- Data is securely sent to the LLSmartVerify Portal
5- The LLSmartVerify Portal anchors the transaction to a Smart Contract on a Layer 2 (L2) blockchain and confirms the registration to the user.
The following information gets anchored to the blockchain, creating an inmutable record for the evidence:
| Field | Description |
|---|---|
| Transaction ID | The unique blockchain transaction hash |
| Evidence Hash | SHA-256 hash of the evidence image |
| Image Timestamp | UTC timestamp captured by LLIMAGER from the device imaged |
| Portal Data Hash | Hash of the portal metadata record |
Verification Logic¶
Anytime a verification is required, the LLSmartVerify Portal omputes an aggregated hash of all fields of the record (called the "portalDataHash") it to the smart contract stored portalDataHash.
If these match → ✅ Verified
If they differ → ❌ Failed (data has been altered)
Independent Verification¶
All transactions can be independently verified using public block explorers
What's On-Chain
The blockchain stores only cryptographic hashes, ensuring that no PII (Personally Identifiable Information), case details, or raw file contents are exposed. Furthermore, the LLSmartVerify Portal utilizes a unique salt to generate the portalDataHash. Deleting this salt effectively renders the blockchain record untraceable to the original portal data, fulfilling "Right to Erasure" requirements through cryptographic partitioning.