Trust Registry Query Protocol
Protocolo de Identidade
Comunidade
Detalhes
Licença Spec: open under ToIP IPR framework; multiple independent implementations including archetech/archon-trust-registry
Status de Dev 🔍 Revisão
Detalhe do Status de Dev Public Review 02 of V2.0 (Dec 2025); core specification separated from transport bindings; initial REST/HTTPS binding
Proprietário Trust Over IP Foundation (project of Linux Foundation Decentralized Trust); developed by the Trust Registry Task Force (TRTF) within the Technology Stack Working Group
Órgão de Governança ToIP / LF Decentralized Trust (Trust Registry Task Force, within the Technology Stack Working Group)
País International (Linux Foundation; global membership)
Ano de Início 2021
Stack Specification only; reference implementations expected via OpenAPI 3.0 client/server code generation; HTTPS as initial transport binding; future bindings to DIDComm and TSP under consideration
Financiamento Trust Over IP Foundation member contributions
Última Investigação 1 de jul. de 2026
Protocolo de Identidade Atributos
Origens ToIP TRTF — formed Summer 2021 in response to COVID-era cross-jurisdiction digital health credential verification needs
Banco de Dados N/A — TRQP queries existing trust registry systems-of-record; storage is registry-side concern; bridges adapt diverse backends including X.509 PKI, OpenID Federations, EBSI Trust Chains, TRAIN, and EU Trusted Lists
Linguagem de Consulta TRQP query types (Authorization, Recognition, Description) expressed as OpenAPI-defined REST endpoints over HTTPS; not a general query language but a small fixed set of typed queries
Formatos de Dados Authority statements as semantic triples (authority, entity, assertion); REST/HTTPS binding follows OpenAPI Specification 3.1.0; assertions in three categories (descriptions, authorizations, recognitions)
Suporte Móvel Yes — HTTPS-based; usable from any mobile client capable of HTTPS
Suporte Web Yes — primary transport binding is REST/HTTPS; future bindings to DIDComm and TSP planned
Aplicativos Nativos Implementation-dependent — OpenAPI 3.0 specification enables code generation for clients in any major language; wallet integrations expected for credential verification flows
Termos Open standard, free to implement (under ToIP IPR framework)
Fundos Unknown — ToIP/LF Decentralized Trust member-fee funded; specific TRTF (Trust Registry Task Force) budget not separately published
Baseado Em W3C DIDs (for authority and entity identifiers); OpenAPI Specification 3.1.0 (for REST binding); ABNF for authorization assertion strings
Permissões Read-only protocol — no write permissions defined; create/update/delete reserved for future protocol versions if demand emerges
Autenticação e Identidade Authority and entity in authority statements identified by W3C DIDs (or KERI AIDs / HTTPS URLs); cryptographic verification of authority statements
Modelo de Armazenamento Read-only query protocol — does not specify storage; bridges adapt to existing systems of record (databases, X.509 hierarchies, OpenID Federations, blockchains)
Interoperabilidade Designed for inter-ecosystem authority verification across heterogeneous trust architectures; bridge architecture allows existing infrastructure to be queried via uniform protocol
Portabilidade de Dados Authority statements queryable across registries; recognition queries enable building federated trust graphs across registries; bridges enable cross-system queries
Governança e Tomada de Decisão ToIP TRTF governance — open meetings, consensus-driven, IPR-protected under LF Decentralized Trust; each trust registry's authority statements derive from its governance framework rather than from TRQP itself
Maturidade / Padronização do Protocolo Public Review 02 of V2.0 (Dec 2025); Implementers Draft phase
Padrões de Identidade W3C DIDs; W3C Verifiable Credentials (commonly the credentials whose issuers are verified via TRQP); ToIP Trust Registry data model
Métodos DID Suportados Any (method-agnostic)
Gestão de Chaves Out of scope for TRQP itself — each system of record manages its own keys; TRQP queries verify against the trust root of the relying registry
Tipos de Credenciais N/A — TRQP enables querying who is authorized to issue or verify credentials, but does not itself convey credentials
Método de Verificação Cryptographic verification of authority DID signatures on authority statements
Recursos de Privacidade Read-only by design (no PII required for queries); transport-binding-dependent metadata privacy (HTTPS for initial binding; future DIDComm and TSP bindings would offer enhanced privacy)
Métodos de Autenticação Transport-binding-dependent — HTTPS TLS for initial binding; future DIDComm and TSP bindings would use those protocols' authentication mechanisms
Mecanismo de Revogação Authority-statement revocation handled by underlying systems-of-record — TRQP queries the current state of the registry; registry policies define how revocation is reflected in query responses
Tipos de Agentes Suportados Software agents (issuers, holders, verifiers, relying parties), governing bodies (authorities), and any party making programmatic trust decisions
Tipos de Carteira/Cliente Wallet integrations (verifiable credential wallets querying trust registries to validate issuers); ecosystem-specific clients; library generation via OpenAPI 3.0
Mecanismos de Recuperação Out of scope — recovery is a system-of-record concern at the underlying registry level
Conformidade / Regulamentações EU eIDAS 2.0 (digital wallet verifier authorization); cross-jurisdiction credential verification (mDL, health credentials)
Protocolos de Troca de Credenciais TRQP composes with credential exchange protocols rather than being one — verifiers query TRQP during issuance/verification flows running over DIDComm, OpenID4VC, etc.
Estrutura de Confiança Layer 1 of ToIP four-layer stack — supports any ecosystem governance framework above it; specifically motivated by EU eIDAS 2.0 "verifying the verifier" requirements
Modelo de Custo Free — open standard, royalty-free implementation under ToIP/LF Decentralized Trust IPR
Resistência à Censura Depends on backing trust registry deployment; protocol itself is read-only and does not prescribe registry resilience