Prove any record is genuine, forever.
Rox Register seals a cryptographic fingerprint of your documents on RoxChain. The documents never leave your systems, the sealed record can never be rewritten, and anyone can verify it is genuine, without trusting Rox.
Seal. Anchor. Verify.
Three steps stand between a document and a permanent, independently checkable proof of its integrity. The last step is the point: verification requires no trust in Rox.
Seal
Your systems compute a salted SHA-256 fingerprint of the record and send only that digest to the Rox Register API. The document itself never leaves your infrastructure, and the unique salt means the fingerprint reveals nothing about the content.
Anchor
Digests are combined into RFC 6962 Merkle trees, and each anchor is signed by a fleet of 3-of-5 MPC nodes, so no single machine ever holds the signing key. The signed anchor is recorded on RoxChain, a chain with independent validators.
Verify
Anyone re-hashes the document and checks it against the on-chain record. A genuine document verifies, a document changed by a single byte does not. Verification is public and requires no Rox account, and no trust in Rox.
Wherever a record must stay true.
Any organization that issues, holds or relies on documents has the same quiet problem: proving, later, that a record is exactly what it was. Every sector below has its own dedicated page.
Built so you do not have to trust us.
The architecture removes Rox from the trust equation on purpose. Your content stays with you, the signing key is never whole anywhere, and the chain of record is run by validators Rox does not control.
One service, three surfaces.
Your operations team, your engineers, and the people you hand records to each get a surface built for them.
Corporate Platform
Where your team runs the operation: vaults and signing keys, sealed records, team roles and approvals, audit trail, and the gas station that fuels anchoring with Rox coin (ROX).
platform.roxregister.comDeveloper portal
Public documentation for the machine API: quickstarts, guides, signed-request reference, webhook catalogue and official SDKs for Node.js and Python.
developers.roxregister.comPublic verification
The other half of the promise: anyone you hand a record to can check it is genuine against the chain, with no account and no relationship with Rox at all.
open to everyoneIntegrate in an afternoon.
Official SDKs for Node.js and Python handle request signing, local hashing, selective disclosure and webhook verification, so sealing a record is a few lines of code. Everything is documented publicly, no signup needed to read.
Developer overview →# seal a record in three lines import { RoxRegister } from "@rox-register/sdk"; const rox = new RoxRegister({ apiKey }); const seal = await rox.seal("./contract.pdf");
Bring provable records to your organization.
Commercially simple: a fiat subscription for the Platform, with anchoring usage settled in Rox coin (ROX) through the built-in gas station. Tell us about your records and volumes and we will set you up with the right plan.