Dimension scores are derived from public data and fields; weighted into the composite. Reference only.
Quidnug is a P2P protocol and Go reference node focused on “relational trust.” Rather than trying to assign global reputation scores to objects, it answers the question: “From a given observer’s perspective, within a given domain scope, who should be trusted, and how much?” Each trust edge is signed by the subject, state changes are protected against replay, and records can be anchored into blocks. The official team also operates a public network and offers domain verification as a service on top of the protocol.
Functionally, Quidnug covers typed trust graphs, ECDSA P-256 identities, per-signer monotonic nonces, event streams, titles, M-of-N guardian key recovery, time-locks and veto windows, as well as Proof-of-Trust consensus. Its consensus is neither BFT nor Nakamoto-style; instead, each node decides which blocks to accept based on its own trust graph. This makes it better suited to consortiums, cross-organization verification, and context-specific trust scenarios. Domains use DNS-like dot notation, with configurable parent-child inheritance to prevent trust from leaking across domains.
It is fairly open: the protocol, node, SDKs, and documentation are all Apache 2.0 licensed and can be self-hosted. The node provides REST APIs, including /api/v1 and /api/v2, together with OpenAPI 3.0 specs, Postman collections, and canonical bytes specifications. Full SDKs cover Python, Go, JavaScript/TypeScript, and Rust; Java/Kotlin, C#/.NET, Swift, Android, React, and browser extensions are available as scaffolds. On the deployment side, it provides Helm, Docker Compose, Grafana, and Prometheus support. DNS verification integrates with Cloudflare, Route 53, and GCP DNS.
The commercial layer is priced by verified domain and verification depth, rather than by seat. Free supports 1 email-verified domain, daily rechecks, and GitHub community support. Pro adds DNS challenges, hourly rechecks, a 99.9% SLA, email support, and a read-only API. Business adds KYB, 15-minute rechecks, read/write APIs, compliance exports, and 4-hour priority support. Enterprise is aimed at shared governance, jointly operated seed nodes, cross-signing, and reserved domain trees. Exact pricing is not public, and some tiers require joining a waitlist or contacting sales.
Its strengths are a clear protocol model, open-source self-hosting, key recovery without centralized escrow, and fairly complete documentation. It is well suited to high-trust scenarios such as finance, AI provenance, developer artifact signing, credential verification, medical consent, and fraud consortiums. The downsides are its high conceptual barrier, making it unsuitable for ordinary login authentication or high-TPS payment chains; its commercial maturity, pricing, and regional service availability are also not very transparent.
The collected text does not state network connectivity from mainland China, payment methods, or local support, so China access is rated as unknown. For domestic deployment, it is advisable to first evaluate self-hosted nodes, DNS service compatibility, compliance requirements, and compare it with DID/VC, Sigstore, PGP web-of-trust, or traditional CA/notary-style verification approaches.
⚠ This review is compiled from public sources and does not constitute a purchase recommendation. Verify all facts on the vendor's official site. Verify on quidnug.com official site.
quidnug.com is an Unknown Dev Tools provider. TG4G tracks its product information, an overall rating of 6.0/10, and a China-accessibility score of Workable. Click "Visit Official Site" to reach quidnug.com directly.