Skip to main content

​
The Problem

Organisations produce thousands of critical documents - contracts, regulatory filings, certificates, board resolutions, NDAs, audit reports. These documents define legal obligations, evidence compliance, and establish accountability. The problem is that digital documents are trivially mutable. A file saved to a server can be altered without trace. A signature on a PDF is only as trustworthy as the system that issued and stores it. When a document needs to be verified - by a regulator, a counterparty, or a court - the verification chain inevitably leads back to a system that someone controls, and therefore someone could have manipulated. Traditional document management systems solve version control. They do not solve trust.

​
How ROOTKey Solves It

ROOTKey anchors a cryptographic hash of each document to the Polygon blockchain at the moment it is created, approved, or finalised. The blockchain record is:
  • Permanent - it cannot be deleted or modified by anyone
  • Timestamped - the block timestamp is set by the blockchain, not by your system
  • Independently verifiable - any party with the original document can verify it against the on-chain record without contacting ROOTKey or you
If a document is altered after anchoring - even by a single character - the hash no longer matches the on-chain record. The tampering is detectable by anyone.

​
Architecture

ROOTKey fits alongside your existing DMS - it does not replace it. Your document storage, access controls, and workflows remain unchanged. ROOTKey adds the cryptographic trust layer on top.

​
Implementation

1

Create a vault for document anchoring

Create a vault scoped to the document category - for example, legal contracts or regulatory filings. Configure the protocol based on your auditability requirements.→ Create Vault
2

Anchor a document at creation or approval

When a document reaches a significant lifecycle event (created, approved, signed, finalised), post it to the Files API. ROOTKey computes the hash and anchors it to the blockchain.→ Create File
3

Create a new version on amendment

If the document is legitimately amended, create a new version. The previous version remains intact on-chain - the full amendment history is preserved and verifiable.→ Create File Version
4

Validate on demand

At any point - during an audit, a dispute, or a routine check - validate the document against its on-chain anchor. ROOTKey returns a valid or invalid result, and the validation event itself is anchored.→ Validate File
5

Share verifiable proof

Provide the file ID and vault ID to any counterparty or auditor. They can validate the document independently - either through the ROOTKey API or directly via Polygonscan - without requiring access to your systems.

​
Key API Endpoints

​
Compliance Alignment

Get started - free account

Access sandbox and production environments. Anchor your first document in under 5 minutes.

Speak with our team

We’ll walk through a document integrity architecture tailored to your DMS and compliance requirements.