every DID method, measured
← Resolver Directory Providers Analytics API docs
did:kscirc
Upstream routedDocker

KSChain DIDs by K4-Security Co., Ltd (Seoul).

Live scores

Popularity 20
Availability 100%
ThisDID canary 24hno data
resolutions: 24h 0 · 7d 1 · 30d 7 · from /analytics

Routing

DIF Universal Resolver docker driver

did:kscirc has an approved and merged resolver docker container in the DIF Universal Resolver repository.

Docker image
k4security/kschain-resolver:v1.0.1
Driver source
https://github.com/siera5466/uni-resolver-driver-did-kscirc/tree/main

Facts

JSON API
/directory/api/methods/kscirc
Last reviewed
2026-08-28

Research

Operated by K4-Security Co., Ltd, a Seoul security vendor (DIF Korea SIG member, Danube Tech partner) — not, as sometimes assumed, a Korean financial-sector institute. The spec is a Notion page (v1.0.0, 2022, draft) whose entire Read section is one sentence: no resolution API, RPC, or endpoint is documented anywhere, the Universal Resolver driver wraps a closed-source binary, and the service domain inside the method's own DID documents (did.k4-security.com) no longer resolves in DNS. Exactly three canned demo DIDs resolve via the DIF dev instance. With no public read API there is nothing a verifying edge driver could verify — the method stays upstream-routed.

Links

Curated method research + live measured scores · A DIF Identifiers & Discovery Working Group project advancing the Universal Resolver and interoperable DID methods · Resolver · Analytics · Status · JSON API · API docs · Source