◆ Incident records
Date your damage photos from the roadside, before you send them.
Weeks later the other party’s insurer says the damage predates the collision or was added afterwards. Record the photo set before it reaches an insurer, a garage, or anyone else. It shows those files existed by that date; it cannot show when they were taken or what caused the damage.
The record sits in Base’s public transaction history, so an insurer can check it without going through us and without our permission. It needs the exact image files you kept and the receipt.
What happens if we shut down →A finalized record means we observed a successful Base L2 receipt, not Ethereum settlement. Independent checking needs the retained file, receipt and suitable Base history access. Read the evidence limits.
◦ Use cases
Ways to use a dated file record
Damage file set
Retain original files, device records, and receipts so their submitted digests can be reproduced.
Condition documentation
Use a checkpoint beside—not instead of—location, identity, witness, and custody records.
Reviewer packet
Provide retained source, receipts, processing rules, and surrounding records to an insurer or adviser.
▸ FAQ
Common questions, answered plainly.
Does this prove the damage came from the accident?
No. Causation is not in the file. It can show the images existed by a date, which is what is actually in dispute when an insurer says the photos were produced afterwards.
Can I do it from the roadside?
Yes — hash and submit the photo set from your phone before you send anything to anyone. Keep the originals: a messaging app can change a photo’s bytes. If the bytes change, the fingerprint is expected to differ.
Do you keep my photos?
No. The file body stays on your device. Notarization sends the fingerprint, filename, size and available type. File metadata stays off-chain.
Do I need an account?
No account is needed to check a file or download the independent verifier. Create an account and verify your email to notarize files and manage your records.