Media Registry

Documentation

Learn how to use OCME Registry for content creation and verification

Reference

Content Verification

Verify the authenticity of OCME content and creator identities.

Verify Content

Content Verification Guide

Learn how to verify the authenticity of OCME content and creator identities using our comprehensive verification system. Protect yourself from fraud and confirm genuine creators.

Verification Tools

Creator Verification

Verify creator identities and profiles

Content Verification

Verify content metadata and ownership

Media Verification

Verify file integrity and technical data

Split Sheet Verification

Verify collaborator credits and revenue sharing

How OCME Verification Works

Cryptographic Proof System

OCME uses advanced cryptographic signatures to create tamper-proof records. Every piece of content and creator identity is signed with RSA-2048 keys and verified using industry-standard algorithms.

Digital Signatures

RSA-2048 cryptographic signatures ensure authenticity

Instant Verification

Real-time cryptographic verification in seconds

Tamper-Proof

Impossible to forge or modify without detection

Understanding DID Types

Creator DIDs

Creator DIDs establish permanent, verifiable identities for content creators. They contain profile information, social media links, and cryptographic proof of identity.

What's Included

  • • Creator name and bio
  • • Social media profiles (X, YouTube, Spotify, Instagram)
  • • Website and contact information
  • • Creation timestamp and verification method

Example DID Format

did:webvh:prod.ocmeregistry.com:creator:john-doe-music

This DID format ensures global uniqueness and enables decentralized verification.

Try Creator Verification

How to Verify Content

1

Get the DID

Obtain the DID from the creator, content platform, or any source claiming authenticity. DIDs look like: did:webvh:prod.ocmeregistry.com:creator:example

2

Choose Verification Tool

Select the appropriate verification tool based on the DID type (creator, content, media, or splitsheet). Each tool is optimized for specific verification needs.

3

Paste and Verify

Paste the DID into the verification form and click verify. The registry resolves the document, verifies its cryptographic signature internally, and displays detailed results within seconds. Note that public (unauthenticated) responses serve a privacy-redacted view of documents that carry payment or legal-identity material — see "Public Resolution and Redaction" below.

4

Review Results

Check the verification status, review the authenticated information, and look for the green "Verified Successfully" indicator to confirm authenticity.

Public Resolution and Redaction

All unauthenticated DID routes — the public did.json endpoints and POST /api/verify/did — apply a privacy redaction boundary before responding:

  • • What is stripped: payment and legal-identity material — creatorData.paymentInfo (USDC wallet address, full legal name, country of residence), #payment and #compliance service blocks, and staff email addresses in the admin audit trail.
  • • Proof removal: when anything was redacted, the document's cryptographic proof is removed too — it covers the pre-redaction payload and could never verify against the redacted view. The response discloses the redaction in a publicRedaction block listing every removed field.
  • • What this means for verification: signature verification always runs internally against the full document before redaction, so the verified result you receive is trustworthy. But a third party re-verifying the redacted public document on its own cannot reproduce the signature check — the absence of a proof on a public document is expected behavior, not a failure.
  • • Unredacted documents: when a document carries no sensitive material it is served untouched, proof included, and standard W3C verification succeeds on the public view. Authenticated/admin resolution paths always receive the full document.

This boundary is a PII-minimization measure: payment and legal-identity fields are not public. Selective-disclosure proofs are planned to replace whole-field redaction in a future phase.

Common Verification Scenarios

🎵 Music Industry

  • • Verify artist authenticity before collaborations
  • • Confirm original song ownership for licensing
  • • Check collaborator credits and revenue splits
  • • Prevent unauthorized music distribution

🎬 Video Content

  • • Verify video creator identity and authenticity
  • • Confirm original content for platform uploads
  • • Check file integrity and prevent tampering
  • • Validate technical metadata and specifications

Start Verifying Content Today

Protect yourself from fraud and confirm authentic creators with our verification tools

Start Verification Creator Guide
Previous: Creator Journey Next: Security Overview