How SecureAuthor works

SecureAuthor calculates the SHA-256 hash of your file, records it with a UTC timestamp and gives you a PDF certificate in seconds. Twice a day, at 00:00 and 12:00 UTC, all new hashes are combined into one summary hash and written to the Polygon blockchain. To verify, you upload the file and the certificate; matching hashes prove the file is unchanged since that moment.

Step 1. You upload a file

Use whichever channel is convenient — they all create the same kind of certificate:

Any file type works: images, PDF, Word documents, audio, video, source code, archives.

Step 2. SHA-256 fingerprint

SecureAuthor calculates the file's SHA-256 hash — a cryptographic fingerprint such as 26be856c7aa5748040bcf998b18d3081cacb2ab1e4e3b34aece9e86152f083aa.

Three properties make it useful as proof:

  • Unique: two different files practically never produce the same hash.
  • Sensitive: change one pixel, one comma or one byte and the hash is completely different.
  • One-way: the hash cannot be turned back into the file, so it reveals nothing about your content.

The file is used only to calculate the hash and is not stored. What is a file hash? →

Step 3. Your certificate

You immediately get a receipt and a PDF certificate containing:

  • certificate (receipt) ID;
  • file name and size in bytes;
  • date and time in UTC, in ISO 8601 and as a Unix timestamp;
  • the SHA-256 hash;
  • the blockchain network (Polygon Mainnet) and the record status;
  • the expected time of the blockchain record;
  • your user ID, if you are signed in.

Step 4. Anchoring on the Polygon blockchain

Receipts created since the previous record are combined into one period hash (shown as "Summary hash" on the certificate). A short JSON record with the period start and end, the period hash and a link to the list of receipts in the batch is written to Polygon in a single transaction. Anchoring runs twice a day, at 00:00 and 12:00 UTC. All records are sent from one public address, 0xa3bb4f9ef78b51b9b9b75757f10db03705b2aabb, so anyone can list them on Polygonscan.

After the run, the receipt status changes to Recording completed and you can download an updated certificate with:

  • a link to the transaction on Polygonscan;
  • the summary hash (period hash) written on-chain.

From then on the record is public and permanent. Nobody — including SecureAuthor — can change it or backdate it. Example transaction

Step 5. Verification

To prove authorship, upload two things on the verification page:

  1. the original file, and
  2. the certificate PDF or just the receipt ID.

SecureAuthor recalculates the hash and shows Files are equal or Files are different, with both hashes side by side. You can download the result as a PDF.

You can also check the whole chain yourself — file hash, Polygon transaction, period hash and batch list — with standard tools. Step-by-step independent check →

One file, one registration

If a file has already been registered, SecureAuthor does not create a new certificate — it returns the original one. This means the earliest registration of a file always wins, and a copy registered later by someone else cannot replace yours.

What SecureAuthor does not do

  • It does not judge originality or check whether the work is yours — it records that you had this file at this time.
  • It is not a government registry and does not give legal advice.
  • It does not monitor the internet for copies of your work.

Frequently asked questions

Why is the blockchain record not instant?

Writing every hash separately would be slow and wasteful. SecureAuthor collects new receipts and anchors them together twice a day, at 00:00 and 12:00 UTC. Your timestamp is fixed the moment you upload; anchoring only makes it publicly provable. The certificate shows the expected recording time.

Which timestamp counts — the upload or the blockchain record?

The certificate shows the exact UTC time of upload. The blockchain transaction, created at the next anchoring run, independently proves that the hash existed no later than the time of that block.

What happens if I upload the same file twice?

You get the receipt of the first registration. A file can be registered only once, so the earliest timestamp always wins and cannot be replaced by a later one.

What if I edit the file?

Any change, even one byte, gives a different hash, so the edited file needs its own certificate. Keep the exact original you registered — without it, verification is impossible.

Why Polygon?

Polygon is a public, widely used blockchain with low fees and a public explorer (Polygonscan), so anyone can check the record without trusting SecureAuthor.

Can someone recreate my file from the hash?

No. SHA-256 is one-way: the hash cannot be reversed into the file.

Do I need a crypto wallet?

No. SecureAuthor sends the transactions and pays the fees.

What exactly is written on the blockchain?

A small JSON record: period start and end, the period hash of the batch and a link to the batch list. No files and no file contents.

Updated:

Protect your next file in seconds

Free proof of authorship: SHA-256 hash, UTC timestamp and a Polygon blockchain record. Your file is not stored.

Add to ChromeProtect a file