What This Platform Does
We help projects prove who they are using Atala PRISM DIDs and Verifiable Credentials (VCs),
and produce on-chain token metadata (CIP-725) that points to those proofs.
End-to-End Flow
- Create DID: Enter company info; we generate a DID Document and an encrypted private key for you to download.
- Save Key: Download and store your one-time key. We never keep your plaintext key.
- KYC & Review: Upload documents; an admin reviews and approves.
- Platform Attestation: On approval, the platform issues a signed VC attesting to your DID.
- Create Credentials: For each asset/project, create a VC signed by your DID.
- 725 Metadata: Generate signed metadata per credential for on-chain use.
What Gets Signed
- DID Document: Self-signed by your DID key (includes your public JWK).
- Platform Attestation: Signed by the platform's verifier key, referencing your DID.
- Credential (VC): Per asset/project, signed by your DID key.
- 725 Metadata: Signed by your DID key; references your DID and optionally the VC URL.
How Others Verify
- Start at the VC: Read the
issuer field (your DID).
- Get DID + Attestations: Use our public DID endpoint.
- Check Signatures: DID Document, VC, platform attestation, and optionally 725 metadata — all verified against public keys.
- Check Status: Call the credential's status URL to confirm active/revoked.
For full API docs, integration guides, and technical details, see the Documentation.