Sending code to a client? Keep these three things.

Andrew Cluev — Wed, 07 Oct 2026 08:44:32 +0000

You've finished a job. The client wants the files. Before you hit send, keep a record of exactly what you're delivering.

No fancy system needed. Start with three things.

1. The exact files

Save a separate copy of the version you're sending. Give it a clear name with the project, version, and delivery date.

Don't rely on a folder you'll keep editing tomorrow.

2. The delivery record

Keep the email or message that says what you sent and to whom. If the client confirms receipt or accepts the work, keep that too.

A file called "final-final-actually-final" won't explain the delivery by itself.

3. A timestamp record

You can also register the file's digital fingerprint.

Our project, Ecode, offers free code registration. The source code stays on your device. The service records its fingerprint in a database, adds an RFC 3161 timestamp, and records it on Polygon.

Keep the certificate and verification files with the exact version you registered.

Put them together

Keep the delivered files, delivery messages, and timestamp records in one clearly named folder. Make a separate backup.

A timestamp records existence. The messages explain the delivery. Neither replaces the other.

You can try Ecode here.

How to timestamp your code without sharing the source

Andrew Cluev — Tue, 06 Oct 2026 09:35:00 +0000

When you need to document a particular version of your software, keeping the exact files matters. A timestamp associated with a file's digital fingerprint can add a separate record of when that fingerprint existed.

Here is how this works, and what you should keep.

A fingerprint instead of your source code

A SHA-256 hash is a digital fingerprint calculated from a file's contents. Even a small change will generally produce a different fingerprint.

A timestamp can be associated with that fingerprint without publishing the file itself. Later, you can calculate the fingerprint of your saved file again and compare it with the recorded value.

Preserve the original file. A certificate cannot recover lost source code.

How Ecode uses this approach

Ecode is a free code registration service. Your source code stays on your device, while its SHA-256 fingerprint is registered.

The service combines three records:

Database. A registration entry.
Timestamp. A timestamp using the RFC 3161 standard.
Blockchain. A record on Polygon.

You receive a certificate with verification information.

What to keep with your registration

Keep the exact file you registered, the certificate, and any associated verification files. Back them up separately from your working copy.

If you change the code, register the new version separately. Give each saved version a clear name so you can match it to the correct certificate.

What the record establishes

A timestamp helps document the existence of a particular fingerprint at a particular time. It does not, by itself, identify who wrote the code.

Keep supporting materials such as development history, drafts, contracts, and relevant correspondence.

Try it and share your feedback

You can register a code file with Ecode for free.

We would welcome feedback on the registration process and certificate verification.

Which step needs a clearer explanation?

DEV Community: Andrew Cluev