JLINC

Protocolo de Identidade

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
Links
Visitar Website Ver esta ferramenta no grafo Sugerir uma correção

Detalhes

Licença 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
Status de Dev 🧪 Alpha
Detalhe do Status de Dev 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)
Proprietário 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
Órgão de Governança 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)
Financiamento Not stated by the project.
Última Investigação 12 de nov. de 2026

Visão de topologia

Esta ferramenta no centro e o que se relaciona diretamente com ela. Cada linha nomeia o tipo de relação.

Visão de topologia: JLINCEsta ferramenta no centro e o que se relaciona diretamente com ela. Cada linha nomeia o tipo de relação.JLINCFedID (Base de, Primitiva de identidade para)FedIDVCs (Compõe-se com)VCsDIDs (Está em conformidade com)DIDsJSON-LD (Está em conformidade com)JSON-LDActivityPub (Inspirado em)ActivityPubdid:web (Inspirado em)did:webKERI (Inspirado em)KERI
  • FedID (Ferramenta): Base de, Primitiva de identidade para
  • VCs (Ferramenta): Compõe-se com
  • DIDs (Ferramenta): Está em conformidade com
  • JSON-LD (Ferramenta): Está em conformidade com
  • ActivityPub (Ferramenta): Inspirado em
  • did:web (Ferramenta): Inspirado em
  • KERI (Ferramenta): Inspirado em

Abrir no Explorador de grafo

Domínios de Caso de Uso

Identidade e Confiança Comunicação

Capacidades

Divulgação contextual Audiências baseadas em consentimento

Protocolo de Identidade Atributos

Origens 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
Banco de Dados The Go reference DID server (didserver) uses PostgreSQL 9.6 or later; the protocol itself does not require a database
Linguagem de Consulta N/A: a signed-message protocol; no query language
Formatos de Dados JSON-LD agreement and audit records, EdDSA JWTs (RFC 7519), JSON Canonicalization (RFC 8785); optional compatibility with W3C Verifiable Credentials 2.0
Suporte Móvel Not stated by the project.
Suporte Web Not stated by the project.
Aplicativos Nativos None stated for the protocol
Termos Mixed code licences (Apache-2.0, MIT, some unstated); the company's on-prem product is licensed under SSPLv1; commercial terms are not published
Fundos Not stated by the project.
Baseado Em 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
Permissões Mixed: jlinx Apache-2.0; jlinc-did-client and jlinc-jwt MIT; jlinc-node and didserver state no licence; on-prem product under SSPLv1
Autenticação e Identidade 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 Armazenamento 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
Interoperabilidade Medium: W3C DID Core, a W3C-compatible option for verifiable credentials, and integrations the company lists (AuthZEN, LangChain, vCon)
Portabilidade de Dados Not stated by the project.
Governança e Tomada de Decisão Company-controlled; the protocol page lists its authors and no standards process or change-control body is described
Maturidade / Padronização do Protocolo Company specification (protocol Version 10, undated; DID method specification version 2, 10 January 2025); not submitted to a standards body
Padrões de Identidade 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
Padrões de Identidade - Lista
Métodos DID Suportados 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
Gestão de Chaves 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 Credenciais Signed agreements (Verifiable Contractual Agreements) and signed audit records; an optional mapping to W3C Verifiable Credentials
Tipos de Credenciais - Lista
Método de Verificação 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
Recursos de Privacidade 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 Autenticação DID-based signatures; the DID document can list a login service; the company site cites AuthZEN for fine-grained access control
Mecanismo de Revogação A DID can be deactivated (irreversible) and keys rotated with the recovery key; the protocol itself has no revocation section
Tipos de Agentes Suportados People and services; a key may be owned by an agent when delegated; the company site mentions LangChain and vCon integrations
Tipos de Carteira/Cliente Not stated by the project; client libraries are published for JavaScript (jlinc-did-client, jlinc-jwt, jlinc-zcap, did-web-auth)
Mecanismos de Recuperação A recovery key (held offline) authorizes key rotation; its hash is part of the DID
Conformidade / Regulamentações The company claims support for SOX, HIPAA and GAAP and legally admissible compliance records; GDPR is not stated on the pages read
Protocolos de Troca de Credenciais The JLINC protocol (signed agreement and audit-record exchange between parties); an optional Verifiable Credentials mapping
Estrutura de Confiança Trust rests on the parties' signed agreements and the audit trail of hashes; no formal trust framework is stated
Modelo de Custo Not stated by the project; the company offers a commercial on-prem product and hosted services
Resistência à Censura Not stated by the project.

Relacionamentos

Como esta ferramenta se conecta a outras ferramentas e organizações, a partir de relacionamentos revisados pelo responsável pelos dados do OpenHaven. Descrevem como os projetos se conectam, não a qualidade deles.

Está em conformidade com
Inspirado em
Compõe-se com
Base de
Primitiva de identidade para