◆ Freelancer records
Prove the work existed before the deadline.
The invoice is sixty days late and the client now says the deliverable was late, incomplete, or not what the scope said. Record the deliverable and the agreed scope the moment you send them. It shows the file existed in this form by that date; that they received it comes from your mail records.
The record is in Base’s public transaction history, where we cannot edit it, delete it, or take it back if you close your account. Keep the delivered file and the receipt, and the date stops depending on your word.
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
Deliverable version
Keep the exact work product and receipt beside the delivery message and recipient records.
Scope version
Checkpoint selected SOW or change-order versions while preserving signatures and communications separately.
Approval packet
Combine retained files and receipts with the identities, messages, and approvals needed to evaluate a dispute.
▸ FAQ
Common questions, answered plainly.
Does this prove I delivered on time?
It shows the deliverable existed in this exact form by this date. That they received it comes from your sending records — the two together are the argument.
The client says the brief said something else.
Record the scope document as well as the deliverable, at the moment you send them. Later, the file each side is holding either reproduces its recorded fingerprint or it does not.
When should I record?
Before you send, every time. Doing it once the dispute has started records only that the file existed once the dispute had started.
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.