Reusable Identity Layer - Verifiable Credentials

Overview

The Reusable Identity Layer allows institutions and individuals to carry verified credentials across the JIL Sovereign network without repeating KYC processes. Once a credential is issued by a trusted authority, it can be presented and verified by any counterparty on the network - reducing onboarding friction from days to seconds.

Credentials follow the W3C Verifiable Credentials Data Model and are anchored to decentralized identifiers (DIDs) on the JIL L1. Users control which fields are shared via selective disclosure, ensuring privacy while meeting compliance requirements.

DID Format

JIL Decentralized Identifier did:jil:{wallet_id}

Every JIL wallet automatically receives a DID upon creation. The DID is anchored to the JIL L1 and serves as the subject identifier for all verifiable credentials issued to that wallet.

Credential Types

kyc_verified Identity verification completed - name, jurisdiction, and document type confirmed

accredited_investor Accredited investor status verified per SEC Rule 501 or equivalent jurisdiction rules

institutional Entity verified as a registered institutional participant - fund, family office, or corporate treasury

aml_cleared AML/CFT screening completed with no adverse findings within the credential validity window

jurisdiction_approved Approved for transactions within specific jurisdictions based on regulatory requirements

Selective Disclosure

Selective disclosure allows credential holders to share only the specific fields a verifier needs. For example, a counterparty might only need to confirm that you are KYC-verified in the US without seeing your name or document number.

{
  "presentation": {
    "holder": "did:jil:0x7Bcff27...aBa2",
    "credentials": [
      {
        "type": "kyc_verified",
        "disclosed_fields": ["jurisdiction", "verification_level"],
        "withheld_fields": ["full_name", "document_number", "date_of_birth"]
      }
    ],
    "recipient": "did:jil:0x84fF59...504F",
    "purpose": "counterparty_verification",
    "expires_at": "2026-03-28T14:30:00Z"
  }
}

Verification Levels

Basic Single credential verified. Sufficient for low-value transactions. 1 credential

Enhanced Multiple credentials verified. Required for mid-value cross-border flows. 2+ credentials

Institutional Full credential stack including accredited_investor. Required for high-value operations. 3+ with accredited_investor

API Endpoints

Method	Endpoint	Description
`POST`	`/v1/identity/credential/issue`	Issue a new verifiable credential to a DID
`GET`	`/v1/identity/verify`	Verify a presented credential or presentation
`POST`	`/v1/identity/presentation/create`	Create a selective disclosure presentation
`GET`	`/v1/identity/credentials/:did`	List all credentials for a DID

Issue Credential Request

POST /v1/identity/credential/issue

{
  "subject": "did:jil:0x7Bcff27...aBa2",
  "type": "kyc_verified",
  "claims": {
    "jurisdiction": "US",
    "verification_level": "enhanced",
    "verified_at": "2026-03-27T10:00:00Z"
  },
  "expires_at": "2027-03-27T10:00:00Z"
}

Verify Credential Response

GET /v1/identity/verify?credential_id=cred_a1b2c3d4

{
  "valid": true,
  "credential_id": "cred_a1b2c3d4",
  "type": "kyc_verified",
  "subject": "did:jil:0x7Bcff27...aBa2",
  "issuer": "did:jil:issuer_jil_sovereign",
  "issued_at": "2026-03-27T10:00:00Z",
  "expires_at": "2027-03-27T10:00:00Z",
  "revoked": false
}

Presentations

Presentations combine one or more credentials with selective disclosure for a specific recipient. Each presentation is time-limited and purpose-bound, ensuring credentials are not reusable outside their intended context. The recipient verifies the presentation cryptographically without needing to contact the original issuer.