Before you send your code to a client, keep a dated record of the file you are delivering.

Ecode is a free service for creating timestamped evidence that can support a code authorship claim. It records your file s SHA-256 fingerprint and provides a certificate with a trusted timestamp. Your source code stays on your device.

Try it with a small code file you wrote. Register the file, download the certificate, and keep both together. You can then repeat the process for an important delivery.

I work on marketing for Ecode. I d like to hear from freelance developers and small teams: what do you currently keep as evidence when you hand over your work?

Keep the file you registered.

Ecode doesn't store a backup of your code. Save the original file, your certificate, the timestamp file and the Polygon transaction link together.

We launched Ecode today. It s free and helps developers gather evidence if someone disputes who wrote their code. The source code stays on your device.

I handle marketing for Ecode. I'd like to make our explanation clearer.

What would you want to check first: how your code stays private, or what the certificate actually shows?

Here's our launch page: