This reference documents the configuration options for the resolver service. The resolver is responsible for translating decentralized identifiers (DIDs) into their corresponding DID documents.
This section documents the complete configuration provided by Vidos.
The complete JSON Schema for the resolver configuration is available:
For CORS configuration options see the CORS Configuration Reference.
Each DID method can be individually enabled or disabled. Some methods support additional configuration options. For details on all supported methods, see the Supported DID Methods documentation.
object
enabled
: boolean
{ "enabled": true }
did:cheqd
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:dht
methodExample configuration:
object
enabled
: boolean
registry.environment
: string
see ebsi.registry.environmentdid:ebsi
methodebsi.registry.environment
OptionsEnvironment | Description | Use Case | Network URL |
---|---|---|---|
conformance.v5 | Conformance Test Network v5 | Development and conformance testing | https://api-conformance.ebsi.eu |
pilot.v5 | Pilot Network v5 | Pre-production validation | https://api-pilot.ebsi.eu |
Example configuration:
object
enabled
: boolean
{ "enabled": true }
did:ens
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:ethr
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:iden3
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:ion
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:jwk
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:key
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:oyd
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:pkh
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:plc
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:polygon
methodExample configuration:
object
enabled
: boolean
{ "enabled": true }
did:web
methodExample configuration:
string
see contentType Options"application/did+ld+json"
Content-Type
contentType
OptionsContent Type | Description | Usage |
---|---|---|
application/did+ld+json | JSON-LD formatted DID Document | Use when JSON-LD context processing is required |
application/did+json | JSON formatted DID Document | Use when JSON-LD processing is not needed |
Example with application/did+ld+json
:
Example with application/did+json
:
string
see preferredPublicKeyEncoding Options"publicKeyBase58"
preferredPublicKeyEncoding
OptionsEncoding | Description | Format Example | Use Case |
---|---|---|---|
publicKeyBase58 | Base58 encoded public key bytes | "H3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV" | Compact representation, commonly used with Ed25519 keys |
publicKeyJwk | JSON Web Key format | { "kty": "EC", "crv": "P-256", "x": "...", "y": "..." } | Web crypto compatibility, standard JSON structure |
publicKeyHex | Hexadecimal encoded key | "0x123456789abcdef..." | Direct byte representation, easier debugging |
Example with publicKeyBase58
:
Example with publicKeyJwk
:
Example with publicKeyHex
: