RMOZ / platform
Know the source. Check the record.
Connect certificates to their issuers, approvals and current status. Share the details a verifier needs while keeping private information protected.
Reduce repeated checks without widening exposure
Education providers, professional bodies and enterprise access teams repeat the same evidence checks. Each RMOZ credential defines the exact claim, its intended audience and the minimum information a verifier needs to see.
Establish issuer authority
A signature can show that a key signed a claim; it does not establish that the signer is qualified to make it. An issuer register, approved verification procedures and clear responsibility for incorrect claims are necessary design decisions.
Plan issuance, presentation and revocation
The flow checks source evidence, authorises issuance, lets the holder present the credential and confirms its current status. Expiry, revocation, replacement and issuer-key compromise are handled as part of the design.
Keep personal data proportionate
Evaluate storing sensitive evidence outside any shared ledger, with controlled access and a defined legal basis. Even hashes and status queries can expose information. The desired outcome is a verifiable, limited claim—not a permanent public profile of an individual.
Continue the journey
FAQ
Questions, answered
Is this a national identity or KYC service?
No. RMOZ credentials prove specific claims, such as a qualification or a licence. They work alongside national identity and regulated KYC services rather than replacing them.
Can a credential be corrected?
Yes. Credentials can be revoked or replaced by their issuer, and the full status history is preserved for verifiers.
YOUR NEXT STEP
Build your next step
on trust.
Find the right starting point for your assets, records and business.
Find your use case