Skip to main content

Can I register my document twice?

Coral avatar
Written by Coral
Updated over 6 months ago

No. EMOZ allows only one registration per document (i.e. unique fingerprint) per blockchain network.

If you see the message: “This file has already been registered with EMOZ”, it means the exact file has already been certified on the same blockchain network, and cannot be registered again, even by the same user or someone on the same team.

This applies to both real certificates (e.g. on Polygon Mainnet) and test certificates (e.g. on Polygon Amoy, our testnet). Test networks are still blockchain environments and are treated as valid for registration checks.

Why only one registration per network?

This rule is in place to:

  • Prevent duplicates and accidental re-registrations

  • Avoid confusion about which certificate is valid

  • Ensure that each network holds a single, authoritative proof of ownership per file

Once a file is registered on a network, it becomes the only valid entry for that fingerprint on that chain.

What is allowed

You can still register the same file on a different blockchain network, as long as it hasn’t already been registered there.

For example, if a file has been certified on Polygon Amoy (as a test certificate), you can still certify it once on Polygon Mainnet (as a real certificate)

The rule is: one file = one registration per network

What happens if someone else registers my file first?

In the extremely rare case that another user registers the same file before you (on any network):

  • EMOZ will block any attempt to re-register the same fingerprint on that network

  • The first registration always takes precedence, based on the blockchain timestamp

Why this is rarely a problem:

  • Fingerprints are based on the exact file content, so duplication is almost impossible unless someone else had your file. This could only happen if you shared it and they registered it before you

  • The odds that two users register the same fingerprint at the same second on different networks is close to zero

  • Every registration is timestamped on-chain, so any conflict can be resolved with verifiable data

Summary

  • You cannot register the same file twice on the same network

  • You can register the same file on a different network, if it hasn’t been registered there before

  • Blockchain timestamps ensure verifiable proof of precedence

Did this answer your question?