Disputes rarely start with a lie. They start with two versions.
Distribution moves fast. Work gets copied at scale, licenses change hands, and files travel over email and chat. When someone disagrees about what was made or agreed, the evidence is scattered across places you don't control.
Which version was agreed?
Terms get revised over email and chat. Months later each side remembers a different draft, and there's no neutral record of the one that counted.
Who had it first?
Showing when a track, video, or document existed usually means pointing to a timestamp that someone else controls and can edit.
Whose records count?
If the only proof sits in one company's database, it is only as trustworthy as that company, and only for as long as it stays in business.
OwnProof writes a fingerprint of the file or contract to a public blockchain. Change one character and the fingerprint no longer matches. Anyone can check.
How the proof works
A file of any size is reduced to a short fingerprint. The fingerprint and a pointer to the full file go on a public ledger, and the file itself is stored permanently.
Your file
Video, audio, or PDF, up to 10 GB.
SHA-256 fingerprint
Always 32 bytes, however large the file. The digest shown is an example.
Arweave
The full file, stored permanently in one upfront payment.
Solana memo
The fingerprint and the Arweave ID, timestamped by the network and impossible to edit afterwards.
Verify any time. Re-hash the file and compare it with the memo. A match confirms the file is unchanged since it was registered.
Cryptographic fingerprint
Change a single bit of the original and the fingerprint changes completely, so tampering can't hide.
Permanent storage
You pay once, up front, and the file is designed to stay available for the long term rather than for a subscription period.
On-chain timestamp
A public, dated record of what was registered, held on a network no single company controls.
A paper trail versus a public record
OwnProof doesn't replace the traditional route. It fills the gap it leaves: fast, dated evidence you can point to at any time.
The usual paper trail
- Formal registration can take weeks or months to process.
- Timestamps live in email and platform accounts that someone else controls.
- Evidence is spread across inboxes, drives, and chat threads.
- Agreed terms are hard to tie back to a specific version of a file.
With OwnProof
- The fingerprint is recorded on Solana within seconds.
- The timestamp is on a public ledger that no single company controls.
- The full file is stored permanently on Arweave.
- Anyone can re-hash the file and compare it with the record.
What this proves. OwnProof shows that a file existed, unchanged, on a particular date, and that it was registered from a particular account. It isn't a copyright registration and it isn't legal advice, so registering with your country's copyright office can still matter. Think of OwnProof as dated evidence that works alongside it.
What the prototype does today
A working path from an uploaded file to a locked, checkable agreement. You don't need to know how Solana or Arweave work to use it.
-
Upload an asset
Add video (up to 10 GB), audio, or a PDF. The file is stored permanently on Arweave. A hash of the file and a memo are anchored on Solana, recording that it existed and when it was uploaded.
-
Draft a contract for that asset
Create an agreement between you and a distributor. The form is organized into sections:
- Streaming and digital distribution royalties
- Sync licensing and other usage royalties
- Ownership and rights granted
AI suggestions are available for some fields to speed up drafting.
-
Get an AI review before you commit
An AI-powered review and risk analysis flags issues in the terms before anything is locked.
-
Lock the terms
The contract's data is hashed and a memo is written to Solana, creating a timestamped record of the terms that can't be quietly altered.
-
The distributor accepts or denies simulated
The distributor's decision is recorded on Solana too. In this prototype the signing step is a mock workflow, not yet a legally binding e-signature.
-
Verify whenever you need to
On an asset's page, Verify re-hashes the file as it exists now and compares it with the hash recorded at registration, so you can confirm nothing has changed since it was locked. Third parties can check a public proof page without logging in.
A dashboard lists all your assets and contracts. Each contract has a details page showing its lifecycle and status, with a direct link back to the asset it covers.
Permanent means permanent. Anything stored on Arweave can't be deleted. That's the point, and it's also why the prototype should only be used with sample files and test terms.
Who it's for
- Musicians and filmmakersIndependent artists who need simple, verifiable licensing and collaboration agreements without a legal department.
- Small labels and studiosTeams managing many assets and contracts who need a stronger audit trail than email and PDFs.
- Their counterpartiesLicensees, collaborators, and distributors who review and agree to terms tied to a specific registered asset.
What's still ahead
- Real co-signingReplacing the simulated accept/deny step with a full counterparty review and signature flow.
- Protecting sensitive termsEncrypting contract content before it goes to permanent storage.
- Finding things fastSearch and filters by status, asset type, date, and counterparty.
- More ways to get startedOptions for people who already have a crypto wallet, and ways to pay without touching crypto.
Try it and tell us what breaks
Upload a sample file, draft a contract, and verify it. You'll sign in with a Google account or a magic link sent to your email.
Please use sample files and test terms only.