DEV Community

GitSerge-crypto
GitSerge-crypto

Posted on

How to Protect Your Freelance Work from Theft for 10 Cents: A Developers Guide

#freelance #web3 #blockchain #copyright

How to Protect Your Freelance Work from Theft for 10 Cents: A Developer's Guide

Every freelancer has been there: you send a client a mockup, a design concept, source code, or a detailed project brief. You get silence or a polite "we went with another candidate." A month later, you spot your work in their finished product — without your permission and without payment.

I'm Sergey, a developer, and I want to share how to solve this problem using cryptography and a technology we originally built for AI agents.

Why Classic Protection Methods No Longer Work

When someone complains about stolen work on freelance forums, the usual advice is:

  1. "Just send images with watermarks" — today, AI tools erase any watermark from an image in 3 seconds.
  2. "Send low-resolution previews" — you can't evaluate UI details from a blurry file, and it looks unprofessional.
  3. "Sign a contract for everything" — for a $50–$100 test assignment or quick concept, nobody is hiring lawyers and spending weeks on paperwork.

So freelancers send their files at their own risk.

The Legal Core: How to Prove Authorship

Under the Berne Convention, copyright exists the moment a work is created. You don't need to register a patent. In any dispute (with a client or a platform's arbitration), you need to prove one fact:

"This specific file, in its exact form, was in my hands on a specific date and time — BEFORE the client received it."

Every digital file has a unique mathematical fingerprint — its SHA-256 hash. Change a single pixel or character, and the hash changes completely.

From an AI Agent Protocol to Freelancer Protection

We originally built the AOTrust protocol for autonomous AI agents. When an AI generates a financial report or source code, the system needs an independent artifact — a PDR (Provenance Data Record) — that proves the fact of creation and carries the agent's signature.

At some point, we realized this same technology perfectly solves the freelancer's problem — and we built shield.aotrust.link.

How It Works (3 Steps):

  1. File Fingerprinting (Zero-Knowledge):
    You drag a file (mockup, code archive, invoice) onto the site.
    Important: the file itself is never uploaded to any server. The service computes the SHA-256 hash directly in your browser using the WebCrypto API. Your commercial work stays on your computer.

  2. PDR Certificate Creation:
    You pay $0.10 USDC on the Base network (Coinbase's L2). The notary server signs your file hash with its Ed25519 cryptographic key and creates a compact 239-byte artifact — a PDR.

Don't want to install MetaMask? There's an alternative: send $0.10 USDC to the service's address from any wallet or exchange (Coinbase, Binance, Bybit) and paste the transaction hash. The service verifies the payment on the Base blockchain and issues the certificate. No browser extensions, no in-browser signatures.

  1. Blockchain Anchoring (NEAR Protocol): The service does not write your file or its hash to the blockchain directly. Instead, all issued PDRs are combined into a Merkle tree, and only its root (the Merkle Root) is periodically anchored to a smart contract on NEAR Mainnet (notary-node.near). This provides a mathematical guarantee: the record history cannot be forged retroactively.

What You Get

You download a 3-page PDF certificate:

  • Page 1: Author name, file name, SHA-256 hash, exact timestamp (UTC), a unique Shield ID (8 characters, e.g. f43e2300), and a QR code linking to verify.aotrust.link/s/f43e2300 for instant verification.
  • Pages 2–3 (Technical): The full Base64 PDR artifact, author signature, public keys of both parties, the notary's identity (notary-node.near), and a Python verification script for independent offline checking.

Offline verification is the guarantee of eternal proof. Even if our service shuts down in 10 years or access to our site is blocked, any independent specialist or lawyer can take this PDF, provide the original file, run the script locally without internet, and mathematically verify that the timestamp and signatures are authentic.

How to Use This in Practice

  1. When sending work to a client: Attach the PDF certificate to your message with the deliverable:

"Sending the finished concept. The file is timestamped via the AOTrust protocol (certificate attached). You can verify authenticity via the QR code or at verify.aotrust.link"

This demonstrates your professional approach and immediately signals to the client that file ownership has been documented.

  1. When a dispute arises: If a client takes the work and refuses to pay, you send the PDF certificate to the platform's support (Upwork, Fiverr) or the client's hosting provider along with a DMCA takedown notice. An independent mathematical proof that the file existed in your hands before the client received it is your strongest argument.

Who's Behind It

The technology is built on the x402 payment protocol — an open internet-native payment standard for AI agents and applications, now developed under the Linux Foundation as of July 2026. This isn't a startup product; it's a vendor-neutral protocol with an open specification. Record anchoring happens on NEAR Protocol — an L1 blockchain with energy-efficient Proof-of-Stake consensus.

Protect your work before you send it. Try it right now at shield.aotrust.link — your first file is protected in 30 seconds. Happy to answer any technical questions about the protocol in the comments.

Top comments (0)