◆ Software releases

Keep a dated reference for the build you deliver.

A client, an escrow agent, or an auditor asks which build you handed over. Record the exact release artifact so a later copy can be compared with its fingerprint. Keep delivery messages and recipient acknowledgements separately: the fingerprint does not prove who received the build or when. This is not escrow; nobody holds your source in trust or releases it on a trigger.

The record is a Base transaction we cannot alter, so an auditor can verify a build years after the contract ended and after we have stopped answering email. Keep the release artifact and the receipt together.

What happens if we shut down →
Public fingerprint
32 bytes recorded on Base
Exact file
Compare every character of the SHA-256 digest
Keep both
Retain the original file and receipt for later checks
Free check
Checking a file needs no account or credit

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

Br

Release artifact

Record the exact built artifact at the moment you tag it, and keep that file. A later rebuild that differs in a single byte is a different file.

Fl

Handover to a client

Give the client the artifact and the receipt together. They can check the copy they hold without an account and without going through you.

Sh

A question months later

An auditor holding a binary can compare it with the recorded digest and read the referenced transaction from Base through any explorer.

▸ FAQ

Common questions, answered plainly.

Is this software escrow?

No. We do not hold source code in trust or release it on a trigger. The record supplies a dated fingerprint of the artifact you retain. Keep delivery evidence separately.

Our build is not reproducible. Does that matter?

Not for this. The record is of the artifact you actually shipped, not of a build anyone can recreate. Keep that exact file: a rebuild with a different timestamp inside it is a different file and will not match.

When should I record it?

At the moment you hand it over, before anyone else has a copy. Recording a build once the argument has started shows only that the file existed once the argument 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.

Need a dated record of this file?

Keep the source data and receipt. A matching digest supports a limited comparison; it does not establish truth, identity, authorship, ownership, custody, or a legal outcome.

Record this file →