JLINC

Protocolo de Identidad

A protocol for sharing data under a signed agreement on the terms of sharing. Its core ideas are Verifiable Contractual Agreements, signed by the DIDs of the parties, and Zero-Knowledge Auditing, in which each party keeps a signed hash of the agreed record so that later use of the data can be audited without exposing the data itself. The protocol is at version 10 and uses a W3C-style DID document for each party, with its own did:jlinc DID method .

Empresa
Enlaces
Visitar Sitio Web Ver esta herramienta en el grafo Sugerir una corrección

Detalles

Licencia Mixed: jlinx is Apache-2.0; jlinc-did-client and jlinc-jwt are MIT; jlinc-node and didserver state no licence; the company's on-prem product is licensed under SSPLv1
Estado de Desarrollo 🧪 Alfa
Detalle del Estado de Desarrollo Alpha (protocol 'Version 10', undated; reference code is small and last updated between 2023 and 2025; no releases listed; the company site describes a commercial product)
Propietario JLINC Inc (copyright line on the company site); the DID method specification is copyrighted to Portable Data Corporation; how the two relate is not stated
Órgano de Gobierno Company-controlled (JLINC; no board or governance body is described beyond officer titles)
País Not stated by the project (the company describes a team based in the Bay Area)
Stack Reference implementations in JavaScript/Node.js (jlinc-node) and Go with PostgreSQL (didserver); Ed25519 keys; EdDSA JWT signatures; JSON Canonicalization (RFC 8785)
Financiamiento Not stated by the project.
Última Investigación 12 nov 2026

Vista de topología

Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.

Vista de topología: JLINCEsta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.JLINCFedID (Base de, Primitiva de identidad para)FedIDVCs (Se compone con)VCsDIDs (Cumple con)DIDsJSON-LD (Cumple con)JSON-LDActivityPub (Inspirado en)ActivityPubdid:web (Inspirado en)did:webKERI (Inspirado en)KERI
  • FedID (Herramienta): Base de, Primitiva de identidad para
  • VCs (Herramienta): Se compone con
  • DIDs (Herramienta): Cumple con
  • JSON-LD (Herramienta): Cumple con
  • ActivityPub (Herramienta): Inspirado en
  • did:web (Herramienta): Inspirado en
  • KERI (Herramienta): Inspirado en

Abrir en el Explorador de grafo

Dominios de Caso de Uso

Identidad y Confianza Comunicación

Capacidades

Divulgación contextual Audiencias basadas en consentimiento

Protocolo de Identidad Atributos

Orígenes A data-sharing agreement protocol. FedID is a separate identity system, a different technology: its own pages describe it as 'FedID from JLINC' and say its DID Document 'is based on the JLINC format for decentralized identifiers', using did:jlinc DIDs
Base de Datos The Go reference DID server (didserver) uses PostgreSQL 9.6 or later; the protocol itself does not require a database
Lenguaje de Consulta N/A: a signed-message protocol; no query language
Formatos de Datos JSON-LD agreement and audit records, EdDSA JWTs (RFC 7519), JSON Canonicalization (RFC 8785); optional compatibility with W3C Verifiable Credentials 2.0
Soporte Móvil Not stated by the project.
Soporte Web Not stated by the project.
Aplicaciones Nativas None stated for the protocol
Términos Mixed code licences (Apache-2.0, MIT, some unstated); the company's on-prem product is licensed under SSPLv1; commercial terms are not published
Fondos Not stated by the project.
Basado En W3C DID Core, JSON-LD 1.1, JWS and JWT (RFC 7515 and 7519), JSON Canonicalization (RFC 8785); the DID method draws on ideas from ActivityPub, did:web and KERI
Permisos Mixed: jlinx Apache-2.0; jlinc-did-client and jlinc-jwt MIT; jlinc-node and didserver state no licence; on-prem product under SSPLv1
Autenticación e Identidad Agreements must be signed with a private key that represents the parties' DIDs; the signing key should be controlled by the end user and may be delegated to an agent; the DID document can list a login service
Modelo de Almacenamiento Each party keeps its own signed agreement record, and a signed hash of it goes to an audit record; audit records can be kept on designated archive servers
Interoperabilidad Medium: W3C DID Core, a W3C-compatible option for verifiable credentials, and integrations the company lists (AuthZEN, LangChain, vCon)
Portabilidad de Datos Not stated by the project.
Gobernanza y Toma de Decisiones Company-controlled; the protocol page lists its authors and no standards process or change-control body is described
Madurez del Protocolo / Estandarización Company specification (protocol Version 10, undated; DID method specification version 2, 10 January 2025); not submitted to a standards body
Estándares de Identidad W3C DID Core; the JLINC DID method specification (did:jlinc, version 2); JSON-LD 1.1; EdDSA JWT; optional W3C Verifiable Credentials Data Model 2.0 compatibility
Estándares de Identidad - Lista
Métodos DID Soportados did:jlinc (syntax did:jlinc:host:id, where the id is derived from a SHA-256 hash of the inception controller's public key and the recovery hash); the protocol's own examples use did:service, which no fetched source defines
Gestión de Claves Ed25519 signing and controller keys; private keys must be held securely and never sent over the network; recovery keys are to be kept offline until needed; key rotation uses the recovery key
Tipos de Credenciales Signed agreements (Verifiable Contractual Agreements) and signed audit records; an optional mapping to W3C Verifiable Credentials
Tipos de Credenciales - Lista
Método de Verificación Signatures on agreements verified against the parties' DID documents; the audit record holds a signed hash of the agreed record rather than a formal zero-knowledge proof
Funciones de Privacidad The DID method recommends a new pair-wise DID per relationship; audit records are designed to hold no sensitive or identifiable data
Métodos de Autenticación DID-based signatures; the DID document can list a login service; the company site cites AuthZEN for fine-grained access control
Mecanismo de Revocación A DID can be deactivated (irreversible) and keys rotated with the recovery key; the protocol itself has no revocation section
Tipos de Agentes Soportados People and services; a key may be owned by an agent when delegated; the company site mentions LangChain and vCon integrations
Tipos de Billetera/Cliente Not stated by the project; client libraries are published for JavaScript (jlinc-did-client, jlinc-jwt, jlinc-zcap, did-web-auth)
Mecanismos de Recuperación A recovery key (held offline) authorizes key rotation; its hash is part of the DID
Cumplimiento / Regulaciones The company claims support for SOX, HIPAA and GAAP and legally admissible compliance records; GDPR is not stated on the pages read
Protocolos de Intercambio de Credenciales The JLINC protocol (signed agreement and audit-record exchange between parties); an optional Verifiable Credentials mapping
Marco de Confianza Trust rests on the parties' signed agreements and the audit trail of hashes; no formal trust framework is stated
Modelo de Costos Not stated by the project; the company offers a commercial on-prem product and hosted services
Resistencia a la Censura Not stated by the project.

Relaciones

Cómo se conecta esta herramienta con otras herramientas y organizaciones, según relaciones revisadas por el responsable de datos de OpenHaven. Describen cómo se conectan los proyectos, no su calidad.

Cumple con
Inspirado en
Se compone con
Base de
Primitiva de identidad para